Beatmapping flex time quantise

I have a freely recorded acoustic guitar part.
If I were to beatmap that acoustic guitar part, such that sometimes there is a tempo change at about every bar, and in some places quarter and half notes with in a bar.
Eg: during any three bars (4/4) there may be 3 tempo changes, or 12.
Now, I track a bass part that contains whole notes.
When I enabel flex time on that bass guitar part, to go about quantizing it to the grid I have created using beatmap
It doesnt work.
I have blue tempo flex markers within the region, and when a sustained bass note plays over one of these tempo markers it alters the sound.
I also have problems if I ignore that issue and attempt to quantize the part.
So my question, is anyone really succesfully using beatmapping and flextime in the way i describe?
I would dearly love for it to work.
(note I have gone in and removed tempo info from the audio file and replaced it till I am blue in the face....)
cheers
Wiz

Flex + tempo changes is troublesome. One thing you might try is to hover over one of the blue markers in the bass part, and hold option, you'll notice the cursor change. This is the "move the flex marker" cursor. Making sure that you are over the top part of the region, you can slide the blue marker so that it sits on a transient area better, it will turn it into a regular flex marker at this point. Note that if you do it on the bottom half of the region you'll create extra markers and accidentally move audio you didn't mean to.

Similar Messages

Flex Time error: Too many disk I/) tasks (Elastic Audio)...

I've been using flex time to take a sample in straight time and make it swing, but I've been having playback issues. I get two different error windows 1) Extreme compress factor detected during playback (Elastic Audio) (-10025) and 2) Too many disk I/O tasks (Elastic Audio). Also, I occasionally get a loud static sound when playing the sample. I don't have this issue when in Flex mode if I only loop the sample twice, but if I try to loop it more than twice, I'll get the errors and/or the static sound. At no point do the stretches make the audio color red, so I don't think I'm over-stretching or over-compressing the audio Is there any way to solve this? Does flex time have limitations to the number of markers used?

Yeah, the I/O error is because you're basically pushing it too hard, it can't read what you're doing fast enough to process it. I got this the other day when I was trying to use flex within a take folder over multiple comped takes.
If you want to swing the audio, why don't you cut it into regions, send it to the EXS 24 and then quantise the samples with swing in the piano roll. That way you're not putting so much pressure on the processor.

Basic Flex Time Editing

I think this is probably the most basic thing I could ask for help with regarding Flex Time. I have an audio track which is a recorded metronome click that I brought over from another DAW. It's in perfect time because it was generated by the DAW itself. At the end of my song, there's a ritard in the rest of the audio tracks, and I would like to slow the click track down to match. Right now the click track is not slowing down at all.
I used Beat Matching to align the tempo to the ritard, and Logic's internal metronone matches perfectly. Now I want the audio click track to match Logic's metronome. I figure I'd use Flex Time for this.
So I turn on Flex Time for the click track and after analyzing the track, Logic moves all of the clicks to a position that I would call "off-beat." This doesn't make sense to me because they were "on-the-beat" before -- from my perspective as a listener and also verifying visually.
I don't want to have to adjust every click. They were fine before. It's just the end that I want to adjust. What should I do?
Message was edited by: racingheart

welshwiggle wrote:
I tap in a manual click for the whole song, beatmap it and it works great.
Then , I foolishly think to myself, I'll just 'tighten up' the drums and bass a little using FutzTime and........DISASTER.
Anyone since Feb 2011 actually got Flex to work well in this way?
Hi,
I don't think there's a need to add a manual click to make this work. Just do the beat mapping before you do anything else (no Flex active, no tempo changes added to the files from previous attempts of making this work etc).
For simplicty, please try this with only one track:
Record something without a click in an empty song.
Use Beat Mapping to make the grid match the audio, and BIP (Bounce-In-Place) that file.
Now, try to correct the hits that ar still out of time, using Flex and either the quantize function or manually edit the regions.
If this doesn't work as expected, what exactly goes wrong?
Note that if you totally beat map the region (every note in the region) befor eyou quantize, quantie won't do anyhting, because all the notes atcually already match the grid - as a result of the beat mapping.
If you explain actually what you want to do - and what goes wrong, it will be easier to help you out.
ETA - the reason I don't think adding a manually played click before you start the quantizing process is a good idea is that such a click rack will add small timing changes. As a result of this, Logic will, when quantizing, try to move a lot of notes to your click ven if they were perfectly fine, simply because your click positions aren't identical to the original note positions.
Message was edited by: ZXC

Flex time editing

Should I bounce each flex time track edit before performing flex time editing on other tracks?

