Is AudioSnap going to work in X1C?

Can we get a hint from someone in the "know"?

I've been getting the impression that the latest hotfix left Audio Snap not working... or maybe it was the second to latest hotfix? One of the upfixes fixed X1's broken Audio Snap and upfix seemed to break it again... or something really confusing like that.

Each hot fix has info that lists what it fixes... but it doesn't seem like there is a list of what the hot fixes break.



Does anyone know if AudioSnap is going to work in X1C?

Will I need to send in a feature request?


best regards,
mike

What actual problems are you having?

+10db to +99db Clicks/pops when Audio Snapping with the '64 double precision engine' checked..... unchecking resolves this. I would prefer this option checked as I have a 64 bit machine and that's the whole point. 

 Also has issues with offline rendering when using all algorithms except 'same as offline'.  Not ALL the time, but randomly a line here or there will just not bounce down the same as you here it unless you use 'same as offline'.  I'm usually using it on a vocal when this happens and would much prefer to use the Solo vocal, or solo. 

I think the OP is implying that a previous update broke AudioSnap, so what is the situation with X1c.

yorolpal


I must be using AudioSnap all wrong (heck, I DON'T use it anymore at all).  All I ever did TRY to use it for was tightening up repetitive rhythm guitar patterns and I could never get it to work worth a dern for that.  I mean shoudn't you just be able to select an audio clip or track, select 16ths or whatever...hit quantize...and be done with it?  All I'd ever end up getting was a herky jerky, phasey crazy hodge podge of guitar which was markedly WORSE than before I tried to quantize it.  I always just reverted to my backup plan of just picking out the best measures I'd recorded and copy/pasting them appropriately...or just re-recording and actually PLAYING IT RIGHT:-)

I find it works best when adjusting the tempo of the whole track which I did for the first time last night.
Edit>SelectAll
View>Audiosnap palette>Toggle Clips to project Tempo
Change project tempo in control bar


The other thing I've used it for is tightening up bass/guitar to drums after extracting a groove to the pool from the drums and then quantising to the pool. It can sound like a 

herky jerky, phasey crazy hodge podge

but I find if you are extremely careful when selecting your transients to quantise you can get very very good results.

In the initial X1 release the snapping part of audio snap didn't work.

I recall that a bunch of people didn't notice the broken feature and/or said they don't use audio snap to snap...  A lot of people use audio snap as a wave knife clip splitter and that still worked.

Then I learned the snapping was fixed in an upfix.

edit to add:

X1B AudioSnap

• Fixed quantize
• Set Project Tempo from Clip is now functioning

Subsequently I have read several times that the snapping part of audio snap was unfixed with a later upfix.

I'm trying to figure out how that relates to X1C.


best regards,
mike

Blogman


+10db to +99db Clicks/pops when Audio Snapping with the '64 double precision engine' checked..... unchecking resolves this. I would prefer this option checked as I have a 64 bit machine and that's the whole point. 

Also has issues with offline rendering when using all algorithms except 'same as offline'.  Not ALL the time, but randomly a line here or there will just not bounce down the same as you here it unless you use 'same as offline'.  I'm usually using it on a vocal when this happens and would much prefer to use the Solo vocal, or solo. 

Has any of this been reproduced by anyone else? I'm not seeing any of it. AS still has some longstanding issues to be sure, but to my knowledge, nothing has changed in the core functionality one way or the other since 8.5.3, except the temporary breaking of Quantize and Set Project from Clip in X1, both restored in X1b.

"AS Quantize continues to work fine in 255 AFAIK."

That is very welcome news.

I love the snap part of AudioSnap!

Thanks!

Yeah, as someone said on the other thread, it could probably do some catching up with the competition in terms of the user experience and workflow type stuff. I'm used to it now, but it wasn't the gentlest learning curve I've ever experienced.

If you have to "hand adjust" your transients...is it really "automated"?

That's what I do. I keep a "live" audiosnap working copy of the track, and cut out bits for bouncing down. I archive that when I don't need to work directly on it so it's not using any CPU.

It strikes me that's probably good practice anyway, to make it easy to go back and re-work stuff if required.

This is what I am talking about.

These screen shots are from about 4 years ago:

They are zoom in images of two tracks that were cloned from a reference track that was setup for audio snap. What you see are the results of rendering with different algorithms.

At some places the results are in sync as one would expect.



At other places in the clips the sync drifts back and forth.







It's just a few samples here and there... but it's ironic that the very application meant to lock down sync seems to have some minor sync issues.

Anyways, I just brought in up in the context of my statements about an interest in exactitude rather than the results of the automated detection.



best regards,
mike

I see what you are saying.

I pretty much work clip by clip and move forward in a destructive manner. I leave lots of backup breadcrumbs by frequently doing "save as" saves and keep all the original audio files but I rarely recalculate a clip once I've moved on with a render.

Also, now that I am more familiar with the results of the algorithm choices, I don't really compare them any more. I just pick the suitable one for the task at hand and move along.

I also like to house keep my projects by clearing out all the transient info when that phase of work is over. I'll have all the older versions saved just in case but I like to think that, for example, after I have worked on the bass track that it is over and all the transient info is either rendered or deleted away and I make a fresh reference save as with a new version number (I do numbers/letter version naming like mysong_17k.cwp) so that my projects stay easy to open etc.

all the best,
mike