Meditadaze.pd (7.1 KB)
Letās take this example, in which begin, stop, metro, metro, seed and slowness should be controlled by the Zynthian.
I only see one metro in the patch and it is controlled with seed. I also had to change the gate 6 object to cyclone/gate 6 . The cyclone externals are included in the zynthian pd vanilla, so Iām not sure why I had to change the object, but at least it works now. I also added a volume control as I include it in all patches. I multiplied the slowness encoder value by 3 so itās current range is 0 to 381. Changing the seed value creates an error: ā$1: argument number out of rangeā. I didnāt try to figure out why but the error occurs on both my windows laptop and the zynthian.
The zynthian control widgets act like midi encoders and send values from 0 to 127. Since start and stop are controlled by bangs, any time the encoder value is changed it will send a bang. Using two labels in the yaml file causes the encoder to display a 0 until the value reaches 63, the halfway point, and from 64 to 127 it will display a 1. Of course as it currently stands, the start can be triggered twice by a slight movement of the encoder without changing the display to 1. Same thing for the Stop encoder, any movement will trigger the stop. I havenāt included a method in the pure data patch to only send one bang when the encoder value reaches 64 to trigger the stop. It also needs a method in pd to send 2 bangs to trigger the start when the encoder reaches 64.
While the start and stop encoders work as is, adding objects in pd to make it respond to match the encoders as previously described would make it proper. Iām out of time now, so I will leave this for you to accomplish. Let me know if you need me to give further explanation.
Meditadaze.zip (2.3 KB)
Thanks for your excellent work!
The precise implications of quite what this means can be found by bashing the monocleād face goood and hard with your clicking finger!
Meaning?
Please record something for usā¦
Does that .yml file for encoders to show up have to be named exactly āzynconfigā ? And the PD file - āmainā, for that matter? Because I gave PD and .yml file my own names , and after uploading to Zynthian from webconf I , too, see that the controllers are missing on Zynthian screen.
As far as I know, the YAML file for pd patches must be named zynconfig.yml but the PD file doesnāt have to be āmainā. The PD file name should be included in the first line of the YAML file. For instance, the first line of the YAML file for the 48Presets patch looks like this: main_file: ā48Presets.pdā
Well, Iām not sure now I renamed my .yml file to zynconfig, made necessary adjustments to pd patch (even renamed it to āmainā, just in case), uploaded to Zynthian⦠- still no visible controllers, Iām not even sure my Zynthian can actually use that PD patch, even though it shows the name⦠The PD patches that come preinstalled work fine and i can control them, so I guess it is whoās doing something wrong; maybe, some important element is missing. I really am at loss.
Iām attaching the zip folder in case someone knowledgeable in Zynthian-PD programming might step in and spot the culpritsā¦
numGen.zip (930 Bytes)
I didnāt test your patch but it does load in zynthian without errors. The problem I see is the indented lines in the YAML file.
I revised your file with a properly indented YAML and it should load your controls:
numGen .zip (899 Bytes)
Regards
yes, now they are there! DIdnāt think thatsuch thing as indentation should make such difference. But then again, Im not programmer. SO, thanks a lot for help Ronsum!
There are some who believe such programming language syntax is the work of the red devil! In āCā based languages, āwhite spaceā is only used to separate commands, parameters, etc. and is otherwise ignored allowing any indentation or line breaksā¦
or none. (See what fun it is too decipher JavaScript embedded in webpages which tends to be all on one line!) If all programming languages were the same, life might be more boring.