Old 02-23-2019, 08:33 AM   #1
multibody
Human being with feelings
 
Join Date: Oct 2016
Location: Germany
Posts: 99
Default ARA-Tempo / artifical benchmark

Hi,
I still don't get the tempo ara- integration in reaper to do the same that melodyne does internally. I made a little benchmark audio file to demonstrate it. It is a simple loop of piano-melody and drums that increases in speed from 110 bpm to 150 bpm:



I rendered the Audio. When it is analyzed by melodyne the tempo has some oszillation at the transition. But nevertheless the melodyne-internal metronome never looses the beat throughout the whole file when turned on:



I would like to achieve two things in Reaper:
Case1: Import the tempo map and let the benchmark audio unchanged
- Project setting Timebase for items: Beats(position only)
- Import of tempomap through Reaper ARA-menu
Case2: Define the tempo in reaper and let melodyne stretch the audio
- Project setting Timebase for items: Beats(position, length, rate)
- Confirm detected file tempo in Melodyne -> changes reaper item play rate

Unfortunately in both cases the reaper metronome looses the beat of the audio. Maybe I am doing something wrong. The audio file and the reaper Projects for both cases can be downloaded here:

https://drive.google.com/open?id=1Ce...fQYTyvNALOttzn

I really want this to work - maybe someone has some suggestions how to improve the results.
multibody is online now   Reply With Quote
Old 02-23-2019, 08:55 AM   #2
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 9,839
Default

Can you also post an RPP that has the original REAPER tempo envelope? Case 2 does not seem to have that.
schwa is offline   Reply With Quote
Old 02-23-2019, 09:19 AM   #3
multibody
Human being with feelings
 
Join Date: Oct 2016
Location: Germany
Posts: 99
Default

Quote:
Originally Posted by schwa View Post
Can you also post an RPP that has the original REAPER tempo envelope? Case 2 does not seem to have that.
Sure, here is the inital project for the audio creation:
https://drive.google.com/open?id=1VD...6KveoTXOXDjegy

From my understanding in Case 2 the tempo map should not be in the Reaper project. In this case only melodyne knows the file tempo and stretches it to match the reaper tempo. Thats also consistent with the melodyne instructions here (Tempo-section):
http://helpcenter.celemony.com/daw/reaper

Quote:
Next select one of the following options:

“Confirm xxx BPM as File Tempo”: This tells Reaper to accept the tempo detected by Melodyne. This triggers Melodyne’s time-stretching and the tempo of the audio file is adjusted to match that of the song (slowing, in our example, from 117 to 83 BPM). Typical application: You are using an audio file (the tempo of which you do not know) and simply wish it to match that of the song
multibody is online now   Reply With Quote
Old 02-23-2019, 10:34 AM   #4
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 9,839
Default

I've asked Celemony for help understanding this issue. As far as I can tell, REAPER is importing the tempo map properly, but I agree that playback does not sync up the way it should. There may be some miscommunication between REAPER and Melodyne after the tempo map is imported.

[edit] ah, I've got it. REAPER is not properly accounting for the fact that Melodyne thinks the first downbeat is not at the start of the audio clip. This should be fixed in the latest development build, which was just posted.

Last edited by schwa; 02-23-2019 at 11:57 AM.
schwa is offline   Reply With Quote
Old 02-24-2019, 06:41 AM   #5
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 9,839
Default

multibody, if you come back to this thread, it would be great if you could verify that v5.97+dev0223a works as expected?

Information about prerelease builds is here:
https://forum.cockos.com/showthread.php?t=22836
schwa is offline   Reply With Quote
Old 02-24-2019, 07:20 AM   #6
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Germany
Posts: 6,623
Default

Great this issue is investigated !!!

I might be willing to buy Melodyne just for creating Reaper tempo maps for live recorded media.

-Michael
__________________
www.boa-sorte.de
mschnell is offline   Reply With Quote
Old 02-24-2019, 10:51 AM   #7
multibody
Human being with feelings
 
Join Date: Oct 2016
Location: Germany
Posts: 99
Default

Quote:
Originally Posted by schwa View Post
multibody, if you come back to this thread, it would be great if you could verify that v5.97+dev0223a works as expected?

Information about prerelease builds is here:
https://forum.cockos.com/showthread.php?t=22836
I did not have much time to check, but my quick conclusion is that case1 now works as expected. Thank you very much for the quick fix. Case2 still does not work correctly.

In my case2-project I tried to make Melodyne play the clip with constant 120 bpm. Melodyne is perfectly capable of doing this. I attached a melodyne-standalone project that plays the clip with constant 120 bpm and the click stays on the beat. This should also be possible with meldyne in reaper and the reaper metronome. Videos on youtube show how this works in Studio one: https://youtu.be/ix1FKDtfiUs?t=335

Another thing: You mentioned you use the offset between the beginning of the clip and the first melodyne-detected downbeat. As I asked in another thread, it would be really nice to get this value for positioning the clip and the tempomap correctly on the Reaper grid. Would it be possible to provide this value e.g. via api? Then a little script "positon tempomap and ara-clip on next downbeat of reaper grid" would be possible.
Attached Files
File Type: zip benchmark_melodyne_standalone_constant120bpm.zip (657.1 KB, 6 views)
multibody is online now   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 08:56 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.