Hi Martin, terribly sorry for the delayed response.
I have committed a small to change to allow the MusE
/internal/ LV2 support libraries to compile.
You must configure MusE CMake for Debug or default mode
/not/ Release mode if you want to use the internal
LV2 support libraries.
In Release mode I used -Werror (treat all warnings as errors).
In Debug or default mode I used -Wall (all warnings).
It seemed to make the most sense, we want the devs to catch
problems (warnings) before they're Released, while still
allowing them (and users) to try the built-in LV2 in Debug mode.
So...
Sadly, the internal LV2 support libraries did /not/ solve this bug.
Locally, I turned on the LV2_DEBUG CMake option to see what was
going on.
Amazingly it crashed less often, it's the first time I've been
able not crash, for about five gui closings/re-openings.
This suggests a classic timing issue since it takes time to
print out all those debugging messages, unless Andrew made
something more code-specific that changes actual behaviour
when debugging mode is on.
There is one more thing: With the LV2_DEBUG cmake option I
discovered a /continuous/ flood of these when the gui is open:
...
LV2SimpleRTFifo:put(): fifo is full
LV2SimpleRTFifo:put(): fifo is full
LV2SimpleRTFifo:put(): fifo is full
...
Oooh, that ain't good :-0
Possibly the /cause/ of this crash ?
Unfortunately I have only one LV2 synth installed: AMSynth.
(That's all that comes with SUSE.)
I think we send some default values to /each/ synth control
upon gui startup. Possibly in this case there are too
many AMSynth synth controls for Andrew's FIFO to handle.
An FIFO should ignore or drop some items in that case, but it
appears maybe they're 'floating' in the FIFO forever without
being 'consumed' by the reader.
Likely then, for Calf and so on it would be a similar situation.
If I'm right, a 'smaller' synth with few controls should not
cause that overflow...
Coincidentally I've actually been studying Andrew's FIFO class
these last few days. While working on mine :-)
Tim.
On 10/12/2017 05:03 PM, Martin Drautzburg wrote:
Am 10/11/2017 um 10:16 PM schrieb Tim:
> Further:
> I note that at least here on SUSE Tumbleweed,
> DSSI synth guis are /not/ opening at all any more.
> The gui thread times out and... nothing.
> Do you have any DSSI synths installed? Try xsynth or Hexter.
> Lemme know if they work for you.
I installed xsynth, but I have never used DSSI, so I don't quite know
what to do.
Same thing as for LV2 synths, no?
Create a DSSI synth track and drive it from a midi track.
I can add xsynth as a track-plugin, though I don't think that makes much
sense. I can open a "native GUI" which shows a
number of patches and a "send test note" button, wich leaves the level
meters at rest and produces no sound.
Mm, pressing that test button in xsynth or hexter /should/ briefly
activate the synth track's meters (check those peak readings closely)
and produce sound out of the routing outputs which MusE usually
automatically routes to the first Audio Output track /unless/
you have more than one Audio Output track. Tests OK here.
No midi track is required to use those Test Note buttons.
Unlike the LV2 GUIs This GUI uses my current Linux UI theme.
That depends. Some DSSI guis are GTK2, others might be Qt etc.
DSSI xsynth and hexter are Gtk2.
Same for LV2, each plugin can use a different gui toolkit.
Then the is a "GUI" which looks like all the other non-native pulugin
GUIs (it is also too narrow ) and appears to
control a single patch. It edits the currently selected patch and
follows changes made in the native GUI (but the native
GUI doesn't follow this GUI).
Mm, it should work both ways.
[Edit] But... it doesn't for synth-specific midi controls added
in the PianoRoll Editor controller panel. Thanks for pointing that out.
Something is messed up with the midi controls reading back the value.
It works fine when you edit the /audio/ controller graphs on the
synth track.
I had thought that I could add a new synth in "Midi appearance and soft
synths", but xsynth is nowehere to be found. I
can only see MESS and LV2.
Whoa, nah it should all be there! You may have to scroll down to see it
because that list isn't sorted :-(
Muse was compiled with
ALSA support
Lash support
OSC (Liblo) support
DSSI support
LV2 support
LV2 Gtk2 UI support
Fluidsynth support
Instpatch support
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/muse-sequencer/muse/issues/587#issuecomment-336266942>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFK9GnahbVEh4UOgwsIbmzSN2INk5mmTks5srn6mgaJpZM4Phun0>.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
