It does better job to find out these strange places that we want to manually edit for each track i.e the data is there and we want to edit it manually …
Well… this api can describe for each detected “section”
exact time when the section starts
exact time when section ends from the begin of the track
section duration
bpm
time signature
key of the section
Same for each bars:
exact time when bar start
duration of the bar
Like in the web example it describes
“bars”: [
{
“start”: 0.49567,
“duration”: 2.18749,
“confidence”: 0.925
}
This means that the
first bar of the track stats in 0.49567s
each bar duration is 2.18749s long with 92.5% confidence
By looking this data
‘Oops!..I did it again’ by Britney Spears, there is single bar with -1 BMP compared to rest of the track, just before the break, so it breaks djpro…
It would be nice if we could set custom downbeat colors for every 16/32/64/128 bars (Ex. Yellow, Red, Blue, Green, Cyan, Pink, Purple, Orange). This would help us identify where in the track there’s a break or a new verse.
Just wanted to wholeheartedly thank you all for the genuinely insightful and informative input you have provided on this topic. It’s a pleasure to see how this discussion has kept going since starting in August '22 and the amount of useful information featured in it
The Devs have already been looking into implementing multiple/custom beat-grids (originally brought up here in the Community), and I will make sure to pass the information from this thread on to them, as I am confident they will find it useful.
It’ll be our pleasure to keep you posted with any updates. Cheers
After replacing the BPM file with a backup, “Straight 165 bpm” fits as good as it can it seems
Both visually and audibly different from the “Straight 165 bpm” on my last attempt, where it was enough off to sound and look trainwreck level nasty.
Could it be some stuck input data, after to many tries?
I’v noticed that sometimes i need to reload a file to a deck before deleting a saved loop or cue point has any effect . . .
