Apply Flex-Time Changes to Project?

I adjusted the tempo of my project by activating the Flex option on all tracks. I submixed all those in a Track Stack so I could then work on a vocal track at the new tempo. The first thing I noticed is that though Flex is turned off on the new vocal track, it turns itself on and insists on evaluating the track each time I record, a bit of a nuisance. I figured it must be because all those original tracks in the Track Stack still had Flex turned on. So I turned them all off, but the tracks all went back to the previous tempo, so I had to turn them all back on.
The question is: Once we've made a tempo adjustment using Flex, how do we apply that change permanently to the project so that we can turn off Flex on all tracks?
Thanks.
Cayce

The question is: Once we've made a tempo adjustment using Flex, how do we apply that change permanently to the project so that we can turn off Flex on all tracks?
Bounce the Tracks in Place.....
Logic Pro X: Bounce a track in place

Similar Messages

  • 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.

  • 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.

  • 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?

  • 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.

  • Flex Time vs. Melodyne - which one first in your vocals workflow?

    Hi all,
    I am curious about what workflow you guys have with vocals.
    The first steps after recording (and perhaps multicomping) the different layers/tracks, are to me pitch-correction in Melodyne and time-correction with Flex-Time (built into Logic pro).
    Which one do you guys do first?
    I haven't yet got enough experience to judge  with much certainty which way serves the recorded audio best.
    Myself, I currently go melodyne on one vocal track at the time, snap-to-pitch off and adjust pitch by ear with the music tracks as guide.
    Sometimes I push formants around, in particular if there's a high note with lots of pitch drifting (those high notes can be difficult to hit ;-).
    After that, I layer vocal tracks that belong together, and work with flextime until they are reasonably well-timed with particular focus on consonants and note ends.
    I tend to keep one recording centered, and two (or more) panned to the sides; a configuration that is very transparent to time differences.
    I *think* I do this because I have this idea that if I do flextime first, I will already have spectral content that is more damaged, that will be more difficult to pitch-correct with minimal artifacts. While as time-stretching or -compressing melodyne artifacts, will not do much to change the harmonic content of the material.
    Whether this is "correct" or not, I don't know for sure :-}
    So, I'd like to hear your experiences and opinion on this!
    Cheers;
    ::E::

    Hi!
    I assume you are on Logic 9. I think your workflow makes sense. With LX it´s a bit different.
    I have noticed that I really don't use Melodyne that much anymore, because of Flexpitch.
    Flexpitch is so much easier to work with, especially if you change computer. Downside of FP,
    however, is that you can't create fades, so first of all I would 'clean up' my vocal tracks, create fades,
    and then apply Flex Pitch and Time, in that order, I guess.

  • I think I solved my time changing issues- hope this helps

    Hey everyone, I think I've had some success with my time changing issues. I originally posted this to another user as a follow up to her question, but I'm reposting it here. Hope it helps:
    "msteinny,
    So i went to the apple store to meet with an apple genius to ask him why my phone's time kept moving up 1 hour everytime I synced my phone. Well he said that he's never seen this problem before, and after a trying a reset and restore he let me exchange my phone. The problem is that when I went to sync my new phone the problem still persisted. They told me it was probably something to do with my computer and its time zone settings.
    So I get home and click on my computers clock in the bottom right hand corner to bring up the date and time properties and sure enought my time is correct, the date is correct and the time zone is correct (Eastern Daylight Time). So I look through the different tabs (Date & Time, Time Zone, Internet Time). The first thing I tried to do was to change where my computer syncs its internet time. It was originaly set on NIST time. I then switched it to Windows time, but this didn't do anything. My clock would still change when I synced to itunes. The next thing I tried was fideling around in the Time Zone tabs. I noticed that the box that says "Automatically adjust clock for daylight savings" was unchecked, so I checked it and my computer's time jumped an hour ahead. So I left the box checked but moved my clock one hour back (to the correct time), clicked on apply and left it at that. I synced my iPhone and voila! The time didn't change! It stayed on the correct time! To to make a long story short, make sure that you computer's clock is set on "automatically adjust clock for daylight savings changes, make sure your time zone is correct, and that the time is right when that box is checked. I hope this helps you. I'm glad I got a new phone out of the deal;)
    Chris P. "

    As I mentioned in my post, whenever I checked that box the time would be incorrect. It would move up an hour. I've messed with this along time ago, way before I got my iphone. I think this had something to do with the daylight savings change that was implemented this year or last year. I dont remember if I never tried correcting it before, or if I couldn't, but this time I didn't have any problems correcting it. Anyway, since I couldn't correct it back then, I just left the box uncheck and decided that I would change the time manually when the next time change occurs. But it seems to work fine now so all is well.

  • IdM Scheduler and Time Change to Daylight Savings Time GMT to BST

    This isn't really a 'question' , but just a topic for discussion.
    We're not live yet, but will be by the time the clocks go back. So I'm just interest to hear everyone's experiences and any issues with regards to the switching to / from DST
    I did some "interesting" (or not) tests last night to see what happens with Pending Values which are due to take effect at the time change threshold of 01:00 GMT when switching to Daylight Savings Time (BST) GMT +0100.
    It seems as if the IdM scheduler keeps going according to UTC or GMT. However any values provisioned to target systems or to local tables using the ddm.datetime8601 system variable are in local time according to the runtime server or SQL server's locale settings.
    I set up a task to output from a javascript the current system date
    using the following in the functions.
    currentTime = new Date();
    return currentTime.toString(); // returns Locale Time String
    currentTime = new Date();
    return currentTime.toUTCString(); // returns UTC Time String
    in the same pass I also output the ddm.datetime8601 system parameter and the ddm.time24 system parameter.
    This task was to update a comment on an entry and Scheduled to run at 00:00:00 and was executed at 00:00:06 GMT all times were still in GMT as expected.
    Local Time: Sun Mar 27 00:00:06 GMT-0000 (GMT) 2011, UTC Time: Sun, 27 Mar 2011 00:00:06 GMT, ddm.datetime8601: 2011-03-27T00:00:06, ddm.time24: 00:00:06
    This task was scheduled at 01:00:00 in IdM and was exectued at 01:00:08 GMT by the runtime, and you can see the local time is being correctly reported as 02:00:08 BST. Note also the ddmdatetime8061 is also 02:00:08 i.e. BST.
    Local Time: Sun Mar 27 02:00:08 GMT+0100 (BST) 2011, UTC Time: Sun, 27 Mar 2011 01:00:08 GMT, ddm.datetime8601: 2011-03-27T02:00:08, ddm.time24: 02:00:08
    In the database the entry values MXI_VALUES ModifyTime field has the GMT / UTC timestamp.
    I also set up some pending value objects to be applied at 00:59:59 and 01:30:00 to see if the 01:30:00 would be 'skipped' as the locl clock change would've gone from 00:59:59 to 02:00:00. Well the pending values were correctly applied and expired and no 'lost' transactions happened as a result of the change.
    So essentially it seems to me that the IdM runtime and scheduler times are all based on UTC / GMT.
    I guess it's only an issue twice a year if you're expecting something to happen at a specific local time 01:00:00 or if you've got a global user base and their account expiry should be in each user's own country's local time. In these cases, it would seem that you'd need to convert the schedule times and pending value times to UTC first before setting them in the database.
    Has anyone else had any issues, thoughts, questions or suggestioins on scheduling tasks which span the DST time change when switching to and from Daylight Savings Time.
    Edited by: Paul Abrahamson on Mar 27, 2011 10:51 AM

    Read here:
    http://www.appleinsider.com/articles/10/10/11/applesays_ios_software_update_to_fix_pesky_alarm_clockbug.html

  • Multiple instances spawned after daylight savings time change

    This is a known issue and there is an SAP Knowledge Base Article created on this issue:
    1448881 - Multiple instances spawned after daylight savings time change
    Below is the information from the SAP Knowledge Base Article:
    Symptom
    Scheduled reports that are supposed to run once a day, run multiple times.
    Duplicate instances are being created.
    Environment
    BusinessObjects Enterprise XIR2 SP5
    BusinessObjects Enterprise XIR2 SP5 + FP5.x
    Reproducing the Issue
    A report is scheduled to be run on a daily basis - this is a Recurring schedule.
    Normally the report runs once a day, at a particular time.
    After Daylight Savings Time change, the report runs at the specified time, but immediately after the successful instance, another instance is spawned.
    Many more instances spawn after each instance completes.
    Cause
    This is a known issue: ADAPT01318487. This issue is because of DST and how our code handles this change.
    Resolution
    There is currently no known fix for this issue. There is however a script that can quickly resolve the problem.
    The issue it seems is related to Daily recurring schedules.
    What this script will do:
    it will run a query to display all your DAILY Recurring jobs
    you will have the option to choose your jobs and reschedule them by 1 hour
    you will then highlight the same job and change them back by 1 hour
    by modifying the schedule times, you are modifying the schedule itself and this will keep the issue of duplicate instances from occurring.
    Exact Steps to Complete:
    Stop the Job Servers.
    Double click on the .hta file.
    Change the System Name to that of your CMS name.
    Add the Administrator's password.
    Click Logon.
    Click List All Recurring Instances.
    Select All.
    Make note of what it says in: Schedule Selected Recurring Instances: Should be 1 hr earlier.
    Click Reschedule Selected Recurring Instances.
    Choose All instances again and change Schedule Selected Recurring Instances to 1 hour Later.
    Click Reschedule Selected Recurring Instances.
    Now start your Job Servers.
    The issue should not occur again.
    The Script is attached here, but please review the SAP Knowledge Base article 1448881 as well

    Hi Nicola,
    - The multiple spawned instances issue ONLY affects XI3 SP3+ only.  For XI3 SP1 and SP2 all Fix Pack levels this is not an issue as it was introduced as a problem in SP3.
    - 1568239 notes the Java version and can apply to all O/S environments and is updated to reflect that.
    If you are located in Europe you can also apply the patches in advance of the DST change to avoid the problem.  If you are in Americas at this point utilizing the clean up scripts for this year is the approach needed to clean up the spawned instances and reschedule the existing schedules.
    Thanks,
    Chris

  • 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

  • 1 new update have been added to the project would you like to close the project and apply these updates message in project 2010

    1 new update have been added to the project would you like to close the project and apply these updates message  in project 2010.
    One of the PM is getting above message and not any recent changes happened?

    Hi,
    This message appears when an update has been sent for his approval and is pending. It could happen while opening the project plan, or when clicking on something like "retreive tasks updates" from the backstage menu of MS Project Pro.
    The PM should go to his approval center and check for any approval pending.
    Hope this helps,
    Guillaume Rouyre, MBA, MVP, P-Seller |

  • 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

  • Changing a project title

    I need to change the main title that shows in the browser on
    a FlashHelp project, as in
    <title>Projectv3.5.3</title>
    I work with RoboHelp irregularly and haven't had to do this
    in a while. I can't remember where to make the change now.
    If you can point me in the right direction I'd appreciate
    it.

    Well, I set up my test, with five instruments added in five different versions, and each time changing the name. I also *Saved As* and created a new folder to save to, a couple of times, and also saved the final version in a different subfolder.
    I then deleted the first version ......... and the final one still played.
    I'm still a weeny bit scared though, to go through deleting so much stuff, even though I'd like to free up my Logic files.
    If I saved all the files as they are now to a USB stick, or burnt them on a CD, would I be able to 'bring-back-to life' any project which didn't open, once I've cleaned up ?
    Kay.

  • How to change iMovie Project from iSight to DV-NTSC?

    I noticed my iMovie project says it's an iSight project, meaning everything will be converted to motion-JPEG's on export in full quality. But my project has both DV and MJPEG clips and I prefer to export my DV clips untouched, not converted to MJPEG. If the project was in DV-NTSC mode, DV clips would be exported untouched. (The MJPEG would be converted to DV but I don't care about that.)
    How do I change the project type from iSight to DV-NTSC?

    Yes, there is always that option. However, I want to make sure that when I export a DV clip to a DV file, it will be exported untouched. If iMovie is in MJPEG mode, I'm afraid it might convert the DV clip to MJPEG and then back to DV.
    It doesn't matter now since I've figured out how to switch between iSight and DV-NTSC modes. You can't do it in the application, but you can if you edit the iMovie project file itself. Towards the end of this file look for either ISIGHT or DV-NTSC. If it's not the one you want, replace it with ISIGHT, if DV-NTSC, or DV-NTSC, if ISIGHT.
    Why is it important which project type you have? I've learned that video effects like transitions and fades are done in the default format iMovie has selected for your project. So if iMovie labeled your project as iSight (MJPEG), then all of your subsequent video effects will be rendered in MJPEG. If iMovie labeled your project as DV-NTSC, video effects are rendered in DV. This is important to know because effects rendered in a clip's original format are rendered much faster and may look better than if they weren't. So if you have a DV clip you wish to apply an effect to and the project is recognized as MJPEG, rendering the effect will likely be slow and the results may look bad.
    This is just another annoying quirk that I've discovered during the course of editing a project. Seems like once I've figured out all the quirks of a particular version, another comes out with a new set of quirks.

Maybe you are looking for