welshwiggle wrote:
I tap in a manual click for the whole song, beatmap it and it works great.
Then , I foolishly think to myself, I'll just 'tighten up' the drums and bass a little using FutzTime and........DISASTER.
Anyone since Feb 2011 actually got Flex to work well in this way?
Hi,
I don't think there's a need to add a manual click to make this work. Just do the beat mapping before you do anything else (no Flex active, no tempo changes added to the files from previous attempts of making this work etc).
For simplicty, please try this with only one track:
Record something without a click in an empty song.
Use Beat Mapping to make the grid match the audio, and BIP (Bounce-In-Place) that file.
Now, try to correct the hits that ar still out of time, using Flex and either the quantize function or manually edit the regions.
If this doesn't work as expected, what exactly goes wrong?
Note that if you totally beat map the region (every note in the region) befor eyou quantize, quantie won't do anyhting, because all the notes atcually already match the grid - as a result of the beat mapping.
If you explain actually what you want to do - and what goes wrong, it will be easier to help you out.
ETA - the reason I don't think adding a manually played click before you start the quantizing process is a good idea is that such a click rack will add small timing changes. As a result of this, Logic will, when quantizing, try to move a lot of notes to your click ven if they were perfectly fine, simply because your click positions aren't identical to the original note positions.
Message was edited by: ZXC

Flex Time with variable tempo not working correctly.

Hey,
Has anyone else noticed that Flex Time doesn't work as intended if you have variable tempo?
To clarify, I recorded a band playing their song and then figured out their various natural tempo changes and adjusted the Global Tempo Track accordingly.
Then, the drummer recorded his part to a click on that track, obviously keeping with the natural tempo changes that the band played to.
Quantization of MIDI works just fine, as in, it matches the increases and decreases in tempo.
However, attempting to quantize an audio track using Flex Time does not work properly.
I was just wondering if there is something that I'm doing wrong or if this is a known bug.
Thanks,
William

Thank you for your answers!
But there are several Problems using a dummy field in an IDOC structure. We have got a naming convension so that we can't create an IDOC-like structure named ORDRSP.ORDERS05.
But perhaps I am thinking to complex and there is an easier way to add a dummy field to an IDOC structure.
Could you perhaps also suggest a solution for that dummy field problem?
Many thanks and kind regards,
Steven

GarageBand 11 - Flex Time a real pain in the ****

Ok, in GarageBand '09 I was able to cut bits out of a MP3 file mainly from acapella but when I try do do it in GarageBand '11 I just can't do it because of this stupid Flex Time crap, it just keeps wanting to turn it on all the time and you can no longer cut out bits from MP3s I absolutely hate it. Anyone know what can be done yet?

Is anyone else puzzled as to what this zero line actually is. If I knew that it would be a lot easier to click below it.
The middle line in the track editor.

What does "Analyze audio for flex time editing" in Garage Band? It's taking so long(3 days)! and I can't shut down my pc.

What does "Analyze audio for flex time editing" in Garage Band? It's taking so long(3 days)! and I can't shut down my pc.

Did you ever figure out what was going on? i've got the same issue.
I record 2 hour choir practices then edit the talking out to make more useful accompaniments for personal practice. During my editing process my MacBk Pro (0r GarageBand) decides it needs to "Analyzing audio for Flex Time Editing". It will finish doing it and immediately start over again. I can not cancel it so I just have to force quit Garageband and lose eveeryrthing I have editied since my last Save. I've shut my mac totally off and rebooted and to no avail. Any suggestions?

Flex time and minor tempo adjustments

Hey y'all!
So I'm working on a project in which vintage analog synths were run through tape before being digitized and brought into logic. Because tape is tape, this introduced some drift into the tempo. Instead of it being a nice clean 120bpm, it's 120.0103 and I want to use flex time to slow it down by 0.0103.
So when I have the flex algorithm set to polyphonic (or anything other than "off") and I have my flex markers in place, I'm expecting to see that when I change the project tempo to 120bpm, the waveform turns orange, indicating that the audio has been stretched.
The audio is NOT turning orange and when I listen to it, it doesn't sound like any adjustments have been made. Is Logic just disregarding this tempo adjustment as negligible?? Or is it actually stretching the audio but there's just a bug in how it's being displayed?
Thanks in advance for any help y'all can provide!

is it actually stretching the audio but there's just a bug in how it's being displayed?
Logic is indeed stretching the audio. It's just not showing the color change. This is because the tempo change is so slight. You will notice the same thing if you drag the edge of the region to cause a tempo change to only this region. If you zoom in close in order to make a very small change, you'll notice that the color change doesn't happen as soon as you start dragging. The color change only appears after your dragging creates a change of a certain magnitude.
So it's the same phenomenon, whether you're changing the project tempo, or just changing the tempo of one region. The threshold seems to be about 0.5%. Is this a bug, or is it just a design choice? I think probably the latter.

Hey Guys, problem with Flex Time.

