How to most easily manage receiving PCs to change a patch? Separate files?

Reply to How to most easily manage receiving PCs to change a patch? Separate files? on Tue, 16 Jun 2026 12:08:56 GMT

jpaskaruk — Tue, 16 Jun 2026 12:08:56 GMT

I'm the guy that posted the FCB1010 pedal thingy a while back, which only went so far as to turn each switch into a bang for PD use. I would now like to start creating different sets of functions for said bangs, for different songs - one might need a bass, another might need an organ pad, etc, all on the most convenient switches with the proper notes or effects pre-planned. I'm not sure what's the PD-Approved way to implement that.

At the moment I'm guessing, I save a different file for each patch, and forgive me for not having plowed through the entire documentation yet, there must be a way to trigger loading said patches? Or maybe you can compartmentalize each switch, so you reload only that section of the patch? I can already wrap my head around changing the notes of a note generator, say, but I want to keep it wide open as far as what could go into each pedal's post-Bang section.

I'm certain there's a bog-standard way to handle this in PD, please guide my dumb ass. I need to get 6-7 songs setup in here by July 1, I'm debuting my Schoolbus-themed parody act at a small Canada Day event.

Reply to How to most easily manage receiving PCs to change a patch? Separate files? on Tue, 16 Jun 2026 16:52:22 GMT

FFW — Tue, 16 Jun 2026 16:52:22 GMT

Don't you simply look for abstraction instead of sub-patch?

Based on your previous patch:

Reply to How to most easily manage receiving PCs to change a patch? Separate files? on Tue, 16 Jun 2026 18:07:11 GMT

willblackhurst — Tue, 16 Jun 2026 18:07:11 GMT

if you want to use the outputs of your multi channel thing on multiple targets you could put sends on the outputs. then you put a multi- spigot machine on each recieve set of a target group. so you make all the different target supatches and just open one of them only at a time.