I discovered more Sonar bugs today while working with audiosnap in a new project.
 
It's worth noting that in the 4 projects I've worked on since buying Version 8.5, these bugs (or similar ones) have arisen in every project. So it's not been "project specific." I am now under the impression that it's virtually impossible to use audiosnap across a whole track without coming across these bugs, which makes it almost unworkable.  I am seriously considering moving over to another DAW right now, which is frustrating because I feel like I have wasted my money. I walked through these bugs with someone over the phone at Sonar, and I've sent the files over to them. In response I just received a generic formletter over email. 

It's so crazy to me that the new Sonar X1 info mentions nothing about whether these bugs have been worked out.

If anyone is reading this because they are considering buying Sonar, I would seriously suggest trying something else. The bugs are just too numerous.
 
1) Once again, it seems that painstaking edits made previously to transient markers have been lost and need to be redone. It's hard to say what caused it this time, but I explained some ways this can happen in the first posts (above). This may actually just be attributable to bad software design, rather than a bug per se. But I have yet to be able to edit transients across a whole track without losing some part of my work.
 
2) Certain transient markers are visible, but cannot be deleted/ reset/ disabled.
 
3) Tempo map- beat markers randomly slide forward, and out of order, 1 to 2 measures ahead of where they should be. They slide forward and out of order, unless arbitrarily locked down in the correct place to a transient. In most cases, this forces me to place a transient where there was no actual beat, ie, where I don't want one.
 
4) Some beat markers refuse to lock to a transient, even if the transient is in the right place. The beat marker just insists on moving unnaturally forward to a wrong location.
 
5) Some beat markers appear in random locations, and without any beat number assigned to them (all you see is the triangle symbol). There are a lot of them.
 
6) When some beat markers are unlocked, they zip off the screen in one direction or another, in a random location, out of sequence. This even happens when all other surrounding beat markers have been locked into the correct locations.
 
7) While working in audiosnap, several measures of the visual wave display seem to have been replaced with waveform that bears no relationship to what is actually being heard on the soloed track.  You *hear* the correct audio when you solo the track, but what you see represented on screen is something else entirely. For example, where a note is heard being sustained, then followed by a rest,  the visual wave form looks like all kinds of notes are being played. This discrepency lasts for about 4 measures for no apparent reason. This makes it impossible to set transients in the right place, when what you see is not what you are hearing.
 
8) Again, this may not be a bug per se... But has anyone noticed that when you select a certain level of resolution in Audiosnap, ie "quarter notes" or "half notes," it doesn't actually work?? If I select "quarter notes," I get loads of transients on 8th notes. If I select "half notes," I have distinct whole notes that are missing transients. This setting is almost useless...

 

By the way youtube explains auidosnap it sounded like a great tool which I would undoubtedly use at some stage.

But after reading this....I have a bit of concern.
I'd give it a shot though to see if what I would use it for will end up causing grief or not.

As for someone saying it's like a maze getting through Sonar, indeed it has been.
I have had to read up a lot and at times think there must be a more straight forward explanation which is where youtube has come in handy along with the users in this forum.

Why doesn't Cakewalk address this post and the issue of how Audiosnap is supposed to work?

Yeah....Cakewalk puts in a great new feature, then leaves the bugs to fester and irritate us for several versions.     

And yes, the videos can be very misleading as they usually demo AS with 4 to 8 bar clips. They should try working with AS on a full 3 to 4 minute song with multiple audio and midi tracks!!!!

....where's the "truth in advertising" paradigm?

Hah I just had to add to the heap...  After writing that last post, I struggled with this tempo mapping until I finally got all the beat markers "locked down" onto a transient. (I had to locked them ALL down, because if I didn't, some of them would slide 1 or 2 measures ahead, all haywire.)   So then I saved my file and called it a night.

The next day, I re-opened the file, and all the beat markers were complete chaos!!  All that work lost. Hundreds of little triangle symbols, most without the numerical beat label, were scattered about wildly- no rhythmic sense whatsoever.

Anyway, so, I sent the corrupted file to Cakewalk to see if I get a response.  (Again, the last time I did this, I just got a "feature request" form email. I'm not sure why they called it a "Feature Request-" AudioSnap already exists. Maybe they should have called it a "Feature working request." )

Ok, so maybe I should just hire a pro bassist to play this track tighter;)

Otherwise, Pro Tools, here I come...!!! For the first time, the new Version 9 works with any ASIO compatible interface, and from what I read on Sound On Sound, the new Elastic Audio feature works even better than Beat Detective.
http://www.soundonsound.c...0/articles/pt_0110.htm

What I really wish is there was some audio quantizing plug-in that I could just buy for $150 and use it within Sonar, because otherwise, I like Sonar. But I haven't found anything current... Any ideas on that??


 

The next day, I re-opened the file, and all the beat markers were complete chaos!! All that work lost. Hundreds of little triangle symbols, most without the numerical beat label, were scattered about wildly- no rhythmic sense whatsoever.

 
WTF?  You just wrote the book on Audiosnap and you're still discovering bugs and losing shiz everywhere.  Uncle! Uncle! Uncle!  I give up.  I notice making Audiosnap make sense wasn't on the just published mind map. 
 
Thanks for at least letting me know I'm not F'd up alone.  I FEEL LIKE I'M TAKING CRAZY PILLS!!!

I'm running X1c  and I have also experienced some issues with Audio Snap Transients vanishing as I scroll along, or even the image of wave on the track vanishing while remaining audible. I was terribly mortified and confused when I began to see my work crumbling. I contacted support and it went so far as the CSR asking me to send him my full project so they could all have a look at what was happening, this after sending them a video detailing my experience. I was told that the above mentioned behaviour has not been observed before and I was not pleased to hear that........

I have noticed what seems to be causing this. I've noticed the "Average Tempo" dropdown list in the Audio Snap control window, the value has a tendancy to change on you. Thus, eliminating/creating transients and screwing with the wave view (odd).  In my mind I don't see why the value would change if the track was recorded in the project at the tempo you're using. As you all read this, is there any advice on how to fix this, how to stop the Average Tempo value from changing? Resetting the Average Tempo value makes everything reappear as expected and you can begin working normally from there.

My solution to all of this goes like this; 

I only experienced the above issues after saving and re-opening the projects. So now, before I close the program after working on Audio Snapping, I "back-up" my work by performing a "Bounce to Tracks" for all parts that I've worked on. This method takes a little more time before shutting down but it gives you peace of mind that your work is done and preserved, and it also writes the new wave with perfect stretching, no oddities in the audio as compared to listening back to the original Audio Snapped track.  

I'm off to go work some more on my current projects. Hope I've helped someone out here who's jaw has just dropped for the first time with this issue. :)