Issues switching to Oram-Bookworm-64 bit branch

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:

1 Like

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.

3 Likes

Indeed the device mode (active channel / multitimbal) is per device, not per chain.

1 Like

Hi Zynthianers!,

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…

Regards




Hi @erasmo !

Only official kits are detected. Custom setups must be configured by hand.

Have you updated the software after burning the image? This is the first thing you should do .

Regards

1 Like

Hi @jofemodo!,

Yes I updated the software on webconf after configuring all parameters of my setup.

It was a very long update.

After that, everything seems to work except pianoteq.

Regards,

Obtener BlueMail para Android
En 2 may 2024, en 0:47, Jofemodo via Zynthian Discourse <discourse@zynthian.org> escribió:

Hi guys!

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.