gmp

26 minutes ago, scook said:

SONAR - Yes, it may be from anywhere.

CbB - No, ALL versions except the most recently installed version should be run from Launchpad.

Make sure to run Quick Copy from Launchpad anytime prior to installing a newer release in order to have the older version available after running the installer.

I understand why  I should use Launchpad with 2019.09 and any later versions, because of CW130auto.dll. And I see only 2 CW130auto.dll in the "sub" folder. So how is Launchpad handling 2019.07 and all earlier versions of CbB? It seems like it would need all those versions of CW130auto.dll in the sub folder also.

4 hours ago, scook said:

yes

 

So just for clarity. From now on I can use the desktop icons and not Launchpad for opening all old Platinum and all CbB from 2019.07 and earlier. For all CbB from 2019.09 I should use Launchpad to open them. And before installing each new CbB version I should use "quick copy" to save the current version and then install the newest version. Is this all correct?

I copied it and now CbB 2019-09 works in Launchpad - thanks for the great tip.

So currently that's the only file change? Yet there may be other different file changes in the future?

57 minutes ago, scook said:

Any version of SONAR may be run from inside or outside Launchpad at any time. 32bit/64bit it does not matter.

The tricky part is running versions of CbB older than the most recently installed version outside of Launchpad. Outside of Launchpad copies of CbB older than 2019-09 will work properly after 2019-09 (or newer) is installed. This is because up until CbB 2019-09 the program would run OK with newer versions of CW130Auto.dll. Changes were made to the dll which broke compatibility with older versions. To address this, starting with 2019-09 Launchpad keeps copies of the dll and insures CbB always uses the correct version.

Because you installed 2019-11 prior to running Launchpad, there is no 2019-09 version of CW130Auto.dll so, Launchpad will not use that version of CbB.

Will 2019-09 run from the command line...maybe. Is it safe? I don't know and that is why Launchpad throws an error. There may be problems with automation.

I like to make the Quick Copy right after a new version is installed. It is easier for me to remember to do it then rather than wait for the next update. But as long as the Quick Copy of the currently installed version is made some time prior to the next update, you will be OK.

 

I found cw130Auto.dll dated 10/11/19  on my backup HD. It resides in  C:\Program Files\Cakewalk\Shared Utilities. Is that the only file that causes the problem? If so I'd assume I can temporarily move the current  cw130Auto.dll to a temp folder and then move the 10/11/19 cw130Auto.dll in it's place in that folder and then 2019.09 would run just fine. Right?

Very impressive work on Launchpad, Steve. I'm sure in your situation in this Forum you find the multiple features very helpful. 

IN my situation I would assume I can just use the very basic features. I quite often need to open 32 bit Platinum 2016.08 to revisit old projects that use 32 bit plugins that won't load in 64 bit CbB. As far me opening older versions of CbB, I only do that if I have a problem with the current version and suspect a bug, like I did in the post your responded to. 

So in moving forward I'm wondering what my best approach is. Should I always open 32 bit Platinum from within Launchpad? AS you suggested I checked "Restore CW130auto.dll on exit". If I didn't open it within Launchpad, what kind of problems would I run into? Maybe not being able to load a plugin because of changes in the Shared Plugins folder?

When I installed 2019.11 Friday night, I wasn't aware of Launchpad or any of this, but I do still have the Shared Plugins folder intact from before Friday's install. Should I save that permanently? I tried opening 2019.09 from Launchpad and got the error message "no usable CW130auto.dll for this version. Or since this is so new should I not worry about 2019.09 and just open it using my desktop icon?

Next time I update to a new CbB, I'll use "quick copy" to make a copy of the Cakewalk Core folder and then proceed with the new update. And when I want to open a CbB that is later 2019.11, I assume I need to do it from Launchpad. Whereas any version from 2019.07 and earlier I can just click on my desktop shortcut and not worry with Launchpad. Is that right?

For Launchpad to work in my situation with future CbB updates, is this all I need to do?

scook, you said "If you start using Launchpad to save versions, it should always be used to run CbB. This way the version is set up properly."

 Once I set it up can I double click a CWP file to open CbB like I currently do? Or can I double click a desktop icon and open CbB to my template? 

43 minutes ago, scook said:

I am not sure a simple copy of the CbB program folder still works and no longer recommend the practice. As a result of changes made in 2019-09, I modified my tool to keep track of more than the program folder. My tool thread is here.

