* The tree root element "next track hint" opens a proposal list for the next track on the right view. It depend on the current playing track, and the tracks loaded to the decks.
* The child elements are probe tracks for reference. The right view contains the proposal as if they where currently playing.
* You can add any probe track you like as child element by drag and drop. The last dummy element is only a feature hint for the user.
The proposal list itself is calculated with all useful properties of a track. I do not know so far what's the right magic formula is. Maybe we can get help from the IMMS team or re-use their code.
The problem here is that original IMMS learns from your personal taste. This will in most cases not fit to you audience taste. So we need the knobs or something different to tune the magic formula.
(The usability of the knobs might be a separate discussion because Mixxx use it extensively ;-))
The default value of each knob it 1. With these setting you will get a more or less fitting proposal list.
If you want to have only track with a small difference in BPM, you can turn up the BPM Knob and the magic formula will give you new proposal list with closer BPM value to the current track.
You are free to sort the list with a header click after that to pick the song wit the best BPM value.
Sometimes you might have a track couple or a better Idea for a next song, so you can resort the list manually by drag and drop.
This will create a rated association of the dragged track with the current track. The next time the magic formula takes this into account.
This rated association picks up Jens’s Idea of a “follower crate”.
Jens's cloud view might be the next step where the distance between the songs is a hint how exact the song will match.
Here is a brief explanation:
* The tree root element "next track hint" opens a proposal list for the next track on the right view. It depend on the current playing track, and the tracks loaded to the decks.
* The child elements are probe tracks for reference. The right view contains the proposal as if they where currently playing.
* You can add any probe track you like as child element by drag and drop. The last dummy element is only a feature hint for the user.
The proposal list itself is calculated with all useful properties of a track. I do not know so far what's the right magic formula is. Maybe we can get help from the IMMS team or re-use their code.
The problem here is that original IMMS learns from your personal taste. This will in most cases not fit to you audience taste. So we need the knobs or something different to tune the magic formula.
(The usability of the knobs might be a separate discussion because Mixxx use it extensively ;-))
The default value of each knob it 1. With these setting you will get a more or less fitting proposal list.
If you want to have only track with a small difference in BPM, you can turn up the BPM Knob and the magic formula will give you new proposal list with closer BPM value to the current track.
You are free to sort the list with a header click after that to pick the song wit the best BPM value.
Sometimes you might have a track couple or a better Idea for a next song, so you can resort the list manually by drag and drop.
This will create a rated association of the dragged track with the current track. The next time the magic formula takes this into account.
This rated association picks up Jens’s Idea of a “follower crate”.
Jens's cloud view might be the next step where the distance between the songs is a hint how exact the song will match.