Bristol_Jonesey

Why not? Autosave has bitten me more than once. Just get into the habit of hitting ctrl + s frequently

My current double album project runs to about 140 minutes. It's mostly audio with a small amount of midi.

Cakewalk by Bandlab nd Cakewalk Sonar are completely separate installations

C to A or A to C?

Do we know that for sure? Can't remember reading that anywhere. But I don't read everything.

Could be a sample rate mismatch, but four semitones is a bit drastic

Importing a track from a CD into Sonar will grab hold of the wav at 16bit 44.1KHz. By its very nature it will be lossless. It's at full CD resolution. There is no other software in play to convert it to anything else

If you're importing directly from a CD they are bound to be lossless

Easiest way by far

I would have thought 32Gb of RAM woul be enough to absolutely EAT any project. This is exactly what I've got and my CPU barely shows anything even when running a fully loaded 135 track Orchestral project.

Exactly what I do. Remember to route it directly to your main outs, bypassing any mastering Fx.

Rapture Pro includes all the old Dim Pro factory patches, so yes, you're covered.

Yep, launch DP in standalone as Administrator.

I would have simply put a volume envelope across the entire recording and drop it where necessary

Apart from Bandlab membership ?

Nope, they'll be perfectly safe. Remember, reinstalling CbB wil NOT reinstate Dim Pro - this was part of previous SONAR installations and never included with CbB

Have you ever hit F5 to refresh the DP Browser?

It would have been intersting to know if it happened with a track envelope as opposed to a clip

Thr first stage of successfully installing DP as a plugin is to configure it as a standalone first - this you seem to have done The next stage as Glenn says above is to scan your plugins, making sure the .dll is in a path that is scanned

what happens if you swap the clip automation for a track volume envelope?

No, the automation doesn't, but the audio will, and might cure it. Bit of a long shot but you never know

Sometimes, bouncing the clip to itself solves problems like this. Nothing to lose by trying it

Might be a good idea at this point to talk about your driver settings. What are they? What are your buffers set to?

Thank you John. I hope the others take this on board.

In that case I'd like to know what you mean by a "nag screen" if it isn't the one regarding activation?