To add a pure data synth to Zynthian I’m assuming that I
Write the patch (include ctlin objects to speak to encoders) and put it in it’s own directory
Put a matching config.yml file in the same directory that maps ctlins to encoders and describes functionality, etc.
Place the directory with those two files and su patches in:
(If the path is a little off it’s only because I’m typing it from memory. Also, I see that Csound is installed and ready to go … (?) (I can run a Csound file from the terminal, for example). But I don’t see a special layer for it as I do with Pure Data …
Am I missing steps with both Pure Data and Csound?
I haven’t uploaded any patches in Csound, but here’s how I add pure data patches. I’ll edit your steps to explain. I do steps 1 thru 4 on a PC.
1. Write the patch (include ctlin objects to speak to encoders) and put it in it's own directory. The
patch should be named with a unique name. In this example we'll call it wow.pd
2. Create a file and name it zynconfig.yml to map ctlins to encoders .and put it in the same directory.
Here's and example of a zynconf.yml file:
3. Use quotes, colons, underscores, spaces and commas just as shown in the example or it wont
load. Don't forget to include the first line showing the wow.pd name as shown in the example.
4. Select your wow.pd, any supporting files and subfolders and the zynconfig.yml file and use
them to create a zip file named wow.zip
5. Boot your zynthian. If you haven't updated your zynthian software since the Nov 17th update,
update it now or the following may not work.
6. Open the zynthian Webconf page on your PC.
7. Under Library select Presets & Soundfonts
8. Click on ZynAddSubFX - Synthesizer to expose the drop down selection menu
9. Scroll down and select PureData - Visual Programming
Select the bank you want your patch to go to. You can type in a New bank name and hit the plus
button if you don’t want to use an existing bank.
Click on the upload bar and then click on the click and choose button
Navigate to the wow.zip file, select it, then click on upload
I’ll give it a try later today. If successful I’ll see what’s possible with Csound (meaning can I figure it out!).
Thanks very much for taking the time to explain and document the steps with the video. MUCH appreciated! Maybe it’s an answer that should go right from here on discourse to a permanent home of the wiki?
Here’s a zynthianized PD patch I’ve been playing with. Feel free to include it if you want to.
It is not for everyone as it is somewhat a toy. However, some may find ways to fit it in to a
I’ll include some sound samples to avoid the monocle . #1 and #2 were made using
the pd patch only, #3 was made with the pd patch in the background and a synth layer
playing on a separate midi channel.
I’m having serious problems with the csound integration. It’s not very stable and i don’t like the csound way very much …
I’m seriously thinking about abandoning the csound zynthian engine and moving to SC, that seems more alive.
Anyway, i would upload a development branch, so you can enable the engine in your zynthian and try it a little bit, OK?
I thought I replied to your last message last night but I don’t see it on the board. In any case …
After more thought … if Csound isn’t stable within Zynthian maybe it’s not worth taking it past where it is now? Which best as I can tell is it’s not listed an an “engine” but it is working from an ssh login from another machine.
That being the case, maybe PD as a front-end for it is all that’s needed, assuming the PD objects that control Csound will run in Zynthian (so PD can call it)…
And SC is then the better bet as an engine? I will see in the next few days if I can get the PD-Cound objects to communicate.
If you make Csound available in whatever form will bang on that too