-
FCP X destroying audio edits in XML output
-
[Scott Witthaus] “I can see your frustrations!”
Part of the frustration is that these issues have cropped up at the point of export and delivery, without any warning while you are working the project. That’s been characteristic of many of the X bugs, like the “paste attributes” bug, the loss of render files, the bad renders on export and the sample-rate related audio distortion I encountered (other threads). This was never the case with other Apple software and is almost never the case with other NLEs.
You are rocking along fine while using the program and then find out there’s no easy way to get where you need to go.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “It’s not the fault of the exchange format IF IT IS A STANDARD – which AAF is. Whether or not companies decide to be compliant to the standard is obviously an issue.
“You say that FCPXML is a copout.
I think that your above statement is a copout. There aren’t even standards for some of the formats that fcpx supports, so who is coping out, exactly? And how long does something need to be vetted before becoming a standard?
-
[Oliver Peters] “This was never the case with other Apple software and is almost never the case with other NLEs.”
Some of us miss FCS3’s “legendary” stability, but this is getting a little weird. I can remember a few export bugs with Final Cut Pro 7 or less, and XML errors (like clips getting a 0 scale so they looked like they were blank).
I mean, here’s the list of bug fixes on the latest release of Pr CC 2014 in July.
Some of these have to do with effects not rendering on export and other export oddities.
These types of problems are not unique to Apple and bugs are certainly not unique to fcpx.
Bug Fixes:
• ‘Async’ asserts could occur when exporting some file types
• Incorrect angles could be shown when separate multicam clips were created with different sort order
• Waveforms could be improperly drawn when nesting a multicam source sequence
• Effects could fail to render within effect mask boundaries
• Garbage could appear around the edge of a layer that had a blur video effect applied and a mask on Opacity
• Masks could offset Gaussian Blur in CUDA mode
• Attempting to move a column to the left of the Name column in the Project panel could break cell selection
• Occasional instance where sequences could never finished rendering
• Relinking to spanned MXF clips could be incorrect
• UI responsiveness could reduce in large projects after relinking
• Exporting merged clips could generate silent or missing audio
• Importing sequences could sometimes fail
• Incorrect timebases could be used on EDL export
• Incorrect field display could occur when using Mercury Transmit with GPU acceleration
• Audio presets were sometimes not working correctly if used with a different format container
• Complex video assets could produce a blurry image every 1 second when encoded into H.264
• Mask Expansion could not be rendered correctly during preview scrubbing on layers that were scaled to 50% or less
• Applying a speed change to a multicam clip could cause the extended duration of the clip to play with no video
• Merged clips that contain clips with sync offsets could display out of sync indicators when used in a sequence
• Crashes could occur during export to QuickTime.
• Masking and Tracking: Brightness & Contrast could be incorrectly displayed in an Adjustment Layer
• File import failures could occur when no assets were selected in the Locate Media dialog
• Asserts and crashes could occur when exporting project to OMF
• Crashes could occur when rendering audio with a locked submix track
• Submixes could sometimes lose audio
• Noise could be heard in submixes with empty tracks
• Source monitor timecode and program monitor overlay could be off from one another in multicam sequences
• Audio overlays for Multicam and nested sequences would only display as audio time units.
• 24p/50p XDCAM EX files were sometimes 1 frame short when smart rendered
• MPEG2 TS files with 6 tracks of stereo audio could only play/show first stereo track when imported in to PPro
• Playing IMX 50 clip could freeze video
• Locking all Audio Tracks could cause the system to slow down dramatically -
[Jeremy Garchow] “And how long does something need to be vetted before becoming a standard?”
There are actual standards that the industry agrees upon (SMPTE, EBU, etc.) and there are pseudo standards that result because of overwhelming use, like QuickTime. The latter gave us gamma shifts, versus MXF which doesn’t, but QT is also easier to use. Pros and cons. So it has nothing at all to do with length of time.
OTOH, QT is only controlled by Apple. Now that they’ve moved onto something (hopefully) better, those who relied on QT as a “standard” will take it in the shorts over time.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Jeremy Garchow] “These types of problems are not unique to Apple and bugs are certainly not unique to fcpx. “
I would agree. As a general trend I think software is released in a buggier state than ever before. That’s certainly true of Adobe and Avid.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Again, I’m NOT suggesting anyone refrain from pointing out whatever flaws any program has. That’s not just fair game, it’s the whole point of these discussion forums.
I still feel that the tone of your post was needlessly alarmist.
And YES, I know that my “CC screwed me” post in the other forum can be seen in exactly the same terms.
So I understand more than perhaps anyone else that in the heat of feeling the damage from something that you NEED TO WORK NOW – it’s really easy to go on-line and bash it.
But it’s a slippery slope. I tried to tread that line by documenting not just what happened, but how.My feeling was that I was illuminating how the CC system functions (or on the weekend regarding licensing issues, does NOT function.) was useful to the readers.
I’m not quite sure how in the end, noting that FCPX XML is far from perfect in all interchange situations is might have the same level of end user impact, but OK . Fair point. Well made.
I’ll just pledge do my best to be much more careful about using “alarmist headlines” when I’m pissed about something in the future.
Perhaps you will as well and we can both do our best to elevate the tenor of the discussions.
Or maybe the occasional on-line wrestling matches is precisely why so many people read this forum?
Hard to say. ; )
Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.
-
[Bill Davis] “Perhaps you will as well and we can both do our best to elevate the tenor of the discussions.
Or maybe the occasional on-line wrestling matches is precisely why so many people read this forum?
Hard to say. ; )”No problem. Although I don’t think the tone of the posts themselves were alarmist, I can certainly see your point about the title. Clearly sometimes these threads are more a case of working out the details online after some give and take. But yes, being more subdued about headlines is a good goal.
OTOH, Tim is laughing all the way to the bank 😉
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “This includes XML conversion and bringing it into FCP 7 or a DAW or converting AAF.”
IA has fixed the translation in Xto7. No more destruction! 😉
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Charlie Austin] “IA has fixed the translation in Xto7. No more destruction! ;-)”
As of when? I have their most current version (App Store, at least) and have been in direct contact regarding this project. So right now, no, it has not been fixed.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “As of when? I have their most current version (App Store, at least) and have been in direct contact regarding this project. So right now, no, it has not been fixed.”
popped up in S/W update about 2 minutes before I posted, seems to indicate an audio rate fix, though I haven’t tried it yet…
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~
Reply to this Discussion! Login or Sign Up