Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto DJ conditions to add newly scanned Library additions of a specified BPM to Auto DJ Crates. #14144

Open
GomuSkelly opened this issue Jan 8, 2025 · 2 comments
Labels

Comments

@GomuSkelly
Copy link

Feature Description

#14129

"With rule for accommodating exact bpm mults/divisions e.g. 320bpm/160bpm/80bpm/40bpm are all added, but exclude new Library additions with different bpm from the Crates."

Will expand on the description shortly.

@ronso0
Copy link
Member

ronso0 commented Jan 8, 2025

So this #13526 + the BPM filter, right?
(the "New tracks" crate can be set as AutoDJ source independently)

@GomuSkelly
Copy link
Author

GomuSkelly commented Jan 8, 2025

Nice. Yes if "New Tracks" can be set independently as AutoDJ source "#13526 + the BPM filter" appears to describe the main utilisation of this feature.

For the MozAIk use case #14129 , combined with #14143 the AutoDJ New Tracks Crate could be constantly replenished with generated material in realtime.

As mentioned in #14129 "Analyse provides a 80/160 BPM tempo for most material generated with "160bpm" in the text prompt. The material that generates at a random BPM, we just delete/hide from Tracks."

It would be useful to be able to transition to different Auto DJ Crates containing material of other BPMs. We found that aside from the generated material that Analyzes in Mixxx at 160bpm/80bpm, with lower frequency, over time there's still a considerable amount of material which generates/Analyzes at 106.7bpm from the 160bpm prompt, which has it's own distinct rhythmic qualities to mix with.

We've never seen anything approximating 53.35bpm or 213.4bpm generate, so it seems to be an odd quirk that 106.7bpm works well. Potentially other bpm/prompts will reveal odd or float numbered bpm's that work well, so our thinking is that the BPM filter could serve the dual function of scanning new Library entries for common BPM, and then add them to separate Auto DJ Crates defined by their BPM.

The option to group mults/divisions of the target BPM (e.g. for 160bpm - 320bpm/160bpm/80bpm/40bpm) in to a single AutoDJ New Tracks Crate, or parse each BPM into their own Crates would accommodate for the MozAIk use case and also have utility for other users as there may be situations where, for instance, 160bpm and 80bpm tracks would not pair well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants