Audio Drift after exporting OMF to Pro Tools and importing back AIFF

Hi,
I have an HDV 1080i50 Final Cut Pro project at 25 FPS (PAL). I exported a quicktime video without sound, as well as an OMF file of the audio. We mixed the OMF audio file using the quicktime file as reference on Pro Tools. In Pro Tools, the mix was done on 25 FPS, same as the original project. Synch was good.
However, after saving the file as AIFF 48/16 and importing it into the original FCP project, there is considerable audio synch drift with the original video.
It was edited in PAL, exported as PAL, mixed as PAL, but now it's not synching with the original PAL video in FCP. It still synchs up with the PAL quicktime, however.
What am I doing wrong? Any ideas???

Problem solved: trashed user prefs.

Similar Messages

Audio Drift after Processing

I'm currently working with FCP and Soundtrack. An 82 minute long audio file had some noise issues and I placed the whole audio timeline onto Sountrack Pro. I removed the ambient noise and saved the file after which it appeared back on the FCP timeline all processed.
But the audio is out of sync and gets progressively so. Is there a workaround for this? Am I doing something wrong?
Thanks.

We had the same issue on our project, and we just figured it out. We are working in 23.98 telecined film footage and our audio was recorded separately on bwf's. We exported our audio cuts as OMF's, cleaned them up in Pro Tools and when we imported the new files, they were drifting.
When we took both video and audio into Soundtrack Pro, it's perfectly in Sync, this told us that it's FCP's bug. In FCP, the length of the .wav file we imported was longer than the original length, in fact it's length was now the equivalent of a 30 fps file, not a 23.98.
I talked to Apple for about two hours on this with three different people, and explained to them that I knew it was a FCP bug, since the files worked in Soundtrack, but they wouldn't take responsibility on finding a solution and gave up on the issue.
My brilliant friend, Greg, spent about 5 minutes looking at the issue and found the problem. The problem is that once you have a quicktime file and it is conformed in FCP, it is tagged in the Audio Directory. So even if you have a 23.98 audio file and pull it up to a 29.97 file in ProTools or Soundtrack Pro, the tag stays with it.
Solution to the problem:
Option 1: Select the file in the browser and then go to Modify, Timecode. If it says "30" and you are allowed to change it to "24," then your problem will be solved. If the "24" is light grey and can't be selected, then do the following steps.
Option 2:
1. Take your audio file, press option and copy it. Rename it something different from the original file, just for safety, I named mine a different name at the beginning of the title.
2. Open a new final cut project, set up the easy setup so that it's totally a 23.98 project.
3. Import your audio and video. Hopefully, FCP will assume it's a 23.98 file, since you're in a 23.98 project.
4. Open you original project and cut and paste the new files. They should keep the 23.98 tags.
It worked for us. Greg thinks that this bug has been addressed in the Leopard version of FCP, but not the Tiger one.

After exporting in Premier Pro CS6 my text flickers in the video

After exporting in Premier Pro CS6 my text flickers in the video, how do I fix it?

I have the exact same problem, but I'm actually using CC. I don't have an option for "match source high bitrate." Is anyone responding to forum questions out there?

Pro Tools and FCP

Hi All
Anyone doing the roundtrip from FCP to Pro Tools and back again regularly? Is it as easy as an exported OMF to PT and then an exported final audio track in the desired format back to FCP to be synched with the video?
My organization is changing from Pyramix to PT, and the aforementioned workflow is what we have used with Pyramix, will that also work in PT?
Cheers
-j-

Unnecessary nowadays for ProTools. It was the best way to get your audio, with your levels and pans and keyframing, to ProTool prior to FCP 6. But FCP 6 and now 7 have a more robust OMF that includes those. Now it is more used for Avid to FCP, or FCP to After Effects, or FCP to Avid...stuff like that.
There still remains that 2GB file size limit...just FYI.
Shane

Pro Tools files imported to FCP X causing QuickTime movie problem

