View Issue Details
|ID||Category||Date Submitted||Last Update|
|0008621||features||2021-03-16 12:48||2021-04-22 08:07|
|Fixed in Version|
|Summary||0008621: Feature Request: Timestretch by BPM|
|Description||It would be a great feature to be able to timestretch (audio&midi) by inserting a target BPM value. |
For sure there will be some challenges concerning sessions with non-linear tempo. But this could be e.g. greyed out, if a session contains such kind of tempo changes, or there could be as well a "Target tempo:" field, if "Use initial session-bpm" is not checked .
|Tags||tempo change, time|
Corrigendum - the above issue description should be:
But this could be e.g. greyed out, if a session contains such kind of tempo changes, or there could be as well a "Initial tempo:" field, if _"Use initial session-bpm"_ is not checked .
doing this would require knowing the initial BPM, in order to compute the amount to change the duration by to achieve the desired BPM.
this information is not trivially available.
True, so there would be several options to get the initial BPM of an audio region, non-fixed BPM in a session clearly being a problem.
I'm just trying to get it together. In the case of a fixed BPM session, initial BPM for calculation could be defined by:
- let the user enter an initial BPM if he already knows it (when importing from Sample sets containing this info e.g.)
- using the session's BPM (user's responsibility, detect by tapping)
- (detect BPM of the region through an algorithm)
In the case of non-fixed BPM throughout the session, maybe taking the BPM at the recent playhead's location as initial value could be an option.
Anyway, it's not at all a stopper. Please close this issue, if it's not a prio.
|2021-03-16 12:48||mikelupe||New Issue|
|2021-03-16 12:48||mikelupe||Tag Attached: tempo change|
|2021-03-16 12:48||mikelupe||Tag Attached: time|
|2021-03-16 12:53||mikelupe||Note Added: 0025603|
|2021-04-22 00:14||paul||Note Added: 0025734|
|2021-04-22 08:07||mikelupe||Note Added: 0025756|