I installed oram on one of my SD cards because I was asked to do some latency measurements after having raised a ticket regarding latency a while back.
After some initial hickups thinking the image was bad because nothing appeared on the touchscreen after booting, I heeded the advice of pointing my browser at the Zynthian anyway and performing an upgrade via webconf, which worked like a charm.
I must say I’m looking forward to the update. One thing I noticed is that adding and removing chains is lightning quick compared to how it was before.
But where has stage vs. multitimbral mode gone? I can’t find the setting, and the device seems to be in stage mode perpetually.
Unfortunately my latency measurements reveal that the latency is higher and varies more than in the stable release. But it’s early days yet.
The Stage vs. Multitimbral mode has changed significantly - it is now an individual setting on a per chain basis I think. If you search the forum for “Multitimbral” you’ll find quite a bit about it. I don’t know what’s the best topic for info, here’s one:
Bold Press the chain and you find MIDI In.
Bold Press the Midi input whose behaviour you want to change.
And now you can turn on multitimbral.
I am not sure, but unlike tunagenes said, it’s not per chain on my device, but per input device.
Or at least it’s a option, that you don’t have to do it for all chains.
If you want to clone midi channels, you have to create a new Midi Chain (an empty one).
Here you see Midi Out as option. Scroll down and select all engines, you want to copy.
This is necessary, if you are on Stage Mode and want to play more than one engine at once.
In Multitimbral mode it is not neccessary, because you can layer the chains with the same MIDI channel.
I am giving a try to Oram, and have found some strange things.
First, after install on a fresh SD card of 64 GB, the system has not detected my configuration as you can see (graphic 1).
(graphic 2) shows the actual config.
Second, everything seems fine except that my 7 inches screen still does not work with any config tested.
Third, the most strange is that pianoteq has dissapeared of my choices. However, when I reinstall the ptq of 8.2.2 , at first instance, when reappears, it seems to unblock all the choices of pianos !!!
However I test it and always sounds the same.
I do a software update (really really long) and AGAIN pianoteq dissapears again. I do not find it in any subject.
The most strange of all is that meanwhile I have installed the version 8.2.2. (graphic 3), ZYNTHIAN shows as installed version 8.1.3 (graphic 4).
Any idea or suggestion?
P.S.: I am testing with Behringer UMC 204HD instead of 404HD (I have both), and though it seems to work fine, I was wondering if this may have any kind of participation in my misadventures…
I got Pianoteq over Oram, after deactivate all engines enabling only Pianoteq.
However, though I have installed v8.2.2, Zynthian engines still shows v8.1.3.
This happened after burning a new image on SD, and proceed to software update prior to install Pianoteq. I could appreciate that BEFORE install the Pianoteq and enter the serial number, the defect configuration was showing 8.1.3 instead of v7.
Strange anyhow.
Not sure if this is the right thread, but I’ve just upgraded my V5 to use ORAM 2024-05-22.
There seems to be weirdness with copying the image. In particular, the /rootfs partition is exactly 13M with now freespace. Going in with my disk editor and opening up the free space fixed that issue.
I’m unable to connect the WIFI to my router.
a) If I enter the password through the Zynthian UI (Nice feature!) It does not connect.
b) Using the webconf, there is no place to enter the password for my WIFI network.
c) The AP option is working though.
It is recognizing the USB midi, so that is much smoother.
Hi @ralmond ,
I don’t understand topic 1. Why do you want to add more free space?
topic 2a) : I upgraded just now now, my connection to wifi is established, I can call the webconf pages.
probably a router issue, or a special character missing, or a typo? Just guessing…
topic 2b): the pages for wifi access for the webconf interface are by purpose deleted, because of redundance - see New testing image Bookworm Oram 64bits - #273 by jofemodo (just 3 days ago).
You can always use the VNC screen of zynthian’s UI to enter the password from remote.
So I can add soundfonts and other things. When installed, the /rootfs should take up all of the sd card not used for the /bootfs, so the extra stuff can be used for user files.
I’m getting the “could not establish connection” message when going though the UI on the router.
I’ve tried two different networks and I’m getting the same issue on both.
Looking at what is in dmesg I get:
[1234.65] brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
I tried setting the region to US, and I’m getting the same issue.
is it a regular zynthian V5 with RPi4 - I think so…
Did you create a completely new SDcard? - I know it’s stupid question, but you wrote “upgraded my V5 to use ORAM 2024-05-22”; upgrading from?
I overwrite the sd card, which previously had the the latest stable version of ZynthianOS.
I used the following steps:
I reformatted the whole card, so that the old partition structure was no longer their using the linux disks app.
I copied the ORAM (5-22) image using pv (I also tried dd with conv=notrunc, but that had much the same effect.) (BTW, the wiki is not quite right as sudo pv xxx.img >/dev/sdx doesn’t have root permission for the second half of the pipe. You need to either use sudo -i or dd there).
After this, the card had a small /bootfs partition followed by a roughly 13G /rootfs partition followed by a huge unformatted partition.
I went into my disk tool again and increased the size of the /rootfs partition to take up the rest of the card.
I then had enough room to put extra sound fonts & stuff.
The image has a constrained root partition to minimise the image size. On first boot, this is expanded and other configuration is performed, after which the system is rebooted. After that first reboot you should find the root partition grown to full size. You should not be manipulating the disk before booting.
After first boot, having waited for the update and reboot, you should arrive at the UI. You should attach to network then perform an update from the admin menu. This will apply the fixes that have been implemented since the image was built (which is quite a lot). After this you should find the experience much better.
Some of your description indicate the system has not been updated after booting.
as @riban described, this is the regular procedure when using images for RPi4. For all other OS for Raspi the resizing and adpting to the card’s real size is done on first boot.
Despite sudo, if you are using it you will have root access. Everything after this command is treated with root access rights. You shouldn’t use /dev/sdx. If you’d use it, you’ll normally get an error message saying that this device is not available. Depending of the number of devices you already have in your desktop/laptop.
Just before that command you can use “sudo lsblk” to check the device, which is new if you are plugging in your SD card. Plug it of, it vanishes with lsblk, plug it in it appears.
sudo -i opens a console with root access rights. With dd you’d also need sudo.
Thanks for the explanation. I’m and old hand at Unix/Linux but new to the Pi. My problem was that I was trying to copy soundfonts on the card before I did the first reboot cycle, so there wasn’t enough free space for everything I want to copy over.
The catch-22 is that I can’t do the update (which may or may not fix the wifi issue) until I can get a working connection to a wifi network.
I think you misunderstood my comment. Suppose that I use df (or lsblk or whatever) to determine that my card is attached at /dev/sdx.
Then
sudo pv /pathto/zynthian-os.img >/dev/sdx
Will give an error telling me I don’t have write permission on /dev/sdx, because although the pv command is run with UID 0 (root), the other side of the pipe, cat >/dev/sdx is run at UID 1000 (or whatever; user).
Here both the input and output file are opened by the dd process running as root.
Also, I saw the trick about reformatting the card if it already has partition information (because it was used previously in as an OS card). I’m not sure how necessary or useful it is.
I was traveling last week, and hence testing with two wifi networks, my hot spot and the hotel. I was misreading the keyboard, so I had the wrong password for my hotspot. But the hotel had the right passwords and was still not working. The Zynthian-AP network worked, but did not allow me to connect the Internet and the Zynthian at the same time.
I’m now home and tried again on my home network which supports both 2.4G and 5G bands. Now, with the right password, both my home network and the hotspot are working.
This link suggests that maybe it is interference on one of the 2.4G or 5G bands. The link is referencing problems with the Pi5 and I have a Pi4, so not sure if the upstream problem is fixed. https://forums.raspberrypi.com/viewtopic.php?t=367466
So I’ve managed to fix my connectivity issues, but I’ll post my error logs here in case somebody has a similar problem.
