• SONAR
  • [Workaround] Seriously, WHAT IS THIS with AudioSnap (p.2)
2014/06/18 09:39:55
dlion16
+1 threshold
2014/06/18 10:16:37
Anderton
Silicon Audio
Anderton
... I presume the AudioSnap engine is similar to loop construction, where markers are sometimes placed even where there aren't transients as reference points to provide less intrusive stretching...

That's certainly not my experience with audio snap.  Where there are no transients, there should be no markers.




I've never seen it THAT defined, but I don't know what his settings are and I don't use AudioSnap all that much. I usually set the Threshold lower than normal to add more points. As I use AudioSnap mostly to do manual stretching of individual transients, this is helpful because the section being stretched is smaller.
 
The reason I brought up loop construction is that if I have something like a sustained pad, there will be a marker placed at the attack transient. However, I often "force" transient markers to every (for example) 1/4 note so the stretching is more consistent over a wider tempo range.
2014/06/18 14:38:50
SvenArne
Yup, I was able to reproduce this in the first project I opened!
 
This song is played free tempo, so nothing should align with the time ruler (tempo=120 bpm). Select the "kick" track, change 'edit filter' to 'Audio Transients' and the markers appear exactly at the beats (according to the time ruler). Go into 'edit map' from the AudioSnap palette and change "beats in measure" to a random number and then back again to "4" and the markers now appear at the audio transients as they should! 
 
I remember having to do this with every drum and bass track in some other unreleated project a while back (probably on X1 at the time). 
 
Sven
2014/06/29 10:54:55
Dyonight
SVEN YOU GOT IT!!!! YEAHHHHH!!!!!!
 
You're officially my saviour!!
 
It was ruinning my workflow I can't express how much!!

Having a marker on every beat and sometimes just before the actual hit prevent the "good" transient from snaping to the grid since the "phantom" marker is already there.... and they are immune to the Treashold setting so I had to manually disable them all!!!!
 
(Drag the picture in an empty space in the top of your browser to have it in full size in a new tab)
 
 
Here are the steps that Sven kindly provided!
 
1. Select a track
2. Change 'edit filter' to 'Audio Transients' and the markers appear exactly at the beats (according to the time ruler).
3. Go into 'edit map' from the AudioSnap (press "A") palette
4. Change "beats in measure" to a random number and then back again to "4" and the markers now appear at the audio transients as they should! 
 
Sorry my version is in french but you'll get the idea.
 
Thanks A LOT!!!!!
 
(Got the image thing at last :D )
2014/06/29 11:46:39
Anderton
Another reason why I love this forum. Thank you Sven for the workaround!
2014/06/29 18:57:08
Splat
So this is a bug and not by design one would assume?
Can somebody report it in Cakewalk problem reporter and let us know the issue number?
 
Cheers!
2014/06/30 11:24:17
Dyonight
I've reported the behavior a couple of times but now that I can explain the workaround I'll send another one right now!
2014/06/30 11:59:35
SvenArne
Glad I could be of help! 
 
I didn't file a bug report way back when, since I wasn't able to consistently reproduce it, nor had I completely ruled out user error.
2014/06/30 12:11:44
Dyonight
"Submitted to Development"
2014/06/30 12:17:23
Splat
Thanks Olivier! Would you mind pasting the CWBRN number here? Cheers..
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account