Thanks for the info. I installed Cakewalk Launchpad and will start using it for saving old versions - thanks

 I save a copy of the cakewalk folder and name it - cakewalk 2019 09. And then make a shortcut to cakewalk.exe and put it on my desktop. The folder is only about 147 megs. I have most of the versions of CbB saved in this way just in case I run into a bug or problem. scook taught me this trick.

Maybe the strange behavior I encountered is a one off. If it happens again, we can dig into it further.  Or if someone else reports it, then we know it's a bug.

I just installed 2019.11 and the first song I loaded had some problems. First I copied the lead and harmony vocal tracks to 2 new tracks, which were setup for an Aux Track mix. I then copied 1 word from a previous vocal and pasted it to the final vocal and that one word was there but yet it was muted. I thought the clip was muted and muted it and unmuted it to no avail. Then I redid the paste and this time it worked. I chalked this up to a weird anomaly. 

A few minutes later, my harmony vocal track, which was working before I think, was muted. I again tried muting and unmuting the clip to no avail. I then thought this must be a new bug, so I saved the song and opened it in 2019.09 and the harmony track was not muted. I finished my work and then reopened 2019.11 and the same song and the track was not muted This time when I opened 2019.11 I got this "Welcome to Bandlab" window which I definitely did not see the first time I opened CbB. I went though and checked all the settings and they were fine.

I'm done with this song so I won't be working on it anymore, unless Bandlab wants a bun or for me to try something. Has anyone else had any strange muting like this? I've never seen this with any version of CbB or Platinum.

Open a song that has this bug happening and on the midi track in the track pane, check the input, output, and channel and see if those are correct. I have something similar possibly even the same thing happen pretty often, but the fix is easy it's always one of those things I listed above.

I always attributed the cause to me going to midi devices and making changes. IN my case I use Studiomix to control automation with flying faders and sometimes I use the faders to control the drawbars on my B3 organ soft synth. So I change my midi devices to use LoopMidi as a midi device.

The other thing I do is fairly often I open CbB using remote desktop when I'm downstairs with the family and I may open a song and export a mix for someone. Using remote desktop if you go to Preferences Midi Devices you'll notice none are there. Midi doesn't work with remote desktop. So this messes up those I listed above, if you save the song.

Does any of this relate to your problem?

Thanks scook, I followed your instructions and it worked perfectly. I now have the 64 bit Lexicon Pantheon reverb and when I open an old 32 bit project in CbB the reverb does load just like Noel said.

Does anyone know about this old plugin - Cakewalk FX Chorus? I used that as part of my template and have it in a lot of old projects and it won't load with CbB. Is there a 64 bit version of it?

I have tons of old projects that used the 32 bit Lexicon Pantheon reverb. When I open them in CbB it can't find the Lexicon Pantheon reverb, because it's 32 bit and CbB is 64 bit. If I install the 64 bit Lexicon Pantheon reverb, will it work with CbB? 

And when I open an old project is there a way for it to use the 64 bit Lexicon Pantheon reverb? Or would I have to manually replace the 32 bit with the 64 bit Lexicon Pantheon reverb in the FX rack? Currently what I do with those old projects is to open Platinum 32 bit and then everything works.

6 hours ago, Noel Borthwick said:

This issue has now been fixed for the 09 release. Thanks for your help sending a repro project file.
BTW you can locally fix the issue by temporarily deleting and undoing the deletion of the Aux track.

That's pretty interesting. So since I'm using 2017.07 that deleting and undoing the deletion of the Aux track, does that in effect bring the Aux Track up to date. In other words was the problem with the Aux Track because I originally created it using an older version of CbB and now the newest version 2017.07 doesn't have this problem when creating a new Aux Track?

The reason I ask is someone tried to test this by creating a new Aux Track in one of his projects instead of downloading my BUN and he wasn't able to replicate the bug.

Still this delete and undo is a pretty nice workaround. Do you think this will work on my template that has an Aux Track? And then new songs I create using the template will no longer have this bug?

Thanks again for your super attentive laser focus on making CbB the best. I knew when Bandlab got you they'd have a gem with your long years of experience with Cakewalk ..

53 minutes ago, John said:

Chuck has one heck of a good memory and is downright helpful. One of the best mods on the this forum!

I sure agree and agree also that we have some excellent mods and helpful people on this forum

7 hours ago, Chuck E Baby said:

I downloaded the bundle file this morning (all 554MB)  but haven't had a chance to load it up yet. If Noel is good with it and knows whats going on I see no reason for me to trouble shoot this. Im just glad it was able to be verified. Problems like this are sometimes very difficult to nail down and only come up in 0.1% of the time.

