[GH-ISSUE #60] [96455ca] Audio capture is broken #55

Closed
opened 2026-05-05 15:04:34 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @LordHDL on GitHub (Feb 15, 2015).
Original GitHub issue: https://github.com/zakk4223/CocoaSplit/issues/60

Test recording: https://www.dropbox.com/s/s5mw3m0dpc6n78y/No%20Audio.mp4?dl=0

Originally created by @LordHDL on GitHub (Feb 15, 2015). Original GitHub issue: https://github.com/zakk4223/CocoaSplit/issues/60 Test recording: https://www.dropbox.com/s/s5mw3m0dpc6n78y/No%20Audio.mp4?dl=0
Author
Owner

@zakk4223 commented on GitHub (Feb 17, 2015):

None of the audio inputs are active there. Click the 'on' button below them to make them active.

That said, I'm open to suggestions on how to better setup that UI; it's pretty barebones and not at all good right now.

<!-- gh-comment-id:74618377 --> @zakk4223 commented on GitHub (Feb 17, 2015): None of the audio inputs are active there. Click the 'on' button below them to make them active. That said, I'm open to suggestions on how to better setup that UI; it's pretty barebones and not at all good right now.
Author
Owner

@LordHDL commented on GitHub (Feb 17, 2015):

Hmm, could've sworn I had tried that.

I do have a suggestion. Currently it looks a bit ambiguous in that you can't tell if it's on or not (until you've learned it, at least). The button "On" made me think it was active, when it apparently means it'll turn on once you click it (and it says "Off").

If you look in Xcode in the Capabilities tab, you'll see sliders on the right where the word Off is against a gray background. If you slide it you'll see the word On against a bright blue.

Anyway my point is not that you should copy that necessarily, but rather it's a good example of less ambiguity; mistaking Off for On or vice versa is unlikely.

Another approach would be if you reverse the button so it says Off when off against a dark gray background, while On would be against a green one to indicate it's active.

<!-- gh-comment-id:74624580 --> @LordHDL commented on GitHub (Feb 17, 2015): Hmm, could've sworn I had tried that. I do have a suggestion. Currently it looks a bit ambiguous in that you can't tell if it's on or not (until you've learned it, at least). The button "On" made me think it was active, when it apparently means it'll turn on once you click it (and it says "Off"). If you look in Xcode in the Capabilities tab, you'll see sliders on the right where the word Off is against a gray background. If you slide it you'll see the word On against a bright blue. Anyway my point is not that you should copy that necessarily, but rather it's a good example of less ambiguity; mistaking Off for On or vice versa is unlikely. Another approach would be if you reverse the button so it says Off when off against a dark gray background, while On would be against a green one to indicate it's active.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/CocoaSplit#55
No description provided.