Well 2 days later and hours on the phone with Apple tech support Senior Advisors, and problem still not solved. HELP.
Everything works fine in FCP X, but when I create the QuickTime movie, it is way out of sync (by many seconds).
We have isolated the problem to audio files that I am exporting to Pro Tools, processing, and then importing back into FCP X. I can create a QuickTime movie with the original video/audio and it is fine.
Information
The original video came from Canon HF M40 camcorder: AVCHD (using MPEG4-AVC / H.264 compression codec), MTS format. Audio is 48kHz, 24 bits.
I used ClipWrap to rewrap the video into ProRes 422 and decompress the audio and save as LPCM.
I simply provide this FYI. As I said earlier, the original video works fine and the resulting QuickTime movie works fine. So the original files imported into the FCP project are not the problem.
The creation of the problem audio occurs as follows:
- Detach the original audio from the original video, and export
- Import this audio into a 48.0 kHz/16-bit Pro Tools HD session and EQ/limit the audio
- Import the resulting audio into FCP X (exact same length file, audio waveforms aligned with the original audio).
This audio works fine in FCP. It is in sync with the video, everything looks great.
I ran Pro Tools at 16-bits because a senior advisor told me FCP runs at 16-bits but does not convert imported stand-alone audio (as opposed to combined video/audio) to 16-bits; thus the Pro Tools session had to be at 16-bits. I changed from 24-bits to 16-bits, and this didn't solve the problem. (FYI, when Pro Tools imports the original audio exported from FCP, it says the audio is 24-bits, not 16-bits).
What is the problem?
The basic question is why does this audio cause QuickTime a problem?
Something is going on in the conversion to the QT movie. In FCP X, I don't have a way to play with the conversion variables except to set "Video and Audio" and "Use current settings" (which is ProRes 422).
The only difference I see between the original audio and the Pro Tools audio is that the original audio is stereo and Pro Tools works with dual mono files (L & R). The mono files work fine in FCP and I can't imagine why QT would have a problem with these, but I haven't tried converting the files to stereo before importing into FCP.
I should also mention that I selected the stabilization and roll correction algorithms in FCP. I assume these don't create problems in QT. I mention this because I didn't use them when I tested making a QT movie with the original video/audio files.
FCP and Pro Tools are used together all the time to do exactly what I am doing......improve the sound of the original audio. They are the premier video and audio professional programs. Of course, the final product is often not a QuickTime movie, but many times it is a QT movie.
What the heck is going on???
HELP.

(1) It is immediately out of sync. It even appears to be speeded up to me initially, but this is subjective. But it is clearly out of sync throughout, not a gradual drift.
(2) When I create the audio files in the Pro Tools session, the files are automatically stored in the audio folder of the Pro Tools session. So I don't actually have to go through an export process. I just close the Pro Tools session, then open FCP X and import the audio from the Pro Tools folder.
I'm not sure what additional specifications you seek, other than:
- wav files
- sample rate = 48 kHz
- Bit rate = 16-bits (and earlier I used 24-bits)
- Files are dual mono, rather than stereo (name_01.L.wav, name_01.R.wav). As I mentioned above, I have not yet tried converting these to stereo before importing into FCP, to see if dual mono causes an issue with QT. It does not cause a problem in FCP. I will try this today if we don't solve the problem.
(3) I can upload a portion of the audio to a server and send you a link to the file so you can download it. Is there a way to private message on the forum so I can get an email address to send you the link?
(4) The original video came from Canon HF M40 camcorder: AVCHD (using MPEG4-AVC / H.264 compression codec), MTS format. Audio is 48 kHz, 24 bits.
I used ClipWrap to rewrap the video into ProRes 422 and decompress the audio and save as LPCM.
The FCP Project was set up at:
- Starting time code - 01.00.00.00
- Format - 1080p
- Resolution - 1920 x 1080
- Frame rate - 29.97p
- Audio channels - stereo
- Sample rate - 48 kHz
- Rendering format - Apple ProRes 422

Pro Tools and Leopard

Just wanted to know if anyone had heard any information about Digidesign patching up Pro Tools to work with Leopard.
I really hope they do it soon...