Don't waste any time troubleshooting since Noel is already on top of it, but thank fro being wiling. And I must say I have a great debt of gratitude to you for pointing me to that obscure post over a year ago that fortunately you remembered. This gave me the clue to try turning on and off input echo.

 You've helped solve a year or so of frustration and troubleshooting, trying to get to the bottom on all 3 of these issues - the dropouts at 2:08, dropouts at 4:17 and the strange dropouts I'd get even when I left the computer for 5 min or more. So this is  a big relief to get this behind me. Thanks for all the excellent help you give in this forum 

Thanks David. Noel tried it and found out it's a buffer problem as he expected. He said he hopes to fix it. Here's his post

Thanks Noel, I guess you also saw David Baay's post where he tried the bun and had a dropout also.  Let us know when it's fixed

6 hours ago, Noel Borthwick said:

@gmpcan you send me a simple project that has the issue? We'll look into it.

Delete all the unnecessary tracks and synths and just keep the tracks required to repro the problem.

Here's the bun, let me know how it does

https://onedrive.live.com/?id=C256E2DAE26B22A5!105&cid=C256E2DAE26B22A5

6 hours ago, Noel Borthwick said:

The aux track defaulting to a hardware out is completely normal. It can't assign to the default bus since it would create a feedback loop.
I tried recording the aux track for 10 minutes with both input echo off and on and could not get any dropout.
Do you have plugins with delay in your project?
It will be easier if you list steps from the start to reproduce this or supply supply a simple project where this happens. The logic is very dependent on the routing of a project so its important to know exactly how its set up.

Based on the symptoms my theory is some internal buffer is overflowing leading to the dropout as a result of the overflow fuse firing. 

Here's the bun, let me know how it does

https://onedrive.live.com/?id=C256E2DAE26B22A5!105&cid=C256E2DAE26B22A5

45 minutes ago, Noel Borthwick said:

The aux track defaulting to a hardware out is completely normal. It can't assign to the default bus since it would create a feedback loop.
I tried recording the aux track for 10 minutes with both input echo off and on and could not get any dropout.
Do you have plugins with delay in your project?
It will be easier if you list steps from the start to reproduce this or supply supply a simple project where this happens. The logic is very dependent on the routing of a project so its important to know exactly how its set up.

Based on the symptoms my theory is some internal buffer is overflowing leading to the dropout as a result of the overflow fuse firing. 

Nothing unusual, no delay active, but 1 is on Aux send 3

lot's of plugins on blank tracks, almost none turned on,

-  I'll see if I can send you a bun later tonight

 The Aux Track which shows up in the Track Pane (not Bus pane) has the output going to one of my sound card outs, not back to the bus pane master bus. Go ahead and try again, if you get no dropout at 4:07 with the input echo off, then maybe it's fixed and I simply need to delete it in my template and create a new one. Thanks for your help with testing 

Thank you Chuck E Baby for the link below to the similar problem involving Aux Tracks. This enabled me to fix my dropout problem

Thank you Chuck E Baby for the link below to the similar problem involving Aux Tracks. This enabled me to fix my dropout problem

  In my previous post was was incorrect - the problem was not solved and cropped up again. I finally did fix it and it has to do with having an Aux Track input echo turned off. If it's "on" there is no dropout  Here's my new post explaining this and warning others that may have this problem. 

I've had a few posts trying to solve some dropout problems I've had for about a year. It turns out it's caused by turning the Input Echo on an Aux Track off. On my template I have an Aux Track and the input echo button is on. But I also use input echo to trigger 2 tracks at the same time -  a piano and a bass. That's also set to "on" in my template. 

At times I want to turn the input echo off, especially i I cloned those tracks and have several now "on". So I always use the global icon in the Control Bar to turn off all input echo buttons, unfortunately it also turns off the input echo button on the Aux Track.

Here how you create an Aux Track: 
right click bus in bus pane - Insert send - choose new Aux Track
Now look in the track pane and you see a new track named - Aux 1. This is the track that the Input Echo must be set to "on" otherwise there will be a recording dropout at 2:08 or 4:17

This has also fixed a long standing problem I've had with when I leave CbB and then come back about 5 min later I see a dropout message at the lower bottom right. Last night I tested it with a stopwatch and the dropout comes right at 4:17 every time, if the Input Echo button is off. If it's on, I never get that dropout. So this has solved 2 long standing mysteries for me.

The bottom line is Aux Tracks are great, as long as you understand this strange little quirk. This happens regardless of whether you're actually using the Aux Track in your project. If it's there in the Track Pane then it can cause this problem.