Ronny Courtens
Forum Replies Created
-
Don’t be frightened by node based compositing. It looks intimidating at first glance but once you understand how it works you find it offers so much more than layer based compositing and you don’t look back.
Nuke is an excellent tool but I haven’t tried it with the new Final Cut Pro. We have been using Smoke 2013 together with FCP10 in a test setup since one year and now we are porting this workflow to daily production on 3 of our bays because it works extremely well. We already have switched completely to the new Final Cut Pro for editing since October last year and now we are making the transition from AE to SMAC for integrated mographs as well. We already have a Flame bay for the higher end work, so trying out SMAC was a no-brainer. So far this process has been quite painless and rewarding for us, and we certainly don’t regret it.
-
The Animation codec only supports a total of 32-bits per pixel (= 8-bits per channel), it does not support 16-bits per channel. This means that going through AE and exporting using the Animation codec is not a very good workflow in your case.
Just import your footage in FCPX without the roundtripping. If your system is fast enough you may be able to edit your H.264 media natively, also depending on how long and complex your timeline is. If you cannot edit natively you don’t necessarily need to optimize to ProRes either. You can create Proxies (like you are doing now) and work with the Proxy media. As has been pointed out the Proxies will retain 16 bpc. When the edit is locked you can switch back to original media for final check and output. Of course, if you wish, you can always optimize to ProRes as well. That’s entirely up to you.
However you proceed this workflow will give you only one conversion generation if this is your main concern. Although I can certify from experience that ProRes 422 withstands multiple generations without visual quality loss, even when projected onto large screens in HD.
Best wishes,
Ronny
-
Agreed. As a professional I always try to base an opinion on personal experience and facts, not on hearsay or rumors. But hey, this is the facebook age after all…
All we know Apple may not be announcing anything at all at WWDC. Will this have any influence on my business? Will our current machines suddenly stop working? Will our clients suddenly stay away? I don’t think so. Still it’s quite fun to read all this ((-:
-
It’s always good company policy to have options and Adobe does not have any monopoly anywhere, certainly not in the professional A/V world.
We have a number of CS6.5 Master Collection licenses and we have decided to not further invest in Adobe software. Not specifically because of the CC debacle, that’s not really an issue for us. But mainly because at NAB I haven’t seen anything that can justify spending more money on Adobe apps.
Since last year we have developed a new workflow around FCPX/Motion, Smoke 2013 and Resolve for national broadcast work in our 2 post houses and so far our creative people as well as our clients have been extremely satisfied with it. These apps work perfectly together and with every update the workflow gets stronger. Smoke was a no-brainer because we already have a Flame station in-house and the workflow as well as the features are very similar. Motion 5 is a perfect companion to FCPX and if Apple brings seamless integration between FCPX and Motion they will have a winning combination for realtime on-edit mograph jobs.
Even with the coming updates Adobe doesn’t offer anything that we cannot already do better in our current workflow, so I cannot justify any further investment in their software at this time.
-
Franz Bieberkopf:
Tim,
Can you somehow put that in the title, instead of FCPX.I agree 100%. I don’t have the time to participate in the debates, but since this forum started I have come here every day for a quick read to see people arguing (rightfully) why they like FCPX, and others (equally rightfully) arguing why it doesn’t work for them at this moment. Very good points were made, wether pro or contra.
Unfortunately in the past few months the debate has become less interesting, or should I say it has shifted from “FCPX or Not” towards a general NLE debate. I don’t mind this at all, but then IMO the title of the forum should change accordingly.
As an example: I for one am extremely happy that all the CC FUD has been moved away from here, because in all honesty this has nothing to do with wether I would use FCPX or not. I can very happily use FCPX (or not) AND use (or not use) other NLEs at the same time. So either this forum could go back to its roots and really focus on FCPX or Not, or it could remain a general discussion forum as it is now (“There’s nothing we can’t argue about in this forum”), but then the name of the forum should not reflect FCPX only.
Just my 2 Eurocents.
Best wishes,
Ronny
-
Lee,
Thank you for the reply. Yes, I have captured DVCPRO50 on this system regularly and until today (touch wood) without any problems. But capturing is always straight from the DVCPRO50 camera or the Panasonic deck through FireWire, using the native codec in FCP. I don’t know if using the AJA will change anything to this, as the io FireWire output is uncompressed. Guess I’ll have to try.
Best wishes
Ronny -
Hi Serge,
Exactly what I was looking for. I was getting in the same direction making a precomp with the video files in reduced size and applying the sphere filter to this set in the final comp. Your workflow makes it clear that this is the way to go. Thank you for having taken the time to send us your project file. I am studying it now. Thanks again.
Best wishes
Ronny -
Hi Randy,
You should be able to see any JPEG (and PNG and TIFF…) files as a thumbnail preview in your browser.
Import your JPEG in FCP. If your browser is in List view: CTRL (or Right) click in the browser window. From the pop up menu, choose “view as icons” and you will see a thumnail preview of your JPEG.
Best wishes
Ronny -
Hi Randy,
Put your clip in the TL, apply motion attributes in the timeline, drag your clip with the attributes to your browser window and voil