Reinitializing audio and midi -- Nobel-prize discovery made.
Reading the 200th post about "I plugged in my midi keyboard and nothing happened", and expecting an answer of "well, you should have plugged it in BEFORE you started. Quit and reeenter." So I was about to post, "Why can't we have a 'reinitialize audio and midi button somewhere easier than buried in Preferences?" Then I started to wonder about the "MIDI Plug" tool on the play-controls toolbar and wondered if it did that.
Well, I don't have a midi keyboard connected on the Mac, so I bet all my chips on it -- I unplugged the earphones, plugged them back in, played some notes, and, of course, they came out the Mac speakers.
So I twice-pressed the midi button, and hit "play". Lo and behold -- the sound came out the 'earphones' (plugged-in amp, actually).
The new instructions for either "my midi doesn't input" and "it didn't see my earphones change" should be to press that button once or twice as needed. Any reason why not?
Comments
That worked. Not intuitive. thanks!
In reply to That worked. Not intuitive. … by Lonny3octaves
It was only discovered yesterday! (The previous, "official" solution, was/is to press "reinitialize audio and midi" in the I/O sheet of the Preferences dialog!).
Don't know if it's good custom here, but as a newbie I'd like to bow in awe, even if it's an old post. After plugging in my Bose headset I needed to "untoggle" midi and then toggle it again. Would never have found it out myself. The Nobel Prize is yours!
In reply to Don't know if it's good… by What goes up
How "nobel" of you! This is now documented standard procedure, even if it is annoying that the underlying problem seems "too hard to fix."
In reply to How "nobel" of you! This… by [DELETED] 1831606
Too hard to fix ... while ANY other application on my laptops detect changes of audio output without any issue
In reply to Too hard to fix ... while… by frfancha
It is my belief (uninformed) that MuseScore's status as an application embedded in Qt somehow imposes these limitations not hobbling other application. I could be completely wrong.
In reply to It is my belief (uninformed)… by [DELETED] 1831606
Indeed using the QT API which by definition have to "hide" the platform specific info must make that kind of audio detection more difficult.
But isn't VLC using QT (not sure about that) and able to do it (pretty sure of that one ;-) ) ?
In reply to It is my belief (uninformed)… by [DELETED] 1831606
It's not QT but the PortAudio library which seems to have trouble with this.
Some users have confirmed that they have indeed seem the same issues when using Audacity for example.
In reply to It's not QT but the… by jeetee
Add me to that list.