thanks, it reassures me that I'm not the only one who thinks that this option is largely improvable, thanks for the link! I don't know if VP22 is on the job to improve it quickly enough because it's a good idea and brings a real plus to the software! Excellent for your extension, I'll look into it. Aren't you the one who already provided me with a script to convert master vegas files and open them in older versions? I think so ;)

@davewire35 @zzzzzz9125,

I've been testing both Tempo and Beat detection and while I have found Tempo detection very useful for trimming video to the beat of the music I cannot find any utility for Beat detection. Magix VPX has a BPM wizard which I used as a basis for testing Vegas Tempo detection and both products produced the similar desired result.

As for Beat detection, it seems to apply markers to ever note played! Increasing the sensitivity slider actually reduces the markers which is counter intuitive to me. I would think increasing the sensitivity would produce more markers rather than reduce them. The problem is, I'm not sure what situation I would apply Beat detection. Is it suppose to be used in conjunction with Tempo detection? Its very difficult to determine what sensitivity setting one should use without a lot of trial and error and its not transparent as to what logic the system is using to apply the markers.

The VP22 New feature notes indicate that Beat detection would be logically used for music files but can be applied to any audio element. For music, I would probably use Tempo detection; not Beat detection. As for other audio, I'm not sure why I would use it. Identifying a door slam or explosion is probably easier without it.

I would be interested in members commenting how they intend to use Beat detection once it is finalised.

@davewire35 @zzzzzz9125,

I've been testing both Tempo and Beat detection and while I have found Tempo detection very useful for trimming video to the beat of the music I cannot find any utility for Beat detection. Magix VPX has a BPM wizard which I used as a basis for testing Vegas Tempo detection and both products produced the similar desired result.

As for Beat detection, it seems to apply markers to ever note played! Increasing the sensitivity slider actually reduces the markers which is counter intuitive to me. I would think increasing the sensitivity would produce more markers rather than reduce them. The problem is, I'm not sure what situation I would apply Beat detection. Is it suppose to be used in conjunction with Tempo detection? Its very difficult to determine what sensitivity setting one should use without a lot of trial and error and its not transparent as to what logic the system is using to apply the markers.

The VP22 New feature notes indicate that Beat detection would be logically used for music files but can be applied to any audio element. For music, I would probably use Tempo detection; not Beat detection. As for other audio, I'm not sure why I would use it. Identifying a door slam or explosion is probably easier without it.

I would be interested in members commenting how they intend to use Beat detection once it is finalised.

thank you for your feedback.

Are you sure that increasing the sensitivity of beat detection removes markers? When I increased it above 25% to test, it seemed to me that it gave me more markers. Like you, I have difficulty identifying where the markers are placed based on the curve and dynamics of the music.

Sometimes there are no markers where there should be, a key moment in the music (even in 25%). Currently, beat detection, as I said above, is not precise, often lagging behind the beat (a little but there is still a delay, for example on a drum kick).

I want to use this function for my vacation roadtrip films that I set to music, I set all my shots to the rhythm of the music like a video clip would. I was banking a lot on this function but given its lack of precision, I don't save that much time because I have to readjust more precisely.

@davewire35 said: "I was banking a lot on this function but given its lack of precision..."

Note that video will only change on a frame boundary. While you might want perfect precision in marker placement the actual location is determined by the Quantize To Frames setting.

What you see in the final render is determined by the frame rate of the source video and the frame rate of the rendered output. 60 FPS would give more precise results than 24 FPS.

I can feel the dew on the weeds all around me. Don't stop me if you've heard this before.

@davewire35

Are you sure that increasing the sensitivity of beat detection removes markers? When I increased it above 25% to test, it seemed to me that it gave me more markers.

I have attached two screen shots to demonstrate one at 25% and the other at 100%. On my system, increasing the sensitivity reduces the number of markers - which I find counter intuitive.

Currently, beat detection, as I said above, is not precise, often lagging behind the beat (a little but there is still a delay, for example on a drum kick).

I think what you are looking for, and what I found, is Tempo detection; not Beat detection. @john_dennis mentions Quantize To Frames which you disable temporarily to adjust your curser to the starting beat of your music. Help is very "helpful" in explaining how this is done with Tempo detection to improve precision. Start playing with Tempo detection with some of your music and follow the instructions in Help and you will improve the precision of your tempo beat markers. Below is from Help explaining the steps involved:

As for Beat detection, I'm still struggling to find a use for it....

@davewire35

Are you sure that increasing the sensitivity of beat detection removes markers? When I increased it above 25% to test, it seemed to me that it gave me more markers.

I have attached two screen shots to demonstrate one at 25% and the other at 100%. On my system, increasing the sensitivity reduces the number of markers - which I find counter intuitive.

Currently, beat detection, as I said above, is not precise, often lagging behind the beat (a little but there is still a delay, for example on a drum kick).

I think what you are looking for, and what I found, is Tempo detection; not Beat detection. @john_dennis mentions Quantize To Frames which you disable temporarily to adjust your curser to the starting beat of your music. Help is very "helpful" in explaining how this is done with Tempo detection to improve precision. Start playing with Tempo detection with some of your music and follow the instructions in Help and you will improve the precision of your tempo beat markers. Below is from Help explaining the steps involved:

As for Beat detection, I'm still struggling to find a use for it....

 

Indeed, strange the number of markers which is decreasing, I will check at home how it is going and tell you again but in my memories, I had noticed that it increased the number of markers.
For beat and tempo detection, for my part, it's really beat detection that I want to use. In addition, I use different songs on the same video so I would have to constantly change the tempo and the reference grids. I explained that I set my footage in relation to the rhythm but it can very well be offset from the tempo, imagine an off-beat break of a single guitar on which I would want to set my cut. In short, a little hard to explain but I play with the rhythm of the music and for me beat detection is supposed to alert me to important and rhythmic passages in the music. Overall, he spots them, what I just criticize him for is his lack of precision, he is always off by a few hundredths of a second and I spot it when watching. It's not the fluidity I'm looking for.

@davewire35

 Overall, he spots them, what I just criticize him for is his lack of precision, he is always off by a few hundredths of a second and I spot it when watching. It's not the fluidity I'm looking for.

I have attached two screenshots. The first is with Quantize To Frames enabled when Beat detection is generated. As you can see from the zoomed in waveform, Marker 5 is set just before the note; as you have experienced.

If you disable Quantize To Frames, and rerun Beat detection, Marker 5 shits to the right and is on the note.

My suggestion to you is to run Beat detection with Quantize To Frames disabled to see if it improves the precision enough for your acceptance.

Hello everyone .. I would like to know if I can delete\remove all or some settings for tempo detection? I selected "set as project tempo" and "enable snapping to grid" .. now I want to delete them and get the project at the very beginning.

Thanks.