Change Flex Time Original Detected Tempo?

When activating flex time on an audio track it looks like Logic goes by whatever tempo is currently active for the project to define what the original tempo is for that region of audio. Is there a way to tell Logic that the region has a different tempo after it has already been scanned with flex time?
I ask this because on occasion I will mix radio shows that use whole songs and I mix them in time to move with tempo changes for various songs. Sometimes I will be off by a small percentage as to what the actual bpm for a song is when activating flex time on a track. Because that is off, it won't match what the project tempo really is. I will then have to rename the original audio file to make Logic think it's a different file and then re-do the process with flex time. I would like to be able to change the source tempo for the region that has already been flex timed so that I won't have to keep re-importing the same audio to rescan it again and again with flex time.

I've been dealing with this today.
I needed to go from 87bpm to 89bpm. Set the tempo to 89bpm and turned flex time on and of course realized that I had to be in 87 for it to lock properly to the grid. I unticked the flextime box and went back to 87 and everything stretched. I then deleted all the markers (as there was not a rescan option) which solved the stretch issue but as there is no option to rescan I can't get any markers up. This upsets me deeply. This is about to give me an ulcer..
There needs to be an option to rescan for transient markers.

Similar Messages

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

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.

Changing Date Time Original Tag from Date Created Tag

Hi,
I need to change programmatically the "Date Time Orignal" tag by copying the "Date Created" Tag so that Media Encoder preserves the date during encoding. I can do this by hand without a problem in Bridget 5.5 but would like to automate it. Can I do this with a script?
Thanks
Axel

I have been als been plagued by LR displaying the capture time to be, say 3 AM (03:00), when I know I took the picture at 1 PM (13:00). I decided to try and see why this happens. With the help of Phil Harvey's exiftool, I can see that my Canon cameras embed the time into the EXIF data without any time zone information i.e.: Date/Time Taken = 2008:04:02 16:09:23.
Here is what I found:
If the image is now edited with Bridge, the information is changed to: Date/Time Taken = 2008:04:02 16:09:23-08:00 (time zone of the editing computer for the date the image was made. In this case the date was before daylight savings time started.)
When edited with GeoSetter (good for adding GPS information) the information is changed to: Date/Time Taken = 2008:04:02 16:09:23+02:00 (time zone for Cairo where the picture was taken.)
Lastly edited with LR, the information is changed to: Date/Time Taken = 2008:04:02 16:09:23-08:00
When the above images are viewed in LR, using PDT, they display the time as 17:09:23 except for the image tagged with the Cairo time, which displays 07:09:23. If the computer's time zone is changed the displayed time changes accordingly.
If the images are displayed with Photoshop CS3 all the times are correctly displayed as 16:09:23 as one would expect.
It appears that the factoring in of the time zone into the displayed time was a conscious decision by the Adobe designers. A decision that several of us are not happy with.

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?

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!

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: manual moving of some notes?

I'd like to select 3/4 notes of a guitar solo and move them up (because they are too delayed in relation to the tempo) but I can't find the way to do it. I only get a stretching effect on all previous notes. How can i do?

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?

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.

Logic Pro 9 Flex Time Problem

I have a problem with Flex Time.
When I start a new project, import a wave file, use Flex Time on it, everything works fine.
But:
When I start a new project by opening a midi-file, import a wave file, use Flex Time on it, the size and speed of the Wave-File changes.
You can check the screenshot. It is the same wave-file. One with Flex Mode on and one with Flex Mode off.
There are several tempo changes in the project and I think it has something to do with that.

I have a problem with Flex Time.
When I start a new project, import a wave file, use Flex Time on it, everything works fine.
But:
When I start a new project by opening a midi-file, import a wave file, use Flex Time on it, the size and speed of the Wave-File changes.
You can check the screenshot. It is the same wave-file. One with Flex Mode on and one with Flex Mode off.
There are several tempo changes in the project and I think it has something to do with that.

Leave Request - can't change the time of pending request

Hello,
We are trying to change the time of a pending leave request and when entering a new time in the duration field, the original time still shows up on the Review and Send screen. The leave request is for one day and for 5 hours - we are trying to change to 2 hours and 5 hours still shows up.
Is this an issue with the code or config? Any help is appreciated.
Thanks

is the note 1238028 implemented in your system?
have you done any modification
Depeding on your requirement you can decide how to use
PT_ARQ_REQUEST_CHECK ie hours field or the clock times.
That means you need to clear the time fields which are derived
from the work schedule and keep it empty since these fields
are hidden in your front end and no option for the pernr to modify
or correct the times.

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.

Date Time Original different in Lightroom and Bridge

Why is it that the Date Time Original in Lightroom is affected by whatever time zone the PC is set to? This is not the case in Bridge.
Example:
I fly from San Francisco to Washington DC and set my notebook's time zone from Pacific Time to Eastern Time upon arrival. I also make the necessary adjustment to the Time on my camera. I shoot a photo at 6pm in Washington DC, upload it to my notebook and import it into Lightroom. Lightroom shows a Date Time Original of 6pm. So does Bridge. So far so good.
I return back to San Francisco and set my notebook's time zone back to Pacific Time. In Lightroom, the Date Time Original of that photo is now 3pm. In Bridge, it still gives a Date Time Original of 6pm.
Confusing? Yes, especially when traveling across lots of different time zones. In some cases, the Date Time Original will change not only the time, but the Date as well (if the change crosses midnight).
Try it for yourself. Take a look at the Date Time Original of any given photo in Lightroom, change the Time Zone on your PC, and see the Time change for yourself.
Since Bridge and Lightroom are both Adobe products, I have to wonder why they display EXIF times differently. Is this a bug? Or intentional?

I have been als been plagued by LR displaying the capture time to be, say 3 AM (03:00), when I know I took the picture at 1 PM (13:00). I decided to try and see why this happens. With the help of Phil Harvey's exiftool, I can see that my Canon cameras embed the time into the EXIF data without any time zone information i.e.: Date/Time Taken = 2008:04:02 16:09:23.
Here is what I found:
If the image is now edited with Bridge, the information is changed to: Date/Time Taken = 2008:04:02 16:09:23-08:00 (time zone of the editing computer for the date the image was made. In this case the date was before daylight savings time started.)
When edited with GeoSetter (good for adding GPS information) the information is changed to: Date/Time Taken = 2008:04:02 16:09:23+02:00 (time zone for Cairo where the picture was taken.)
Lastly edited with LR, the information is changed to: Date/Time Taken = 2008:04:02 16:09:23-08:00
When the above images are viewed in LR, using PDT, they display the time as 17:09:23 except for the image tagged with the Cairo time, which displays 07:09:23. If the computer's time zone is changed the displayed time changes accordingly.
If the images are displayed with Photoshop CS3 all the times are correctly displayed as 16:09:23 as one would expect.
It appears that the factoring in of the time zone into the displayed time was a conscious decision by the Adobe designers. A decision that several of us are not happy with.

Changing the time of a jpeg file

I have Photoshop Elements 12 installed and am trying to convert the times taken of photographs taken whilst overseas. In those days I did not change the time on the cameras (Canon 20D and a Canon Powershot) to reflect the clock differences but have since learnt it is far easier to complete it at the time! The problem I face is that when I convert the photograph times; the two sets of JPeg files are not synchronising and the Powerhot JPegs are an hour behind. Given the lack of functionality in Window Vista and Windows Picture Gallery, these photo times can only be changed in Elements but when I do change them, the original file on the hard drive does not change accordingly. To get around this I have to change them in Elements to one hour later than actually shot. Does anyone know how to change the time simultaneously on the hard drive as with Elements? Its only a problem with the Powershot - the 20D is smarter!

Thanks for the reply and the suggestions. I changed the time of a Powershot file in Elements and used the file/write metadata to files as you suggested but with the same outcome - an hour's difference between what is in Elements and what is recorded on the hard drive. The messages stated metadata safely saved to file. I also checked the file properties - achive was ticked not read only....

Change Flex Time Original Detected Tempo?

Similar Messages

Maybe you are looking for