[OLD THREAD] Graphical error: Trans markers won't display properly after reopening project

EDIT June 5, 2015: This is an old thread back from X2 days which caused me a LOT of problems, most of which were resolved in X3 and now SPlat. I have not however done any intensive Audiosnap work like I was attempting when I posted this so I don't know if things are better with the updated AS. No need to read through my posts. It was revived by someone looking for help though so see the lates posts at the bottom of the thread. http://forum.cakewalk.com/FindPost/3234459
 
Original Post
============================================================================
Oh, boy. After hours of inserting my own markers yesterday I saved and closed the project before I had finished adding markers up to the very end. I was close but needed to stop for the day. Now upon opening the project the markers are there when zoomed out but disappear and reappear randomly as I move the cursor across the tracks. When I zoom in all the markers I added as well as the disabled auto detected markers completely disappear up to the section I had not completed yet (the disabled auto detected markers are still there). On top of that on the Audiosnap Pallette my auto detect transient threshold is now reading 88% when I had left it at 100%. If I turn it back up to 100% I get a message telling me it's going to stretch the audio. I have no idea why.
 
So now if I can't figure this out I won't be able to manipulate the audio how I want because my markers disappear when I zoom in far enough to do so. Anyone encounter this? Is there a fix?
 
Win 7 64
X2a 64
Gigabyte video card 1gb video RAM
i7 2600k
16GB DDR3 RAM
Barricuda 7200RPM HDDs
Focusrite Scarlett 18i6
 

Try clearing the picture cache to force the project to redraw.

It is a manual process, delete the entries in the directory defined in Edit > Preferences > File > Audio Data  "Picture Folder". Select and delete all the files in the directory.

Okay, I'll try that. Thanks. I just tried the following after some searching...
 
o redraw waveforms
1.
Select the clips that you want to redraw.

2.
Right-click a selected clip, and choose Associated Audio Files on the pop-up menu to open the Associated Audio Files dialog box.

3.
Click the Recompute Picture(s) button. A dialog box appears, asking if you want to recompute the pictures on the selected clips.

4.
Click OK.

 
http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X2&Lang=EN&Req=AudioPerformance.24.html#1124221
 
I'm wondering if that ini file stuff would help me in the future but I don't understand that type of thing. If this is what's going to happen to me though I think I'd better learn. Have you done those ini tweaks? Do you think they would apply to me? Gawd, this type of stuff makes me feel like a freaking n00b all over again. ugh

Not at my computer at the moment but I believe there is a setting for the memory allotment of the PictureCache. Check under preferences.
 
There seems to be something going on with the Picture Cache in X2a. I've never had any issues with it in the past and within the last 6 weeks my wave forms seem to consistently go away. Not that big of an issue when tracking but for mixing it is a real drag.
 
Regards,
 
 

The AUD.ini entry is PicCacheMB details here http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X2&Lang=EN&Req=INI_Files.6.html#1134652
 
You can get to it by Edit > Preferences > Configuration files "Edit Config File" button.

What scook wrote...and if you are worried about the file deletion just move all the files to a new folder for safety. What's that saying "measure twice, cut once"
 
Regards,

That didn't work. Darnit. I may have to do this part of the project in X1 if X2 just can't handle it. Then again who knows if X1 will behave any better. I also don't like the idea of not having the time ruler drag/zoom function. What... a... drag.

After poking at it some more I think the project is simply corrupted somehow. If I allowed one edge of the clips to remain visible I could zoom in but sweeping the cursor around would make the transient markers appear/disappear randomly. I tried to give myself a little more room by dragging the track pane divider to the left and when I tried to drag it back the clips pane spilled over the divider and the graphics would freeze up. I could only get the track pane back by opening and closing the inspect via keybindings. If I tried to select the visible transients by clicking or lassoing they wouldn't select at all. The project is scrap. I'll have to start from an earlier version.
 
Just wanted to document the problem.
 
Edit: Oh and for some reason shut down of the computer took an unusually long time. Not sure what that was about. Maybe it was trying to clear the RAM or something.

@mmorgan... Naw, you taught me a little tidbit about the cache preference setting. May not have fixed the problem at hand but it is knowledge and appreciated. I'm just grumpy because I'm in pain today and I'm disappointed that I lost my work from yesterday. It was all just a tester sample anyway of how I'm going to deal with the larger project so it's not like I can't go back and start over. I was however very close to getting to the next phase of the test (actually stretching the audio) so it's frustrating. This is typical in my world though. Two steps forward, five steps sideways. Tomorrow I'll try X1 and see if that's any better or maybe just commit to completing the entire process in one session with X2 in hopes it remains stable long enough to do what I want.
 
Thanks for trying. Cheers.

