Please Help!! I broke audiosnap and don't know how to repair it.

I feel silly suggesting this to a fellow Silver member, but there is a setting for sensitivity or threshold in AudioSnap. Is that all the way up or down? Try turning moving it significantly in the other direction.

I've always found the logic of AudioSnap convoluted a bit since it can be used for so many different timing/tempo/beat functions. It's a great set of features if the song was recorded to a click in the first place. If not, there is a chicken/egg problem I run into where the threshold/sensitivity wants to think on a grid, but the song isn't on one unless I've first defined some measures/beats so Sonar's measures and beats match the actual performance.

What I would love would be two modes of sensitivity/threshold:

1. Manual Threshold- what would be EPIC would be to have a view similar to iZotope RX where I could see the intensity of every frequency over time, like below, and mark the kind of information I want to trigger a transient, along with a threshold. Every time that pattern of sound was repeated for a particular frequency range (above a threshold I set), a transient would be generated automatically. In essence, I tell it where the kick is and it sets a transient marker every time that same pattern of sound happens. In this way I could take a drum overhead track and export MIDI for individual instruments easily by running the process multiple times while focused on sounds that are of a certain velocity at a certain frequency for a particular range of time. This would be truly brilliant.




2. Musical Time (basically combining the above with the way it works in Sonar now- a threshold based on musical time but the ability to view and move markers in this hybrid view.)

It is important to note that a user tweakable hybrid view would be better than a pure spectrogram (like in RX, it could be crossfaded by the user for pure waveform, pure spectrogram, or a mix of the two.) While the spectrogram gives a lot more information about the content of the sound, the waveform is better at pinpointing transients to the user. Thus, a hybrid view would be the best of both worlds.

Peace,

Tunes

Ha, thanks for the suggestions, but of course I tried moving the sensitivity. You cant adjust sensitivity on something that has not been selected. Thats the problem, none of the transients are being selected when you enable audiosnap on this track. When I hit "A" when selecting that clip, nothing happens. Also, when I go to View and select "audiosnap pallette", it opens but there is no transient button at the top of the audiosnnap pallete, like there normally is. Obviously I hit something somewhere, just don't know how to make it normal again.

Nope, thats not it either. Even if I copy the clip, and bring it into a different project, I still cannot get it to see the transients. But all other clips I try this on will work, in the other project.

Could I have accidentaly mad it a groove clip? It's just a kick drum from the kit I recorded last week.

I remember reading that you can't use audiosnap on groove clips, so hopefully thats what happened. I guess I could bounce it to clip and try then.

You didn't do anything, this is a bug in Sonar. I've emailed in pic of exactly what you're describing. (transients that shouldn't be there on every single beat, and won't go away even if you try to select and disable. try bouncing to clip and re-checking until you see it work right. (It's random, I notice it more on frozen tracks or bounced to clip tracks, but have seen it freshly recorded tracks as well... Cakewalk customer support told me to do my timing adjustments in 8.5.3 as it still works correctly there.

Thanks Blog,

Glad to see I didn't do anything wrong. I could not for the life of me figure out what I had done to cause this. Wow, they actually told you to do your edits in 8.5?

Just so I can get a handle on what you are seeing.....

1. You've set the edit filter to "Audio Transients"
2. You can see transients as hollow diamonds with tails? Everywhere, even on silence?

Here's a few ideas.

Do you have the pool active? Right click context menu with either the M:B:T or Clip options checked? Showing the pool? (Same menu)

Have you at any stage merged and locked markers?

What happens if you use the filter control? Turn down the threshold or adjust the resolution? Does that change anything?

If it is really screwy in every project on every track it may be something more than just audiosnap like an install issue.

The only time I've ever had issues with audio snap is working on tracks that haven't been tidied up and bounced down prior to turning audio snap on. As soon as you get any errant noises such as studio outtake at the front of clips audiosnap then becomes problematic because of the false transients that are there.

They can be the cause of the dreaded "Beats out of range" message. Trim the clips and bounce them or apply trimming before you do anything else and see if that helps.

 
 
 
This is what I get. Now I do have the actual transients from my kick track, but it also puts those other transients in there, almost like a metronome. And when I copy as midi, thos transients are copied also.  Last night i was able to salvage the track by going in and manualy deletint all of those phantom transients.

I get this to but can adjust them off with the Threshold being raised.  Your threshold doesnt turn them on and off as you slide it?

If it does adjust them off, delete the old midi track and remake with new markers.  Sorry if Im confusing 

Also, when I select my clip that Im adjusting, when I take the mouse and left click somewhere in the gray area off of a marker, the entire clip outlines in "white" showing the clip is selected.

I have seen and watch for the outline because you can have the track selected as seen in your pic but the clip wont be selected.

I have tried adjusting the threshold, and the section that you select 1/8th, 1/16th, etc, without any luck.

I am just hoping X2 somehow doesn't have this issue. I've learned to live with it and work around it, but I can see I'm not the only one.

Here's a link to my various correct and not correct bounces showing the same problem. https://dl.dropbox.com/u/...unced%20transients.PNG

Im not certain, but if I remember correctly, they act just as if they were rendered from the track, not manualy created. I can check that for sure when I get in the studio tonight.

fooman


No they are manually created because they can be deleted. As I understand, the track's "actual" trsnsients (created by Audiosnap) cannot be deleted, just disabled.

Yes that's correct.

But these manually-created notes appear simply when enabling the audio-transient filter within a track. No manual-intervention otherwise. At least in my projects I've had to work around it. It's truly an annoyance, not a show-stopper. 5 minutes of work around (or less depending on the amount generated), and you're golden.

What sort of material is it? I've never seen it but I have a very set routine and most of my use is on live drums, mainly extracting timing from improvised recordings plus tidying up here and there and the odd bit of drum replacement.
 
I discovered that to get the best out of audiosnap material such as that is best trimmed, bounced and then the clip map checked. Any none relevant noise at the front of the clip such as studio chit chat, generally confuses audiosnap.
 
I haven't used it extensively on much else other than moving the odd bits of bass, guitar etc around