Audio Snap Bug Revisted

This kind of thing has been noted by me and (I believe) others but here is some more visual evidence.

Below is a pic of an audio snap clip. Notice two things about the transient marker (TM) at 54:04:404. First, it has three dots to the right of its head, indicating that there are other TMs to its right that are not visible at the current zoom level. Second, that the clip shows no waveform in the range to the TM's immediate right. In fact, there is audio in that clip, in that time range, that audio has been audio snapped, and it plays back correctly.




Below is the same clip after zooming in one or two levels with Alt-mousewheel. Notice that the waveform on the right shows up, but that the TM head at :404 still indicates that there is a hidden TM.




Finally, below is the same clip after one more zoom. Here, all the TM markers disappear altogether. (Normally, TMs can be seen even at maximum zoom levels.)



I noticed this when I bounced the clip and the resulting audio starting at :404 didn't sound like it had been audio snapped (though the front end did.)

This clip was AS'ed several days ago. The way it stands now, I can't bounce the clip, nor can I get my mouse on the hidden/missing TM to try to somehow re-edit it. The unbounced clip plays the way it's supposed to even though it looks wrong -- I can hear all the AS changes I made -- but there are some audible glitches at the TMs of the kind that usually go away when an AS clip is bounced.

I still have the original audio, most likely slip-hidden in one of the adjacent or nearby clips (or at worst in a bak cwp), so I haven't lost anything (other than the time it took/takes.)

This is one of those occasions when I continued to keep a couple of clips in AS mode even though I knew I was done editing them, and even though past experience tells me that's a mistake, and that in one way or another live AS clips can find ways to get messed up, either while you're editing them, or just from being around.

The moral of this story: When you're pretty sure you've got an AS clip the way you want it, bounce it, or first copy it and then bounce it. The worst that will happen is that you'll have to redo it. But you might have to redo it anyway.

Keeping AS clips short is also a good idea, but not fool proof. This one was just a measure.

Also... This clip was in a multi-lane track. I don't know it that was a factor. I've found other AS glitches associated with having AS clips overlap across lanes, but that was not the case here. The clip also has a vol env. But I've encountered this identical prob when there was no env.

EDIT: Additional info. None of the transient markers in the clip can be edited, and they do not highlight as I mouse over them -- as dead as a screen cap. Strangely, I CAN enable and disable AS using both the AS icon on the clip and F12; when the clip is disabled, the waveform snaps back to its orig position, which is normal.

The clip below shows the original AS clip and a bounce of it (actually, a straight drag-copy of it) directly below it. Notice that the waveforms do not line up... though I can't say that I can interpret what's actually happening... or not happening....

I'm having a very similar problem complete with disappearing transient markers, disappearing waveforms, incorrect bounces, but correct in-project playback. The problem seems to manifest when I open an Autosave copy of a file. Which is a real bummer because I had just done 3 hours of work without making a backup when the program crashed. Went to restore from Auto-save and now this AudioSnap problem...

Older backup projects kept stayed good, but the new Autosave file is corrupted. I tried clearing the picture cache, but when the pictures were recomputed, they simply had new, different AudioSnap errors...

If anybody knows of any hacks to fix this problem, please post! If I determine a solution, I'll do the same...

This is still a problem.  Any word on this getting fixed?

Actually upon reflection, its probably pointless to ask for an official reply in this thread...no need.

I would just say this though, and its more directed at the "industry" as a whole than Cakewalk per se...but this is exactly why I am starting to sit on upgrading the things I own.....in the past I have been among the first out with my credit card....but its all wearing a bit thin.

cheers

Wiz

they only thing we can do, is vote with our wallet.

madfloyd


I hear you.  I've upgraded each year except for this year.  Each time, while I've been happy to get various small upgrades, I've never had any success with the bigger features like Audio Snap or ACT.  When I read that there was a brand new version of AudioSnap I was very excited - until I read all the posts here.

Also mysterious: Cakewalk is advertising Roland V-Vocal as being 'new' in 8.5 which confuses the heck out of me since we've had it for a couple years now.

Reading the posts here is not relevant to Audiosnap 2 - although that is not to say the problems are fixed. 
 
This thread was started in the days of Sonar 7 (July 2008) and I see no posts that refer to 8.5 although there is one that indicates similar problems in 8.3.1.
 
BTW I think V-Vocal has now been added to Sonar Studio which IS new and apparently it is now on a new version (1.5)

The problem persists as bad as ever in 8.52.

Which one? There are many issues mentioned in this thread, some of which have been resolved, and some I haven't seen for a while, but might still exist.


In any case, 8.5.3 was almost all AS fixes, so you should probably install that patch if AS is important to you, unless you're staying on 8.5.2 because Set Measure/Beat at Now is broken in 8.5.3. 

The whole problem with the disappearing transient markers.

Are you familiar with the effect of the Threshold and Resolution sliders in the AS palette?. The default setting for Threshold when you first enable AS is 75%, which means only transients above that level (not sure if that's a linear amplitude scale or...?) will be displayed, although you'll still see grayed out diamonds where the other markers are. Setting threshold at 0 shows everything, and it's a per-track setting.


I haven't had any trouble with markers disappearing for a while, but there are still issues with transients not being detected initially, so you have to place some manually.