Adobe Premiere (A DISSAPOINTMENT)

	Re: Adobe Premiere (A DISSAPOINTMENT) by Eric Jurgenson on Apr 24, 2009 at 12:33:47 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). Respond to this post   •   Return to posts index

	Re: Adobe Premiere (A DISSAPOINTMENT) by Mike Cohen on Apr 24, 2009 at 1:19:15 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 Respond to this post   •   Return to posts index

	Re: Adobe Premiere (A DISSAPOINTMENT) by Lucas Windsor on Apr 24, 2009 at 3:42:14 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. Respond to this post   •   Return to posts index

	Re: Adobe Premiere (A DISSAPOINTMENT) by Tim Kolb on Apr 25, 2009 at 12:20: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... TimK, Director, Consultant Kolb Productions, Respond to this post   •   Return to posts index

	Something to check out by Paul Thurston on Apr 25, 2009 at 10:10:55 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. Regards, Paul ----------------------------------------------- Paul Thurston Producer Chile Respond to this post   •   Return to posts index

	Something to check out II by Paul Thurston on Apr 26, 2009 at 1:03:40 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 ----------------------------------------------- Paul Thurston Producer Chile Respond to this post   •   Return to posts index

	Re: Adobe Premiere (A DISSAPOINTMENT) by Tim Kolb on Apr 27, 2009 at 12:51:41 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. TimK, Director, Consultant Kolb Productions, Respond to this post   •   Return to posts index

	Re: Adobe Premiere (A DISSAPOINTMENT) by Eric Jurgenson on Apr 28, 2009 at 12:39:17 pm Jason, you've got so much going on in this clip, it's hard to tell what is a technical issue and what is intentional. But let's presume that this is intended to be a straightforward edit with cuts and dissolves, and all the positional and temporal jumps, and the wierd color transitions are caused by a glitch in the machine. In that case, you are running Premiere on the wrong system, dude. None of this stuff is normal, and I've never come across this type of problem, personally or in the forums. In fact, if I weren't a naturally trusting soul, I would suspect that you are pulling our leg. Respond to this post   •   Return to posts index

	Re: Adobe Premiere (A DISSAPOINTMENT) by Jon Barrie on Apr 29, 2009 at 1:06:59 am 640x480 with 25fps is not a standard format, how was this footage recorded? I think there is something going on with the MPEG-2 style of recording (long GOP) conflicting in the export process. Have you tried to reinstall? Jon Barrie aJBprods www.jonbarrie.net Respond to this post   •   Return to posts index

	Re: Adobe Premiere (A DISSAPOINTMENT) by Jon Barrie on Apr 29, 2009 at 1:22:06 am Hi Jason, Please understand that we are all stumped by this. we are only trying to help. asking questions is how we get a clearer picture on the situation. When I say 640x480 with 25fps is not a standard format, I mean no camera to my knowledge shoots NTSC frame size with PAL frame rate. Not that the camera is not professional. I've worked with Adobe Products for years and they do support more formats than most, I'm downloading your link to the original footage. I'll get back to you about the findings. - Jon Jon Barrie aJBprods www.jonbarrie.net Respond to this post   •   Return to posts index

	Re: Adobe Premiere (A DISSAPOINTMENT) by Jon Barrie on Apr 29, 2009 at 5:09:52 am Hi Jason, There is no need to get your hands on any other software other than what you already get with CS4. 1. Open the Adobe Media Encoder, as a stand alone app. 2. Click on the Add button, select the first mpg clip 3. Set the Format to Quicktime, Preset to PAL DV 4. Click on Add button again and select all the rest of the clips. 5. They should all have the same settings applied to them all. 6. Hit the Start Queue button, Once the renders are done they can be imported to PPro and edited properly. The footage you are starting with is in a poor format that is running a very small data rate. The progressive nature of the recording makes the footage stutter, the camera seems to not have a stabiliser on or at all again making it stutter and jumpy, the fact that it's MPG means the GOP format is not suitable for editing. I think this camera is meant to be used for instant record/upload to web and not for editing. Good Luck. - Jon ';) Jon Barrie aJBprods www.jonbarrie.net Respond to this post   •   Return to posts index

	Re: Adobe Premiere (A DISSAPOINTMENT) by Jon Barrie on Apr 29, 2009 at 6:39:19 am Hi Jason, You need to match the frame rates from the original. If you alter the frame rate you create jumpy stutter issues. this is rule of video. Glad to see it's all working to some effect. I noticed that the original footage is not true 25fps. it holds a frame every 2nd or 3rd frame for one frame. How did you get the footage from the camera to the computer again? - Jon :) Jon Barrie aJBprods www.jonbarrie.net Respond to this post   •   Return to posts index

	Re: Adobe Premiere (A DISSAPOINTMENT) by Jon Barrie on Apr 29, 2009 at 6:50:01 am The original footage dictates the rest of the workflow. If the recording was 25fps you need to work in projects with 25fps, the frame rate should be matched too, but there is some flexibility with that, keep to a preset format like PAL DV Standard for your stuff. If you do convert the original footage then the conversion must stick with the same frame rate. Staying with the same frame size (640x480) as the original is going to maintain the best sharpness of the image. Adobe Cs4 is a complicated set of tools for trained professionals and can be daunting and frustrating to those that don't understand the theories of Video and Editing, so hats off to you for asking, providing material and working it out. You've in effect experienced more than a course teaches in a month. ;) - Jon :) Jon Barrie aJBprods www.jonbarrie.net Respond to this post   •   Return to posts index

	Re: Adobe Premiere (A DISSAPOINTMENT) by Jon Barrie on Apr 29, 2009 at 11:32:10 pm From the two clips you uploaded the mov converted one looks fine, at the quality of the flv file it looks like how it should. If you are working with progressive frame rates you should keep working in those. frame rate is crucial - can't stress that enough. You can make a custom desktop mode editing preset where you can set the frame size, the frame rate, audio sample rates etc to match the properties of the captured footage. But always convert this type of footage to an editable frame accurate, each frame is a complete self contained frame that doesn't rely on other frames to work out the compressed chroma/luma information (long GOP - MPEG). Premiere Elements has the codecs for consumer formats like MPEG-2 and MOD from JVC Everio cameras, etc and works with them better. Only draw back to Elements is that it is only on the PC. But you can use it to convert your footage, it's not that expensive either. (the link you provided in last post doesn't link to it, the first post does though) - JOn :) Jon Barrie aJBprods www.jonbarrie.net Respond to this post   •   Return to posts index

	Re: Adobe Premiere (A DISSAPOINTMENT) by Jon Barrie on Apr 30, 2009 at 11:08:06 pm Jason, No that is not crazy - actually quite a common process. The problem with it working immediately and not as a one by one file relink case is that the file extension is different, so you may get a warning each time you force a relink. But that is the way to do it and keep the edits you've made. Just so long as the frame rate is the same as the edited versions and the absolute first and last frames of all the clips are exactly the same = same duration, then it will all come together nicely. - Jon ;) Jon Barrie aJBprods www.jonbarrie.net Respond to this post   •   Return to posts index

	Re: Adobe Premiere (A DISSAPOINTMENT) by Alex Udell on May 1, 2009 at 5:38:42 pm Hiya... Diagonal bars on a clip or transition in the sequence is an indication that the Clip event on the timeline is of a longer duration than the media file it's connected to. Sounds like something is not quite right with the conversion....with regards to the frame rates...where the new sources you are connecting to are too short... that's also why things are going black.... you need to compare the original source versus the converted source in the timeline and see if the converted source plays a little too fast... Alex Respond to this post   •   Return to posts index