[Charlie Austin]

[Tony Peck] “I’m looking for a audio plugin to reduce some background noise for interviews. I was looking for something that has more control then the built in one in FCPX. Any suggestions? Are any new plugins out there?”

Izotope is the standard bearer, but pricy. I’ve been using SoundSoap and it’s really good.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Lillian Young] “Okay. I created the keyword collection. I’ll have to get used to this workflow.

Thanks to you both.
“

It’s functionally the same as bins (which are really just folders). Here’s how i do it using smart collections. I can get more specific by creating regular KW Collections and dragging projects to them (like bins). it’s quite flexible, so you can pretty much do whatever you want…

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Lillian Young] “Is there a way to organize them by creating what would be bins in legacy FCP?”

Yep, as Robin says, just create keyword collections and think of them as bins. You can then further organize these into folder, subfolders, whatever works. If all your projects/versions have unique names (project A V.1 etc, you can use smart collection to organize everything for you. It’s way better than 7 or anything else in that regard, at least for me…

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Jeremy Garchow] “[Charlie Austin] “Would make my life easier though. X to 7 to whatever or vice versa is like a game of telephone. What you end up with isn’t necessarily what you began with…”

What began as a what you necessarily want with, you didn’t end up there.

Am I holding this phone correctly?
“

I wanted a phone, but I didn’t end up with one.

Next! 😉

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Andrew Kimery] “[Charlie Austin] “Pr C imports/exports FCP 7 XML, not FCP X xml.”

Ah, thanks for the clarification.”

It actually works pretty well in the latest CC versions. It would be nice if Adobe and Avid would read FCPXML, it’s a moving target, but the documentation is available. I guess they have no desire to work with the competition in this arena. And Apple probably doesn’t care one way or the other… 😉
Would make my life easier though. X to 7 to whatever or vice versa is like a game of telephone. What you end up with isn’t necessarily what you began with…

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Andrew Kimery] “PPro can import and export FCPXMLs (I think that was added 2 or 3 versions ago). Avid, from my limited understanding of programing, is an entirely different beast under the hood though, as previously mentioned, Automatic Duck exists as a possible bridge.

I’ve only used the Duck once though and it didn’t go very smoothly. While reading up on it I learned that the final version of Automatic Duck was released when Avid’s AMA functionality was very new so there are a lot of shortcomings of using the Duck with tapeless workflows.”

Pr C imports/exports FCP 7 XML, not FCP X xml. And MC imports neither. Auto duck still works OK for picture… You lose a lot of info, but the cuts come over OK. But that requires FCP 7 or Pr, so, like Adobe.. no X to MC straight shot.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[james henson] “firstly, Vegas does not export to fcp/fcpx, that is simply incorrect, i have spent too many hrs trying to do so. If you google how to do so, there are perhaps three sites that superficially cover how you do this.”

Seems fairly straightforward:

https://www.sonycreativesoftware.com/webhelp/vegaspro/12/ENU/Content/Importing_and_Exporting_Projects.htm

From the File menu, choose Export, and then choose a project type from the submenu:

Pro Tools AAF File
Media Composer AAF
Premiere/After Effects
Final Cut Pro 7/DaVinci Resolve
Final Cut Pro X
EDL Text File

I guess whether it works is another question… 😉

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Jari Innanen] “It is worth mentioning, that Sony Vegas supports fcpxml.”

Interesting isn’t it… Vegas, Smoke, Davinci and a bunch of other post support apps read and write fcpxml. Avid and Adobe need to get with it. lol

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Will Granzier] “I’m on 10.1.3…. !? Very weird
“

Don’t take my word for it, but that seems to “usually” (meaning maybe..) be a permissions issue with the drive. I’d start there…

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Fabrizio D'Agnano] “By the way, I never succeeded installing Soundtrack Pro on Mavericks, did you install it from the disc or in some other way?”

From Disc Images… Gotta be FCS 3 though, earlier installers won’t work…

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~