I just got this info from Digidesign on LE and Leopard.
Hello Everyone,
I'm Dave Lebolt, general manager of Digidesign. I wanted to take a moment to talk to you about what is happening with Mac OS X Leopard and support in Pro Tools. Some of you have commented that getting Leopard qualified far earlier than now would seem like a "no-brainer," or that Digidesign is often far too late in coming on line in support of newer OS versions. Some have hypothesized that we will charge for an upgrade just to offer you Leopard support. Some people have even said that it's possible that Apple may be causing problems for Pro Tools on purpose. And some folks have said all of these things at once!
The first thing I want to say to all of you is: I'm sorry. I'm sorry that getting here is taking so long and that we have not been able to communicate more about it, and also because we really do care about your experience as customers... People working here are passionate about Pro Tools, a lot of us here want to use our product with Leopard too, and most of all we care because we genuinely want to do anything we can to help you be creative and successful in what you do. So I'm sorry if we're letting you down by not getting things released sooner.
Lack of Leopard support across our product line affects many of you (and affects our business), so I wanted to give you some insight into what's been happening and where we are in the process. Some quick answers to the above statements:
* We have an excellent working relationship with Apple. I have regular communications with senior folks there, as do many others in our organization with their peers (especially engineering and test). The people I talk to at Apple want Pro Tools to be compatible as much as we do; they know that a lot of you are our mutual customers. Ultimately, Apple considers Digidesign to be an important developer on the platform.
* Rest assured, we will not charge Pro Tools 7.4 owners for an update to support OS X Leopard. In fact, it is not our policy (nor has it ever been) to charge for a "dot release" where the only change is support for a new OS version.
* We'd love to have the new Leopard compatible version out to all of you, and it's very painful not to have it for everyone right now. We start work on the qualification (and development process as required) early in the cycle. We begin work on the "seed" versions of the operating system as soon as they are available and sometimes things are changing even as the initial OS release goes to market. If anything changes after that (i.e., a dot release), we sometimes have to start over in addressing any problems that may be newly introduced and go through entirely new rounds of testing to ensure quality.
What's The Current Status?
We have been working hard on supporting OS X Leopard since its introduction to developers at WWDC in 2006 for many months (including some period of time prior to Leopard's release). As is often the case with entirely new major OS versions, there were some quick "dot" releases after introduction. Many of the problems that Apple addressed in these dot releases were critical to improve OS X Leopard operations (you can read about some of them on the support section of Apple's website). These improvements and fixes were very valuable to a broad base of Mac users. Unfortunately, the currently shipping OS X Leopard release, 10.5.2, contains some changes that actually caused problems with Pro Tools (and some other apps as well). In our case, the problems included audio interfaces not being recognized by the computer, track counts dropping to near zero, and errors coming up during normal operation. Some of you who may have experimented with Pro Tools and OS X Leopard 10.5.2 may have encountered some of these problems.
We have worked closely with Apple's engineering group, who have been working very hard in cooperation with us to get the problems ironed out. The good news is that we're getting close to the home stretch, but we have to do a lot of testing of the fixes that have been implemented in order to be sure that we're in good shape. We need to make sure that our product works well and you're not just getting something that's marginal, and it takes time to exercise all of the newly changed code.
What Works on Leopard? Anything At All?
Currently, only Pro Tools|HD systems running Pro Tools 7.4.1 software are officially qualified with OS X Leopard 10.5.1 running on the new generation Mac Pro 8 core desktop machines (with "Harpertown" processors). This means no support yet for Pro Tools LE and M-Powered, and it means that users of the new Mac Pros need to stick with OS X 10.5.1 for the time being.
Why this Message?
We have posted this information along the way (just a couple of weeks ago our head of customer service posted information to the DUC), but the amount of time that is passing combined with our concern within the company prompted me to want to reach out to all of you. We work cooperatively with Apple, and want to respect the process that we have in place for fixing problems; but I wanted to give you a bit more information about what's been happening and why we're not there yet...
When Will It Ship?
We hope to have the new release within between 1 and 2 months from now; some of that timetable is contingent on Apple. We'll keep you posted as we get closer. Normally, we don't want to give specific dates because that can cause problems in expectation and it's better not to have negative surprises, but I'd like to share this info with you in the spirit of keeping closer to you as our customers.
I hope that my note gives you a better idea of what's been going on — thanks for listening.
- Dave L.

I bought Logic Studio from a pawn shop with Pro Tools and an iLok. It didn't include the serial numbers, which I thought were on the iLok. Is their any way to us this as an upgrade from like eBay?

Can I buy a used version of Pro Tools with the serial numbers from eBay, then istall Pro Tools and Logic I bought from a pawn shop using them as an upgrade?

If it sounds fishy, it probably is. Serial numbers from eBay typically don't work, because they are stolen, reused, etc. Logic Pro has nothing to do with iLok. And Apples doesn't offer cross-grades or upgrades anymore. If you want their software you go to the Mac App Store application and buy it. That's the only way.

Export from Apex 3.2 and import to Apex 4.0

I apologize if this has been asked before (and I am sure it has).
We are about to move all our Apex/Oracle apps to a server where Apex 4.0 is installed. Our current Apex version is 3.2. My question is can we export from Apex 3.2 and import in Apex 4.0 and expect everything to work (assuming it all works fine in Apex 3.2 and all Oracle objects were moved properly to the new server , both servers have Oracle 11g).

