Forum Replies Created

Page 111 of 180
  • Gary Huff

    February 9, 2013 at 5:49 pm in reply to: Premiere Pro – I could be convinced!

    [David Roth Weiss]
    I’m looking forward to seeing your review of CS7 after your first look.”

    Are they skipping CS6.5?

    EDIT: Glad I’m Cloud…automagically upgraded!

  • Gary Huff

    February 9, 2013 at 5:40 pm in reply to: FCPX has gone MISSING!

    Thanks for all the replies. I will be checking on this issue come Monday and will post what I encounter.

  • Gary Huff

    February 9, 2013 at 5:36 pm in reply to: Premiere Pro – I could be convinced!

    [Bernhard Grininger] “I do not get ‘pissed’ at Adobe.”

    I didn’t mean you. I meant the universal “you”.

    [Bernhard Grininger] “Yet I have to activate 32bit float and MRQ manually.”

    You’re activating it for the MPEG render files that Premiere generates when you select the “Render Work Area”. You don’t need to bother with this unless you want Premiere to utilize these MPEG render files when exporting the final, which I never do. You’re just wasting your time otherwise.

    [Bernhard Grininger] “Good point. Then why does the dialogue appear at all?”

    Because some people might get upset if that wasn’t the default? I have no idea, but clicking “Cancel” takes a second.

    [Bernhard Grininger] “How do You know what I need for 90% of my work :-)”

    Because I would assume by “work” you mean more than just stitching clips together? Willing to concede that I’m wrong if that’s all you actually do.

    [Bernhard Grininger] “Agreed. Dynamic linking is great! But tools directly inside PP would be more streamlined.”

    Except each app is geared towards different kinds of workflows. You can make a jack-of-all-trades NLE, but then it wouldn’t excel at anything. Premiere is powerful enough for basic stuff in and of itself, and then AE adds an additional level of complexity for projects that require it, all easily accessible with each other through Dynamic Link.

  • Gary Huff

    February 9, 2013 at 4:47 pm in reply to: Premiere Pro – I could be convinced!

    [Bernhard Grininger] “Also confusing is the sequence setting by codec instead per video standard. I also get headache when I need to do rocket science to get full quality out of it (GPU yes/no, 32bit float yes/no, etc…) or hack my app for GPU support at all… WHY???”

    Because you’re not using a support GPU? Perhaps you should try paying attention to the specs? Plus, Adobe needs to certify that the GPU in question would cause issues in rendering. Why support what you haven’t thoroughly vetted and then, it if causes errors, then people get upset. This way, you know what you’re doing isn’t officially supported yet, and if you happen to get a render error, you very well can’t get pissed at Adobe. And don’t for a second think it’s easy to vet a GPU.

    BTW, why are you setting your sequence settings manually? I’ve never had to do this, I just load up my footage, drop it into the timeline and Premiere will ask if I want it to automatically set the timeline for it (hint: the answer is “yes”). You don’t have to create a sequence as soon as you start a new project if you’d rather do this. Just click “cancel”.

    [Bernhard Grininger] “Too many plugins and other CS-apps needed…”

    For what exactly? You do realize that everything you’re using in FCPX to apparently do 90% of the work you need is actually a plugin too, right? And at least with Premiere you get stuff like Curves.

    [Bernhard Grininger] “(100% 32bit float, motion-compensated de-interlacing, spline-masks, color-grading, etc…) so that 90% of work in 90% of the projects could be done within PP.”

    It’s already there (not spline masks, but that’s easy enough with AE dynamic linking…and besides, doesn’t that require Motion to pull off anyway?).

  • Gary Huff

    February 8, 2013 at 3:18 am in reply to: For kicks: Apple in the medium term.

    [Lance Bachelder] “Hadn’t noticed.”

    Wouldn’t really expect you to.

  • [Steve Connor] ” I’ve used it on a feature, only because I’m an Apple fanboy though and of course it was cheap”

    Walter Murch totally comes across as an Apple fanboy to me in Behind the Seen, basically willing to test a $83 million dollar movie on an early version of Final Cut with the powers that be at Apple basically being a complete dick to him the entire time. In fact, he came very close to not pulling it off, and only via a third party that took a chance that Apple would completely disown them was what allowed him to make it happen.

    Premiere CS6 is kicking ass for me. I have a music video coming out in a few days I did in X that worked out fine, but I ran into the third-party plugin bug which made me compromise what I wanted to do with the piece. The color board is not intuitive to anyone who is familiar with the standard color wheel representation, and the damn magnetic timeline doesn’t help with precision-type editing.

    My current project involves a hell of a lot of animated elements (provided for me in .PSDs) and that would be virtually impossible to do in FCPX without resorting to Motion, but then there’s nothing analogous to Dynamic Link yet, so I would have to render out an intermediate every single time there’s a change (and there have been plenty of those).

    Instead, editing this project on Premiere CS6 on a Windows workstation, I have each of my animated elements in an After Effects composition that’s dynamically linked to the timeline. Every change is automagically updated without having to do anything. I have the edits exactly where I need them to be for the flow of the piece without having to mess around with the crazy way the timeline works in X. On top of that, I have Curves built in without having to resort to a paid third-party plugin!

    Finally, I had a unique situation that I will share. This project was shot on a C100. The first time was AVCHD + ProRes 422 HQ via the Ninja-2. I edited the original footage from the ProRes clips. Well, the client decided to reshoot to condense some material and present it in a slightly different way. ProRes is overkill for this project, so to save space, I simply relinked all the media from the Ninja-2 ProRes HQ files to the AVCHD from the internal recording. It worked perfectly. FCPX, on the other hand, can’t even accept clips if they are updated with audio tracks added! Granted a very unique scenario, but just another way in which working in Premiere makes me happy.

  • Gary Huff

    February 7, 2013 at 4:06 pm in reply to: ProCutX iPad interface

    [Rick Lang] “These criticisms of the current implementation are all quite valid but may be a hint of what is to come in future versions.”

    I don’t see how future versions will solve the tactile feedback problem.

  • Gary Huff

    February 7, 2013 at 4:06 pm in reply to: For kicks: Apple in the medium term.

    You must need some Yoga this morning because you’re really stretching here.

  • Gary Huff

    February 7, 2013 at 12:41 pm in reply to: For kicks: Apple in the medium term.

    [Aindreas Gallagher] “Who, in their right living mind, would trust the lunatic software mad house that is Apple.Inc again?”

    People who approach their beloved mega-corporation with emotion rather than rationality and imbue to it some kind of epic power that will transcend everything.

  • Gary Huff

    February 7, 2013 at 12:40 pm in reply to: For kicks: Apple in the medium term.

    [Lance Bachelder] “The guy never ceases… something stronger than merlot fueling the ire…”

    Except he makes actual, specific points.

Page 111 of 180

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy