MCCGenerator no longer working in Patchwork

[tonycore]

Well, there's a whole "host" of problems here. Firstly, Melda's naming convention is to call the first cc generator in MCCGenerator "CC1" regardless of which controller it's assigned to - confusing, but not fatal.

I'm using BC Patchwork within Digital Performer. If I load an instance of MCCGenerator (VST2, yes, in all examples) into its own slot in a DP track (Instrument or Effect), it all works fine, and using Mod1 of MCCGen to modulate the value of the first controller within MCCGen works as expected. But if I load BC Patchwork in a slot, instrument or effect version, and then load MCCGenerator into Patchwork, Mod1 of MCCGen does nothing. In other words, MCCGenerator works in Digital Performer directly, but not within Patchwork.

I can't use the "learn" function in Patchwork because I suspect it's looking for an external control input. When I click "Learn" and try to wiggle the CC1 Value knob I just get an alert beep.

I'm not sure if BC supports Digital Performer (or Gig Performer, the other host I use). I doubt this would encourage them to add those...

[tonycore]

Ok, more experimenting.

I got it to work using MIDIShaper by cableguys, and then got some ore functionality out of MCCGenerator. But there is still some weirdness, whether it's with Melda or Digital Performer or Patchwork, I don't know. Some of it is there is some confusion around MIDI controls in Patchwork, local and global, and how they interact with MIDI coming from MIDI-generating plugins...at least, I am confused. But things are more or less working, in a way I can deal with. There are also issues with some other plugins and how they handle MIDI and parameter automation. Thanks to all who helped.

[Blue Cat Audio]

Well, there's a whole "host" of problems here. Firstly, Melda's naming convention is to call the first cc generator in MCCGenerator "CC1" regardless of which controller it's assigned to - confusing, but not fatal.

I'm using BC Patchwork within Digital Performer. If I load an instance of MCCGenerator (VST2, yes, in all examples) into its own slot in a DP track (Instrument or Effect), it all works fine, and using Mod1 of MCCGen to modulate the value of the first controller within MCCGen works as expected. But if I load BC Patchwork in a slot, instrument or effect version, and then load MCCGenerator into Patchwork, Mod1 of MCCGen does nothing. In other words, MCCGenerator works in Digital Performer directly, but not within Patchwork.

I can't use the "learn" function in Patchwork because I suspect it's looking for an external control input. When I click "Learn" and try to wiggle the CC1 Value knob I just get an alert beep.

I'm not sure if BC supports Digital Performer (or Gig Performer, the other host I use). I doubt this would encourage them to add those...

I am not sure I understand what you are trying to do, but if you want to reuse the MIDI controllers outside of PatchWork, have you selected "Host" as the output of the plug-ins that are supposed to produce MIDI messages?

[tonycore]

I was just comparing whether MCCGen works outside of Patchwork, which it does. It's only inside BC Patchwork that there's an issue.

I'm still encountering strange behavior with MCCGen and Patchwork. I'm going away for a couple weeks, when I get back i'll try to make a clear video showing the issue. Thank you for sticking with me.