Scott C. Stahl

Perfect Space clicks and pops on new Sonar on a mix I had ported from Cbb. I had been using it often because the Classic Lexicon Dark plate was a fav.

I have thrown the impulse onto Pro R2.

I think I'll be fine with that going forward, but curious if anyone else had seen that behaviour?

I tried like crazy the first cpl times I had it open to get it to work and it refused. Then suddenly when I opened Sonar again later in the day, the behavior stopped and has gone back to normal. Believe me, I have been editing mixing notes on Sonar forever and had never seen anything quite like it. Hopefully, a one-time glitch. Thanks for the replies!

Just pulled the trigger on Bandlab membership and using New Sonar for real for the first time.

While docked normally on right side, Notes module will not let me edit notes in body of text or add notes to the bottom now. It will only allow me to add notes at top. When I undock, the issue goes away. Now I have to undock every time I want to add mix notes. I've always added new notes on the bottom so unless I reverse the order, putting latest notes first, this will be a continuing pain. Will this be fixed or will I be forced to change my workflow on this? In other words, is this a new feature or a bug?

Seems like user feedback would be  a metric they would or should look at. I'm sure I'll get on board myself as the bugs are ironed out and the pricing is set. (Unless it's something crazy, which I doubt)

Hearing opinions of people either happy or unhappy with the rumour mill can contain some useful info. I've been on these forums since the 90's and have seen a lot worse than the complaints here. 

BTW I've seen some blowup from Studio 1 users about their marketing and sub plans. All of this potential pricing and subscription upset is not happening in a vacuum

I'm liking the new look TBH. (Dark theme) The lettering looks crisper to me. It's running stable on even bigger VI heavy Projects.

I'd be sad if it was Subscrip only because I just won't go that route. Otherwise, I'd love to take it for a proper spin and see what it can do

on export and saving.

I would miss the custom theme I worked to put together, but the dark theme is actually better on the PRV for me.

Given a reasonable price, I'd probably go for the yearly upgrades just like the old days, but I just HATE the "Clock ticking in the background" feeling  Subs gives.

Aint gonna happen here.

I have CC+ Sub w/EastWest but this will be my last year for that very reason 

1 hour ago, OutrageProductions said:

The rest of us figured this out last August, so you're catching up...

Damn! You mean I'm not a computer genius?!?

Still, none of the posts in this particular thread are very old, so I feel it still might be helpful to some.

I didn't have to use BBCSO for quite a while so I can't be sure how long it was broken for CW. I had thought it was a recent problem.

I found the answer in the Spitfire forum for BBCSO. I tried the various suggestions and after a bit of trial and error, was able to get it to load.

I basically got rid of the BBCSO .vst3 sitting on it's own in the C:\Program Files\Common Files\VST3. There is also a BBCSO folder there as well. I Renamed the folder (getting rid of the .vst3 suffix.)

I Then went into that folder and pulled out a BBCSO .vst3 file that is in there.

Replaced the earlier vst3 file I had deleted (The one that was sitting on it's own in the common files) with the one I copied. Success!

My guess is the various .vst3 filenames in different spots threw Cake off on which one to use.

I Also made sure to scan when I got rid of the .vst3 and then scanned again after restoring with the new .vst3 so Cake did not get confused.

I might not have had to do all this, but it worked (finally) so I'm temporarily a computer genius!

YMMV, But I hope this helps.

https://community.spitfireaudio.com/discussion/2737/bbc-symphony-orchestra-v1-7-0-update-vst-plug-in-error

Windows always updates. Pain in the @#$@

Been awhile since I used BBCSO so there have been many updates since. No amount of re-installs or other measures have worked. The only plug except for SM EQ 4 that has problems

11th Gen Intel(R) Core(TM) i7-11700K @ 3.60GHz   3.60 GHz   128 GB Ram   Windows 10 Pro   OS build 19045.3930

Same here with BBCSO. Works fine in ableton

6 hours ago, Quinellipe Zorn said:

So, for a lot of/most people, I'd say get current, but as you are engaging a very stable and controlled environment functioning to your satisfaction, makes sense not to change - you likely won't get satisfactory improvement on the little bugs versus the risk that something becomes destabilized, however unlikely that is.

Exactly

On 1/9/2024 at 3:21 PM, David Baay said:

Which problems are those? Many of us have no problems. The only "problem" that has been somewhat frequently reported since this release is"slow loading", which is a generic symptom with many possible causes, most of which have turned out to be system/project/plugin-specific and none of which are specific to this release.

Thanks for the reply.

Which problems are those?

All you have to do is read this very long thread. I admit it's been a bit of a slog to do so and I have not read EVERY post. Slow loading, activation issues, various problems for users that have stopped them dead in their tracks and as far as I can tell, no resolution of their problems have been noted.

On 1/9/2024 at 3:39 PM, John Vere said:

That’s the thing, I read about people issues daily and it always comes back to it’s not an issue with Cakewalk, It’s almost always something caused by a plug in or computer , hardware issues 

 

For sure it still has a few weird little bugs but those are so  on the very fringe of what the majority of users would even be aware of.
 

I spend a lot of time working in Cakewalk and last time I had a crash was 100 % because of a plug in. I have never had any issues ever outside of plug in issues. 
 

The latest version of Cakewalk is BETTER than the last version because they fixed    the bugs they were aware of.
The rest we are told will be addressed with Sonar. And as we speak there’s an army of people swatting any bugs that they find there. 

So holding out on the last release is only based on miss information you have gathered. I’m also in the middle of dozens of important projects and I updated to make sure I was using the BEST version.
Having backup copies of all my projects is more important than thinking upgrading software is dangerous .  

I've been a constant Cake user since the 90's and have downloaded every update and purchased every new version on offer for the past 30 years, so I'm not new to this. The posts in this thread have given me some real pause, so I simply thought I'd ask. This is a weird period where us Cake users are at a temporary dead end of an era. No way to roll back and no clear path forward yet.

I'm pretty sure most of these "Slow load" and other problems only cropped up for users AFTER the update. None of these problems were happening before.

Obviously, if I want to stay with CbB I'll have to comply at some point. I do keep my projects backed up, so It wouldn't be total disaster if it turned problematic... just a big, pain in the ***** hassle I just don't need right now.

Agreed, most bugs wind up being user/system/plug specific. I just don't want to be the one dealing with them when I am perfectly happy now. I try to work as fast as I can to clear out my project backlog, but it aint happening tomorrow.

Believe me, over many years I've seen new problems for somebody on almost every update, but this one has generated a lot of complaints.

Most importantly, the Bakers say this is it. No more updates in this free Cake era. So having us:

"Step forward and update, but you can't go back. Oh by the way, this last step is a dead end too".

Has me a bit hesitant.

I think once the "New" Sonar is up I'll be less worried about updates since this will be an ongoing high priority for the bakers. Plus, I can buy Sonar and download it right next to the old stuff. (That would be my guess) I still have all the legacy Sonar's sitting on my system as well.

Appreciate the encouragement, but I'd sure be happier when the New Sonar has a clear premiere date.

I have been a happy user of 2022.11. Have the problems pointed out by so many been addressed?

I've read a ton of the thread today and in the past, but have not seen anything that really says most issues are resolved. Truth be told, my current build is something I'd rather not part with anytime soon. Especially if there are continuing problems.

I have a ton of big projects in progress and things are working great. Last thing I need to do is FAFO

I opened a project that had been repeatedly crashing after uninstalling SM EQ4. It is working perfectly now. This project wasn't even using SM EQ4 in the first place, but the uninstall seems to have done the trick. Truth be told, I'm kinda shocked.

Never experienced just having a plugin in your SYSTEM cause problems like this. Like many, I have Hundreds of plugins that have piled up over the years

(Win 10)

I uninstalled SM EQ4 and will let you know if things improve for CW now.

BTW, Have the problems with the final CW update been resolved?

I'm on the next to last version right now and it was (Up till this happened) very stable. I have not wanted to mess with what was working

On 12/25/2023 at 7:08 AM, El Diablo said:

WARNING!!! Smart EQ 4 crashes Reaper!

Yep, just like Smart Reverb, it crashes Reaper!

I lost my whole project because of it!  I couldn't load the project because Reaper would crash everytime it loaded Smart EQ 4!!

After using a older backup file and writing over the project file, I find out that Reaper has a safe mode that will not load any VST.  😢 It's sad because I find out later after I overwrote the file.  I ended up using Smart EQ 3 INSTEAD because it's stable!

SMART EQ 4 should be known to be unstable for production!!

Just a heads up!

 

Sorry to see this. I'm having problems in CW as well

I picked up the upgrade for 29$.

Ever since, CW has been going a little crazy with unusual crashes and choking up that were previously only rare. It could be something else, but I noticed it crashed CW right away on a project the day I downloaded it. CW has now been cranky on almost everything since. With or without SM EQ4 in the project. Anyone else experiencing anything like this?

5 hours ago, scook said:

It seems you may have been using an out-of-date user theme.

Either stick with the themes supplied with CbB, update the custom theme or use one of the themes published in the theme forum

I was. I had tried to edit the old theme and re-save, but no soap. I will check out the new themes available. Thanks again!

No. I'll try that! That did the trick! Thanks!

I'm using build 2022.02 and finding the Archive buttons on the track view are half hidden. no matter how I change the settings or themes it remains this way. Obviously I could try the next version, but I see no info about this problem in the update notes. Anyone else see this? This happens on all tracks regardless of expansion level

This release has caused me major problems. I have a support request in. The procedure they outlined has caused more and different problems. I finally rolled back my entire computer system as far as it could go. Some weirdness, but I have fixed a few items and am currently limping along. Win 10 New system working perfectly up to this point. Would not recommend

I had an issue with the update. During the update an error message came saying msvcrt.dll or something like that was missing. now my sonitus plugins are not operable and Pro channel is acting weird. What went wrong? Not sure how to reverse the process

I missed that one! Did the trick! Thanks!

Downloaded Reaper. Problem disappears. Not sure what CW is doing to goof these up. I'd rather not learn a whole new DAW but the ease of MIDI clip handling was beautiful. It's got me thinking!

Sonokinetic and Instruments stop sounding after recording MIDI. Both Cappricio and Indie. They respond to MIDI but no sound. Purging does not help. Reloading restores them but they stop responding again. My system Win7 DAW Cakewalk.

No problems with other Kontakt instruments.

Scaler also goes dead after any MIDI Recording or movement.

Sonokinetic support said this "It sounds like your DAW is applying automation to the library. Have you tried the libraries in standalone mode outside of your DAW to see if you still get the same issue?"

I tried this and Both work fine in Kontakt as a stand alone.

I've tried just about anything I can think of. Changed settings, etc. Nothing

Any suggestions? 

As I figured, I would lose all my passwords and tons of other info and settings to upgrade on this system. I will have to build a new one and slowly port over everything. The old computer will make a fine office computer anyway. Thanks for the input everyone!