Hey Guys,
i have a problem with Flex Time. I was searching for a way to copy my 1-Tackt Timplin Beat to make 12 out of it, but there were always "wholes" between the new inserted regions. So i found Flex Time, but then when i choosed a Region, pressed the Flex Time button, nothing happend, except that the Header became a little bit bigger, as if there would been added a few more options, but there came only more free space .
Would be great if somebody could help me!:)

I would suggest Option dragging the bottom right edge of the Region so it fits precicely to the grid, then copy. This is a quick way to time stretch...

Flex Time Creates Random Pops

Flex time is creating random pops after just minor correction of a monophonic bass line. The pops vary depending on where the playback starts in the file and they are recorded into merged or bounce in place audio. No plugs on the channel either.
Bob

I am getting that exact same problem too. A bass line that after using Flex time on, would randomly get clicks on it. I think it's doing it to the guitar lines too.
What seemed to work for me was changing the Flex time setting from Monophonic to Slicing. It kind of defeats the purpose of Flex time, but at least it sounds right again.
Hope Apple fixes this soon!

A Flex time success story

I posted this in the Logic Express section but it's also related to Logic Pro so I wanted to make sure users of Logic Pro who may not check out the LE section hear about this success.
I’ve run into some surprisingly great Flex results recently. I’m not a professional recording engineer, I’m a gigging multi-instrumentalist musician and home song writer. Over the past decade I’ve been recording on a Korg hard drive 16 track recorder. (Great home equipment for it’s time and expense) Unfortunately I no longer have the unit and the only recordings I have of those songs are mixes of the 16 tracks mastered to stereo. I play mostly Prog-rock and because some of the parts I played on some instruments were a stretch for my abilities some of the timing of some of the parts were not as tight as I would have liked them to be. Still I transferred all my songs to my iMac and Logic Express 9. (BTW Logic Express IS a serious recording program on par with Logic Pro in the majority of it’s functions, it‘s NOT just a better version of Garage Band.) My goal was saving these tunes and also to see if I could help the mix out a bit. I couldn’t totally re-mix because the tracks are mixed stereo and can‘t be separated but I thought I could tweak and compress. ANYWAY … a few songs had parts that were not perfect in regard to timing so I decided for yucks to try FLEX on these stereo tracks. Mind you I’m talking about ONE stereo track that’s a total mix down of 16 tracks from a prior hard drive recorder. I had the track analyzed and quantized It using polyphonic at 1/96 and I’m totally shocked at the results!!! I didn’t think the program would be able to help timing on lets say a guitar part without destroying a drum pattern played in the background or making something sound strange but it did it!!! I actually have a tune played in 15/16th with a LOT of odd timing interplay and Flex fixed all my little guitar timing imperfections without making the underlying instruments sound out. I don’t know how the program did that considering were talking one single stereo track with 16 tracks of instruments all recorded on the track but it worked wonderfully. HECK … I haven’t been happy using Flex and quantize on a simply kick drum part but the function worked wonders on a track that I thought was unfixable.
Anyway much of what people write are in regard to problems they are having. I thought I would share my GOOD NEWS with you for a change!

I also has this problem but it didn't happen when undoing a Flex Time edit and it only happens occasionally. I reported this a bug to Apple with the crash report. But the bug you have witnessed might be slightly different than the one I witnessed. Try reporting this bug to Apple via http://bugreport.apple.com/ and attach the crash report with it. The Crash Report is located at Library > Logs > CrashReporter. It will start with GarageBand and then the date. Choose the latest one. Attach it in the report (in the Configuration Information section). You should also include a System Profiler Report:
To obtain a full System Profiler Report, select "About This Mac" from the Apple Menu and click the "More Info" button. This automatically launches the System Profiler application. Once the System Profiler application has been launched please follow the steps below:
1. Select "View > Full Profile" from the File menu (cmd-3)
2. Select "Save" from the File menu (cmd-s)
3. Keep the format as 'System Profile'
4. Click the "Save" button
A System Profiler Report can also be obtained via Terminal using the following command:
/usr/sbin/system_profiler -detailLevel full -xml >mymachine.spx
This command will create a full System Profiler Report, named "mymachine.spx", which will open in System Profiler on another machine.
Please attach the file to your bug report (under Additional Enclosures section). Depending on how your ranked the report, Apple should see it within the next few days. Also note that even though Apple doesn't reply to your report doesn't mean they didn't see it. Apple's Developer section is always busy with bugs that they don't have time to reply to every single report!
Bo

Is there a way to completely undo all flex time mods to an audio file?

I have an audio drum track that i thoroughly destroyed messing around with flex time and audio quantizing. I believe these are nondestructive edits, but i can't find anyway to get it totally back to its original state. Is this possible?
Thanks

