Need help; struggling with rack-level-mappings

[poulpoulsen]

Hello, after some pause I investigate and play with Pylades again. Currently I use a huge patch to jam with, and I think it is worth playing with your wonderful extension.
I want to map a bunch of PatchMaster modules with PyLades. But unfortunately I am not able to map more than one PatchMaster module. The end result is always the last mapped module. I know how to map with "keep assignments," but could you describe the exact way to map more than one PatchMaster module? and the necessary options.

A big thanks for developing this module.

Poul

[rjsmith]

Hi Poul,

Thanks for your message, its great to hear from anyone actually using these modules.

For controlling parameters on different modules but from one TouchOSC set of pages, use the "Rack" mapping, not the individual per-module mappings. I designed the "rack" mapping exactly for your scenario.

See https://github.com/rjsmith/rsbatech-modules/wiki/Orestes%E2%80%90One-Module-User-Guide#rack---level-mapping

(the same setup applies to Pylades). The idea is that you save a single rack patch - level set of mapped parameters (e.g. within a bunch of Patchmaster modules) using the "Save rack - level mapping" context menu option instead of the per-module "Add module to library" option. This causes Pylades to save those mappings in its module state within the current VCVRack patch ... you must then remember to save the vcv file itself! (otherwise your rack mapping will be lost). Then, next time you open the vcv file, connect up Pylades with your TouchOSC controller, then press the "Rack" button on the TouchOSC preset. It will load the patch-level controller mappings.

By switching between the TouchOSC module select page and pressing the "rack" button, you could even alternate between using any patch -level mappings you have made, and individual mapped modules from your factory library.

Please let me know if you figure it out , or not .. I can provide more step by step instructions if needed..... :-)

Edit - I went ahead and added some step-by-step instructions to the Wiki at the above link anyway. Hope that is clear now!

[poulpoulsen]

Hello, yes the normal usage I understand and it works. but I struggle or don't understand to map more than one patch master module. my patch master modules maps to different other modules to create a smooth GUI. as far as I understand, it is possible to map these patch master modules also to touchosc. could you please describe, how this process works and what I have to do, to map multiple patch master modules as racks level mapping?

…

