Good Day, 
 
Ive been recently trying to learn to use Audio Snap function, and been having some issues, and wondering if anyone else has seen or knows about this.
 
Ive installed latest 2017.03 version of Sonar PLT (i cant say if this is a factor, as I never really tried using Audio Snap before).
 
This seems to keep recurring consistently, basically about 5 to 10 minutes into a session, moving, creating, disabling markers and map editing, typical functions, Im assuming, also Im only working on a single track at a time 
 
 
- my display starts going all funky, i.e., sections of the display window, (inspector, tracks, control panel, will start to go blank, or black out, or flash on and off, I may or may not be able to select menus, save, or may loose ability to key save shortcut, and/or close program.
Ultimately it freezes up/crashes Sonar, requiring to close via Task Manager, or may possibly recover if I wait long enough, may or may not generate error report function, may or may not create a recovery file.
If Ive been able save, markers are in place as last seen when I reload project.  
 
Ive only so far have ever seen this issue using Audio Snap, any guidance would be appreciated.
 
  

I haven't used audio snap, but based on your symptoms, I have to ask if audio snap is creating a bunch of small clips? If so, try doing a section at a time and then bouncing the clips to a single clip. I've seen Sonar exhibit similar symptoms when I've done a lot of editing and have many clips.
 
Regards,
Dan

Yea as Dan points out, if you're using AS and having it split clips, it will create a ton of clips and cause problems. I find it better to NOT have it split clips and just move your markers where you want, allowing it to stretch/compress the audio. Then do a bounce to clips to render it correctly. 
 
gabo

dcumpian
I haven't used audio snap, but based on your symptoms, I have to ask if audio snap is creating a bunch of small clips? If so, try doing a section at a time and then bouncing the clips to a single clip. I've seen Sonar exhibit similar symptoms when I've done a lot of editing and have many clips.

 
Thanks for replies, Dan, and Gabo,
 
I thought something like this, but the thing is, Im not choosing to split beats into clips, and also even tried working with only 8 bars, at a time, which Im taking out of source track, into its own track, applied trimming, so its only those eight bars and yet it still seems to do this eventually. To start with its only 1 guitar, 1 bass, 1 vocal track about 105 measures, at about 110 (so quite small project, and only so far only working on bass track (with no FX on this track either), considering its supposed to work across multiple tracks, seems odd, also my PC is somewhat substantial, so this shouldn't be an issue. Since Im just learning, and experimenting is why Im taking a long time with each clip, but not doing anything to radical, I dont think). 
Its almost like as though after a certain time period pass's (as in time of day), it decides to crap out, not necessarily because of what Im doing (Teamster possibly?). LOL
(guess Ill stick with Melodyne when trying to do this).
 
Cheers
John
 
 
 
 
 

 
So are you using AS to tighten up the performance? If you are, are you going to the clips and doing a "bounce to clips" on the track when you're done? Once you've stretched and moved around things with AS that's the way you "render" the track so it uses the offline algorithm to apply the edits. If you're just stretching them and leaving them like that, it could be causing the problem.
 
gabo

gbowling 
So are you using AS to tighten up the performance?  
gabo

Yeah pretty much, this is scenario,
 
Its kinda of a one off recording, of a random jam/party, with no drums or time to establish click bpm, (i.e., songs were pretty much written or improvised live at the time, I just hit record and let it run for jam duration) with a bass, and a acoustic guitar/vocalist, so, tempo drifts a bit as well as guitar and bass being a bit out of sync in places, (not the most accomplished musicians, LOL), I had separated various songs from the jam night into separate project files to work with.  Anyway just I wanted to establish constant tempo, tighten up and add VI drums, just to have the basic structure demo/example of the song(s), for posterity or future recording properly, (family from out of town).
 
I figured it may be a challenging exercise to try and learn to use AS, apparently so, lol. So once this issue started, I did start bouncing, every few changes, then went back with AS to continue where I left off, again if I took too long, or made too many changes before bouncing issue would happen again. Then I tried to just pull out one verse, and chorus parts, separately, sync them separately, bounce them, then splice back together into full song, I was more or less successful, but somewhat of more of an ordeal, then I expected to have to do. LOL.
 
Cheers
John        

Yea that's not right. Especially if you have a large computer with all the updates. I notice you use an RME UFX (that's what I have as well) so the driver for that are rock solid. The hardware drivers on some of the lower cost interfaces can cause these problems. 
 
I can pretty much do an entire track without any issues, then do a bounce at the end. I have 32gig ram and an I7 processor and it hardly blips to do these.
 
So, if you're got all your drivers up to date, are using the RME interface, have the latest version of sonar platinum, and have a reasonable computer, you shouldn't be having this much trouble. 
 
Since the display seems to go whacky on you, maybe it's a display driver or video card that's causing this issue? Be worth a try to do some checking on your video drivers and see if that does anything to help. 
 
gabo

gbowling
Since the display seems to go whacky on you, maybe it's a display driver or video card that's causing this issue? Be worth a try to do some checking on your video drivers and see if that does anything to help. 

 
My thought as well. I've had some outlier issues that could be traced back to video.
 

Anderton

gbowling
Since the display seems to go whacky on you, maybe it's a display driver or video card that's causing this issue? Be worth a try to do some checking on your video drivers and see if that does anything to help. 

My thought as well. I've had some outlier issues that could be traced back to video

k thanks, Gabo and Craig,  
 
Video card is NVIDIA GeForce GTX 960 (2 Gig), they're doing driver updates constantly, I think just last week one came, Ill see if I can find any video card diagnostics I could run. 
 
Otherwise, Im still using Win7, recently updated also, any chance that's an issue? (i.e. time to go to Win10?, Ive been dreading/procrastinating doing that still. LOL)   
 
Cheers
John 

win7 should be ok.
 
I have a GTX 970M. But since I have a laptop, I also have an integrated graphics processor. For the nvidia, there are a bunch of settings in there that can affect things. For sonar you really don't need any advanced GPU stuff.
 
So under "adjust image settings" I have "let the 3d application decide"
under "manage 3d settings" I have "auto select" for the preferred graphics processor and under the "programs settings" tab if I find sonar it's listed as using only the integrated graphics processor. So I'm not really using my nvidia for sonar.
 
In the "set PhysX configuration" my laptop display is set to use my onboard graphics.
 
gabo