Patchwork 2.1 standalone midi setup

Official support for: bluecataudio.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Altough I'm not a MIDI noob, I feel completely stuck setting midi in Patchwork standalone with MIDI hardware or virtual interfaces. The manual reports an audio/midi setup but the window shows only audio settings. What I'm trying is playing VSTi wrapped in Patchwork standalone from Ableton Live and/or a midi keyboard.
Where I configure my MIDI interfaces? I loaded a VSTi and set Midi Host to all channels but no sound sending MIDI from either Live or keyboard. What am I missing in such a basic topic?
Thanks a lot.

Post

With PatchWork standalone, you do not need to configure your interfaces, as they are all used by default. You just need to make sure all the interfaces are up and running before launching the application.

Post

Hopefully this doesn't derail the thread too much, but the question seems relevant enough to post here anyways:

Regarding MIDI routing in Patchwork (or Axiom), I'm having trouble with getting a sequencer VST (Monoplugs B-Step) to talk to a synth that's also loaded into Patchwork. The sequencer's MIDI settings are set to "in-host routing." If I specify a particular MIDI channel (let's say B) for the MIDI output on the sequencer, then specify the same for the input on the synth, nothing seems to happen.

I realize you guys can't support third party plugins, but hopefully my question is general enough regarding MIDI routing so I can understand some best practices here to get things to play nicely with each other. And I'm also curious about how to isolate a sequencer to only talk to one particular plugin (let's say a synth), without communicating to another VST, like a drum machine?


Thanks. :)

Post

This is odd. You should indeed use the same port (A,B... to P) for the output of the sequencer and the input of the synth. Maybe you need to make sure "all channels" is selected? Also, is the sequencer sending data to the same MIDI channel as what the synth expects? BTW you will also need to unselect the "host" MIDI input for the synth if you don't want to listen to external events sent from the outside of Patchwork (or Axiom).

Also, the sequencer has to be placed BEFORE the synth in the signal chain. MIDI events are otherwise dropped by our software.

Since there are 16 available internal ports, each one supporting up to 16 MIDI channels, there are up to 256 independent connections available: a plug-in listening on Port A will not receive data from plug-ins sending MIDI to port B for example.

Hope this helps!

Post

Blue Cat Audio wrote:This is odd. You should indeed use the same port (A,B... to P) for the output of the sequencer and the input of the synth. Maybe you need to make sure "all channels" is selected? Also, is the sequencer sending data to the same MIDI channel as what the synth expects? BTW you will also need to unselect the "host" MIDI input for the synth if you don't want to listen to external events sent from the outside of Patchwork (or Axiom).

Also, the sequencer has to be placed BEFORE the synth in the signal chain. MIDI events are otherwise dropped by our software.

Since there are 16 available internal ports, each one supporting up to 16 MIDI channels, there are up to 256 independent connections available: a plug-in listening on Port A will not receive data from plug-ins sending MIDI to port B for example.

Hope this helps!
Maybe the order of the plugins was creating the problem? I don't exactly remember what I did the first time.

Either way, my sequencer is talking to Repro-5 now. All good, thank you. :D

Post

:party:

Post Reply

Return to “Blue Cat Audio”