Forum Replies Created

Page 2 of 2
  • Connor Roberts

    January 24, 2008 at 4:56 pm in reply to: Premier pro failed to return a frame

    sometimes this happens when lots of effects are stacked on one clip, or just one effects is on a file like a PNG or something obscure that premiere pro is not used to working with. this also happes when lots of audio editing has occured, so what i always do is export my audio before i render, and just have one finalized audio track in the timeline, THNE i render.

    also, export using Adobe Media encoder instead of AVI, that way when it stops you will still have the file…whereas when you export to AVI, the file is deleted if it doesnt finish. If you use Adobe Media Encoder, you will can watch the part it did export up until the problem point and find out which frame(s) are giving you trouble, and just go in and modify those.

    I have found that just restarting premiere many times will let me export…OR just render that one problem segment by itself (razor/cut it our of your main sequence to its own sequence, render it to highquality AVI or whatever format you are working in, then put that rendered piece back into the timeline…sometimes i have to render 7-8 AVI pieces for my projects, then put them all together because I use lots of 3rd party plugins that premiere doesnt like when having to do one long render.

    ::: Connor

  • of course not. would the macbook run it? no, it isnt “pro”, so why would the marcbook air run it? the old macbook pro’s are still better than the new macbook air. it is like a macboon mini kinda. ipod better than ipod mini. stick with macbook pro if you want a mobile editing machine.

    ::: Connor

  • Connor Roberts

    January 21, 2008 at 5:13 pm in reply to: Premiere Pro on Mac vs FCP?

    NO NO NO NO NO!

    I am a 10yr Premiere Pro user, and the new CS3 is HORRIBLY slow on MacOS. It is not nearly as quick and responsive as CS3 on Windows, and crashes doing basic things that never happens on Windows. this may be a limitation of MacOS and how it handles memory worse than XP, or could be the fact that CS3 is new to Mac (vastly different than old Mac versions) so it is basically all new programming.

    Trust me, or don’t trust me – just use Premiere Pro on Mac for a day…you will hate it. I edit with Premiere Pro every day on PC/XP and NEVER have issues; my workflow is like lightning. I tried the same set up on Mac (Premiere Pro CS3 and Encore CS3)….no dice man. It ran slow, crashed on simple tasks like audio fades and stuff like that.

    If you are on MacOS use FCP, If you are on Windows use Premiere Pro. Contrary to popular belief, they BOTH are just as powerful as one another now, and the only reason studios use FCP over Premiere Pro is because in the 90’s, Premiere Pro was far behind. Now, in many ways, it’s technology is far ahead, and the interface is identical. Just go to Google images and look up FCP Screenshots, and Premiere Pro screenshots…there is all this talk about how one is better than the other, and the people who say that are the ones who have never used anything but ONE of the programs. They both do the same thing, and they both do it just as powerfully…all have same native transitions, effects, color correction, export features, etc…

    BY THE WAY: I have one of the newer Intel iMacs 24″, 2.8ghz intel core2duo, 4gb ram, and I run Windows XP on it with PPCS3, and it runs SOOOO fast. So I would recomment installing bootcamp, and make a 100GB partition with with Windows XP and CS3 installed, then install CS3 on Mac partition also, and try it yourself…everything I have said in this post will make sens when you do.

    ::: Connor

Page 2 of 2

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