HEY APPLE: FCPX scores an F for audio handling…

[Robin S. kurz]

[David Battistella] “1. Better handling of r3d embedded audio. “

That’s is a long standing issue of XtoPro not of FCP X, sorry. If it’s not working then you might want to yell at Marquis Broadcast.

[David Battistella] “ability to quickly and easily remove all levels”

Hmmm… maybe try ⌥⇧DELETE?

[David Battistella] “and effects”

Why would you care if you’re handing it off to a DAW?

[David Battistella]

I’m working with Marquis. the r3d handling is brutal.

ON the FCP X side. Once a proxy file has been created then perhaps it would be good if the XML could reference the rendered proxy audio (if i could set that as 24bit 48K that would be nice). Then we would not have to worry about relinking r3d audio at all.

Still. This third party solution is Apples solution to audio export (at a pretty heft cost compared to the price of the software itself) so apple needs to know that this ain’t working.

Thanks for the tip on the delete levels option.

Battistella

______________________________

https://www.bottegabattistella.com/blog/

[David Battistella]

I’m working with Marquis. the r3d handling is brutal.

ON the FCP X side. Once a proxy file has been created then perhaps it would be good if the XML could reference the rendered proxy audio (if i could set that as 24bit 48K that would be nice). Then we would not have to worry about relinking r3d audio at all.

Still. This third party solution is Apples solution to audio export (at a pretty heft cost compared to the price of the software itself) so apple needs to know that this ain’t working.

[Robin S. Kurz] “Why would you care if you’re handing it off to a DAW?”

If I have used compression or eq’s in the rough premix, it would be nice to remove all that, if I have to export role, which is now what I will have to do….

______________________________

https://www.bottegabattistella.com/blog/

[Robin S. kurz]

[David Battistella] “This third party solution is Apples solution to audio export”

No, it’s a 3rd party solution from a 3rd party. Apple offers a fully open XML for anyone to use. It’s up to the third party how they decide to parse it, not Apple. And if you have LPX you can go straight over.

[David Battistella] “If I have used compression or eq’s in the rough premix, it would be nice to remove all that”

Then simply do it with 2-3 keystrokes in the DAW! (assuming they even make it over which AFAIK could only happen with LPX as of XML 1.3). It’s not like they’re rendered into the file. Have never done it any other way. My LPX using audio guy kept what was useful and killed the rest. Done.

[David Battistella]

[Robin S. Kurz] “Then simply do it with 2-3 keystrokes in the DAW! (assuming they even make it over which AFAIK could only happen with LPX as of XML 1.3). It’s not like they’re rendered into the file. Have never done it any other way. My LPX using audio guy kept what was useful and killed the rest. Done.”

If I export as roles, then it’s “burned in” to the file.

FYI the delete combo does not work but, selecting all audio, then selecting the audio pane in the inspector and resetting the volume and pan parameter does work. 🙂

Battistella

______________________________

https://www.bottegabattistella.com/blog/

[David Battistella]

It’s not entirely on Apple, it is on Marquis very much, but a simple AAF export that I could open in Logic Pro X or any other DAW would probably be much more efficient than this long way round.

if this could be as smooth as any of the assistant editing offerings, or even resolves round trip, then my bitching about audio roundtripping would be over with. the fact that I am still (after this long) going through hoops to mix audio outside of FCPX is flat out failure. Even if it is R3D or Marquis. Apple needs to care enough to get it fixed.

Battistella

______________________________

https://www.bottegabattistella.com/blog/

[Robin S. kurz]

[David Battistella] “If I export as roles, then it’s “burned in” to the file. “

No idea what you’re doing or how you’re doing it, but sure doesn’t do that here, otherwise I would never use it.

[David Battistella] “FYI the delete combo does not work”

Works just fine here.

[David Battistella] “but, selecting all audio, then selecting the audio pane in the inspector and resetting the volume and pan parameter does work”

Or that, sure. Whereby the audio reset button is probably the better option to use, come to think of it, since the command actually removes any and ALL keyframes from the selected clip(s). Meaning any animations or the likes on the VIDEO as well.

[David Battistella]

Hey Robin,

I don’t want to tit for tat or nick pick here. I mean that your suggestion did not work as the most efficient method to reset the parameters for all of the clips in the timeline and get back to a “flat/normal/just as it was imported/state.

This does work really well in the inspector when using the method i described and by resetting the effects portion you get rid of all of the effects, eq’s hum removal or anything you might have applied to an audio clip, which would be included in the file if you were to export roles as tracks.

Of course, this would not be the case if I were able to get X2Pro to create an aaf file that I could import into a DAW where those parameters would not be baked into the audio.

Thanks for responding though.

Battistella

______________________________

https://www.bottegabattistella.com/blog/

[Robin S. kurz]

[David Battistella] “It’s not entirely on Apple”

Actually, Apple isn’t responsible for other companies’ software AT ALL, to be exact, no. No idea why anyone would assume that. Even partly. They’re responsible for THE XML, yes. And they’re continually developing it further and adding more options. It’s up to the OEM’s to implement those changes, which many HAVE. Just XtoPro doesn’t seem to feel that updating is part of customer service.

[David Battistella] “but a simple AAF export that I could open in Logic Pro X”

LPX does FCPXML. Why would I want an AAF instead?? Because yes, that’s a completely superfluous step. And the fact that ProTools won’t do it has to do with nothing other than Avid’s arrogance. Period. Even PPro can import FCP (7) XML.

[David Battistella] “the assistant editing offerings, or even resolves round trip”

Aha. So Apple’s responsible for THAT now, too?? :-))) And you realise that you’re making MY point with that, right?

[David Battistella] “Apple needs to care enough to get it fixed.”

Apple “fixed” LPX and it supports direct import of FCPXML. Last time: any other software, talk to the respective maker. It’s not actually as complicated as you’re making it out to be (for yourself). Simply taking the shortest route because it’s convenient doesn’t make it the best or most logical. 😀

[Robin S. kurz]

And mind you, I’m not saying that FCP’s audio is somehow perfect. I’m just saying it works fine for ME and my needs, as long as I know what to look for and know my options. The FCP X devs are sure to continue to get together with the LPX devs in the future to improve things as needed, as they have in the past. Anything else (ProTools et al) are NOT their responsibility, as much as it would seem you’d like them to be, sorry. And at least in comparison to FCP *7’s* audio it would never get anything less than maybe a C- from me. Other than maybe the missing “Send to” it trumps 7 by a longshot.