Some time ago I was working with some patches in Patchwork that used Melda's MCCGenerator to automate a plugin in the following column slot. Now it doesn't seem to work - I tried it in Digital Performer (current version) and in the standalone Patchwork (latest version, 2.61), and I can't get MIDI from MCC Generator (latest version, 16.04) to affect a plugin in the next column.
Arbitrarily, I have PW's Control 1 set to Channel 1, CC 75. MCCGen is in the Parallel 1:1 slot of PW, it's "CC1" Module is outputting cc75 on MIDI Channel 1. MIDI Output of the plugin is set to Port A. I put BC's Gain utility plugin in the Parallel 1:2 slot of PW. It's MIDI Input is set to Port A, Channel 1. The Gain control is mapped to Control 1.
The Control 1 assigned control knob functions properly, adjusting the Gain control. But moving the value knob in MCCGen does nothing.
This is true if I run PW as a plugin (in Digital Performer, latest version) or as a standalone, on a 2015 iMac running Monterey 12.6.3. It is also true of all versions (AU, VST, VST3) of PW, MCCGen, and BC's Gain plugin - all versions and all combinations of versions.
I will also report this to Melda. But I'd like to know if anyone else is successfully using MCCGen in Patchwork currently, and if so, what are your settings?!
MCCGenerator no longer working in Patchwork
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981 - KVRAF
- 6345 posts since 8 Sep, 2004 from Paris (France)
I am not sure I fully understand your setup: Why would you control the gain parameter both via MIDI from another plug-in AND mapped controls?
-
- KVRist
- Topic Starter
- 295 posts since 19 Jul, 2016
The mapped control was just there to see if the control was working at all, since the modulator coming out of MCCGenerator was not. It is not a significant part of the setup nor would I use it in practice.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6345 posts since 8 Sep, 2004 from Paris (France)
Well the mapped control may actually not move, as it checks that the target plug-in(s) parameters are actually being edited (to avoid infinite loops, as you can now map multiple parameters at once). So you may want to open the gain plug-in GUI and see if it moves there.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6345 posts since 8 Sep, 2004 from Paris (France)
Just doubled checked today, and using the DP Meter Pro plug-in to send MIDI CC based on incoming peak level, it still works:
BTW which plug-n format are you using for the Generator? It is possible that some plug-in formats have not fully implemented MIDI output (I know some manufacturers still do not support MIDI out for Au or VST3). Have you tried with the older VST format for example?
BTW which plug-n format are you using for the Generator? It is possible that some plug-in formats have not fully implemented MIDI output (I know some manufacturers still do not support MIDI out for Au or VST3). Have you tried with the older VST format for example?
-
- KVRist
- Topic Starter
- 295 posts since 19 Jul, 2016
Thanks - I am on the road and will check more when I return at the end of the week. I checked with all plugins in all formats in all combinations, as I have indeed found that some plugins only work in BCC in certain formats. But I will check again...
Meanwhile, have you checked using Melda's MCCGenerator, which is the specific plugin I have not had success with? Just for confirmation, thanks - it looks like BCC is passing MIDI correctly. I will also report to Melda.
Meanwhile, have you checked using Melda's MCCGenerator, which is the specific plugin I have not had success with? Just for confirmation, thanks - it looks like BCC is passing MIDI correctly. I will also report to Melda.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6345 posts since 8 Sep, 2004 from Paris (France)
-
- KVRist
- Topic Starter
- 295 posts since 19 Jul, 2016
sigh...here's the reply from Melda: "I'm afraid I can't help you with that, it works in pretty much all DAWs, so I'm throwing the hot potato back 
. Note that you should NOT use AU, as MIDI output seems not to work with most DAWs. But there should be no problems with VST2 / VST3."
. Note that you should NOT use AU, as MIDI output seems not to work with most DAWs. But there should be no problems with VST2 / VST3."-
- KVRer
- 23 posts since 28 Jun, 2021
I can confirm that the following setup works:
macOS, PatchWork standalone 2.61
With MCCGenerator 16.04 VST2 version in parallel chain 1:1 with MIDI out going to Port A, CC1 set to Controller 74 on Channel 1.
Dune AU plugin in PW parallel chain 1:2, getting MIDI in from Port A. By default, Dune has MIDI CC 74 mapped to filter cutoff.
Moving the control in MCCGenerator for CC1, I see the filter cutoff in Dune moving.
Not sure if that directly relates to OP's situation, but can at least confirm that there are combinations of PatchWork and MCCGenerator that work.
macOS, PatchWork standalone 2.61
With MCCGenerator 16.04 VST2 version in parallel chain 1:1 with MIDI out going to Port A, CC1 set to Controller 74 on Channel 1.
Dune AU plugin in PW parallel chain 1:2, getting MIDI in from Port A. By default, Dune has MIDI CC 74 mapped to filter cutoff.
Moving the control in MCCGenerator for CC1, I see the filter cutoff in Dune moving.
Not sure if that directly relates to OP's situation, but can at least confirm that there are combinations of PatchWork and MCCGenerator that work.
-
- KVRist
- Topic Starter
- 295 posts since 19 Jul, 2016
So I can get that to work, but only with absolute default settings. As soon as I begin to change anything, the CC number, control assignments...everything stops working.
-
- KVRer
- 23 posts since 28 Jun, 2021
Are you changing CC numbers in MCCGenerator, or in the target plugin that you're modulating (or both) when things break? I know in the past I've wasted a lot of time with the AU version of MCCGenerator in PatchWork, and have had more luck switching to the old VST2 version of the plugin.tonycore wrote: Mon Mar 13, 2023 1:31 am So I can get that to work, but only with absolute default settings. As soon as I begin to change anything, the CC number, control assignments...everything stops working.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6345 posts since 8 Sep, 2004 from Paris (France)
Many manufacturers have indeed not implemented MIDI output for Audio Units (hosts and plug-ins). It is a part of the specification that is not much documented. You usually cannot go wrong with VST2 though.drohnee wrote: Mon Mar 13, 2023 2:08 am Are you changing CC numbers in MCCGenerator, or in the target plugin that you're modulating (or both) when things break? I know in the past I've wasted a lot of time with the AU version of MCCGenerator in PatchWork, and have had more luck switching to the old VST2 version of the plugin.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6345 posts since 8 Sep, 2004 from Paris (France)
Once you change the MIDI CCs, have you tried to simply "MIDI learn" in the target plug-in?tonycore wrote: Mon Mar 13, 2023 1:31 am So I can get that to work, but only with absolute default settings. As soon as I begin to change anything, the CC number, control assignments...everything stops working.