Steve Moddelmog

I got it to work by opening in SPLAT, deleting a take that wasn't used, and saving it. But I do have a backup of it in the "problem state." Do you want to take a look at it?

Thanks. I will be crying my eyes out, even though my wife has sternly instructed me not to blubber.

I did two things and the project is working in Bandlab Cakewalk again: (i) closed PRV that the project would always open to in Bandlab CW and then re-saved the lens, and (2) opened the project in SPLAT and deleted one take lane that was muted and not going to be used.

I seem to have no choice. Which is fine, just driving me a little crazy, and gives me slightly less confidence in Bandlab Cakewalk - that a version that has supposedly fixed many bugs since the last SPLAT has a bug that is not in SPLAT.

Yeah. She seems genuinely happy with it. Didn't want to embarrass her.

Thank you!

Thanks everyone. Has given me more confidence to let this be played.

It's the only project with the issue. And it works fine in SPLAT, just not Bandlab Cakewalk, so how could the problem be project corruption?

Haha - my daughter knows my limitations. She asked me to play the song, not sing it.

I need some ears for mixing critique on a very important project. My daughter is getting married in 4 weeks. She asked me to record myself playing Love Is All Around on guitar and wants me to walk her down the aisle to it. I accidentally ran it through an Ozone preset twice. I sent that version to her (one of many takes), and she said it was perfect. Now I'm wondering if it sounds over-processed - it definitely sounds different from a "corrected" version. I have some moderate hearing loss, so I'm no judge as to what really sounds "better." Does it sound ok? No need to listen past a minute or so - it's looped so the DJ can fade it when we get to the officiant and groom.

My daughter got engaged a year ago and asked me to record myself playing Love Is All Around to walk her down the aisle to. I've worked on it here and there, and now the time is upon us - wedding in 4 weeks. The project has gotten a little squirrely over the past year - for a while any editing in Bandlab Cakewalk was impossible - the project would be frozen when I opened it. I discovered that I could still edit it just fine in SPLAT. Also, when I opened it in Cakewalk, PRV for the drum track would showing, even though that's not how the project was saved and not how it opened in SPLAT. About a month ago, I found I could open and edit in Cakewalk again, though it still always showed the drum track PRV when I opened it. Now today I tried to add a track, and the track view scroll bar froze and "filled up." CTRL-z would delete the added track and return scrolling to normal, but every time I try to add a track now, the same thing happens. And once again, no editing is possible. I've confirmed that it still works fine in SPLAT. What couldbe going on?

Drum maps aren't really necessary, but I do use them. There are drum maps already created for many drum VSTs - Addictive Drums, for one - so you don't necessarily need to do any work other than searching online and following the instructions to get them into Cakewalk.

About 95% MIDI / VST. Synthpop and post-punk mostly. It has worked well for me since the first version called "Sonar." I have a ProTools license but don't even have it installed currently and have never finished a project in it.

Please post here if they say anything useful. Thanks.

I have one. It certainly isn't designed to work seamlessly with Sonar, but I haven't had the problems you describe with muting notes and playing only the selected track. Maybe reach out to Nektartech support?

It seems like there were some kind of compatibility issues with NI keyboards not too long ago. Have these been resolved, or am I not remembering correctly?

Not a stupid question, at least to me. I've wondered the same thing.

Try deleting the file TTSSEQ.INI in app data\roaming\cakewalk\cakewalk core. You will then need to recheck the boxes for your MIDI keyboard in Preferences.