Hi Andrew,
Recently I implemented MIDI and Audio saved preferences in the Settings
window, and also making such settings from the command line as saved ones. This
makes the compile-time options redundant and I would like to soon remove them.
In fact, I used hooks that Cal had already put in place.
However, if you start with the wrong settings for any reason, Yoshimi still
bails out (although you can now always correct that from the command line).
In Config.cpp Cal provided no-midi and no-audio as well as the ones I used, but
trying to force-set these results in a bailout again. I feel sure Cal
originally intended to make use of them to provide a safe fallback position,
otherwise why have them?
Is this something you'd be interested in looking at?
I envisage a failed start still with Yoshimi up and running. If (say) MIDI was
OK, you'd see Yoshimi responding but just with no audio out. Whereas if audio
was OK you've be able to use the built-in virtual keyboard to produce sound.
You could then access the settings to correct the problem without having to go
via the command line.
In a perfect world it would be possible to change these and have the changes
activated immediately without needing a restart - I've no idea how practical
that would be.
A further practical option would be for both Jack and ALSA tabs to be disabled
when running as LV2.
Hope you've been enjoying the holidays,
Will.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Yoshimi source code is available from either:
http://sourceforge.net/projects/yoshimi
Or: https://github.com/Yoshimi/yoshimi
Our list archive is at: https://www.freelists.org/archive/yoshimi
To post, email to yoshimi@xxxxxxxxxxxxx
