The Digital Performer Tips Sheet

[Tritonemusic]

I'm not sure if this one is in here but...

When bouncing, if you switch to another application during the bounce, it goes _much_ faster - sometimes over twice as fast for me...

I wonder if it's because it takes the focus off of DP's graphics during the bounce...

[joelmusic]

I'm not sure if this one is in here but...

When bouncing, if you switch to another application during the bounce, it goes _much_ faster - sometimes over twice as fast for me...

I wonder if it's because it takes the focus off of DP's graphics during the bounce...

I'm not sure but it is sure a timesaver on those looooooong bounces!

[bayswater]

I'm not sure if this one is in here but...

When bouncing, if you switch to another application during the bounce, it goes _much_ faster - sometimes over twice as fast for me...

I wonder if it's because it takes the focus off of DP's graphics during the bounce...

I'm not sure but it is sure a timesaver on those looooooong bounces!

Whatever the reason, it should be reported to MOTU tech support. There's an obvious opportunity for improvement here.

[James Steele]

I'm not sure if this one is in here but...

When bouncing, if you switch to another application during the bounce, it goes _much_ faster - sometimes over twice as fast for me...

I wonder if it's because it takes the focus off of DP's graphics during the bounce...

Wow! Seriously? So the bounce happens *faster* when DP is in the background?? That sure seems counterintuitive!

[joelmusic]

I'm not sure if this one is in here but...

When bouncing, if you switch to another application during the bounce, it goes _much_ faster - sometimes over twice as fast for me...

I wonder if it's because it takes the focus off of DP's graphics during the bounce...

Wow! Seriously? So the bounce happens *faster* when DP is in the background?? That sure seems counterintuitive!

Yup - I know... I've been bouncing that way for years and just now thought to post it on the tips sheet... I just discovered it by accident one day - switched to another application and the 'bounce' dialogue window started flying!

[johnrude]

Thanks for the explaination.

[Amita579]

Thanks for a such a great contribution.

[MIDI Life Crisis]

Weird!

[HCMarkus]

Thought I'd put this here, in the Tips Sheet, maybe get this thread rolling again...

Stumbled across this the other day when updating an instance of Kontakt from K7 to K8 in my template. The K7 instance had an instrument loaded. When I used the DP drop down menu to change the instance to K8, I noted that the instrument that had been loaded in K7 was now loaded in K8.

I've confirmed this works with multiple instruments loaded in a single K8 instance, too.

As such, when updating instances of Kontakt, one can do so knowing any instruments loaded in K7 will still be there in K8. I've not tried disabling K7 in DP to see if K8 will automatically replace it.

Even better...

If you disable K7 in DP, when you open a project file with K7 instances, these instances will open in K8! I had read about this working in Cuebase, but didn't know if it would in DP. Tested it at the end of my day and it works!

I opened DP, disabled K7, and opened a project file that pre-dated K8. Enabled a K7 VI Track and the track opened with the instrument assignment intact in K8. I thus appears that one could, if one wishes, simply disable K7 in DP and projects will open running K8 in K7's place.

I didn't test with K6 or K5.

Edit: I should’ve mentioned I tested AU only

[stubbsonic]

That's good to know. I'm not sure if I've seen similar behavior from earlier versions of Kontakt.

When I open an older DP file, I'm asked about a few missing sound files, then asked about converting legacy instruments, then I'm warned about "obsolete (invalid)" MIDI events; CC0 and CC32, then I get an effect error which shows older version(s) of Pianoteq (-- but with no option to choose a later version).

It would be nice if there was a way (is there?) to have DP try to find a newer version Pianoteq in the same way it does for Kontakt 7/8.

[James Steele]

It would be nice if there was a way (is there?) to have DP try to find a newer version Pianoteq in the same way it does for Kontakt 7/8.

I suspect that capability requires some coding on the part of the plugin developer. Probably not something MOTU can do.

[Michael Canavan]

Thought I'd put this here, in the Tips Sheet, maybe get this thread rolling again...

Stumbled across this the other day when updating an instance of Kontakt from K7 to K8 in my template. The K7 instance had an instrument loaded. When I used the DP drop down menu to change the instance to K8, I noted that the instrument that had been loaded in K7 was now loaded in K8.

So this is likely due to the plugin internal reporting being just "Kontakt" not Kontakt 7 or 8. Pigments is up to 5 I bellieve and all versions open older songs no problem, with NI the name prevents it, but internally it must be able to read DP's patch settings for that track, i.e. it doesn't report to DP it's a new plugin.

You might recall that Kontakt 6 does not include "6" in the name, so NI must've decided on a compromise, i.e. if people want the older version to load they do nothing and if they want to update it doesn't kill your patch.

It's definitely a step in the right direction, as a Mac user I've suffered through endless amounts of hassle with Kontakt plugins over the years because Kontakt 3 didn't make it to Intel Mac, and 4 didn't make it to Apple Silicon etc.

[mikehalloran]

I didn't test with K6 or K5.

That would be interesting to see. Would have to have been created in 5.81 (64 bit) or later and be AU (Mac) or VST3 (Mac/Win) since VST2 and earlier are not supported in K 7/8.

[HCMarkus]

I should’ve mentioned I tested AU only