DP 11.11 released

[bayswater]

This release didn't fix the issue with not being able to edit continuous cc in the MIDI editor with the pencil tool (if the cc data was input from a MIDI channel other than channel 1). The MOTU techs were able to acknowledge and reproduce it, but I guess there wasn't time to fix it in this release.

The best workaround is still to export the affected tracks as a MIDI file, and re-import/replace them. Then the pencil works normally.

I’ve read this and the earlier comments a few times, but I’m confused. Looks like DP can’t deal with MIDI date it generated, but if you export and import it, somehow, that turns it into data it can deal with. I guess that’s good for this particular workaround but seems to me if DP export and imports data, the result should be identical. If it didn’t work before the export/import, it shouldn’t work after. And vicey voo. No?

[mikehalloran]

I had to force-quit after saving and closing my project today. I expect this to work itself out—such things often do.

[HCMarkus]

@HCMarkus _ Update for Guitar Rig 6 in version 6.2.3. _

Thanks, but I'm still on Komplete 12 (hence Guitar Rig 5, not 6); I'm not planning to update any NI stuff until they get further along with porting their plugins to Apple Silicon Native.

[Killahurts]

This release didn't fix the issue with not being able to edit continuous cc in the MIDI editor with the pencil tool (if the cc data was input from a MIDI channel other than channel 1). The MOTU techs were able to acknowledge and reproduce it, but I guess there wasn't time to fix it in this release.

The best workaround is still to export the affected tracks as a MIDI file, and re-import/replace them. Then the pencil works normally.

I’ve read this and the earlier comments a few times, but I’m confused. Looks like DP can’t deal with MIDI date it generated, but if you export and import it, somehow, that turns it into data it can deal with. I guess that’s good for this particular workaround but seems to me if DP export and imports data, the result should be identical. If it didn’t work before the export/import, it shouldn’t work after. And vicey voo. No?

I know, it's hard to explain.. DP11 (I think) introduced multi-channel MIDI recording on a single track. But you can't edit the CC data that was recorded from any channel except channel 1.

e.g. If I record cc11 data from channel 2 of a MIDI controller interface into a MIDI track, when I go to edit the cc data in the MIDI editor, I can see it, but any attempt to edit it creates another cc11 "ghost" stream on channel 1, and that is the only one you can edit. There is no way to get into this internal channeling, to put the data where it belongs for editing. Exporting as MIDI file, then reimporting back apparently removes the DP channeling and puts the cc11 data onto a single-channel (standard) MIDI track, using channel 1 (where the notes would also be, if there were any). If I record cc data from channel 1 of the interface to begin with, I have no problems, but to record all 10 of my pedals at the same time, I have to input from different MIDI channels.

[mikehalloran]

@HCMarkus _ Update for Guitar Rig 6 in version 6.2.3. _

Thanks, but I'm still on Komplete 12 (hence Guitar Rig 5, not 6); I'm not planning to update any NI stuff until they get further along with porting their plugins to Apple Silicon Native.

NI Upgrades are half price through June 30. Sometimes, they’ll do it again in November but that’s never a given with them.
https://www.native-instruments.com/en/ ... mplete-13/

[bayswater]

Thanks Killahurts. I get it now.

[HCMarkus]

@HCMarkus _ Update for Guitar Rig 6 in version 6.2.3. _

Thanks, but I'm still on Komplete 12 (hence Guitar Rig 5, not 6); I'm not planning to update any NI stuff until they get further along with porting their plugins to Apple Silicon Native.

NI Upgrades are half price through June 30. Sometimes, they’ll do it again in November but that’s never a given with them.
https://www.native-instruments.com/en/ ... mplete-13/

Thanks Mike. Yes, I've been aware can upgrade my Komplete Ultimate package for $250, great, except I don't really need anything new and the only AS-Native component in K13 is Kontakt, which I already have. And I can see NI releasing K14 with full AS-Native compatibility and requiring a paid update then. It has the potential to be NI's Compact Disc (remember when we had to re-buy all of our albums when CDs came out?). I'm not in the mood to give NI any more money until they get further along with the AS port.

As I've noted, if I take my time with Guitar Rig 5, it seems to work fine under Rosetta2. I can't use FM8 or Absynth, but I have Arturia's DX7 (and so many more)... resources are clearly NOT lacking!

