Had to put my attention toward other meatworld demands for the past couple days but I'm about to jump back into my great audiosnap experiment. Just wondering if any of you who use audiosnap or the Transients filter setting more stable in X1 than X2. I want to use X2 for this due to some of the new zooming features but it's been finicky. If X1d is less glitchy for this type of work then I'll probably use that for this phase. If not I'll just keep trying to get X2 to do what I want.
 
Thanks.

This was actually one of the good areas of improvement for me in X2.
In X1d, I often use Audiosnap to detect transients and copy/paste them as midi events in Session Drummer to sample drums.  Often I have to manually look at the tracks as a whole and make sure the transients were triggered correctly and at the right times.  Also, after pasting I am then having to restart the session because X1d takes much longer to save after that.  I assume it's storing stuff in memory and restarting clears things... not sure.
 
Anyways, in X2 the transients detected much better and I didn't have to restart after pasting transients as midi events.  Also, a few other idiosyncrasies were fixed up.  I don't use X2 due to other issues that don't vibe with my workflow, but Audiosnap was definitely working better.

Thanks, fooman. I wasn't looking forward to bumbling around X1 again. I found it much harder to use than X2 but thought maybe because it had been patched so many times this aspect might work better. Guess not. One thing... are you able to save/reopen your projects if you have been working with transients but stopped before rendering? I got halfway through what I was doing, saved, shut down and then the next day the project was completely unusable. It was... frustrating. Cheers.

Interesting you bring this up.
I found in Sonar 8 that at times Audiosnap would completely spazz out and transients would be placed completely wrong and I would have to do work-arounds because on the audio clips as they were, it would be unusable as you kinda describe. My work-around would be to bounce the clip down to the exact same thing (new clip, same audio... just to reset the transient detection on the new clip), and then I'd have to spend that 20 mins or so making sure all transients were properly placed/detected.
 
Lame.  BUT in X1 I have not experienced this.
I always always always turn off transients on all tracks once I'm done and have pasted a track as midi events.  I have to cause saving is then very slow.  I rarely ever re-open the transient view after I'm done with this process though.   My workflow is probably different than yours, so this is just what I've noticed.

Yeah, from now on I just won't be closing the projects until the render is done. It seemed to be going along okay until I closed and shut down (aside from the usual annoying graphical glitches with transients). What I'm doing though is very time consuming so I could easily see a track taking a day or so to get through and I do not like leaving my system on in case of power failures or electrical storms during the night. Oh well. Gotta do what I gotta do. I may end up cutting everything up into sections but I was trying to avoid that.
 
Thanks.

When you say you close the project as it's still rendering, what do you mean?  Just curious, because all rendering that takes place with audiosnap takes seconds at the most for me.  Just curious if my thoughts on what rendering is are different than yours.

Sorry. What I'm doing is inserting my own transients for audio stretching to time correct and tighten things up. I don't mean stopping during the render process (well the offline render anyway). I mean I inserted transients up to halfway through the project and had to shut down for the night. So I wasn't done setting up my markers and had not yet done any stretching so I was no where close to the offline rendering stage. I was hoping I could just reopen the project and continue from where I had stopped. When I reopened the project all my user defined markers were disappearing if I zoomed in to any workable resolution, I could no longer select the transients or insert new ones, my transient threshold had reset itself to 88% when I had originally had set to 100% to get rid of all the auto detected transients, if I resized the track pane or other stuff it caused really bad glitches like work areas spilling over the divider lines and freezing up, I was getting some weird errors and IIRC I actually got a minor crash after messing around trying to get things to work. Basically it just totally munched the project so I have to start over.
 
I'm just not sure if maybe it's just not designed to stop in the middle of this type of work or if maybe my computer set up is causing issues (I think I may have my drives set up in a non standard way but it hasn't caused problems before AFAIK). Seems more likely that audiosnap is just a finicky feature. It is pretty complex and I've seen a LOT of people talk about its bizarre behavior.
 
Whatever it is though I just need to solidify a procedure that is less likely to fail. I'm totally new to audiosnap so I have fleshed out its quirks yet.
 
Cheers.

Yes, that's kinda what I experienced a version or so ago in S8 (I think it was 8).  Markers would get mis-placed and no matter what I did they would not drag to the correct spots or allow me to place things correctly.  It's mostly fixed in X1 from what I can tell.
I have not experienced any marker info being lost when restarting a project.  I could be 100% wrong, as I usually do not sto working till I'm done my transient work on a track for that very reason ;)

Thanks for confirming. It'll save me from trying workarounds that are unlikely to work. In light of how long this process takes it's not one of those things where I can just muck around with different methods quickly so it is appreciated. Cheers.

Nope! Copy transients and paste as midi for drum replacement is so hit and miss. For example, if replacing or layering a snare with a sample, I'll gate the track then bounce out to a new track. This cleans out a lot of unwanted artifacts. Transient detection is usually early and so the sampled sound is out of time.  
 
When it works it's brilliant. Mostly it's a waste of time If anyone has any clues about catering for that incorrect transient detection I'd be grateful.
 
Best
 
Gary