MOTUnation.com

Wondering if anyone else has had this problem or has found a reasonable workaround:

I have projects that heavily leverage NI Komplete synths as VIs. I have some Patch Changes I've embedded into the MIDI data. For some of these synths (particularly Massive), these changes don't always seem to work on playback. Some do, some don't. FWIW, they seem to be worse when I Bounce to Disk.

Is it possible that these patch changes are the lowest priority events to DP when taxed, or Massive is churning so hard it doesn't have time to make the patch change?

I have a pretty beefed up machine (see signature), but I'll look at its Performance indicators when this happens.

I'm on the verge of printing the audio from these synths and saying to hell with playing them as VIs, but I thought I'd ask.

Regards,

What are your patch change numbers? As far as I know, you can only specify bank and then
patch 1-127. That doesn't work if the VI has close to 2000 patches organized by category instead of banks.

David,

Thanks for responding. I'm just opening the MIDI event viewer window for the MIDI track controlling the NI instrument (in this case, Massive). I'm inserting a patch change and specifying a number (typically just between 1 and 16) corresponding to the number of a patch as it appears in the program list.

Sometimes the patch change works, sometimes not. No apparent pattern, and the problem is noticeably worse when doing Bounce to Disk. It's not like the patch change doesn't work. It's just inconsistent and doesn't seem to be following a discernible pattern.

It may be that I'm maxing out the demands of my machine, but with 16G RAM, a Quad Core i7 and a SSD, I'm not so sure, even with a project that has maybe 9 VIs, a couple instances of CPU hungry processors and a little audio.