-
The iMac “Pro” rumor looks interesting
-
[Robin S. Kurz] “but say nothing about the performance for any and everyone overall, which is what I was looking for”
There’s no such thing. Everyone has different use cases and therefore, this gets into operational efficiencies of one versus the other. That’s something I purposefully avoided. There are plenty of things that I find to be faster in Premiere for me and most of the other editors I work together with. I’m sure you would dispute any example I presented, so why bother. Likewise, I can also point to specifics where X is faster. It’s a rabbit hole argument that’s been debated extensively since this forum was opened. So, as I said, I answered the question you asked.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “It’s not a matter of searching. It’s simply nothing I’ve ever encountered, nor seen with any of the other editors using Premiere that I encounter. “
And yet, it’s a seven page long thread spanning over two years and, again, only one of many. Go figure.
[Oliver Peters] “There are plenty of things that I find to be faster in Premiere for me and most of the other editors I work together with.”
Exactly the thing I was looking for, yes. Which is why I have to wonder why you didn’t mention them then.
[Oliver Peters] “I’m sure you would dispute any example I presented”
Bit of a cop-out, don’t you think? If they are legitimate points, how could I?
[Oliver Peters] “So, as I said, I answered the question you asked.”
I’ll just respectfully disagree.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Robin S. Kurz] “Exactly the thing I was looking for, yes. Which is why I have to wonder why you didn’t mention them then.”
I explained why, but I guess I’ll take the bait. Here are but a few:
1. Replace edit – I do a lot of commercials with variations to the graphics – version A, version B and so on. This process is considerably faster in Premiere. Swap out one phone number graphic for another simply by highlighting the new clip and choose replace from bin (right click function).
2. Adding filters – in Premiere I can selectively copy & paste individual or groups of effect filters between clips without going through the paste attributes dialogue. So if I have a second color correction filter that I want to apply to some clips, I can copy it and then paste it into the effects control window for the desired clips.
3. Global audio mixing and adding filters to audio tracks – still faster in Premiere even with the Roles function in X.
4. Speed – interpretation. For example, 29.97fps that needs to be played at 23.98fps. In X this requires a speed effect. In Premiere I can “interpret” the footage to be played at 23.98fps. And I can do that for batches of clips.
5. Multicam – I don’t want to deal with “through edits” in my multicam clips. I find the Premiere method less convoluted than in X and, therefore, faster.
6. Adding audio fades – I can globally change all audio transitions in 2 steps (highlight cuts & apply default trans) in Premiere.
7. Doing color correction with the Lumetri control is vastly superior to X’s color board. No extra plug-in required. Therefore, advanced color correction in Premiere is a faster process.
8. Direct interaction with After Effects compositions isn’t really possible with X. There is no true Motion roundtrip for complex, multilayered compositions, so there’s really not even a comparison there.
9. Certain camera formats in X require that you first copy the video into the library and do not allow external linking, unless you transcode with another app first. Not an issue with Premiere.
10. The large number of contextual menu and right-click mouse functions in Premiere can be daunting for some; however, these offer a lot of fast and direct control of the UI that simply doesn’t exist in X.
As I said, just a few…
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “Seems to match a lot of what I’m seeing these days. I have to say that after teaching post workshops for a number of years at a local college film program, the general computer literacy I encounter has gone down over the years. Largely the effect of phones as computing devices.”
Agree. I instruct a night class (FCPX, PPr, Ae and Maya) part-time.
It seems people are not caring much for what they are using as far as tools.
You will get the few that knows their PC/Mac but a ton that just don’t care.
I don’t mind holding their hands through the process, but as long as they are able to create their vision, I’m good ☺On another side-note, I honestly dont care if the new XEONS can rip through h264 converts.
I just want my web output to match my damn Resolve grades 😛
-
[Oliver Peters] “[Robin S. Kurz] “Try something like the “flashing timeline thumbnails” bug in Premiere, that actually stopped your show”
I have no idea what you are referring to. I’ve never seen that myself.
“I have. Not on one of my setups, but on a client setup with the 2015 version. Its intermittent and annoying, and easily gotten rid of by turning off timeline thumbnails. Its long gone as a bug, afaik.
-
[Oliver Peters] “There are plenty of things that I find to be faster in Premiere for me and most of the other editors I work together with. I’m sure you would dispute any example I presented, so why bother. Likewise, I can also point to specifics where X is faster. It’s a rabbit hole argument that’s been debated extensively since this forum was opened. So, as I said, I answered the question you asked.”
Indeed!
-
https://forums.adobe.com/thread/1663472
You found some people who had a problem. There may have been a total of 100 people who had this problem.
Here is what you should have read.
“I was able to do some testing on a new edit (about 30-40 clips) and it got to a point where the thumbnails were refreshing constantly. I then closed all open apps (iTunes, Safari, IM) and the refresh issue went completely away. I opened the apps back up and the refresh issue instantly came back. I repeated this several times and ran a screen cap: Dropbox – apps-issue.mov
“I isolated the problem to Safari. I tried Chrome (normally not open) and it did refresh once or twice, but not nearly as much as Safari.”
That is a Mac OS X issue.
Safari is what caused the issues for some. Perhaps Adobe should drop Premiere Pro from the Mac platform. Having said that you like to find videos and forum threads where a few people are having problems with Premiere Pro. Why didn’t you post videos of FCPX users having problems?
https://www.youtube.com/watch?v=VPo9ac7U3Nw
[Robin S. Kurz] “I did. Only none of what you wrote, aside from maybe the waveform thing, had anything to do with general use i.e. performance that could be relevant to ALL users of either app. As I said, “niggles and bugs” or rather specific use cases that may apply to you, but say nothing about the performance for any and everyone overall, which is what I was looking for. Unless of course you’re saying “FOR ME”, in which case, that’s fine. Just not what I took it to mean or meant myself.”
The supposed timeline thumbnail bug that you mad a big deal out of probably effected less than 100 people. In fact I will ask the obvious question. Has anyone in these forums experienced the timeline thumbnail bug that supposedly brought Premiere Pro to it’s knees? From what I can tell Premiere Pro did not actually crash like FCPX did in my video link.
-
[andy patterson] “From what I can tell Premiere Pro did not actually crash like FCPX did in my video link.”
From version 10.0.6?
Scott Witthaus
Owner, 1708 Inc./Editorial
Managing Partner, Low Country Creative LLC
Professor, VCU Brandcenter -
[Scott Witthaus] “From version 10.0.6?”
I know, right? ????????
-
[Scott Witthaus] “[andy patterson] “From what I can tell Premiere Pro did not actually crash like FCPX did in my video link.”
From version 10.0.6?”
Do you seriously think that is the only bug FCPX has ever had?
The difference between Premiere Pro users and many FCPX users is the fact that Premiere Pro users do not constantly bad mouth FCPX in order to make Premiere Pro look good. I think some people are in these forums to give honest criticism and feedback. I think others are here only to shake their pom poms for Apple. What good does that do other than become annoying? Having said that constantly bad mouthing Adobe or Premiere Pro is not going to make FCPX any better so why do it? Does it make some of you FCPX user happy when a video editor is having problems with Premiere Pro? I can find YouTube videos of bug issues with FCPX. I can also find discussion forums where people have bug issues with FCPX. Why would I want to post about the bug issues with FCPX when I use Premiere Pro? If I start bad mouthing FCPX is not going to make Premiere Pro any better. I myself hope things get fixed with Oliver’s problems when he uses FCPX with third party hardware because I like using 3rd party hardware myself. It may be a bug that is part Apple’s fault and partly a BMD driver issue. Who knows for sure but I hope things get resolved soon.
Reply to this Discussion! Login or Sign Up