Scott C. Stahl

Something's up with this. Not sure on which end, sadly

Think I have it, but never tried loading an outside IR. Thanks for the heads up!

I actually have it go to a "Lead Guitar" Bus but wanted separate processing for the individual channels. Didn't want a global GR7 for them all. Still could prob create a separate Bus for just that particular track, put GR7 there then send that Bus output to the main Lead Guitar Bus. Great idea! I'll try that out as an experiment. I'm sure that would work tho. Shame to have to go thru any of this to get a plug to work as it should! Thanks!

Hello J. That'd be one way to go! It's faster for me to just shut off the GR7, fire up a Melodyne region, then turn GR7 back on. Easy, but another couple unnecessary clicks in the workflow to avoid something that shouldn't be happening in the 1st place. Hopefully addressed by the bakers or NI, but not holding my breath!

Trouble is having the processed sound play as I make or alter Melodyne adjustments is important. As I said, I'm good as long as I make sure to shut off the effect in the bin before creating the Melodyne region. BTW I always bounce to clip after Melodyne adjustments when I'm completely happy with what I hear, but I make sure to save 1st! A couple projects I have will crash on any render of Melodyne. I've sent dmp files to the Bakers, but the issue is intermittent. They have replied, but no answers

Hi John. I was using GR7 in the effects bin. I've never used Melodyne on processed audio. I might do that for some interesting effects, but I doubt it. The only thing I'm editing is raw audio. Instantiating Melodyne on the raw audio as a region (Which is how I always use it as well) causes GR7 to go dead. As long as I shut GR7 off in the effects bin before creating the region or editing too much, it's fine. A simple solution, but it shouldn't be going dead at all in the first place. Since it's happening on both CwbB and Sonar I suspect a GR7 bug, but who knows?

I decided to add some new lead guitar work to a track. I set an audio track to record and added Guitar Rig 7. (Newly updated) I needed to tune up a few spots so put Melodyne 5 advanced on the guitar I just recorded. When I did it, Guitar Rig stopped sounding. I could get it to play again. After some time, the easiest fix I have found was to simply save my GR7 preset, delete the plug, then add it again. After doing so, everything was back to normal. Then went back in and edited something else with the Melodyne that was already instantiated and Guitar Rig went dead again. This happened 5 or 6 times. Finally decided to try turning off plugin before edits. That seemed to prevent GR from going dead on me. Is there something I'm missing? I always uncheck "Zero controllers when play stops" Yes, I know GR7 is not a VI, but an effects plugin. Known issue? Could be a bug in GR7, Sonar, or both. I have not tried it in CbB yet. UPDATE: Just tried it in CWbB and GR7 goes dead the exact same way

I'd have to check. Don't get on that computer too often. I sometimes dig for old legacy files...

Thanks Giorgio! I'll take a look at that!

After trying a couple new verbs (Like Pro R and Valhalla) I reloaded Perfect Space and it was fine. Still blew away the others. Even with Pro R able to emulate the Classic Lexicon from PS IR I just could not dial in a sound I was as happy with

Actually, I just reactivated an old version on an old computer. Prob a couple years old at least. No problem. I was surprised, but it did it without a hiccup. Just happened a few days ago. Go figure 🤷‍♂️

OK Seeing this again. Apparently the problem is project specific. I once again had to undock notes in order to get it to add mix notes at the bottom. If I open a new project and try, even after adding other notes, it works fine. Just this particular project I'm working on. I can just leave the window float there at the same spot so it's not a huge hindrance, but something's not right

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

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

Exactly

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. 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)