Lance Bachelder
Forum Replies Created
-
I thought I was being fairly objective in my PPro views being a long time fan of the app even with its past shortcomings.
The big difference is I’ve actually used PPro for years off and on for fairly high level work – most of the folks posting here including some of the leaders in this forum are not actually using FCPX for paying gigs and just slamming it and Apple as a hobby or sport and not based on any actual use of the program. You’re a prime example David – you’re a Leader on this forum and I can’t recall anything but negative crap from you concerning FCPX. Why even be a leader?
When someone like Bill Davis or Craig post something positive they are instantly jumped on by the naysayers, who for the most part have less real pro experience than them.
I’ve been a Cow Leader for over 10 years and just for you David, I promise this will be my last post ever in this forum.
Lance Bachelder
Writer, Editor, Director
Irvine, California -
Thanks for the detailed reply Dennis. I will say there was a period early on when Adobe was listening during the ver. 1 and 1.5 days when there was a different team i charge. I was one of the first editors on the planet to attempt, with Adobe’s involvement, editing a narrative feature with PPro and Cineform – this was right after Dust to Glory. I was also the 1st Editor to cut a 2K 3D Cineform Prospect show in Premiere Pro. Once that team left Adobe, there was a period when Adobe was NOT listening and English was definitely the 2nd language for the programming team, none of which seemed to have ANY editing experience.
I’ve seen a lot of progress in the past 2 rev’s and actually paid for my upgrade to CS5. I’ve tested 5.5 with approved nVidia card and it is awesome! However I’ve not come to the point of trust yet where I would cut my next movie on it… maybe someday.
Correction as far 64 bit. Sony Vegas Pro has had side by side 32 AND 64 bit versions since Vegas 9, long before CS5 was released. I cut my last indie feature in Vegas Pro 10 64bit because the constant crashes we were having in CS5. 5.5 seems much better and I would think 6 will be even better.
Lance Bachelder
Writer, Editor, Director
Irvine, California -
I was a tester from PPro 1 through CS3 – also After Effects and a little Photoshop during the same period. The PPro team was always a problem – NEVER listened to a word we said and never implemented a single feature we asked for. I had real hope for the program and still do but many of those features we asked for are still missing as my post states. I would have loved to stay involved but you can only handle so much rejection and closed minds.
Glad there is a new regime handling PPro and really hope you keep up the good work, but other than Mercury Engine I still still NO PROGRESS in simple day to day editing tasks.
Lance Bachelder
Writer, Editor, Director
Irvine, California -
Love that folks are finding shortcomings in PPro. I was on the beta team through several revs and they would just never listen when we asked for “pro” features. Like marking clips, and how about setting and in/out to quickly export a clip? Or setting an in/out and sub clipping that section? Or moving a clip without using modifier keys? Or setting an in/out just to simply copy/cut? I don’t want to use the work area thingy – it’s fine for AE but slows me down in PPro.
All the “pro” EDITING features we use everyday with Avid and FCP7 are just not there! Sure the mercury-engine is awesome and the dynamic link is cool but when it come to editing and mixing it just kinda sucks. I also hate the Adobe Media export thing – just a pain to find the right settings for audio and video – nothing like the ease os export w QT conversion in FCP7. Also, the built-in color tools are just terrible, you’ve got to install Colorista or forget it.
FCPX is also still missing some of these everyday features – but I will say a lot of the new stuff just rocks and there is a foundation here that could blow everything else away if Apple doesn’t screw up. Using Tonalizer in FCPX for Color Timing is the most fun and best results I’ve ever had quickly timing shots and scenes.
Lance Bachelder
Writer, Editor, Director
Irvine, California -
What codec/setting are you rendering to? You can also go into preferences and change try reducing the number of render threads.
Lance Bachelder
Writer, Editor, Director
Irvine, California -
Also make sure you’ve done the Pro Apps update which lets FCPX see all the various XDCAM flavors.
Lance Bachelder
Writer, Editor, Director
Irvine, California -
Also since your project is effects heavy maybe switch project to 32 bit Floating Point (video levels) in properties just for the render – quality will go way up. Make sure render is set to Best also.
Lance Bachelder
Writer, Editor, Director
Irvine, California -
Why Sony .mxf? I would recommend using Sony AVC and choose one the preset that matches your project settings or desired output. You can render the audio as .aac and adjust the butyrate to the quality you like. It will play in Quicktime or Windows Media Player and most other players.
Lance Bachelder
Writer, Editor, Director
Irvine, California -
I would look at the new GoPro/Cineform software – they have a free version which you can use to transcode your Nikon clips into high quality .avi’s that Vegas can understand:
https://gopro.com/3d-cineform-studio-software-download/
Lance Bachelder
Writer, Editor, Director
Irvine, California -
Great in-demand Editors, at least here in LA in the feature film world, get to dictate whatever tool they want to cut with.
Lance Bachelder
Writer, Editor, Director
Irvine, California