FL Edison 2 messes the file Bpm

Audio Plugin Hosts and other audio software applications discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

Can anyone explain this strange behaviour:
Set up:
My Live is set for 48 kHz/24 bit.
Edison is set for 48 kHz /32 floating bits (doesn't have 24 bit option)
Live tempo is 111 Bpm
Edison is set for host synced tempo, and shows the same 111 Bpm

I put the Edison (ver. 2.2) to the Live's audio track and record some loops. Playback in Edison, Live hosted sounds all OK.

When I drag the file from Edison to the Live, Live recognizes the file tempo 148 Bpm (!), and if the Live's auto warp is on, it messes the file tempo, when the host has 111 Bpm.

Turning the auto warp off keeps the file in the OK tempo, but if I want to use warp, I have to manually edit the file tempo to Bpm 111 (which it originally, as recorded in Edison, should have been).

Question: Where's the clue?
And: does the above procedure decrease the file quality? :?:

Post

Just a guess:

Live does calculate the tempo of a file (loop) from the file´s length guessed to a meaningfull tempo/grid...

This means, if the length of your dropped file isn´t what Live is expecting (1 bar, 2 or 4 bars) but perhaps 3 bars long... Live´s tempo calculating fails and you have to adjust manually...
This would happen to any file (with for Live "odd" file length) you drop into Live and is not related to Edison... i.e. Live always fails with audio files of FX sounds with a long reverb tail which got a "tempo" but because of the tail not a corresponding file length...

Post

Hmm... I don't get this explanation, because the file recorded in Edison is made by looping a background file at the same time in Live, both files, after the recording, should have the same lenght and be based to the samw Live grid.
But some incompability there is, that's sure.
This can be fixed, as described above, but I wonder how this affects to the file audio quality?

Post

As I said... just a guess...

Just curious: How long is the recorded file from Edison?? Is it exactly 1, 2, 4 or 8 bars long???
Asking because it depends when you stopped the recording in Edison..

Post

Harry_HH wrote: Thu Aug 01, 2019 8:58 am ...but I wonder how this affects to the file audio quality?
As you just reset the time stretching, it shouldn´t affect the audio quality at all.

Post

Thank you for commenting.

In this case the file lenght is 5 bars. As said, the file was created by letting the background file loop in the Live, Edison was set recording in other track, and the Edison made regions depending how many times the background file was looped. I guess this is one of the most common ways to use the Edison.
It lets you make as many "takes" as you wish, and you can choose the best, or even edit the final file from many different takes.

BTW, this was easy when I had Logic, it has a mode, which created always a new track for each take automatically. Live is missing that feature, but Edison takes care of that, basically.

Post

Hmmm, I´ve no idea... if I make a 4 bar loop out of a 5bar 111bpm loop (that is what Live likes to do: assuming a loop would be either 1, 2, 4 ...etc... bars long and warping it like this...) I end up with a tempo of 138 Bpm but not 148 Bpm like you say Live identified...

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”