View Issue Details

IDProjectCategoryView StatusLast Update
0008621ardourfeaturespublic2022-04-16 02:42
Reportermikelupe Assigned Topaul  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionno change required 
PlatformAllOSAllOS VersionAll
Product Version6.6 
Summary0008621: Feature Request: Timestretch by BPM
DescriptionIt 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 .

Tagstempo change, time

Activities

mikelupe

2021-03-16 12:53

reporter   ~0025603

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 .

paul

2021-04-22 00:14

administrator   ~0025734

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.

mikelupe

2021-04-22 08:07

reporter   ~0025756

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.

Thanks

paul

2022-04-16 02:42

administrator   ~0026398

see notes

anonymous

2022-04-16 02:42

viewer   ~0026399

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
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
2022-04-16 02:42 paul Assigned To => paul
2022-04-16 02:42 paul Status new => resolved
2022-04-16 02:42 paul Resolution open => no change required
2022-04-16 02:42 paul Note Added: 0026398
2022-04-16 02:42 anonymous Note Added: 0026399
2022-04-16 02:42 anonymous Status resolved => closed