Scott C. Stahl

When I do a "save as" with changes in the project it goes back to the 40 second routine. Sorry about the confusion. I should have been clearer

I was working on mix 186a. Without changing anything in the project, I did a "save as" 186b. That went quite a bit faster

I'm on Win 10. I did use my cell phone cam to catch the save behavior tho. My project takes 40 seconds from the time I click the dialog save button to finish. First, it sits for 5 or 6 seconds, then flashes a "not responding" message for a split second. The progress bar then moves normally after that till the halfway point and stops. It sits at that spot for another 15 seconds or so, then finishes the save. For a total of 40 seconds. As an experiment, I changed the version # of the mix without any actual changes to see how it would do. It zipped through the save without a hitch

That would be interesting to compare, thanks! I don't know how to video my desktop or have any software to do so like camtasia or something. The drawing issue not terribly important at this point to me anyway as it is intermittent and a fairly fast effect. Like a swipe effect in a video from left to right. Just thought I'd report what I've been seeing. On another note: I tried the ctrl/exit. I then opened the project up later to make some changes and found it did not remember the last project it had open. I had to go to the project file via explorer to open the latest project. Projects do open faster in general and the VST scan is much faster now as well... so very good there! Thanks!

1st "Big" Project opened with .09 Faster, that's for sure. I lowered my Midi buffer from 200 to 50 which helps playback speed a bit. I'm finding standard saving suddenly seems pretty darn slow. Can't say crazy slow, but it is noticeable, and already is a bit of a pain. However since this is the first project I've tried, I'm not sure how universal this is on my end. Also since the last update, my GPU must be getting pushed a lot more because screen redraw suddenly is slower...opening up like a curtain from stage left. Mildly entertaining the first few times it happened. Not really a problem for me, but worth noting

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!