Greg Wynn

My rollback surprisingly worked fine.

Ya, I saw the “your computer isn’t ready for this” (paraphrased) message this morning. Pretty cool I just built it in January and it’s an i9 9900, 32 gig 3400 ram, all latest and greatest good stuff with the exception of my interface. i do wonder if it’s freaking out about my MOTU Track16 usb but I’m not gonna mess with it as it’s been flawless for years. Well done, Microsoft. Take the rest of the day....

Failed twice for me as well. So strange...

Just hit that as well. Freaked me out but I think the message is in error.

Thank you !

Agreed completely. I’ve been running on “3” for hours tonight with no issues. It used to cause weird glitches. That’s on an i9 9900k with 32 gig DDR3400. Thank you !

Thanh YOU ! You’ve done the difficult work.

Donation sent - thank you !

Thank you guys !

Love it !

Thank you !!!!

Tracked for the last 7 hours or so. No issues and was great ! thx bakers !

Good luck, man! it was seamless for me.

hehehe. I was thinking how much work there would be for the outstanding theme developers like yourself.

looks great ! ill have a chance to check it out tomorrow. You’ve done a great job with these and I’ve been using one of your themes for a long time now (forgot the name right now). Thank you for your work !

I have the same specs to some degree (i9-9900KF, 32GB RAM. Win 10) and haven’t had any of those issues. i just finished building it a few weeks ago and have been amazed by its speed. The boot drive is an M2 (also contains Sonar) and most of my samples (a LOT of Superior Drummer stuff) are on another M2. Are you using an HDD or SSD/M2 ?

Thank you !!

Gave it a whirl last night with the new scheduler setting and so far so good. It’ll get a far better workout this morning. Thank you Bakers for all that you do !

Thank you, Noel. I’ll attempt to reproduce.

Hi Noel - thanks for your responses. All of the items listed below were post the .11 release with the hotfix (version 63 I believe). For some background I have been using Cakewalk since Pro Audio days (2002 ?) and I’d like to think I know my way around fairly well Ripple Edit being enabled - While I guess it would be possible I enabled it by accident it would be the first time I’d ever done that. ALL audio inputs and outputs reassigned - this was a surprise.Right after I Installed the base (non hotfix) .11 release I found all of my inputs and outputs reassigned. Did you save the exports that don't open in WaveLab and can you open the same wave file in CbB itself? I did not save it (I should have) and did not attempt to open it in CbB. Were you doing a realtime export? Indeed. By habit I’ve been doing that for years to listen to the export as it’s happening. Format and bit depth - wav and 24. Just as I’ve been doing for over a decade. What audio interface are you using, what driver mode and did you get an engine stop message? MOTU Track16 (it’s been a workhorse), ASIO, I did get some akin to “Audio Engine Stopped unexpectantly” NOTE - I did do some work last night and everything worked fine EXCEPT every once in a while there were some clicks and crackles. I can replicate them in track view sometimes by clicking anywhere while the audio engine is engaged. Fairly loud too. If there is any other way I can assist please let me know.

Just ran into another “gotcha”. By default it looks like ripple editing is enabled with the latest update. I only have ever used it to check it out way back when it was first introduced by never since. Today I did some editing of an audio track that has some silence at the end of it and I deleted it. I then started the project from the beginning and listened to it and as if by magic a bunch of my tracks were WAY out of alignment. The culprit ? Yep, you guess it. Freaking ripple edit was enabled. Took me a little while to figure that out... Anyway hopefully this helps someone.

Glad you found the issue !

Check your outputs and see if they were reassigned during the update. ALL of my inputs and outputs seemed randomly reassigned. SO damned frustrating.....

Here’s a new one I’ve never seen before. Last night did a lot of work and encountered too many issues to list right now (but will later). I’ve been a user since Pro Audio days and I don’t know what’s going on with the latest version of CbB (WITH the hotfix candidate installed) but it’s clear something is sick. Check this out. Exported a project to wav with audio enabled so I could listen to it one last time. Export went fine and then opened the resultant wav in Wavelab. Here is where things got bizarre. A dialogue box opened in Wavelab that said something to the effect that “the wav file you are attempting to open is not a valid file and Wavelab is closing to prevent damage”. Say WHAT ?? I’ve never seen that either and have been using WL also for 15 years. So I reaccomplished the export thinking something must have glitched. SAME bizarre error in WL. Now I’m less that happy as I’d been encountering audio engine stops randomly (NEVER had that before), garbled sections of audio tracks that were acoustic guitar and were recorded properly gain staged, non-normal split clip behavior on audio tracks, on and on. By 2AM this morning I’d had enough of a very long frustrating night. The only thing that changed (besides the .11 version and resultant Hotfix candidate) was that I’ve started using Kazrog True Iron on my audio tracks. Are there any known issues with it ? By the way - this morning the project exported fine and opened properly in Wavelab. And I’d changed nothing.

Just a general “thank you” to the Bakers not just for this update and hot fix but for keeping my favorite DAW well alive and kickin’. I’ve been onboard since Pro Audio (I think version 9 ?) in 2001 or so. Thanks guys !