Short version is: factory is older and uses less severe cpi, third party is new and uses more. But pi4 is a bit light at high poly indeed
would be great, if you can share the surge-vocoder setup on zynthian-oram?
I used the native GUI via VNC to add the vocoder plugin to one of the scenes. The effect chain in Surge XT is at the top right of its GUI. Right click on one of the cells (I used the first one) and select the effect to insert.
You can then save the preset from Zynthian UI by bold press SELECT on the chain to go to the chain options. Cursor down to the processors in the tree and select Surge XT then select “Save Preset”. This puts the preset in a new bank that has no name. (@jofemodo we should fix that.)
Select another chain from which you want to side-chain, e.g. an audio chain if you want to vocode an audio input. Bold press SELECT to access the chain options and select “Audio Out” then enable the side-chain inputs to Surge XT. Side-chains are prefixed with an arrow.
You can then save the ZS3 / snapshot so that you can recall the preset and routing.
I have not spent any time creating an actually useful sound patch. I just added the side-chaining feature and proved it worked. I look forward to hearing some use it for real…
3 Likes
Just a quick confirm : we are planning our 1.3.2 stable release. You are all good with surge at head and need no more changes right? If there’s something still needed please open up a gh issue and let us know!
Glad it works for you all! Have fun!
5 Likes
Hi @baconpaul,
thank you for your kindness.
I would like to have one more topic that fits into a rather turbulent week.
It’s about OSC. It is disabled by default. So to run it in Zynthian you need to have VNC turned on (which takes some resources) and in the natural GUI go to options and turn it on here (which again requires having some computer turned on and time for this transaction).
I don’t know about the Zynthian developers, but I would be in favor of having OSC enabled by default.
Gotcha we don’t want that for all our users obviously but making it so there’s a way to force it on in headless mode would indeed be useful.
What’s easiest for zynthian? We have a user prefs xml in the user dir we could use or I suppose we could check an env var. once we know the mechanism you want it’s a one line change at startup
2 Likes
Maybe it would be enough for the LV2 version of the Surge XT to remember that OSC was on.
When I execute the sequence:
- switching on OSC
- restart zynthian
- zynthian uploads the last snapshot
So the Surge XT will start again with OSC disabled.
It does that now but it stores it in the daw session part of the state which isn’t I think how your system works since you don’t really use a daw I don’t think
Plus I imagine you want to specify in and out port and out ip somewhere and start surge with that right? Which is why I thought of env var perhaps
Knowing how zynthian manages lv2 lifetime would help
1 Like
Zynthian uses jalv to host LV2. It instantiates an instance of jalv when a processor (e.g. surge) is added to a chain and kills it when the processor is removed. This might occur when a user adds or removes a chain or when a snapshot is loaded, e.g. at startup. Zynthian uses jalv’s CLI to control and monitor the processor.
2 Likes
Gotcha so we save osc state in the save state but if you start an empty surge or a factory surge it is off
We obviously don’t want it always started for our users. What’s a way you would like to communicate osc to us which works for you? Env var seems like the obvious choice to me but I can also check file existence or any other unity type thing
Is it possible to implement/compile “Surge XT FX” in Zynthian, then it is easier to use f.e. the vocoder or other FX as a plugin?
I don’t think it is complete. If this is the repo then it says, “As of April 24 2023, they are a work in progress with only the Reverb and Flanger effect being factored here.”
I was going to try but couldn’t find a repro with all the effects.
1 Like
@riban, got the vocoder-surge-setup to work, thanks for your advice for the setup.
But I have some problems to store the setup, after reboot it did not work by default, will see…
So for today one more jam with Torso T-1. Five times the Surge XT this time.
Presets:
- 1# Kinsey Dulcet/Very Versitile Bass
- 2# Nick Moritz/Demon Power
- 3# Jacky Ligon/Bell Drum
- 4# Argitoth/Snare
- 5# Malfunction/Rusty
014-Surge.zss (9.1 KB)
The main repo builds two plugins surge and surge effect with all the effects outside the synth. That repo I us refactoring them so they can be used outside of surge repo but they are all in the surge repo and exposed in synth and in plugin
2 Likes
Surge XT Effect is already available in Zynthian. Simply activate in the webconf.
1 Like
@spurkopf
great, after activating found it the Audio FX / Others
2 Likes
I think that Surge XT is the best and more complex synth we have in Zynthian (togheter with Odin 2) but it’s a pity that there’s lack of usable controls. I opened the VNC interface, wich is great, and i noticed that i can assign midi CC and also do midi learn for almost everything. So i tried to assign basic stuff like cutoff, resonance, envelopes… with my MPK mini plus but it’s impossible to complete the task. Midi learn won’t respond running from Zynthian to Windows pc, and whern i assign a midi CC manually and save the patch i can’t load it from the Zynthian interface. I wasn’t even able to find the exact position of the single patches in the directories so it’s impossible to overwrite manually.
Any suggestion for a method to have some basic mapping to a hardware control?
In vangelis (testing) branch we have a new version of the LV2 plugin host which exposes the parameters of Surge-XT. There are a lot of them so it may be challenging to find and map what you want but it should be possible. Then you can save and recall presets within zynthian’s preset management mechanism.
4 Likes
Hi Riban, i’m using the Vangelis branch but i can’t see the parameters. Am i doing something wrong?