Oops. Two more things:
1) Martin I replied to some of your questions, scroll down.
and...
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.
2) SOLVED! Answered on LAD today. Details there.
Solution: Check your /etc/hosts file! If your machine
name is /not/ in there you might want to add it.
liblo will /silently/ fail because it cannot resolve
your machine name!
According to one SUSE responder, the machine name should not
need to be in /etc/hosts.
But the original poster pointed out that it causes problems
for some apps, even 'ping'.
liblo supports IPv6 but it is not enabled by default and is
said to have some issues at the moment.
I'm not sure if that's what would really solve this.
If liblo could resolve my machine name using IPv6 without
it being in /etc/hosts.
Would it be able to?
Thanks.
Tim.
> 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
