Menu
What's new
By:
Filters

Patchboard public release

ok great. now If we can get a bunch of reaper users including me interested in spending some money to develop this in combination with patchboard, reaper and reaticulate that would be awesome, maybe by starting a new poll thread to see if there is any interest ?
cheers, lokotus
 
Patchboard users - I imported a Logic articulation set into Patchboard for the first time today to start a patch... and it imports the switches into "Alt Triggers" in the patch - which don't seem to send any MIDI data. this is from a beta build from last year so this feature isn't mentioned in the docs yet. Is there a way to use these "Alt Triggers" yet? If I set up the regular trigger column with the same data, all works as it should. But I'd like to not have to do that :). Thanks if anyone knows!

EDIT: I figured out it is very simple to drag over the alt triggers to the regular triggers so this was not that big of a deal, but I'd love to learn what the lat triggers are still if anyone is running this beta.
 
Last edited:
studioj said:
Patchboard users - I imported a Logic articulation set into Patchboard for the first time today to start a patch... and it imports the switches into "Alt Triggers" in the patch - which don't seem to send any MIDI data. this is from a beta build from last year so this feature isn't mentioned in the docs yet. Is there a way to use these "Alt Triggers" yet? If I set up the regular trigger column with the same data, all works as it should. But I'd like to not have to do that :). Thanks if anyone knows!

EDIT: I figured out it is very simple to drag over the alt triggers to the regular triggers so this was not that big of a deal, but I'd love to learn what the lat triggers are still if anyone is running this beta.
Click to expand...
The "Alt Triggers" are a mechanism I added for storing the underlying MIDI messages the articulation set or expression map sends to the instrument to trigger it. In most cases where you're using articulation sets, for example, you don't send those triggers to the instrument directly. Instead, you'll send some remote trigger that the articulation set uses to activate a specific articulation. Another use case would be importing an existing articulation set just to get the data imported but you're not using it in Logic. In that case, you want to talk to the instrument directly so you'd want to move the Alt Triggers over like you did.

It's kinda half-baked as a feature right now. The eventual goal is to be able to export patches as expression maps or articulation sets so you could import them into your DAW. It would then auto-generate new triggers for you and move the "direct" triggers into the Alt Triggers.
 
mrmiller said:
The "Alt Triggers" are a mechanism I added for storing the underlying MIDI messages the articulation set or expression map sends to the instrument to trigger it. In most cases where you're using articulation sets, for example, you don't send those triggers to the instrument directly. Instead, you'll send some remote trigger that the articulation set uses to activate a specific articulation. Another use case would be importing an existing articulation set just to get the data imported but you're not using it in Logic. In that case, you want to talk to the instrument directly so you'd want to move the Alt Triggers over like you did.

It's kinda half-baked as a feature right now. The eventual goal is to be able to export patches as expression maps or articulation sets so you could import them into your DAW. It would then auto-generate new triggers for you and move the "direct" triggers into the Alt Triggers.
Click to expand...
Ah great, thank you! So to be clear the "Alt Triggers" are midi messages received by Patchboard to trigger the articulation rather than pressing the pad on the iPad or App right? But don't actually do anything with the DAW. Maybe "Input Trigger" would be a better name or something like that if that's a correct understanding.

The set I imported had no "switches" programmed, only "outputs", and those were put into the alt triggers. I did want to use this patch in Logic, but the alt triggers don't send data and so I moved them over to the triggers yes. Love the idea of your eventual goal, that would be incredibly useful. I've created hundreds of patches that I use with Pro Tools and so it would be awesome if I could export those as Articulation Sets to then use within Logic when working with that DAW. looking forward to that. thx!
 
Is there a way to batch tags in PB? Or does the tagging need to be done for each track one by one ?
Can disabled tracks still be tagged inside PB without being enabled first ?
 
Anyone using Cubase 12/13 Mac Silicon having issues with Patchboard crashing Cubase?

I recently upgraded from a Mac Pro 2019 to a Mac Studio and Patchboard won't work with Cubase 12 or 13 running natively. It does work with Rosetta, obviously. I'm just trying to gauge if this is a local issue or a Patchboard issue.
 
Bender-offender said:
Anyone using Cubase 12/13 Mac Silicon having issues with Patchboard crashing Cubase?

I recently upgraded from a Mac Pro 2019 to a Mac Studio and Patchboard won't work with Cubase 12 or 13 running natively. It does work with Rosetta, obviously. I'm just trying to gauge if this is a local issue or a Patchboard issue.
Click to expand...
No crashing issues here. Running Cubase 12 natively on silicon on M1 Pro.
 
Very recently, i bought patchboard too (the DIY version). It'll take me a long time to completely overhaul the template to work with patchboard, but it's very easy and fast to create a patch in there. Importing an articulation set from logic wasn't super straight forward, and i'm not sure it recognizes multi-midi-channel sets. But overall, i think it will save me a lot of time in the long run.
I also saw the macro panel, but haven't tried this one yet
 
You must log in or register to reply here.
Top Bottom