I see two ways to fix the situation:
A) in the track context menu > BPM submenu, have a BPM conversion preview next to the conversion factors like 2/3 (174 BPM)
B) add a 'Tap correction' action to the track context menu > BPM submenu that opens a dialog that
* allows to tap
* multiplies BPM with all available fractions [2/3, 3/2, 4/5, 5/4]
* picks the one that comes closest to the tapped BPM)
okay, now I understand.
I see two ways to fix the situation:
A) in the track context menu > BPM submenu, have a BPM conversion preview next to the conversion factors like 2/3 (174 BPM)
B) add a 'Tap correction' action to the track context menu > BPM submenu that opens a dialog that
* allows to tap
* multiplies BPM with all available fractions [2/3, 3/2, 4/5, 5/4]
* picks the one that comes closest to the tapped BPM)
( detected BPM )
[ TAP button ]
( tapped BPM )
( assumed target BPM )
[ Apply ]
I think we should go with the BPM preview ;)
Imo the fractions we have available produce BPMs that are easy enough to distinguish, right?
From the library table, this would work for single tracks only though.