Did you update in the last 2 days?
1 Like
Done now. It’s great, thanks. I noticed parameters even in Monique!
1 Like
It seems that despite Raspberry Pi5 there are still performance limits and therefore not all programs are usable in Surge XT, e.g. Surge XT/Guitars/John Valentine/Distorted Electric Guitar. I use V5.1 with Pi5/8GB and get xruns with the red exclamation mark in the display. I have set overclocking to medium. And yesterday I had selected a Surge XT sound which caused Zynthian to freeze. Can’t remember which one it was.
Is this also the case with you that there are some sounds where the performance of the Pi5 is not sufficient?
I am not surprised that some Surge presets exceed zynthian’s resources. It is a very powerful synth with many complex options.
Do you have VNC disabled?
I will check if vnc is disabled. I didn’t use vnc until now. If it’s not enabled by default it should be disabled.
By the way - a happy new year.
1 Like
Just checked it, VNC is disabled. Wifi and Bluetooth are also disabled.
What if you could deactivate individual presets? This would prevent you from repeatedly clicking on individual presets that do not work or only work to a limited extent due to hardware restrictions?
Today I started looking into SurgeXT’s ttl if one could make a meaningful parameter ordering. Apart from that there are some considerations left for the 775 parameters, here’s what I also witnessed:
The parameters are not updated on Zynthians UI on preset load, besides all being normalized 0.f to 1.f they all default to 0.f (UI wise). Means that if you accidently touch a parameter it will be immediatly 0.f (Funny with OSC keytrack).
Also it comes up with another parameter ordering everytime you load it. But that would be another thing after ttl editing.
I think this may be similar to an issue reported in the issue tracker.
1 Like
This is a specific issue with Surge-XT. It seems to not send LV2 parameter updates when loading presets from GUI.
Regards
1 Like
I’ve been trying to get the delay in Surge XT to sync to the zynthian tempo. I am in the VNC interface, and have right clicked the delay time sliders and selected Tempo Sync, but it isn’t working.
I’m running Oram 2505.1
Is there a setting I’m missing?
Are you starting tempo transport from zynseq? Symply play any pad.
Regards
1 Like
I can’t get Surge XT to sync its delay to LV2 host either. It may not be properly implemented. Has anyone managed to do this in another host, e.g. ardour?
Tried on the desktop PC. Opensuse/Reaper/Surge XT 1.3.4 LV1 - the internal delay effect is synchronized
I just tried in Ardour and could not get sync to work. @spurkopf can you show steps to make this work in Reaper?
The effects are on the right-hand side. DLY is selected as the global effect. The pop-up appears when you right-click on the Delay Time. Tempo Sync is the default setting.
Yep! I go that but wanted a full example of how to show the tempo change happening… but I have been able to do this in reaper so confirm that Reaper can set the tempo of Surge XT delay. It is not yet clear what mechanism is being used. We use JACK transport and its tempo but that needs to be translated to the LV2 which has its own transport mechanism. I’m sure we have our tempo changing other LV2 plugins so this looks like an oddity with Surge-XT but it seems to also be an issue with Ardour, so maybe Reaper does something different???
I can’t say what’s up with Ardour, I’ve always avoided it. I hope I can try it out on the Zynthian in the evening.
Super simple setup, can confirm, delay does not sync.
012-Surge XT Delay.zss (35.8 KB)
perhaps you could try sending MIDI clock?
select from the tempo screen in zynthian ui
I had already tried this before, no change here.