[Nick Ring]

It’s been a long time since I tested it, but I used to regularly export to DVD and Vimeo. If I created a bundle that created the DVD first, it would stop the process at the point of the dialog box for making another DVD copy. Not helpful. I sent feedback, but I don’t think anything has changed on that front. However, for exports not involving DVDs, it’s been helpful.

[Nick Ring]

I’m using the final Yosemite public beta and I haven’t had any problems with FCPX, though I’ve only done basic work in it. I had been keeping an eye on compatibility reports and ran a test instance before I went whole hog. I also saw on twitter this morning that Alex Gollner (Alex4D) had FCP 7.0.3 running on Yosemite.

I think that “some minor GUI tweak” is selling it (or any OS update) short. The compelling reasons to updating to Mavericks and now to Yosemite have outweighed the downsides. Currently on Yosemite I’m finding continuity very useful and I appreciate the broader access to 3rd party extensions in sharing and such. It’s also been very speedy.

If an upgrade breaks needed functionality, then it isn’t much of an upgrade. But if that’s not happening, I look first to the benefits that it offers and am willing to give it a go (test instances and backups are good!). And functionality is different than “this is how I’ve done things”, it’s about end results. There are times to not mess with workflow, but the unexamined workflow is kind if like the unexamined life (a trite cliche?). Where can I improve by seeing things differently? [insert FCPX comparison here]

-nick

[Nick Ring]

The 9to5Mac post included this line:

Sources also say that Apple is preparing updates to iMovie and Final Cut Pro with improved tools for editing high-resolution, 4K footage.

so, perhaps. I am intrigued by the notion of 4K editing in iMovie.

-nick

[Nick Ring]

There are others who can speak to this with far more expertise than me (and this may be too late to be useful), but…

– Be mindful of the 3:1 rule (description 1, 2)
– Hanging chorus mics can be useful, but if they are too high above the actor’s heads, you might end up getting more room tone than useful signal (and lighting buzz, AC vent noise, proximity to reinforcement speakers depending on location of those)
– The more mics you have open the more you are increasing the room tone noise relative to the signal you’re trying to capture

If you can map out the space and the actors’ marks that can really help you identify optimal mic placement. Will you have a dedicated sound mixer?

-nick

[Nick Ring]

Not holding my breath yet, but I’m in the camp that it had to wait for 10.9.3 (for whatever reason). Here’s hoping.

[Nick Ring]

I am a bit dense at times, but I had trouble using RX as a FCPX plugin. Exporting the audio and processing in RX standalone has produced much better results for me.

I haven’t used Audition since Cool Edit Pro days and since I’m not working with CC and don’t have 6 installed here, I haven’t had a chance to test it out. I have, however, heard really good reports about it.

-nick

[Nick Ring]

Thanks much!

-nick

[Nick Ring]

This is one of my issues with the move to libraries as well. There’s a lot I like about it and I don’t mind having library>event>projects so much, but to not have keywords at the highest organizing block (as we did with events in FCPX<10.1) is frustrating indeed. There may be a structural/database reason why it may be complicated, but that’s not anything I’d know about one way or another.

[Nick Ring]

What do you prefer to use for MPEG2 encoding? In my limited experience, I’ve tended towards Adobe Media Encoder over Compressor (5.0-6, haven’t tried CC). Still working with MPEG2 on a regular basis, so a potential improvement could be nice.

[Nick Ring]

Similar, but different here. I was provided a new rMBP by work and installed FCPX on it. First computer in 8 years that hasn’t had legacy FCP automatically installed on it. There are computers with 7 and Premiere available to me, but I haven’t needed to use either. So far so good.