I'm have troubles routing the demo version of Midi Shaper in the demo version of Patchwork. I don't think it matters that i'm using the demo versions since the only major limitation is that you can only have one instance of the plugin opened.
So I have MidiShaper and Pro-Q in parallel in patchwork. Within MidiShaper, I have set the midi cc destination to 10 and set the midi output out to host. In patchwork I have set the midi output to host.
In Pro-Q, I have assigned a param via patchworks param learn mode. In patchwork, I have set Pro-q to receive midi info from host and have enabled midi to the assigned param, channel 0 and set midi cc to 10 in the MIDI & Automation window.
I'm probably doing something wrong since the routing isn't working properly. any help would be apreciated.
edit: I'm using the latest version of Studio One 3 and both pathwork and midishaper are updated to the latest version.
Patchwork and Cableguys MidiShaper compatibility?
-
- KVRian
- 811 posts since 2 Aug, 2013
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981 - KVRAF
- 6349 posts since 8 Sep, 2004 from Paris (France)
Can you maybe post a screenshot of your session/routing so that we can have a better idea of how the plug-ins are configured?
Anyway, the issue here is that you seem to be using the wrong target and source for the MIDI ports: "host" is the host application, so you are basically sending the MIDIShaper output to the outside world (after the PatchWork plug-in), and the other plug-in is listening to the host events (sent before the PatchWork plug-in), and they are probably not connected in Studio One.
Provided that plug-ins are in the appropriate order, using a virtual internal port (port A for example) with the same settings should work.
Hope this helps!
Anyway, the issue here is that you seem to be using the wrong target and source for the MIDI ports: "host" is the host application, so you are basically sending the MIDIShaper output to the outside world (after the PatchWork plug-in), and the other plug-in is listening to the host events (sent before the PatchWork plug-in), and they are probably not connected in Studio One.
Provided that plug-ins are in the appropriate order, using a virtual internal port (port A for example) with the same settings should work.
Hope this helps!
-
- KVRian
- Topic Starter
- 811 posts since 2 Aug, 2013
Here's my setup, I used the virtual ports instead of host and it still isn't working.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6349 posts since 8 Sep, 2004 from Paris (France)
Thanks for the details. MIDI routing is indeed right. But from what I can see here, you are trying to control the Pro Q plug-in using a PatchWork parameter (mapped to your sub plug-in parameter). This will not work, as the mapped parameters are only used to expose the parameters to the outside of the plug-in: they are not available inside the plug-in for MIDI control.
Why don't you directly configure the Pro Q plug-in to receive MIDI messages instead? (I think it does support it). This would look like this:
MidiShaper [MIDI]-> PortA -> [MIDI] Pro Q
if the Pro Q plug-in does not support direct control (which I doubt, but some other plug-ins indeed do not support it), you could also wrap it inside another instance of the PatchWork plug-in and expose its parameters like you have tried to do above:
PatchWork 1:
- MidiShaper -> Port A
- PatchWork 2 (listens to Port A)
- Pro Q (mapped parameter, controlled by MIDI)
Hope this makes sense.
Why don't you directly configure the Pro Q plug-in to receive MIDI messages instead? (I think it does support it). This would look like this:
MidiShaper [MIDI]-> PortA -> [MIDI] Pro Q
if the Pro Q plug-in does not support direct control (which I doubt, but some other plug-ins indeed do not support it), you could also wrap it inside another instance of the PatchWork plug-in and expose its parameters like you have tried to do above:
PatchWork 1:
- MidiShaper -> Port A
- PatchWork 2 (listens to Port A)
- Pro Q (mapped parameter, controlled by MIDI)
Hope this makes sense.