[mikehalloran]

Thanks, but I'm still on Komplete 12 (hence Guitar Rig 5, not 6); I'm not planning to update any NI stuff until they get further along with porting their plugins to Apple Silicon Native.

NI Upgrades are half price through June 30. Sometimes, they’ll do it again in November but that’s never a given with them.
https://www.native-instruments.com/en/ ... mplete-13/

Thanks Mike. Yes, I've been aware can upgrade my Komplete Ultimate package for $250, great, except I don't really need anything new and the only AS-Native component in K13 is Kontakt, which I already have. And I can see NI releasing K14 with full AS-Native compatibility and requiring a paid update then. It has the potential to be NI's Compact Disc (remember when we had to re-buy all of our albums when CDs came out?). I'm not in the mood to give NI any more money until they get further along with the AS port.

As I've noted, if I take my time with Guitar Rig 5, it seems to work fine under Rosetta2. I can't use FM8 or Absynth, but I have Arturia's DX7 (and so many more)... resources are clearly NOT lacking!

Point taken.

I suspect that Komplete Ultimate 14 will be when we see everything else upgraded to AS. NI has a nasty habit of not offering discounted upgrades for the first year and a half after a major version release. They certainly did that with 13.

If you don’t need it now, no reason not to wait.

[mhschmieder]

Strangely, I didn't get the notice until launching DP 11.1 tonight, even though I've used DP almost daily for the past few weeks.

As a result, I didn't scroll down far enough, thinking the release was today, and made a now-deleted duplicate post.

I don't see the MPE bug on the list of fixed issues. Not affected by it personally, but a lot of people are, and it has its own topic.

[LaudMusic]

Anyone else here notice CPU spiking after the update? I'm getting them all the time. The version prior to 11.11 was rock solid. Now it's a mess. I only have a few VIs running...it's nuts and frustrating.

I posted on the Facebook group and other are also frustrated with this new development. I even upped my buffer size, which worked for a few, then back to spiking and crackling.

I always monitor CPU and Memory usage and it's not use any swap memory, etc.

MacBook Pro 14"
M1Max
64GB
TB4 RAID for VI libraries (throughput ~2880)
Motu M4

[HCMarkus]

Anyone else here notice CPU spiking after the update? I'm getting them all the time. The version prior to 11.11 was rock solid. Now it's a mess. I only have a few VIs running...it's nuts and frustrating.

I posted on the Facebook group and other are also frustrated with this new development. I even upped my buffer size, which worked for a few, then back to spiking and crackling.

I always monitor CPU and Memory usage and it's not use any swap memory, etc.

MacBook Pro 14"
M1Max
64GB
TB4 RAID for VI libraries (throughput ~2880)
Motu M4

I'm not seeing this. Perhaps you should revert to 11.1; hopefully that will fix things for you and you can sit this release out. If it doesn't fix things for you, then something else is at the root of the issues.

Any other updates along the way? OS, Drivers, Plugins?

[mikehalloran]

Anyone else here notice CPU spiking after the update? I'm getting them all the time. The version prior to 11.11 was rock solid. Now it's a mess. I only have a few VIs running...it's nuts and frustrating.
…

Not seeing this at all even on my M1 MBAir.

What does the Activity Monitor say?

[mhschmieder]

Less crash-prone than before, and I'd say also better able to handle a gazillion plug-ins enabled at once, including heavy lifters.

[Michael Canavan]

There are at least 3-4 new bugs that aren’t there either, most noticeably the Novation MKIII launchpad control surface support is almost completely broken in 11.1, hopefully it’s fixed but not listed, be able to tell later tonight when I get back to the studio.

So this turned out to be a corrupted DP11 preference file, removing it got rid of the busted MKIII controls surface support!

[Phil O]

Anyone else here notice CPU spiking after the update? I'm getting them all the time. The version prior to 11.11 was rock solid. Now it's a mess. I only have a few VIs running...it's nuts and frustrating.

Sort of, I think.
So... I have this project I use for testing. It consists of 54 audio tracks with lots of cpu intensive plug-ins (in both a 48K version and a 96K version). I opened the 48K version in DP 11.11 and immediately got cpu spiking, but when I opened the 96K version it ran fine, which makes no sense to me. So something weird is going on. BTW, both of these project run fine in DP 11.1.

Your friendly neighborhood Phil