No you can bounce in place and ease processing..
but thats still non-destructive cause logic creates a new file.
I'm sure our friend has a file about somewhere just doesn't know how to get to it
TXBDan are you looking for the audio file name thats the same as your region file?
If so than try remembering what the original file was called and look for that.
if you can't remember the name than try organise the files by date in your audio file folder and checking the files that were created on the day of the recording..

Need flex time help, lots of songs, lots of BPM's multiple tempos

Newbie here, trying to finally make the switch from Pro Tolls to Logic and flex time really sold me but I'm having some growing pains that I need to speed up for my current project.
I have about 20 songs that I need to:
first, find the bpm for each (quickly)
second, be able to mark them in a way that the bpm for each song would change to match the tempo track (which will fluctuate through out the editing process)
third, some how still have control of the anchor point in flex time which seems to get locked
In the end I am trying to create a remix of multiple songs that start off with different bpm's and fluctuating tempo.
I am able to do most of this but I think I am missing some steps, or perhaps the order of steps, that would make this process go much faster. I have worked other programs such as Ableton Live and elastic time in Pro Tools and at times it seems I can handle whole songs better in those programs than in Logic but I'm sure it more user error than the actual program.
I welcome any and all suggestions. Thanks.

Received this advice and responded on another forum but still need help.
Thanks for the response!
Had a few problems trying your suggestions.
*"Finding BPM: select the audio region and choose from the local Arrange area menu: Audio > Detect Tempo."*
Since it is a whole song and not just a part, such as drums, with well defined transients, it either can't detect the tempo or when it does it is wrong.
*"Make it follow the tempo track: Use Flex Time (in the track parameters, choose a Flex mode). "*
This would be fine if I didn't have to redefine all the transient markers as correct flex markers. Since Flex Time has problems defining the correct transient markers for complete songs it can be very time consuming.
Maybe I'm still missing something?
*"Third: what anchor? Do you mean the transient? Or the flex markers? You can move the transients in the Sample editor, and the Flex markers right on the track in Flex view (Click the Flex button in your toolbar)."*
The audio region anchor in the sample edit window, the orange arrow. I think this is some how turned off after turning on flex time and I am unable to move it. I use this to line up the first beat if there is something before the music starts, such as someone speaking or a lead in with a different tempo than the song tempo, that I would still like to keep. That way I can move the region in the arrange window and it will line up according to the first beat and not the beginning of the region. Am I making any sense?

Enabling flex time speeds up my track

Hi guys,
I have this problem with some frequency. I enable the purple "Flex time" button for a track, and the track instantly slows down. Here's a screenshot that sort of shows what happens:
As you can see, just clicking that purple button slows the track considerably. I want to start editing with the track at the existing speed.
There are no flex markers in the track
I've tried Edit->Tempo->Remove Tempo Information From Audio File and it had no effect on the behavior

Hi Thi Thach,
You're having the same problem as me. You'll be happy to know that I solved my problem.
(Albeit at the expense of keeping my Mac user profile linked to my Apple ID)
The shutdown delay is due to a file called:
"com.apple.coreservices.appleid.authentication.plist"
It is located in the folder:
"/System/Library/LaunchAgents/"
You have to trash that file (the OS will ask you for the admin password) and then restart the system. After that, all shutdowns will become very fast as there will be no 20-second delay.
This file is responsible for linking your user profile on the Mac with your Apple ID. Apple gives you the option of linking them so that if you forget your login password on the Mac, you can reset it by using your Apple ID.
Once you trash that file and restart the system, if you go to "Users & Groups" under "System Preferences" and look at your user page, you will find that the system forgot your Apple ID that you associated with your user profile. Instead, next to where it says "Apple ID" on your user page, you'll find a button called "Set". If you set it again to your Apple ID, the shutdown delay will come back.
If it's important for you to keep your Mac user profile and your Apple ID linked, then don't trash the file and just live with the shutdown delay.
Of course, this process is fully reversible: You can always return the file where it belongs and restart and you'll be right back where you started.

Loving Flex Time

For the past few days I've been editing vocals for the first using flex time for a remix. the original tempo of the song was around 89-90's. I wasn't provided the original tempo. But my remix is 120 I imported the vocals put the tracks on Polyphonic and they pretty much snap to where they should be at a 120 tempo and moving vocals around for different phrasing is a blast. This remix would have been a breeze if the vocals were delivered separately as lead and stereo backgrounds but was delivered as one stereo file lead and backgrounds together.

I am getting that exact same problem too. A bass line that after using Flex time on, would randomly get clicks on it. I think it's doing it to the guitar lines too.
What seemed to work for me was changing the Flex time setting from Monophonic to Slicing. It kind of defeats the purpose of Flex time, but at least it sounds right again.
Hope Apple fixes this soon!

Beatmapping flex time quantise

Similar Messages

Maybe you are looking for