Michael Prescott
Forum Replies Created
-
The timeline codec was 8-bit uncompressed 4:2:2. I thought this would actually help the graphic look better. Also, the Sequence frame size was 720×576 even though the original graphic was created at 1024×576.
-
Right you are, David. It is mush. It was not lit properly but I should have made the woman look better before trying to match it to another shot. I’ll give it a go and thanks, as usual, for your advice.
-
Terry: the above pictures were JPEG’s only for posting here; its not what was used in the project. But I just discovered something interesting: the NTSC graphic was indeed saved as a TIFF, but the PAL was saved as a PNG. I had always thought the consensus in this Forum was to use PNG but I’ll redo it as a TIFF to see if its better.
Dave: the graphic was created with a text only on a transparent background so, in Photoshop, nothing was erased. In fact, I used the exact same file for each version, only resizing for the proper aspect ratio.
-
I agree with you that the .1% pitch variation is not detectable. I never should have told them I did it in the first place!
I’m still trying to understand why the timebase was changed to 24.98. The XML was adjusted by a search and replace of “all” instances of from FALSE to TRUE. If this correction was just limited to the audio files, would it have left the video timebase at 25fps? Or, is there some other reason?
Thanks again for all your patience and helping me get my head around this frustrating and complicated issue.
-
… that’s all “timebase” tags were set to 25.
-
Actually, my saga is not over…
Even though setting the audio speed to 99.9% put everything back in sync, the producers do not want to do this. (It is a famous rock act and they don’t want the audio altered in any manner. I guess its already been tweaked too much as is.) So, I decided to perform a different approach:1) Changed FCP Easy Setup to PAL 25fps 48khz.
2) Exported XML of PAL sequence
3) Deleted audio assets from timeline and browser
4) Closed FCP
5) Edited XML file and changed all tags to TRUE
6) Opened FCP and imported revised XML file
7) Set Sequence Settings to DV PAL 48khz 25fpsUpon import of the XML file, the following error message appeared: “Non-critical errors were found while processing XML document. Required element has a value that is out of range. Resulting sequence item definition may not behave correctly.”
Notwithstanding this error message, the audio was, in fact, now in sync. All seemed good. However, the Sequence Settings had the Timebase at 24.98.
Is this correct?
Why was the Timebase changed from 25fps?
Will this cause problems when I export to Compressor and, eventually, DVDSP to make the PAL DVD? And, most importantly, while the clip properties say 100%, has this process changed the speed or pitch of the audio file?**I did go back and check the original, unedited XML file and noticed that all tags were set to 25. Could this have created the problem??
-
Thanks for the explanation. Just a quick follow up:
Why does FCP lock the timebase of audio clips to the initial Easy Setup parameters? Shouldn’t it be intuitive enough to play it at the same rate as the sequence settings timebase? It makes it very difficult to do an NTSC and PAL version in the same project file.
-
I just changed it to 99.9% and it worked. Thank you very much!
Could you just take a second to explain in detail why this workaround is necessary and whether this is a bug or a feature in FCP?
-
I just tried this fix recommended by Apple (https://support.apple.com/kb/TS1256), but it also did not work:
Delete audio files from Timeline and Browser; change Easy Setup to PAL; quit project and reopen; re-import audio file.
-
I’m not exactly sure what you mean by having “FCP set to NTSC”: the timeline was DV PAL Timebase 25. For good measure, I set up a new timeline, changed the name of the mixed audio aiff file, then imported the new aiff, and the problem remained the same.