Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Forums Adobe Premiere Pro Adobe Premiere (A DISSAPOINTMENT)

  • Adobe Premiere (A DISSAPOINTMENT)

  • Jason Harris

    April 24, 2009 at 2:21 am

    ok i will admit adobe has its strengths, and dont get me wrong I LOVE some of their products, but i have been seeing a downhill slide in certain things, and please lets not tell me its MY system, besides the TEN we tried it on here, numerous people have reported this across the platform of pro users.

    the starting basics are

    system used (FYI this is a system that is not available to the general public yet, our parent company does a lot of work with the GOV so we have some systems we test for them on occasion)

    XP on all systems (NO VISTA) we have enough issues with ADOBE without M$ global F#$%up being in the mix!

    4.9 GHZ ZX core
    4 GB RAM
    2 TB RAID 0 drive
    adobe premiere pro CS4 (and also tried cs3 with a bit better results)

    ok so i take the source footage, which was shot on a sony camera, not sure which one though, i edit it, then i make the output video, but for SOME REASON all the output videos are “jumpy” i mean i know a cameraman sometimes shakes (especially when doing these sorts of sports events) but i REFUSE in fact the SOURCE footage also refuses to show this.

    something with the encoding is screwed up, i dont know if adobe thinks we want to wait 25 minutes for the encoding of a 4 minute video to find out it got screwed up (our company is currently looking for alternatives after this mess up)

    one thing i SUSPECTED was the Frame rate was 25 fps in the source, and adobe was making a 29.97 frame rate output, however when i adjusted this i saw a bit of a change but not enough for a pro video

    we have used

    MPEG 1 (850 MB)
    WMV (45 MB)
    FLV (12 MB)

    none of them show any improvement

    does anyone have any suggestions, the encoding time clearly got better when we tried CS3 and that encoder, but as for the shakiness it still exists, ill be happy to post a link so people can watch the FLV clip, any suggestions would be great, pretty sad for adobe to let its products get released with such major production bugs such as the encoder being so slow and its molesting video during encoding!

    thanks everyone!

  • Eric Jurgenson

    April 24, 2009 at 12:33 pm

    By “Jumpy”, do you mean “Flickery”? Or is the footage actually jumping around on the screen?

    To get the best results, your project (sequence) settings should match your camera settings (resolution, aspect ratio, frame rate, progressive or interlaced scan).

  • Mike Cohen

    April 24, 2009 at 1:19 pm

    Yes, please give more details of project settings. Is this HDV video?
    Premiere, to the new user, can cause some grief even on the super top secret WOPR computer. But once you get used to it it is a brilliant tool. Rendering WMV especially takes time – 25 minutes is not a long time.

    We are here to help, not to judge.

    Mike Cohen

  • Lucas Windsor

    April 24, 2009 at 3:42 pm

    Sorry you have problems, but I have been using Premiere for seven years without almost any major issues. The software itself is just as rock solid as any other popular video editor. I use Final Cut Pro as well and they both run pretty solid.

  • Jason Harris

    April 24, 2009 at 6:15 pm


    I guess what i mean is it LOOKS like the cameraman was shaking his camera, the video is not JUMPING persay, the footage just looks i dont know lol, should i post a flv file so you all may look at it, im not judging premiere right away, i am certainly not new to DV editing, however this is sad,

    25 minutes for a 4 minute clip (wow i have seen vegas and avid do it in like 2 minutes before!)

    ok ill post a flv and let you guys see whats happening before we go further

  • Tim Kolb

    April 25, 2009 at 12:20 am

    I think a link would be helpful.

    Not knowing what camera shot it would make editing with the correct settings a challenge I’d think…

    Director, Consultant
    Kolb Productions,

  • Paul Thurston

    April 25, 2009 at 10:10 pm

    Hi Jason,

    I carefully read your hardware/software system. Some suggestions:

    1. OS… you have CS4 on WIN XP system. That would do it. Even if it’s the 64-bit WIN XP… You have to install CS4 in Windows Vista 64-bit Ultimate. Don’t waste your time with other versions of WIN software… they can work, but you will suffer if you use those other versions.

    2. 4GB of RAM for CS4 is too restrictive. The rule of thumb is 2Gigs of RAM for every processor the OS detects. Too little RAM will make you suffer… it will cause Premier to crash in well-understood programming subroutines too.

    Also, is the RAM the right type? All most everybody gets this part right, but then again, you have to check. Some motherboards, believe it or not, have clear restrictions on what type, amount and slot position RAM is to be installed. Not all motherboards are designed to have RAM in all the RAM slots available.

    3. CS4 seems to like a minimum of two physical processors installed in two physical slots. So if your motherboard has slots for two processors, you’ll be happy if you have processors on all those slots. If you have multicore processors in those slots, you will do even better.

    4. You may have a great RAID-0 that gives you great bandwidth, but did you check the speed of your C-drive. CS4 resides on the C-Drive, and so it’s important to check how many MB/s is this drive giving you. You want a C-drive that gives you at least 50 MB/s. If the C-drive is slower than 50MB/s, you will suffer.

    5. Finally, are the chassis, motherboard, power supply, fans, and other peripherals optimized? Some chassis are just not cool (meaning the internal air flow is restricted causing internal heat to build up… that’s bad news.) Is the motherboard designed for video editing? Some are and work wonderfully. Is the power supply able to handle correctly the amperage requirements of the electronics? In other words, can it supply the number of Watts required? Some power supplies have three or four rails (circuits) and if you connect all the high wattage stuff to only one circuit, you’ll be sad, quite often I might add. Are the fans helping keep things cool? Sometimes you wonder. Are all the softwares running with the proper software updates? If you installed QuickTime, then Premiere, THEN updated QuickTime… bad news. Once Premier is installed, you don’t update QuickTime. If QuickTime is set to update automatically, you’ll be sad and WILL suffer when it updates.


    Paul Thurston

  • Paul Thurston

    April 26, 2009 at 1:03 am

    Here’s something else,

    If you captured the video via Firewire and your timeline setup is not for PAL DV video, the video will flicker on playback. PAL DV has the video fields reversed from NTSC DV video. So it you start with a DV timeline that is for NTSC framerate, the PAL video will playback with fields reversed even if the media is forced to playback at 29.97 fps.

    If the video was shot in PAL and your timeline uses a DV PAL setup and upon playback it still jumps or appears as the fields are reversed, then you have two options.

    1. Put the video on a PAL DV timeline and export the sequence. Edit using only the exported sequence.

    2. Use After Effects to reverse the fields of the media and Edit using only the exported sequence in your PAL DV timeline.

    If your computer has a video capture card, AJA Xena or BlackMagic, you captured uncompressed, you used a PAL timeline setup that works with one of these cards, and it still appears the PAL playback has fields reversed, customer service for the card is in your future.

    Exporting video that has the field order reversed will greatly increase render times.


    Paul Thurston

  • Tim Kolb

    April 27, 2009 at 12:51 pm

    Jason? Do you have that link for us?

    Paul’s input is all correct of course, XP is simply a roadblock to Adobe’s software getting the RAM it needs to run well…even CS3 ran far better on machines that could recognize more RAM.

    On encode…the only way a framerate is getting changed is if you specified that that be the case in the encoder settings…so check those…though the image physically “jumping” as if the camera was shaking is different than it stuttering.

    There are a lot of users who do run this software and if this was a problem in the app, I’d think we’d have heard about it by now.

    So…we’re waiting for a link.

    Director, Consultant
    Kolb Productions,

  • Jason Harris

    April 27, 2009 at 8:56 pm

    hello everyone

    I am sorry for the dealy ,mwe have been busy testing vegas pro, and avid (which are proving to be TEN TIMES faster and MORE reliable then premiere, right now i just want to get a good copy of this video outputted, then cs4 can be done,

    there are faster ways to get reliable production done in my ho

    here is a link to a ZIP file of the FLV output of Premiere pro, sorry its a zip, but cannot upload just flv apparently

    if you have any sugfgestions please let me know (i dont even care how long the encoder takes, as long as its a decent outputted file (or files) because it will be the LASt

    as for the specs, while not concerned to much with all that, i did check with the gurus, they all said specs are running where they need to be, as for vista 90% of consumers contact out IT division to have it REMOVED from their pcs, AND NONE of our business clients will install it whatsoever (and we have over 300 including the GOV) so i dont think anymore needs to be said on that!


Viewing 1 - 10 of 44 posts

Log in to reply.

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