Ivan Knežević
Forum Replies Created
-
Yeah, but I need Premiere Pro for multicam stuff, I do that a lot. But anyway, thanks for reply
-
Hello Dave, thanks for reply.
No, I didn’t rendered same exact footage on older Macbook, but I rendered much complex footages over years of using it, with more LUTs applied, Noise added, name it. But frame rate, dimensions, codec and media container are always the same, Full HD 25fps, h264 .mp4 file. Maybe it could be that I felt like it was faster, but then again, why Premiere Pro is forcing Intel graphic card instead of AMD dedicated one, which has more power.Also, recently I rendered some short video on new macbook in older Premiere Pro CC 2017, and I noticed that AMD GPU usage was higher. (sorry but I need to mention more things I noticed between these two Premieres) On Premiere Pro CC 2017, scrolling through timeline as butter smooth, and clips were appearing almost instantly on my monitor window, with Premiere Pro CC 2019 that isn’t a case, it takes about a minute or longer if I decide to scroll at the middle of clip, like it is conforming clips every time I try scroll through some parts of timeline. And sometimes, it even eject my external drive (where clips are located). One more thing to say, LUTs are horrible in CC 2019, I always have frame rate dropping, and it lags even on 1/4 quality playback…with older Macbook (in CC 2017), that wasn’t a case, and in new Macbook in CC 2017 that isn’t case too.
I honestly more and more think it could be a CC 2019 problem, but I don’t get it, what they are trying to do with newer software, cut every single user with weaker performances, and if that is a case…ok, but why do that to Mac users who use 2017 models? (which, if you ask me, isn’t that old and weak laptop)
Seriously, I like Premiere Pro and all workflow in it, I’m using it over 5 years or so, but I think that I should give a try to Final Cut (even tough I don’t like it workflow, but it seems I’ll be forced to use it)
Sorry for long post ☺
Cheers!
-
Wow, thanks man for such a huge reply.
I’ve been on Premiere Pro since CS6, so, I could say, long time…and after seen so much posts about latest version of FCPX, speed, performance, exporting time, I was just curious is that really better in performance and speed, so I gave it a shot. So, as you can see, problems right away, as I get used to Premiere and all of it wide spectre of offers with Codecs, different file formats ect. I kinda didn’t like the FCPX at first, but now I see where all my problems is. And to mention it, I import straight trough AVCHD container and it was much much better and faster, also with unchecked “create proxy” and “optimize files”. So in the end, I found the solution for my problem, but I think that, still, I’m gonna stick with Premiere Pro.
Thank you again for such great reply, I see that you spare your time and test it also…I appreciate.
Cheers!
-
Check video above that I just posted.
-
https://www.youtube.com/watch?v=KD3k9ohu6WA
Here is the link, screen record of my problem. Read the description for more details.
-
Hello guys,
First, my specs:Macbook 15″ Late 2013
2.3 Ghz i7
16GB RAM
Nvidia GT 750M
1TB SSD
Sierra OS
My issue is quite similar, but yet different. I’m using AVCHD footage from Panasonic GH4, and problem occur in timeline of sequences, depending on capacity of video files in sequence, my timeline starts to lag, while playback runs smoothly, and when I try to pause, or even change camera in multicamera editing, or even change the color of video label, I need to wait around 2 seconds for action I asked for. It’s not quite big deal, but it starts to annoy me. I’m using latest Premiere Pro CC 2015 10.4. with CUDA acceleration.Could it be cause of OSx, or Premiere has bug or two, or my macbook is not strong enough for video editing?
-
Thanks for reply,
Usually, I export video files of 3+ hours, and I’m trying not to cross 12-13 GB of video file, that usually takes about 6000 to 8000 bitrates. Maybe that is too high?
-
I did that “flatten” thing, and that is the nearest solution for my question.
Thank you!