I haven´t any part from the kit, but after doing these changes I can start gui (no need to change fb1->fb0) simply ssh’ing, start qjack and running zynthian.sh (i´ve changed hw:0 to hw:CODEC in jackd line). ATM I didn´t manage to have any sound from MOD-HOST, due to audio card drops.
Very responsibe, I noticed I can use cursor keys and mouse to navigate up-down. There is, at least, some keys to ENTER and/or leave submenu?
BTW: even if you don´t change anything, thank you for your work!
(tios estoy como un niño chico el dia de reyes)
The Zynthian GUI is not intended to be used with a mouse and keyboard, so there are no keys for doing anything, only the standard keys associated by default by the GUI toolkit (tkinter).
Perhaps it’s a good idea to configure some keyabord’s keys… but also, you could test the emulator … or better, build a zynthian box
Jeje! Of course!! In the next revision i will create some standard keyboard shortcuts for the Zynthian GUI, so people can test the GUI from a standard terminal
You have to put a “zynthian_hw_version.txt” with “PROTOTYPE-3H” in the “/zynthian” directory. Probably this will change in a few days
Yes. This happends because there is no pedalboards in the folder. I should copy some example pedalboards.
Yes. I’ve this problem too. I’m trying to figure what is the problem. I can’t see any problem in the installation process, o probably the problem is related to the last changes in the MOD software. Any help with this will be welcome
I’ve been tracing the audio output connection problem and i can see that mod-ui is trying to connect to “mod-monitor” instead of “playback”. And “mod-monitor” outputs doesn’t exist in zynthian, so this is the problem.
Searching in the mod-ui repository, i’ve seen that falktx has made, recently, some changes related to monitor outputs, so it should be easy to find the problem.
Ahhh, ok - i thought it was a special problem on my installation. Just saw that there were much changes on mod-host. Hm - very strange what they have done. I currently have no idea for what the changes are needed - we will see. I think I will checkout an older version
Found the problem: You have to start mod-monitor. This is an internal jack-client so you have to load it after starting jack with jack_load mod-monitor. I have added this to the systemd service and loaded mod-host also as an internal client. Also disabled the mod-host service and it works!
Your solutions is quite elegant, but i would prefer to not enable mod-monitor “by now”. It’s only a hub that redirect output to system output and, if available, to mod-peakmeter.
Using environment variables we can disable the mod-monitor feature in mod-ui:
Environment=MOD_APP=1
Environment=MOD_LIVE_ISO=1
But this also produces some unwanted side effects, like disabling “pedalboards bank feature” in the GUI, so, i’ve modified mod-ui, adding a custom environment variable that only disable mod-monitor usage:
As you can see, the zynthian mod-ui fork also add some extra messages to websocket protocol that are needed for sending the pedalboard name to the zynthian UI:
When the new image is released, i will try to get this changes into the MOD main trunk. Will see …
Regarding the mod-host change to run as a jack internal client, i like this, so i will try to integrate it in the new image.
machine=uname -m 2>/dev/null || echo unknown
if [ ${machine} = “armv7l” ]
then
model=cat /sys/firmware/devicetree/base/model 2>/dev/null || echo unknown
if [[ ${model} =~ [3] ]]
then
CPU=“-mcpu=cortex-a53”
FPU=“-mfpu=neon-fp-armv8”
else
CPU=“-mcpu=cortex-a7 -mthumb”
FPU=“-mfpu=neon-vfpv4”
fi
FPU=“${FPU} -mneon-for-64bits”
fi
echo “Hardware: Architecture: ${machine} Model: ${model}”
export CFLAGS=“${CPU} ${FPU}”
export CXXFLAGS=${CFLAGS}
It would be nice to have the standard variables exported for using when logged in. The rest of the statements configures the compiler flags on base of Raspi2 or Raspi3 which (perhaps?) creates more optimized binaries.
The fantasía installation fixup and your improvements for .bashrc are accepted. It will be in the repo this morning.
Regarding the last one, i was installing lvtk from git repo, using your “recipe”. Do you think is better to install from the repo?
