It does this in the Source Monitor or the Program Monitor? If it's OK in the Source Monitor, but not in the Program Monitor, I'd guess that your sequence field order does not match your footage field order. The footage should be Upper Field First; your sequence should match.
A quick way to set this up and test this theory would be to drag one of your clips to the New Item button at the bottom of the Project Panel, like this:
Any better when you do that?
It occurs in both monitors and in the final rendered video. I did try the new sequence (as suggested by the help for certain problems like this), but that didn't change the behavior.
Does it occur with media from all cameras, or only this one?
[Thanks, by the way, to both of you who responded.]
I only have the one camera, but I'll try to find someone with a .mts file that I can download and try.
I downloaded a sample .mts file from dpreview for a Sony 1920x1080 avchd camera, and it seems to exhibit the same problem. (At least in the source window; I didn't render any video or move it into a sequence.)
I also have a Canon Vixia HFS100 and do not have the problem you discuss
I use 1920 x 1080 60i FXP 17Mbps instead of MXP 24Mbps
What happens if you go down to the FXP setting?
My CS5/AVCHD 1st Impressions http://forums.adobe.com/thread/652694?tstart=0 includes a link to the computer I built
OK, if it happens with both cameras, I'm leaning towards a graphics driver issue. Try downloading the latest from either the nVidia or ATI (AMD) web site.
Thanks, Jim. I assume you're talking about not just displaying the video, but how the graphics card is used during the original decoding and rendering process. I can view the final video on other machines (e.g., such as on my iPad through the YouTube link above), and I see the bounce.
I know I have the latest nVidia driver; I just checked.
I'll try an FXP video from my camera. I can also try a second machine.
Thanks for your thoughts.
It doesn't have anything to do with the graphic driver--graphic drivers don't influence exports (in that way). The files are somehow being interpreted incorrectly. Can you upload a short sample somewhere as a test?
graphic drivers don't influence exports (in that way).
That's a good point.
This may or may not be of any help but your original issue rang a bell...
If I remember correctly,
1) I received a dvd of home videos to strip out a clip of a kid playing guitar
2) The source footage played fine on the disc
3) I placed the VOB file into a PPro CS5 timeline and while it played back it also had the jumpy motion you are referring to
4) When I changed the extension from .vob to .mpg and reimported it played fine with no jumpiness (I never tested an export)
I have no idea why the extension would matter but it seemed to clear things up. I never went deeper into the issue after it was resolved.
Hope this helps,
I used the ImageMixer software that came with the camera to extract a 20MB file. In ImageMixer, it displays fine. In Premiere Pro, it moves up and down slightly, a couple of times a second.
Here's a link to the file:
If it looks okay to you in Premiere Pro, there must be something wrong with my Premiere Pro's decoding of the file.
The file works/looks fine here in both CS5 and CS5.5 (Windows). No up/down shake, that I can discern.
I think you're right that there is something wrong locally where the video is being decoded improperly. You don't happen to have something like ffdshow installed, do you? That can royally mess up Premiere Pro--looks great on the surface because you can import everything but it has a horrible habit of overriding the proper and optimized importers and decoders for Pr. Anything like that installed currently?
I tried on a second machine. (An entirely different machine; the original's a desktop/the second machine is a laptop.) I still see the up/down motion.
Perhaps it's something in my sequence preset choice. I chose AVCHD 1080i30 (60i). (I also chose AVCHD 1080p30, to compare, and it didn't seem to make a difference.)
I don't know that I have ffdshow installed, but I suppose some other software package might have installed an ffdshow decoder somehow. The only other video editing software I have is the PIXELA stuff that came with the camera.
That's very odd. As mentioned, the file is fine here; tried it on another machine, and it's rock-solid there, too.
The sequence preset would be a plausible explanation if you were only seeing this in the Program Monitor or in an export--but you're seeing it in the Source Monitor as well. The Source Monitor always displays footage exactly as it was shot, without any interpolation based on the sequence settings. And, I'm able to play this back perfectly well in both the SM and the PM. That's what inclines me to believe that something external to Premiere Pro in your setup is affecting decoding.
Is this Pixela stuff installed on the laptop, as well? When you play back the file on either machine in Premiere Pro, do you see see some sort of icon appear in the Windows tray (that area around the clock on the right end of the taskbar)? In Task Manager (right-click on the taskbar and select Task Manager), do you see any sort of unknown processes operating? Can you uninstall the Pixela software? A lot of software manufacturers will include things like ffdshow in their products, since they don't have to pay for licensing of these codecs; the problem is that they are usually completely inappropriate for a professional editing environment, and can lead to issues like the ones you're describing.
>used the ImageMixer software that came with the camera
Hmm... as I said in the link I provided earlier, I just use Windows Explorer to copy the MTS files from the camera's memory card to my computer data drive
I wonder if the problem is being introduced by the Canon software?
Try using WinExplorer to just copy the entire folder from camera memory card to hard drive, and then import files from that hard drive folder to PPro
The laptop doesn't have the PIXELA software installed. I also don't see anything in the system tray when playing video, on either machine.
I will try copying the files directly from the memory card.
And just to make sure I'm explaining myself clearly, can someone confirm that they see the issue with the YouTube video (link above)?
Oh yes--it's there and very obvious. But as mentioned, it doesn't happen when I import, playback, or export your file.
Can you right-click your clip, go to Modify > Interpret Footage and post a screen shot of that? Also, do the same with your Sequence Settings.
OK, everything looks square with that; the clip you posted imports exactly the same way and a sequence with identical settings exhibits no such issues.
I'm stumped at this point. If there isn't anything else coming between the file and Pr, there's really no reason that you shouldn't be OK with this file. Have you tested other non-AVCHD media? I know you tried another AVCHD clip, but try this one: http://www.mediafire.com/?migauydde2mf16h. It's AVCHD, but a progressive format.
By the way, is CS5 fully updated? You should be on CS5 5.0.3.
Thanks for your help.
Since that video clip was handheld, I couldn't really tell if it had the problem.
I am running version 5.0.3.
I did download some other non-AVCHD media, and did not see the problem. I downloaded some other AVCHD media, and did see the problem.
I tried to find some progressive media in AVCHD format, but there's a lot of stuff out there that's not clearly labelled as to whether it's progressive or interlaced.
So there seems to be something wrong with whatever decodes AVCHD video. Is there something I can check in Windows or in Premiere Pro to see what decoder is being used? Is there a way to tell Premiere to use a different decoder?
D'oh! Silly me. Try this: http://www.mediafire.com/?gdbdlcbknccm1ek
That's 1920x1080 at 23.976p. It's locked down, so it should be a little bit easier to tell if it exhibits the problem. This clip is from a totally different camera, but about the same bitrate.
If you're only seeing it with AVCHD, of whatever flavor, it's something coming in between the footage and Premiere Pro--not Premiere Pro itself. You can probably open Task Manager (described above) and keep an eye out for any odd programs popping up when you playback the MTS files.
I'm befuddled as to why it might be showing up in another system of yours, however, but not mine...
Colin, the latest progressive video you uploaded is rock solid, so the problem appears to be with AVCHD interlaced videos. I also need to go back and try creating an FXP (2nd to highest quality) video to see what happens.
Interesting. OK, you said that the short test snippet you posted above displays the issue, right? Can you create a project using just that file, drop it in a sequence, confirm that the problem appears, and then upload the project file for testing? No need for the clip, if you use the one above--I've still got that one.
3:2 pulldown artifacting? Try adjust the 24P conversion method in your playback settings.
Brian--you've really got me stumped on this one! Everything is checking out--project looks fine, media looks fine, settings look fine. At this point, I'm about 100% positive that there is another decoder wresting away control of the AVCHD footage from the Premiere Pro decoder, but what that is, I'm not sure.
If you're willing, try uninstalling the Pixela software. Do you have any other video applications installed? If there is anything you have installed, post a listing; maybe something there will stick out.
Ah.... The 24p clips were Colin's, not Brians. Nevermind.
Just for fun, I uninstalled Premiere Pro and reinstalled it. It still exhibits the problem.
Other video-related software installed... QuickTime, iTunes,Windows Media Player on both computers.
On the desktop, I also have some webcam software (but not for movie-making; just working with the webcam) and Windows Media Center, but these aren't installed on the laptop.
My desktop is Win 7 Ultimate. The laptop, I believe, is Win 7 Enterprise.
Brian--you're killing me here, man!
Alright, let's try this file: http://www.mediafire.com/?il5p11y7p3vkndp
That's the M2TS file you uploaded, rewrapped as an MP4 file--same video, same audio, different container. That will tell us if the splitter/decoder for MPEG Transport Streams (the container used for AVCHD) is being hijacked somehow. As an MP4, it might be using the same splitter, but it's worth a shot.
The mp4 file you uploaded also shows the problem.
OK, with the M2TS file in Premiere Pro, in a sequence, open up Task Manager; you can right-click on the Taskbar to do this. Go to the Processes tab, and take a screenshot; you might have to take two if the list is long. I want to see everything that is running whilst Premiere Pro is running.
No wonder you have problems. The number of processes should be around 40-50 on a good system. Kill all the crap and try again.
Thanks, Harm. I'm pretty sure, though, if I kill all of those processes, Windows won't function. Do you see specific processes that I should try to kill?
That is a lot of processes, but that's not necessarily the cause of the problem here. That quantity would certainly affect performance to a degree, but not cause the issue you're seeing.
I was hoping to see something obvious like "ffdshow," but it looks like mostly standard computer and networking stuff. There are a couple I'd suggest disabling--or even uninstalling--and those would be any with Roxio or PowerDVD or similar names. I'd recommend trying to completely uninstall those, unless you desperately need them; those may have some other decoders they are installing that are overriding the "good ones" in Pr. Give that a shot, if you're game...
Harm, I started killing processes. From time to time, I tried playing the clip, and it continued to have the problem until I killed enough processes that Premiere Pro stopped responding. And then I rebooted--I had to power cycle, because Windows wouldn't shut down all the way.
Colin, I uninstalled both Roxio Creator and Cyberlink PowerDVD, and sadly, the problem persists.
iPod, iTunes, IBM, McAfee, mDNSResponder, jusched, in addition to what Colin mentioned are the first ones that you can easily kill. If you use ProcessExplorer to make a new screen grap of running processes, I will give you other processes to kill.
It may pay to use CCleaner to prevent processes at startup like iPod, iTunes to nestle themselves on your system.