I am having trouble finding "update application" under any of the utilities.
Also one of my applications gives me the following error when I try to import it from Apex 3.2. to 4.0
ORA-20001: GET_BLOCK Error. ORA-20001: Execution of the statement was unsuccessful. ORA-02290: check constraint (APEX_040000.WWV_FLOW_WS_RPT_CHART_AGG_CK) violated <pre>begin wwv_flow_api.create_worksheet_rpt( p_id =&gt; 24053127534342788+wwv_flow_api.g_id_offset, p_flow_id=&gt; wwv_flow.g_flow_id, p_page_id=&gt; 60, p_worksheet_id =&gt; 24052412232342516+wwv_flow_api.g_id_offset, p_session_id =&gt; null, p_base_report_id =&gt; null+wwv_flow_api.g_id_offset,
I have no clue how to fix that.
George

The date and time is not working after setting it to current date and goes back to may,26 2011

the date and time is not working after setting it to current date and goes back to may,26 2011; 2 PM . I bought my ipod tocuh 4th gen on july 18th

On the iPod, make sure your Calendar is set to Gregorian (Settings > General > International > Calendar). Also make sure your date and time on your computer is correct as well as the Time Zones on both.

Clear process to unisntall Folio Producer Tools and go back to previous version

Does anybody know where we can find a clear process/tutorial to uninstall the last version (v19) of the Folio Producer tools AND go back to the previous version please ?
Because this is not clear enough to me
"To uninstall the Folio Producer tools, do either of the following:
In Windows, use the Control Panel (Add/Remove Programs) to uninstall the Adobe Folio Producer tools. (For older versions of the Folio Producer tools, you must uninstall InDesign CS5.5 to uninstall the tools.) "
What does "For older versions of the Folio Producer tools, you must uninstall InDesign CS5.5 to uninstall the tools" mean ???
Does it mean
1: "if you got old version of FPT and want it remove, do so" or does it mean
2: "if you want to go back to a previous version, do so" ?
Thanks for not bashing, i just get lost ....

Neil is right that Add/Remove Programs works to uninstall the most recent versions of the Folio Producer tools. If you have a much older version (such as v12 or v13), you need to uninstall InDesign CS5.5 to remove the Folio Producer tools.

How do I export detached audio files as separate files, for Pro Tools processing?

My project is a live band performance. I have every song as a separate Event with associated audio. I have detachd all the audio from all the video Events. I now want to Export the audio files to Pro Tools for editing, then Import the edited audio back into FCP X and snap the edited audio to the associated video Events.
My problem is this: FCP X keeps exporting the audio as a single large WAV file, rather than as separate WAV files. In fact, the video events are separate, and so the audio associated with the video Events are separate.
I first renamed the Role of every audio file as "Music", then did a Share --> Export Media of all "Music" audio Roles. After exporting, I found it was one large WAV file, rather than separate files of different sizes.
As a 2nd try, I created Sub-Roles for each audio clip, and named each one with a distinct Sub-Role name. I then Exported all these Sub-Roles (yes, tedious). The result was that every exported WAV file was the same size, the same as the file size in my first try. The only audio that could be heard in each file was the audio in that particular song, but FCP X still created the very large file with silence in all the rest of the file. Since the file lengths don't match the original audio fil lengths, there will be a problem when I Import the edited files back into FCP X and want to Snap them into place.
Question:
How can I export the individual detached audio clips as separate files, the length of each file equaling the length of the original audio file in FCP X?
Do I need to separate the detached audio into separate Layers visually in the Project Timeline, so they are not touching? Or does this matter?
Help!!

Michael Holmes1 wrote:
I have to record all the color changes I make in one Project, so I can repeat them in the other 17 projects, etc.
No.
You need to explore Compound Clips. This workflow may or may not be of help.
Select an Event with clips in it and press Option+G to make a (blank) compound clip.
Select the Event Browser, create a new Event and call it 'Effects'.
Drag the Compound Clip into this Event.
Right-click the clip and select 'Open in Timeline'.
Select the timeline and press Option+W. This will add a Gap Clip to the timeline.
Select the gap clip and press Ctrl+D then type in the duration you want the clip to be.
Now open a project and select and copy one of the clips with effects etc.
Open the Compound Clip in the Timeline again, select the gap clip and press Option+Cmd+V to paste the effects into your Compound Clip.
This clip is now saved in your Browser and will remain there for you to copy and then paste the effects into any clip in any project.
It's a bit clunky, but it works - and once you learn about Compound Clips, you can work wonders with them. As an example, if you want to add more effects without overwriting the effects in the Compound Clip, simply make the Compound Clip into a Compound Clip (again) and add the effects. They will be added to the original effects.
Andy.

Audio Synch Drift After Export

I'll try again, since no one answered the last time I asked. No problem with synching video/audio in FCP. However when I export either via compressor or QT movie I get audio drift that worsens as the film continues.
Video is in SD.
I would appreciate any helpful response. Thanks!

The audio is a remix done by a sound engineer to replace the original audio which had some serious problems.
The audio rate of the original and the remix is 48 Khz. The original was 16 bit, the mix is 24 bit. I'm a little new to this, so I'm not sure what you mean by sequence settings. Thanks.

Exporting AAF for Pro Tools.

So I got an OMF from FTP into STP with no problem, only to find that I couldn't export it again - hopefully a feature in the new STP? Anyway, my only option was to export an AAF (don't have the original FCP timeline to work with) - this audio needs to go to Pro Tools.
But my Pro Tools guy is saying he can't do anything with the AAF file if it's not consolidated into one file - like the OMF normally is.
So - is there a way to export a consolidated AAF? I don't see the option.

