Bryan Wilson

On 7/4/2021 at 2:27 PM, Glenn Stanton said:

you have to change the icon in the file, save it as a "normal" project file, then rename the extension to .cwt instead of .cwp. otherwise the image embedded will not change. if you open a .cwt file and a .cwp file you can see how the header of the file in the cwp contains a large MIME encoded image in the first part of the file, whereas the cwt files have the image embedded further into the file which is then used when you save the template-generated project as a cwp.

here's the sequence:

new (or existing project or project from a template you want to modify:

add your image

save as a "normal" project file

rename .CWP as .CWT

copy or move the file into the project templates folder

when you open the start screen and select new project, you should see the template with the image

if you want to change an existing image - use the RED X to remove then add a new image, remember to resave as CWP and RENAME to CWT

 

YES. THIS WORKED. YES.

On 5/13/2023 at 1:06 AM, Promidi said:

and sample buffer size?

Did you try real time export and/or turning off 64-bit Double Precision Engine (done in Preferences - Audio - Driver settings)

I am assuming you have disabled the NVIDIA audio drivers (done in Device Manager > system devices >  High Definition Audio Controller, right click, disable)

Tried all of this and it didn't work. I actually pinpointed my trouble back to changing the default project sampling resolution from 48KHz to 44.1KHz. In that time, I opened several projects that had already been started in 48KHz resolution, and I heard my sound interface "clicking" as it changed to 48KHz from the new default 44.1KHz that Cakewalk opened with.

This issue has occurred with only the files that I opened while I had changed the default sampling resolution. I changed it back shortly after running into this issue and have had no problems with files I've created and/or opened with the resolution back at the original 48KHz.

On 5/14/2023 at 9:07 AM, JohnnyV said:

It’s always a plug in . There’s been no change to export for a long while. Even the warning tells me it was probably a plug in. Did it generate a crash dump. Send it to Cakewalk. 

To JohnnyV's point: it is a plugin. I saved a copy of the one of the problem project's and deleted every plugin in the project. Attempted an export.

It worked.

Went back and deleted each individual plugin one by one to find the culprit.

Deleted all Fab Filter Pro-Q 3 instances: Export failed.
Restart Cakewalk.
Deleted PSP Stereo Controller: Exported failed.
Restart Cakewalk.
Deleted iZotope Ozone 3: Export failed.
Restart Cakewalk.
Deleted iZotope Ozone 10 Maximizer: Export failed.
Restart Cakewalk.
Deleted Waves C1 Gate Stereo: SUCCESS.

It was Waves. Not the 20 year old DX or VST 2 plugins I'm using. It was freaking Waves. If I had to guess, the sampling resolution change made the existing instance that had been inserted at one resolution go wonky when I opened the Cakewalk in a new one.

Deleting the instance and reinserting it solved the problem. Thank you guys so much for your help!

1 hour ago, Promidi said:

What are your PC Specs? (see my signature for example).

My PC is configured as per my signature and every export using CbB 2022.11 has been successful.

I am assuming latest drivers, plugin versions and Windows fully patched.

Also what sample rate, bit depth and buffer size are you using?  have you tried larger buffer sizes?

Have you tried real time export.  Tried turning off 64-bit Double Precision Engine, seeing if that changes anything?

I'm running Windows 10 Home 64bit
Version 10.0.19045 Build 19045
Dell XPS 8930
Intel Core i9-9900 @ 3.10GHz, 3096Mhz, 8 Cores
32GB RAM

Focusrite Scarlett 18i8. ASIO mode. 24bit 48khz

NVIDIA GeForce GTX 1660 Ti

I'd seen the 2022.11 update prompt for the last 6 months, but never updated. I'd been running 2022.09 successfully and didn't have any problems with it in my workflows. But I finally decided to update it and I've been having some trouble with export.

At present, I'm revisiting tracks mixed 1-2 years ago (natively in Cakewalk) and remastering them. All effects are added on the master output bus before being exported. Because I came up with an FX chain that served all my needs, I turned it into an FX Chain Preset and simply import it into the master bus. I tweak the settings in the active plugins, bypass the ones that are only present for stereo or loudness monitoring, then export. This had been working great with all of my projects, even those that are over 2 years old. There's a long delay when I first add an FX Chain Preset, almost as if Cakewalk is crashing, but once it loads it usually works great. No issues with extracting the plugins from the preset, moving plugins around in the bus, or exporting audio into any format.

Then I downloaded v2022.11. The update goes through smoothly. The next project file I open, I spend about 1hr remastering as I've outlined above. Once I'm done, I attempt to export. Except I get the following error message when I do:

Quote

An unknown error occurred during processing, possibly caused by an invalid parameter.

I click "OK" and try again.

Quote

An internal error occurred while processing the mixdown. The operation was unsuccessful.

Catastrophic failure.

Ouch. And after that catastrophic failure, I can no longer play the file at all. It gives me about 1 millisecond of output on the meters before it stops itself. The transport bar never moves and neither does the 'Now' time. Once I close the project file, Sonar gives me the crash and dump error message. The text file it created is attached.

So I of course restart the program. No change.

I restart my computer several times. No change.

Then I came across the rollback feature on the forums. Handy! So I found the rollback link in the 11.2022 update log. Rolled back to 09.2022.

Started up the file that had given me trouble, and...same error.

Fortunately, I have all my project files inside of Dropbox with some extra features. So I can restore an older version of the exact same file, which I choose to do in this case. So I roll it back to 2021, before I started tampering with it again. Opened the file, pressed play. It works. Exported the entire file as-is with no added plugins or FX Chains. It works. I add the mastering FX Chain Preset. Play and export both work.

Then I extract the FX Chain Preset so all the plugins populate in the bus fx bin. Try to export, then start getting the error messages and crash.

So I rollback to the untouched version of the file again.

In every attempt, if I add the FX Chain Preset but don't attempt to delete or extract any plugins, the file will continue to play and export perfectly fine. But once I add the FX Chain Preset, even if I don't extract it - I deleted an older plugin from the bus that wasn't part of the fx chain - I get the error messages and crash if I alter the bus plugins in any way.  Adding the FX Chain Preset is definitely the trigger.

Any ideas on how to resolve? I've been so involved with this process that I haven't checked to see if it's going to affect other projects yet. I suppose I could add the plugins one by one, even if it wastes a lot of my time, but at least could complete the remaster. Besides that, has anybody else had this issue? Was this a problem with update 11.2022? Is there something I need to download to resolve this?

_05112023_144539.txt