Save the relevant portion of the project as a new project to a new folder, zip it and send to us. We may be able to see whats causing the issue and fix for the future.
In Platinum there is also a new feature to clear all AS markers in the project if you wish to recover it. You have to right click the AS button in the AS toolbar to get to that menu item.

I just dug out the original clip of the offending track from a backup and pasted it into the current project - everything seems to be working fine.  Appears to be solely related to a corrupted clip somehow.

No, I didn't bounce at all - didn't see that in any of the documentation on Audiosnap/ Audio Transients, so I just assumed it was rendering the wave maniupulations as a new clip whenever I stretch/move Transients.  I have always bounced each clip when using Melodyne or V-Vocal, but that's pretty obviously still sitting there as a manipulated, unbounced wave until you do so.  I do always use shorter clips for the manipulations too.
 
What you suggest may be the problem - but the other tracks I had also manipulated all seem to work fine, it was just this one track.  I have had more than my share of Sonar crashes of late, I wondered if perhaps one of those somehow corrupted this track...

I had some odd behavior with this just this week.
 
I spent an evening working on AS with 2 acoustic guitar parts. Saved the project and the next day I opened it and the transients would disappear at some zoom settings... but only on one of the tracks. The other track displayed the markers just fine.
 
Even though the markers were missing they were working so this is a visual thing.
 
After fussing around with it I managed to loose all the edits on that track. :(
 
I was able to redo the work in short order after I disabled as for that track bounced the clip and then enabled AS again.
 
So far (knocks wood) it has not repeated this problem.

I think really on an ideal system under ideal circumstances we wouldn't (shouldn't) have to worry about such things but let's face it... we are all working on various PC configs (and those who aren't... like the Bootcampers are even worse of than better). My rig is good but I built it myself and I am no DAW builder. Most other are working with off the shelf stuff that's been tweaked or have done like I did and built their rigs themselves. Then there's hardware and blah dee freaking blah... that adds all sorts of complexities.
 
If I had my druthers I'd be running a professionally built DAW tweaked to specifically handle Sonar and all my various outboard crap and a/d converters.
 
When you think about how insanely complex things like audiosnap/melodyne calculations must be in the grand scheme of things (we are what... like only fifty-60 years removed from lightbulb and punchcard computing... lulz) then it makes sense that the program may vomit all over itself on a consumer or even "prosumer" PC.
 
To me I think my issues are HDD related and an inability of the DAW to recall such inticate silliness fast enough. The CPU may be willing, the RAM may have enough space but something somewhere is bumpling about and borking things up... so I just try to be careful and aware of the limitations of my personal home technology.
 
I would like to point out some of the videos on this very site produced by Cakewalk themselves on their own ultra tweaked, high performance machines. If you look at the old CakeTV Drum Production webinar with Seth and Ryan (or other vids here and even on Groove3) you can see some of these strange graphical glitches occuring with Audiosnap (and other areas of the program).
 
I recognized those little glitches immediately as I saw them but seeing how various doods just hammer through them gave me a little hope and I've learned to somewhat ignore them but also be aware of them as indicators that PERHAPS something was about to go all crashy smashy on me. Which is why I Save As repeatedly so when it DOES happen I've only lost maybe 5-20 minutes worth of work instead of 4+hours of work (which is what happened when I originally posted this thread).
 
I bounce and archive and freeze and watch my synth/vst count. I try to make sure I don't allow my project to have a million tracks with a million active takes. I keep the performance module open whenever possible to keep an eye on resource consumption. I micro manage all the other processes that might be going on on the system (like antivirus stuff, auto updates, internet/network weirdness).
 
Essentially I treat my rig like a living entity that b*tches and moans and cries and wheezes when I'm abusing it. If I listen and try to not kick it in the teeth any more than I need to I can get things done. If I don't... well there is a whole wack of hair pulling, screaming and running here to the forum to kvetch and try to sort out WTF I did wrong (which is time consuming and not pleasant for anyone involved).
 
My point is... don't temp fate. Before doing things like AS manipulation do a Save As, make a plan, do a bit of experimenting to see how that plan is working out and how your system is handling it THEN do another save as and start the work proper, do it quickly and in chunks bouncing and Save As'ing as you go.
 
It's annoying and semi time consuming to do things this way but since I've gotten ULTRA paranoid and cautious about stuff like this the amount of time and stress I've actually SAVED from avoiding epic catastrophes MORE than makes up for adding those steps into my workflow.
 
Sonar works better and better every year since I've owned it (like WAY better) but in computer terms we are essentially putting a man on the moon with some of these "simple" tasks we take for granted every few minutes or so.
 
Just taking a break from my tracking so I sorry for the long, boring, pseudo-philositechno post but really... unless you can buy a dedicated DAW built by a DAW builder caution and awareness of what your system is trying to tell you is advisable... and even if you do get the ultra high quality Studio Cat custom builds you still should be careful.
 
Cheers.