Our round trip workflow works, but still hoping for a better alternative in the future.
Duplicate & Rename the sequence for export (just a good habit to have... "videoblah.002, 003, etc). Then clean up any potential audio / video problems; clips that are not enabled, duplicate audio, delete blank tracks, and all the stuff the seems to crowd in the back of my timeline.
-It is a good idea to label your audio tracks for transfer (right-click> rename)
After that I export an OMF. (File>Export>OMF) and select the settings below:
That's just audio so for video, I export a quicktime H.264 video for ProTools DVtoolkit (video import plugin). Protools will except H.264 .MOV files, but it will not ingest H.264 .MP4's. It will also handle 1920x1080 files, but if I am rendering out a long project I like to keep the file size smaller by cutting the resolution in half or more.
The audio guy then takes it from there and gives me back a 24-bit single track audio wav file.
Thus far it seems to be a workflow, but if I want to go back and make changes, then either I have to do it all over again, or tell the audio guy specifically what needs done.
All in all, it's not efficient as using a roundtrip workflow such as AVID > ProTools and back again in AAF form.
Hope that helps.

Audio drift when exporting and non-native playback

Hi there,
We shot some footage with the HPX500 and recorded sound straight into the camera. The audio is 48kHz at 16 bit and the video is 720 at 24PN.
The footage is recorded in P2 and then transferred to hard drives and digitized through Final Cut Pro. We are currently using FCP 5.0.4.
Everything is fine with editing and playback on the sequence timeline.
The problem occurs when we start to play it outside the native timeline.
When I pull out the nested sequence into a DV/NTSC 23.98fps timeline, the audio experiences a 3 to 4 frame drift.
When I export the file as a native quicktime, the audio drift occurs too.
Same thing happens when I export and convert a DV/NTSC quicktime.
All the audio settings completely follow its HD source.
Am I missing something?
Thanks.

Did you ever get a solution to this? This happened to me as well, and now they're even off in FCP as well as the export. They used to be all fine.

Losing audio quality when exporting from premiere pro

I have now had this happen with two different videos. I play the video in premiere pro and the audio is fine. I export the video and lose most of the quality of the audio portion. One project is a music session when exported I only get the main vocal the drums aren't audible only a buzz sound is made where the kick drum would usually come in. On another project is a thank you video for a family member and the audio is distorted after being exported. The audio sounds fine inside of the session. Once exported the audio will still work fine on my computer and my iphone 5s as long as I'm wearing headphones, once I try to play the video through my iphone 5s speakers the audio quality is gone, making the noises as previously stated. My iphone can still play other tracks fine but videos and audio exported from Premiere Pro are distorted. Any advice on how I can export the video so I wont lose audio quality when playing the video on an iphone? I know it's not my iphone speakers, they play other songs just fine.

The source files as far as the audio goes are wav files that I've pulled off of my desktop. My sequence settings are 1920 by 1080 at 29.97 frames per second. The export settings are H.264 with the preset YouTube (HD 1080 29.97 FPS) and I've also tried HD video 1080p 29.97 FPS. If this isn't enough information please let me know I'm in the learning phase. Audio wise the quality is set to high and I'm exporting at 4800 kh and a bit rate of 190. I've also tried a bit rate of 320 and 264 I think it is and still had the same problems. Let me know if I need to do screen shots I really want to figure this out.
Thanks for your help!

Audio Drift after exporting OMF to Pro Tools and importing back AIFF

Similar Messages

Maybe you are looking for