andy-chiles
Hi!
I had an idea of being able to navigate the browser to the bpm of the current playing song.
Something like browser_move “bpm” (instead of only “top” or “bottom”).
This surely depends on what column the browser is sorted…
To manage this it could first sort the browser by bpm and then move the selection to the current playing bpm.
(I think this has some advantages compared to filtering the tracks by bpm.)
But since we’re already talking about expanding the “browser_move” command, there could be some other options too.
Like navigating to the current rating, or files with the same file path or same artist…
All by sorting the browsers column and the going there.
But to be honest, the bpm thing would be the most interesting.
I had an idea of being able to navigate the browser to the bpm of the current playing song.
Something like browser_move “bpm” (instead of only “top” or “bottom”).
This surely depends on what column the browser is sorted…
To manage this it could first sort the browser by bpm and then move the selection to the current playing bpm.
(I think this has some advantages compared to filtering the tracks by bpm.)
But since we’re already talking about expanding the “browser_move” command, there could be some other options too.
Like navigating to the current rating, or files with the same file path or same artist…
All by sorting the browsers column and the going there.
But to be honest, the bpm thing would be the most interesting.
Posted 3 days ago @ 3:07 pm
locodog
browser_move is about moving tracks in playlists, don't you mean browser_scroll ?
I just made something with a virtualfx [available on all platforms], it found the right thing in near the bottom of a folder of 1000 in about a blink, folders of 10,000 it would be a couple of blinks. Because it's a button presses a button type of loop [to get the speed] it needs a 50ms break every 1000 queries.
I just made something with a virtualfx [available on all platforms], it found the right thing in near the bottom of a folder of 1000 in about a blink, folders of 10,000 it would be a couple of blinks. Because it's a button presses a button type of loop [to get the speed] it needs a 50ms break every 1000 queries.
Posted 3 days ago @ 5:30 pm
andy-chiles
locodog wrote :
browser_move is about moving tracks in playlists, don't you mean browser_scroll ?
Oh yes sorry, you are right.
My idea was to scroll to the needed bpms.
(I just saw the "top" and "bottom" thing in the description and thought it was what I searched for)
So your solution sounds like some good start if the devs don't want to give this a chance.
In case this gets not implemented, would you share your idea with me?
But again to the devs:
Of course I (or the people who like this idea) would prefer an official solution.
I think this would speed up the workflow while navigating through a lot of tracks.
Posted 3 days ago @ 6:30 pm
locodog
check PMs
Posted 3 days ago @ 7:37 pm
