Thanks for getting back so quickly.
Yes that's exactly right :)
On Tue, 29 Dec 2015 23:41:15 +0400
Andrew Deryabin <andrew@xxxxxxxx> wrote:
Hi Will,
There was no feedback from me for a long time, though I still stay tuned
with latest changes in yoshimi :).
I try to summarize the list of changes:
1. If both midi and audio are connected at start with saved settings,
everything is ok.
2. If midi fails to connect (it only can be for saved jack binding, I
think), there can be 2 variants:
a) If yoshimi was started with no gui, then try silently to connect to
another backend and warn about it. If this also fails, simply print
another warning and continue with no midi input.
b) If yoshimi was started in normal mode, then show question dialog if
user wants to connect to another midi engine. Regardless of answer just
continue to work.
3. For failed audio the fallback algorithm should do the same sequence.
4. When starting in lv2 mode, just hide jack/alsa menu.
Correct me if I missed something :)
29.12.2015 21:40, Will Godfrey wrote:
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.
