After some time using my Zynthian V5 I must declare that is awesome!
I’m amazed at the ability of the raspbi 5 to process effects and sounds. In configurations with 3 audio inputs, with chains of 3 and 4 effects each and 2 or 3 keyboards, no problem so far.
However some doubts have arisen. As are 2 different ones I will open a new thread for each.
First of all comes to Pianoteq.
I don’t know why with v5 the first settings screen it lacks the VOLUME, PAN, MODULATION or CONDITION (really interesting), showing instead REVERB SWITCH, REVERB DURATION, REVERB MIX and ROOM DIMENSIONS.
Attached: first settings Pianoteq screen vs first settings Fluidsynth were are shown VOLUME, PAN, MODULATION WHEEL and EXPRESSION.
As long as I remember on V4 this settings were all accessible.
Am I missing something?
Referred to Pianoteq too, another question is related to UI and controls.
I suppose that given the lots of controls of Pianoteq; on Zynthian it has been made a rearrange to show the most relevant of them.
If so, why do I get adjustments of GUITAR LEGATO, FRET, VIRTUOSITY, GUITAR BODY or GUITAR EASY FINGERING when I am playing a PIANO? I should prefer a more comprehensive access to effects instead, if possible.
2 new screenshots attached showing this controls under Piano MKI Gentle Chorus.
There should be something wrong with you installation I think. I’m pretty sure that in my installation the parameter pages are named and ordered (latest vangelis). I think if anybody really knowing whats going on they might want which OS you are running.
I think even the Pianoteqs native plugin UI displays these “unmatched” parameters. Plugin parameters are fixed and global, with each having a unique ID. And they really should, because how else would hosts get automation done? So the number of parameters must be known to the host on instantiation. If plugins hide specific parameters in specific situations, they are basically only hidden UI wise. I think zynthians UI is basically a representation of hard coded, uniquely identified plugin parameters. In the case of an LV2 plugin it uses the corresponding ttl-file, were parameters can be hidden (not deleted) globally, but not dynamically.
So, in short: Pianoteq itself keeps all the parameters present, no matter which preset you chose.
That doesn’t describe the version. Is it the “latest image”? The latest stable release? The latest update to testing? The latest update to any repository? Post a screengrab of your webconf dashboard so we can see what actual version you are running.
Looks like your hanging on the eighth-latest point release. Probably the way would be to really chose the latest stable on webconf Software->Versions and update afterwards. I don’t know if there were any reasons to burn a new image instead?
I’m on vangelis and have PTQ 8.4.3. installed. Though I’m not on the official V4 or V5 hardware, but on V5 profile. See below.
Mine shows 8.4.3 also in the engine list.
I don’t see any reason why V4/V5 hardware should behave differently, because the handling of the parameters shown is a software issue. And regardless you have a V4 or V5 hardware your latest release would be Oram 2506.1.
If I were you, I’d go to my engines VNC, go to Preferences → About in the Pianoteq UI and post what’s under your Product info:
At this moment I´m trying, one more time, install a new Zynthian OS from the link provided.
Prior to continue I want to open a parenthesis. I have remembered that the last time I burnt the Zynthian OS I had to struggle a bit. I erased the micro SD on the Rasbpi Imager an then, “toasted” in Balena Etcher but with an issue. After some trials, finally I got a working installer without letting Balena Etcher finishing check process. All the times before that allowed Balen check, the process ended with failure. So I am not aware if that could be the origin of inconsistencies such as mentioned.
Must say I am working on Mac.
Now, after doing the same process and obtaining failure with the last stable image provided, I made a search on internet and found a recommendation to toast the Zynthian OS inside the Raspbi Imager.
I have done so a couple of times. What do I get? Basically nothing. Zynthian shows a lot of code passing with letters white and green, a one in red that could not read because of the inverted screen. And after that I get the message:
Debian GNU/Linux 12 Zynthian ttyMy IP adress is 192.168.1.138 blablabla
Zynthian login:
Well. Cannot enter in webconf. Tried on Chrome and Safari. It seems is “thinking” but no results. Have tried too access via ssh. And though it seemed yes, was not.
So my question before continue is which is the recommended method to write the microSD?
It sounds like the 32GBb old uSD Card is either defective or worn-out. The current recommendation is to use Raspberry Pi imager to write the Zynthian OS, due to problems with Balena Etcher the last couple of years.
It seems so. I can corroborate than Raspi Imager performed well.
Now I’m running the latest stable and have found, not only that controls on Pianoteq returned to their position as always, nor than their pianos sound is now more crisp and clear. In all the range, but in a more defined way in the last 2 octaves. How should I say?, sound more musical.
Pianoteq on zynthian on RPi5 will run at full sample rate. On lower spec RPi it is run at half sample rate which results in band-limited audio, hence sounding less bright.
