![]() |
|
|
|
#1
|
||||
|
||||
|
I want to create a BPM extraction tool for VSXU. Has anyone had any particular success or better results from any particular formula?
We can extract a bass bpm from a 10 band eq or 2 band low/high.
__________________
|
|
#2
|
||||
|
||||
|
There's a somewhat usable example in the Bass_Fx extension to the Bass Audio Lib. You can basically set it up with a callback function that will be called at a fixed interval with the current BPM. It's not terribly accurate when doing it realtime, but it's pretty good when processing an entire audio stream.
__________________
<a href="http://www.haivision.com/products/coolsign">CoolSign</a> CoolSign |
|
#3
|
|||
|
|||
|
Hello,
The Bass.dll as johnnylocust said is very good and easy to implement. I purchased a 1-Software Distribution License for 100 bucks and I'm very happy with it. Stex
__________________
per aspera ad astra |
|
#4
|
||||
|
||||
|
Ok so it acts like an FFT essentially. Nice- I guess thats what I've been looking for but alot of mulah for an open source project (I wonder if they have a concession
I probably want something reasonably accurate in realtime. Most of vsxu drives on opengl so theres a little more cpu to play with than a regular vj app.
__________________
|
|
#5
|
||||
|
||||
|
I'm looking at Bass and Bass_FX at the moment. It seems pretty accurate, granted it gets lost in areas and particularily heavy parts of electronic music though. However it seems like a good solution when coupled with some of your own program logic to interpret expected future beats and a manual override / tap to re-align things. This is what I plan to do in the near future.
|
|
#6
|
||||
|
||||
|
Quote:
__________________
<a href="http://www.haivision.com/products/coolsign">CoolSign</a> CoolSign |
|
#7
|
||||
|
||||
|
I just got BASS working under OsX in c++. It was medium / difficult for me (im very newbie programmer really) but it was not that hard... just a matter of piecing together from the documentation. Unfortunately I couldn't find a tutorial, but I'm starting to realise this library is self documenting because its functions are self explanatory.
|
|
#8
|
|||
|
|||
|
Quote:
![]() stex
__________________
per aspera ad astra |
|
#9
|
||||
|
||||
|
well, only tests and experiments at the moment... but eventually a much larger system.
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|