-
1. Re: 550D Footage playback stutter with fast cuts
Jeff Bellune May 4, 2012 5:00 AM (in response to 0rtix)Help us to help you:
Adobe Forums: FAQ: What information should I provide when asking a question on this forum?
You're off to a good start with the MOV file info and some of your hardware specs, but there are still some key details missing.
Jeff
-
2. Re: 550D Footage playback stutter with fast cuts
edengrey May 4, 2012 5:34 AM (in response to 0rtix)Can't you use low res clips and then link to the hd clips once the edit is complete?
-
3. Re: 550D Footage playback stutter with fast cuts
Jim_Simon May 4, 2012 10:49 AM (in response to 0rtix)Based on the information given so far, my best guess is that your system just isn't up to the task.
With this kind of media, ideally you want a fast machine, with an Intel i7 model processor, at least 8GB (and preferably more) RAM installed, and at least three fast hard drives. I suspect if you had that, there would be no problem.
-
4. Re: 550D Footage playback stutter with fast cuts
0rtix May 4, 2012 12:50 PM (in response to 0rtix)Sorry for the late reply guys (and the lack of info, was in a rush and forgot some obbvious stuff)
Here's is a rundown:
Premiere pro CS5.0.3
Windows 7 x64, i7 Q720, 4GB RAM and a Quadro FX 550M.
The video is h.264 in a MOV container. The mediainfo dump can be found here:
As for the general problem description:
This has worked before with MTS files from my canon hf s10, but there were not fast cuts there. Here the cuts are at most 3 seconds long but usually a second or 2.
Furthermore I am running the latest CCCP codec pack and that's it really. No other garbage installed on here. The videos have no effects at all. Mercury GPU and Software give exact same result (software seems a little better) and this happens in all resolutions when I preview.
Hope this helps (and helps me too! )
-
5. Re: 550D Footage playback stutter with fast cuts
Harm Millaard May 4, 2012 1:14 PM (in response to 0rtix)1 person found this helpfulDon't know if this will help but if you never shoot, you will never hit anything.
Rewrap the .MOV files in a MTS wrapper (leaving the H.264 codec intact). It may be that this step will avoid the 32 bit QT server and its inherent slowdown.
I'm not familiar with the CCCP codec pack, but when I hear the word 'Codec pack' I almost get a severe heart attack. Most of the time it is disastrous, requiring a complete reformat and reinstallation of OS and programs.
Basically when scrubbing you need really fast disks and it appears you do not even have the practical minimum of three physically different 7200 RPM SATA disks installed. One disk will not do.
-
6. Re: 550D Footage playback stutter with fast cuts
0rtix May 4, 2012 1:31 PM (in response to 0rtix)I did not think that such high specs would be necessary to edit DSLR footage... iMove has no issues whatsoever with this and i'm running that on a 2009 MBP. This is also not a movie editting computer. It's just a school computer. I just do this for fun. I got PP for a crazy discount since I'm a student. I'll try rewrapping it though.
-
7. Re: 550D Footage playback stutter with fast cuts
Harm Millaard May 4, 2012 2:00 PM (in response to 0rtix)1 person found this helpfulJust a wake-up call: DSLR is one of the most difficult codecs to handle. It really requires a beefy computer. Second, and that is where a lot of people make mistakes, is that editing requires a lot of disk I/O and the problem with SATA disks is that the connection is half duplex. Traffic is only allowed in one direction at a time, it can't read and write at the same time, so in effect traffic going in one direction must wait for the traffic from the opposite direction to have passed before it can use that single lane. That always causes delays, especially when you take into consideration the Windows housekeeping tasks that also require the use of that single lane.
Just the other day I tested the required sustained transfer rates with a single track AVCHD timeline and it needed around 50 MB/s, with three tracks it went up to around 95 MB/s and with the addition of RED 4K material and some more tracks, it needed more than 300 MB/s transfer rate for simple playback. Scrubbing the timeline requires even more.
-
8. Re: 550D Footage playback stutter with fast cuts
Stephen_Spider May 4, 2012 2:36 PM (in response to 0rtix)CS5x edits the footage natively, while iMovie, Final Cut Transcode the material to a less complex codec.
-
9. Re: 550D Footage playback stutter with fast cuts
Jim_Simon May 4, 2012 3:26 PM (in response to Harm Millaard)I tested the required sustained transfer rates with a single track AVCHD timeline and it needed around 50 MB/s
Given that the data itself only requires 5 MB/s or less, I find that hard to believe. You sure you didn't add an extra 0 there?
-
10. Re: 550D Footage playback stutter with fast cuts
Harm Millaard May 5, 2012 9:25 AM (in response to Jim_Simon) -
11. Re: 550D Footage playback stutter with fast cuts
0rtix May 5, 2012 11:53 AM (in response to 0rtix)It seems that I had to rename all the MOV files to mpg. This seems to fix the issue (now the files don't have to go to the 32 bit QT engine). So anyone any idea on how to batch replace the clips?..
-
12. Re: 550D Footage playback stutter with fast cuts
Ann Bens May 5, 2012 11:58 AM (in response to 0rtix)1 person found this helpfulYou can do that in the Bridge.
-
13. Re: 550D Footage playback stutter with fast cuts
0rtix May 5, 2012 12:01 PM (in response to Ann Bens)I know I can batch rename the footage, but how do i replace the footage INSIDE premiere pro. After the footage is .mpg, the files are offline and need to be linked or replaced.. Ideas? Going through 100+ clips manually is kidn of a game breaker :')
-
14. Re: 550D Footage playback stutter with fast cuts
Jim_Simon May 5, 2012 6:14 PM (in response to Harm Millaard)Single track AVCHD just playing the timeline.
What does this look like:
It looks like it's time for you to take some of your own tweaking advice there, Harm. Here's what I got.
1 stream...
4 streams
That's from a single drive. Yes, it peaked at around 50, probably to fill the cache, but then leveled off to the expected average of 5MB/s for 1 and 20 MB/s for 4.