---------------------------------------- Von: Richard Smith ***@***.***> An: rjsmith/rsbatech-modules ***@***.***> Kopie: poulpoulsen ***@***.***>; Author ***@***.***> Datum: 13.04.2026 22:06:09 Betreff: Re: [rjsmith/rsbatech-modules] Need help; struggling with rack-level-mappings (Issue #9)

[Bild]*rjsmith* left a comment (rjsmith/rsbatech-modules#9)[#9 (comment)] Hi Poul, Thanks for your message, its great to hear from anyone actually using these modules. For controlling parameters on different modules but from one TouchOSC set of pages, use the "Rack" mapping, not the individual per-module mappings. I designed the "rack" mapping exactly for your scenario. See https://github.com/rjsmith/rsbatech-modules/wiki/Orestes%E2%80%90One-Module-User-Guide#rack---level-mapping (the same setup applies to Pylades). The idea is that you save a single rack patch - level set of mapped parametyers (e.g. within a bunch of Patchmaster modules) using the "*Save rack - level mapping*" context menu option instead of the per-module "Add module to library" option. This causes Pylades to save those mappings in its module state within the current VCVRack patch ... *you must then remember to save the vcv file itself!* (otherwise your rack mapping will be lost). Then, next time you open the vcv file, connect up Pylades with your TouchOSC controller, then press the "Rack" button on the TouchOSC preset. It will load the patch-level controller mappings. By switching between the TouchOSC module select page and pressing the "rack" button, you could even alternate between using any patch -level mappings you have made, and individual mapped modules from your factory library. Please let me know if you figure it out , or not .. I can provide more step by step instructions if needed..... :-) — Reply to this email directly, view it on GitHub[#9 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACAFDKZZMLOGK26IFJWMLL34VVCCLAVCNFSM6AAAAACXX2KEJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMZZGI4DIMRSGE]. You are receiving this because you authored the thread. [Verfolgungsbild][https://github.com/notifications/beacon/ACAFDK2O3WIQXCDFD6AM6E34VVCCLBFCNFSM6AAAAACXX2KEJCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTX4VZL73JTSMVQXG33OUZQXK5DIN5ZA.gif]

[rjsmith]

Hi - did you follow the steps I listed here ? https://github.com/rjsmith/rsbatech-modules/wiki/Orestes%E2%80%90One-Module-User-Guide#rack---level-mapping

There is also a section in my intro video on Youtube that shows you the process https://www.youtube.com/watch?v=Kb1bYARAQpY&t=938s

Let me know which step(s) do not seem to work for you?

[poulpoulsen]

Yes i follow the steps and i am struggling on step 4. i attach two screenshots, where you can see, whats wrong. The first screenshot shows, that i mapped some patchmaster modules. The yellow points in the patch and pylades show, that mapping works. But in TouchOSC if i push "Rack" or if i apply rack-level-mapping, nothing happens.[

](url)

[rjsmith]

Thanks for the screenshots very useful. Although you have added Patchmaster controls to the Pylades list, you have not yet mapped any of those to fader widgets on the TouchOSC preset .. thats why you can see the "...." strings on each row showing an empty MIDI mapping. You are missing the step where you need to click on a row in the Pylades list, then move a knob on the Pylades TouchOSC preset. This will create the mapping between between a specific knob on the TouchOSC preset and a row in the Pylades mapping list.

From the point shown in your screenshot you need to:

1. Press the bottom right-hand "Clear" button on the TouchOSC preset. You will see a 6x6 grid of faders ready to be mapped
2. Click the first row on the VCVRack Pylades module parameter list. It should now show "Mapping..."
3. Now move the knob in the 6x6 grid that you want associated with that mapped parameter. Because this is a Patchmaster button widget you are mapping not a knob or slider, you may need to move the TouchOSC slider past 50%.
4. The VCVRack Pylades module should receive the data from the moved TouchOSC fader, and then show something like "FDR000" instead of the "...."
5. Repeat 2 - 4 for each of the rows in the Pylades parameter list, each time using a different fader widget on the TouchOSC 6x6 fader grid. Remember you can also switch to any of the 6 pages in the TouchOSC preset if you have more than 36 controls to map.
6. Then select the "Save rack-level mapping" context menu option to add your Pylades mappings in the vcv file, then remember to save the vcv file itself.

Please see this part of the intro video (this is for per-module mapping, but the same sequence applies for Rack mapping parameters also). https://youtu.be/Kb1bYARAQpY?t=651

[rjsmith]

Here's a super-simple vcv file with a Pylades module and two Patchmaster modules, each with a single button that are themselves mapped to the reset and Run buttons on a Clocked module. Open the vcv file and select an audio device in the VCv Audio module (otherwise mapping will not work at all). Then If you connect the Pylades to your TouchOSC client,then press the Rack button, you should see the two mapped knobs

PyladesPatchmasterMappingExample.vcv.zip

[poulpoulsen]

Thank you, I can patch/map modules. But I don't know how I can add some more. Yesterday I mapped some PatchMaster modules, and today I want to work further on them. How can I manage it? I do not want to map all of it from the beginning. Is it possible?

[rjsmith]

Yes, just scroll down to the end of the mapping list on the Pylades module, to the first empty row, then:

1. Click on the row, it will show "Mapping..."
2. Click on the pAtchmaster control u want
3. Move the associated TouchOSC knob widget you want to map it to

Then select the "Save rack-level mapping" context menu option to update your Pylades Rack mappings in the vcv file, then remember to save the vcv file itself.

[poulpoulsen]

Ok thanks for the fast reply. But unfortunately it does not work here. Pt1 works; Pt2 works. But how could I move a "free" widget in TouchOSC? I only see the widgets from the mappings i already did? If I push Clear, all mappings are gone and I see all widgets.

[rjsmith]

When you press Clear, it shows all the knobs, You just need to remember which knobs you had already mapped, and then map new knobs. The existing mapping will still be there , and will reappear when you press the Rack again (after saviung the Rack mapping again of course).

[poulpoulsen]

Aha, thank you. I will trest it.

[poulpoulsen]

Currently it works for me the way I thought.
A final question:
Am I right that implementing buttons is not on your roadmap for the module?

[rjsmith]

Hi @poulpoulsen Good to know you got it working.

I guess you mean using button controls on the TouchOSC preset vs faders? The problem is that VCVRack module developers have used many different ways to implement button widgets (and their associated visual display of pressed / toggle state). This makes it very difficult to generically handle any mapped button with feedback of their pressed / toggled state in my plugin. For now, I have found using a finger swipe movement to move a TouchOSC fader mapped to a VCVRack module (vs a tap for abutton) to be not too bad ....