Scott C. Stahl

Excellent! I actually had that happen previously. I did wait 2+ hrs on the last try for that reason, but no soap. Maybe I'll try an overnight!

Wow, thanks for doing this! The only 32 bit plug I use is Perfect Space. Still my Fav despite buying almost every other Reverb made. Fortunately it loads up fine on other projects.

Hello. I'm not getting a response after posting the link to my .dmp file to support and on here. Would be interested in hearing what may have been found. Thanks!

I originally started recording this in 2011 so it's OLD. I had been rolling along fine in whichever version of Sonar, CbB, etc. There are a ton of older plugins and ways of doing things abandoned or deleted over the years so who knows what is specifically setting this off. Project versions worked on before late December open ok. After that, none of the last 5 or 6 versions open, even tho I worked on it the last time without issues on Dec 30th. So whatever changed between then and now is what I would have to suspect. I'm on build 2024.12 so nothing should have changed between then and now. Perhaps something in my system, but with others also having similar issues, I'm at a loss. Fortunately, it works fine in CbB and I've made the changes I wanted. So far, so good. Working in CbB again makes me miss track colors badly, I mean real track colors...Not some dinky bar next to it

I forgot how much I liked my old Cbb! Opens up fine here... whew! I'll try to finish my changes and resave 40 diff ways from sunday. Was able to get mix notes from 273 on copied over to the text doc as well. Gettin sloppy! I also noticed that I must have been fooling with the transient match at one time because it gave me the notification it was generating them (Something the New Sonar will not do). Every mix I do crank out will be glorious 24 bit in case the whole ship goes down, that's for sure!

I've been suspecting my system HDD for some time (an M.2 2 TB) I'm running out of time... I suspect the whole thing will go soon. Oh well, more money, aggravation and time. What else is new?!? lol Thanks for checking it out

The project is years old and started out in the old sonar, then Cbb, then a number of reworkings in the New Sonar. I have Cbb, (Jeez, I forgot about trying that!) I'll try it out and see if I can't streamline it some way. I did manage to get mix 244b to open which is (40+ iterations ago) in Sonar last night so I'll concentrate on the changes since then. Probably some corrupted data or Kontakt issue. A shame because I was just a cpl of adjustments away from being finished and sounding good despite the bloated nature of the thing! Thanks for the input and work! I copied the mix notes up to mix 272 to a word document so I'll at least have a few clues on some possible things I did in between to concentrate on. I sent a link to the .dmp file to the bakers, but have yet to hear back. I'll paste the link here as well for giggles. Thanks again! https://drive.google.com/file/d/1LhkGnySzoVzD9yNTc_PCDlUG3Tf2Ibva/view?usp=drive_link

Very generous! Here's the onedrive link. It won't load on my system even without audio files or plugins. Here's the link. Thanks! https://drive.google.com/file/d/1zXcHOhRzkBLixxbUTux9PAMPBqOhc8lW/view?usp=drive_link

Sonar Crashes trying to open a particular project no matter what mix number. Seems to open fine with other projects. I have multiple crashes generating multiple .dmp files. Always crashes the exact same way Seemingly installing all plugins then hanging as project files start to load. Win 10 Latest Sonar build. Already tried installing the new redistributable provided and no change. Also tried safe mode installing no plugins. Still no dice. In the process of send a dmp file to support

This happens with every large project for me as well. I wind up selecting "No" just to get the annoying window out of my way and just wait till sonar finishes it's bookkeeping. sometimes have to click "No" thru 2 cycles. Really long closing times have been happening for quite a while now... since at least later versions of CWbB. If I do not wait till it finishes the close, CW does not even "Remember" that I had the project open previously. More and more I find myself opening projects direct from windows explorer just to make sure I'm opening the last project I was working on and not some earlier version

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?