Andres Medina

See the pic and the video -

I would contact Vienna...

They have a very good customer service.

Double check your Ilok setup.

---

Is your cloud session active?

Remember, Ilok needs to be connected to the internet.

Oh, you mean you are soloing take lanes... that's a different scenario.

If you already selected your comp lanes, then the dim solo should work in relation to the other tracks, not to the take lanes.

I'm not 100% sure, but I guess the dim solo does not apply to soloing a lane.

4 hours ago, charles kasler said:

Got it, thanks. I didn't know the order mattered.

Well, not really... you could solo a track and then engage dim solo and it should work too.

But for the purpose of troubleshooting , I thought it was a good idea. jeje 

Be sure to engage dim solo button on the control bar, THEN solo the target track. All other tracks should lower the volume to provide context for your soloe'd track.

Be aware that you can delete the dead space inside Melodyne (along with any unwanted noises).

I used to clean up the clips before applying Melodyne, but nowadays I find it redundant, as all editing can be done within Melodyne.

My workflow for vocals is basically: record (using comp) - create the master comp track - duplicate this composite track (for safety reasons) - apply melodyne to the whole track - edit, edit, edit.... - render the edited track.

But this is a workflow that suits my needs. I'm sure everyone develop a prefered workflow that serves them well.

For complex recordings, you can even apply melodyne to assorted clips inside the comp track to adjust timing, etc, before commiting to a master track.

On 1/16/2024 at 4:29 PM, jono grant said:

Andres, with the H264, do you get the Cakewalk issue where it adds some padding at the file beginning, resulting in your exported audio being a little late? (Not late within Cakewalk but late when you export for other platforms) Curious, I've had that issue with any QT or MP4 video since version post Sonar 8.

Good to know that H264 might have less CPU load 

The thing is, as many others on the forum point out, I rely on an external video editor. I had so many problems exporting from within CW, that I abandoned this idea.

I use Adobe Premiere, but there are plenty of video editors, some of them free, that allow you to just import your finished audio and re export the whole video+audio in any format, resolution, etc. I also re export using H264 codec. So far, no problems at all with clients.

Hope this helps!

Some Virtual Instruments have a dedicated configuration option to do this (change the Hz from standard 440 to 420)

Don't know yours, but worth check the manual or contact the manufacturer?

I would add that Melodyne works best with high buffer settings (512-1024)

I have had this error before, and in my case it was due to a faulty plugin: the one I had installed when saved the project was updated with a newer version, that CW was not able to update. I tried everything, and gave up-

My workaround was to use the newer version, and copy the midi tracks to the new (updated) instrument. 

About video file: I settled in H264 codec, after many trials an error tests.

Very good resolution to work with while composing, and low load in the CPU.

...or in English (Help menu):

Sign out, then sign in again. That's it -

I got the activation toast today. Funny thing, clicking the toast notification does nothing. Had to logout-login within the Help menu.

Also, be sure automation READ is enabled.

Up and running with both versions-

Thanks all!

I thought CA20 was lost for ever for me -

30 minutes ago, Glenn Stanton said:

the CA-2A is. and you can find your product code in your product list.

Thanks!

4 hours ago, Glenn Stanton said:

interesting. the opposite of my system until i just downloaded the updated PC2A. maybe re-install the CA-2A? 

Good idea... it's downloadable from the old Command Center, right?

CA 2A extremely unusable (crashes badly), at least in my system.

PC2A very good, but as said, no sidechaining.

You can move track content along with the arranger tracks: just enable the corresponding button:

... and remember that you can select all OR a some of your arranger sections to create markers, AND viceversa.

An alternate way to organize (option 1)

Keep everything as it is, as you can lose backwards compatibility with older projects if you delete those plugins, AND use the exclude option to get out of view your older plugins.

You won't have to move plugins in C:/ or anything.

---

An alternate way to organize (option 2)

Organize your plugins in a meaningful way outside CW, in your hard disk - i.e I created a "Plugins" folder in C:/ to consolidate all plugins in one place (when possible)

Rescan plugins in CW.

... because the original wave file was timestamped in Mac - usually files coming from Pro Tools default to this setting: it provides a SMPTE code embedded in the audio file, for syncing purposes. 

If Cakewalk has activated the "Always Import Broadcast Waves at Their Timestamps", then the clip will land in the stamped SMPTE.

Deactivating it inseide Cakewalk is the easiest way to avoid your problem, as David pointed out.

In Track View, press D (it will open the console view, and there you will find the master volume fader)

You can do this outside event list:

• Select all your tracks in track view 
• Use menu Edit/Select/By Filter ; check the appropriate boxes; Enter
• All your unwanted controllers/data will be erased