INFO:root:STARTING MOD-HOST & MOD-UI services…
INFO:root:Connecting to MOD-UI websocket…
INFO:root:Getting Bank List for MOD-UI
INFO:root:MIDI Chan Selected: 0
INFO:root:Getting Bank List for MOD-UI
INFO:root:Loading Controller Defaults
INFO:root:Getting Bank List for MOD-UI
No, the port didn’t change. Check that MOD-HOST and MOD-UI are running in background.
Perhaps the last MOD-HOST versions have some problem … i will try tomorrow.
I took your SF2 and created a FluigPlug-LV2-plugin: makes sound out-of-the-box.
...
Created a new pedalboard.
Changing sounds worked, Poweroff-Button not
...
Yes - seems to be a bug inside FluidPlug. The original FluidPlug does the same. Will try it on the MOD-Duo to see if this happens there also.
...
In Log when changing a program
DEBUG:root:WS >> param_set /graph/GenericFluidPlug_NiceTest program 0.000000
ERROR:root:Parameter Not Found: /graph/GenericFluidPlug_NiceTest/program => unorderable types: str() > int()
WARNING:root:zynthian_gui.zyncoder_read() => 'Classic Steinway'
This is weird, because I didn't copy the Classic Steinway sound.
My NiceMarkus.sf2 has it, but I removed the NiceMarkus plugin already...but didn't restart the zynthian box...which I do now.
...
Hmmm - yes, I know this problem. It is not a plugin problem but a problem of how the Zynthian-UI is handling the parameters of a plugin, see MOD-UI pedal for SFZ input - #18 by C0d3man
...
Starting mod-ui on the zynthian-box.
Pedalboard is gone..didn't save it before.
Creating a new one. Same behaviour...don't know about the log messages yet..will save first..."NOTHING TO SAVE"
That's one of those "unstable" things. I saved a pedalboard before, but doesnt work now.
...
Do you have updated mod-ui and mod-host before you send your log? I think this is not a plugin-problem but a problem inside MOD-UI. I am not using an external MIDI interface (or let’s say: currently I am not using). Storing a pedalboards works also fine - but there were problems some time ago.
Can you update mod-ui/mod-host and confirm if this solves the MOD-UI problems?
I hope that the Zynthian-UI problems will be solved for the next release and I will look deeper into FluidPlug to solve the problem with enable/disable the plugin.
just want to let you know, that after the update (and an additional mod-host update) everything works like a charm.
Now I will test, how it works with the new layers
Generally it works. But mod-ui layers doesn’t let you define the midi channel.
How should we do this? For each channel a separate pedalboard with a midi filter or is it possible to have one pedalboard and a certain midi switch device , that does the routing to generating devices?
Only 1 layer with MOD-UI can be created. The MOD-UI engine should be removed from the engine’s list when one MOD-UI layer exists.
Probably there is some bug in the Zynthian UI related to having several instances of the same plugin. Let me sometime to take a look. This code is a little complex
Perhaps you can recompile the standalone version of FluidSynth and use the multitimbric/multilayer features, without MOD-UI. If you want to “filter” the output, perhaps you could prepare a MOD-UI pedalboard an tweak the zynthian autoconnector to send the FluidSynth audio output to the MOD-UI pedalboard … It’s a little bit tricky, but very powerful.
I’ve been thinking about it in the last weeks: sending the audio from the standalone synths to MOD-UI, that would act as effect chain
I can’t really follow.
Before I tested mod-ui, i had 4 layers of fluid-synth on 4 different midi channels.
But at 440Hz.
So i don’t understand, what I should recompile.
And how would I route the outcome of those 4 layers to a mod-ui chain?
Hm - this maybe a problem wirh the instance itself. I will have a look at this. Normaly this should work with “endless” instances (you know: we all have “endless” memory in our computers )
Currently I have so much projects at the same time, so I cannot react JIT - sorry.