T2i Jumpy video with T2i, PC processor problem?

six60

New member
I'm a new DSLR user and just bought the t2i. i did some small video clips as tests and they look great playing back on the camera but once on my PC they are jumpy. Im using a class 10 sd card. I did notice my processor is only 2.2 ghz and the recomened is 2.6, would that make it jumpy? any thoughts?
 
Copy your media to a hard drive, transcode it to something less taxing to your computer. Don't use a USB 2.0 drive, stick to eSata, or firewire.
 
Copy your media to a hard drive, transcode it to something less taxing to your computer. Don't use a USB 2.0 drive, stick to eSata, or firewire.

While eSata can help speed things along, its nowhere near the bottleneck of a slow CPU. Firewire isn't always faster either (If I recall correctly, firewire is better at sustained throughput, like copying a large file, but USB2.0 was faster at short bursts, which is what you would be doing if scrubbing through a timeline). While I agree that its good advice to get eSata over USB2.0 if you can afford it, that would be my LAST suggestion, after you've done anything else you can. A good computer can edit fine over USB 2.0 drives. Better yet, if you're not using a Mac, you can go with USB 3.0 if the drive supports it (last I checked, Apple still didn't show any love for the new USB standard, despite the availability even on low-end Netbooks!), which is just super fast and awesome, not to mention backwards compatible if you need to move to hum-drum editing station that only supports USB 2.0 for a bit.
I used to edit on a eSata, then took my work home with me only to realize I had forgotten my home computer does not have eSata external ports. Much happier sticking with USB, and no noticeable speed difference honestly.

Transcoding is great advice, I would try the Avid DNxHD codec (free) and one of the recommended transcoding apps on the forum. Your footage will take up tremendously more space, but use far less CPU power to work with. Remember, h.264 is an extremely computationally expensive format to decode, and only used in our cameras because it can get great quality-to-size ratio with the limited space of an SD card. It is murder on processing power to play without hardware acceleration, and widely regarded as an inefficient format for editing.

However, there are some editing suites that are better at it than others. Final Cut for example, is notoriously bad at editing native files from our camera, as was Premiere until recently.
Sony Vegas has been supporting great h.264 native support for a few years now, and Premiere CS5 now offers it as well. What NLE are you using to edit? Is it choppy in just playback as well (using, say VLC player), or only in the editor?

If its choppy even just playing back in your media player, than your computer just isn't strong enough. I had an editing laptop that I used to bring on-site for quick edits, but the specs were a little dated now (core 2 duo 2.1Ghz), and when I switched to HDSLR footage, it barely was able to keep up. Yes, transcoding would help, but if you're not some sort of hell-bent MAC-only user, you can replace your old PC with something really fast for less than the price of an Adobe upgrade these days, which I found a MUCH better option!
I ended up taking advantage of a 20% off the Dell Outlet coupon a few months ago to replace my editing laptop. Got a really nice refurbished Core i5 2.5Ghz for around $400 shipped to me, and managed to sell my old laptop for around $300 and change. The Core i5's architecture makes h.264 editing a breeze, and running Production Studio CS5 as well as Vegas 9 on it are just an incredible value. Not sure what your specific situation is, but I'd look into that. As long as your not Mac-exclusive, editing stations are cheap these days!
 
Last edited:
Its choppy in my media player, thats where i first discovered it, and in Premiere. I'm not sure what to do now.
 
What generation processor do you have? I see 2.2Ghz, but is that a core 2 duo? Core Solo? i3? i5? i7? Athlon?

On an i7, a 2.2Ghz chip is MORE than powerful enough. But on a Core 2 Duo, its just barely at that mark that would make editing (and even just playback at 1080) a problem.

You could always transcode, but you shouldn't have to with a modern computer.
 
Its choppy in my media player, thats where i first discovered it, and in Premiere. I'm not sure what to do now.

Silly question but did you render the footage? Otherwise, try using the software that comes with the camera - it does a good job of at, the very least, letting you look at the footage.

Otherwise, I think you need to break down exactly what you're running, software and hardware-wise.
 
I did notice my processor is only 2.2 ghz and the recomened is 2.6, would that make it jumpy? any thoughts?
A 2.2Ghz Celeron processor running Windows is not going
to have enough horsepower to deal with the t2i MOV video
format. You'll have to transcode the MOV file into something
less compressed first to take that work off the processor.
I transcode into DV format and that will generally allow a
lower power processor like a 2.2Ghz Celerion to deal with
the MOV format. But still things run slowly even under the
more efficient Linux OS.
 
Okay, i got it converted using Prism (not sure if thats the best) and now the video plays fine, are there any tricks for the quaility with settings?

my processor: AMD athlon 64 x2 dual core 4200+ 2.2GHz.
I edit in Premiere CS3.
 
Back
Top