DV Info Net

DV Info Net (https://www.dvinfo.net/forum/)
-   Canon EOS Crop Sensor for HD (https://www.dvinfo.net/forum/canon-eos-crop-sensor-hd/)
-   -   DNxHD coded stuttering in CS4 (https://www.dvinfo.net/forum/canon-eos-crop-sensor-hd/471464-dnxhd-coded-stuttering-cs4.html)

Perrone Ford January 24th, 2010 10:31 AM

Quote:

Originally Posted by Jack Derman (Post 1476470)
Perrone:
I have worked with HDV material on an first generation AMD dual core from 2005 with only 2 gigs of RAM. No problems on that. The .mov files I created from the original .m2t were very smooth and nice. Granted, as you have explained, that material has about half the bitrate of the 7d files, but then again my current machine is about 4x as powerful as my previous. It is far from a "consumer" spec PC, so I very much doubt my computer is at fault here. I'm more compelled to blame Windows 7, which, in retrospect, should have never upgraded to...

Not only is HDV half the bitrate, it's also not full frame, and it uses a completetely different encoding strategy with MUCH simpler math required to decode on the fly. For most people this trifecta is too much to overcome... higher bitrate, larger frame size, far more complicated codec. It's nothing like HDV.

Quote:

Originally Posted by Jack Derman (Post 1476470)
The codec just makes my life easier while editing, it doesn't increase the quality of production or the piece of work.

Quite the contrary. Moving to a 10bit codec in post can increase your quality as you manipulate the footage. The difference can me quite large and very easy to see. Especially if you are manipulating colors (white balance, color grading).


It seems I cannot convince you of what you're up against. So I wish you the best.

Jack Derman January 25th, 2010 02:09 AM

Interesting, I will need to look at some options regarding my computer...perhaps I need to run those adobe updates I've been delaying...

And Perrone, you have not failed in convincing me. I KNOW I should probably be editing in a 10-bit .avi codec, but I'm just not convinced that I NEED cineform to do that.

I'll work with proxies for now as its doing pretty fine. My question is, however, do I replace the proxy footage with the original 7d h.264 .mov files, or link them to DNxHD files? I'm judging by the information in this post that my various cuts will have less of an impact on the DNxHD files than the h.264 files.

Perrone Ford January 25th, 2010 02:46 AM

Quote:

Originally Posted by Jack Derman (Post 1476470)
And Perrone, you have not failed in convincing me. I KNOW I should probably be editing in a 10-bit .avi codec, but I'm just not convinced that I NEED cineform to do that.

What other 10-bit .AVI codecs are you aware of? I'm not aware of any.

Quote:

Originally Posted by Jack Derman (Post 1476470)
I'll work with proxies for now as its doing pretty fine. My question is, however, do I replace the proxy footage with the original 7d h.264 .mov files, or link them to DNxHD files? I'm judging by the information in this post that my various cuts will have less of an impact on the DNxHD files than the h.264 files.

The point of Proxy footage is that you have a low-res but accurate representation of the original or source footage on the timeline to work with. The inherent problem here is that you either need an AVCHD proxy set to work on and replace with the full-res AVCHD files, or you need a proxy DNxHD set which is DNxHD 36, but that will still run like a dog in Premiere. And you'd need to replace it with the full res DNxHD files instead of the original AVCHD sources.

Ideally, you'd want your proxy files to be encoded with the same codec as the source footage so the color space is the same, and so that the changes you make on the proxy will accurately reflect the changes on the full sized images. You just cannot guarantee this if your proxy is encoded differently from the full size files. I've done it that way and it was always more work.

There's lots of ways around this problem. But all will cost you time, convenience, or quality. I "can't" use Cineform, so I choose to sacrifice time, because I refuse to sacrifice quality.

Peter Moretti January 25th, 2010 03:04 AM

Quote:

Originally Posted by Jack Derman (Post 1476470)

... my current machine is about 4x as powerful as my previous. It is far from a "consumer" spec PC, so I very much doubt my computer is at fault here. I'm more compelled to blame Windows 7, which, in retrospect, should have never upgraded to...

Bruce:
I very much agree with you, budgets account for many different factors and for myself, the $99 cost for a codec just isn't justified right now. Perahps in the future, but as it stands not so much. The codec just makes my life easier while editing, it doesn't increase the quality of production or the piece of work.

...

You mention later on that you have not applied Adobe updates, which leads me to believe that you did not do a clean install of Windows 7. In which case, who knows how well your computer is running.

That said, I believe Cineform has a free trial. Check it out and see if does the job for you. Once you realize that it actually increases the quality of your image, not just the speed of editing, you may think it's worth the $100. I think there is no doubt that it is.

Mike Calla January 25th, 2010 03:35 AM

WinXP 32, but i do cuts only, and nothing longer than one minute (tv spots bascially).


All times are GMT -6. The time now is 01:07 AM.

DV Info Net -- Real Names, Real People, Real Info!
1998-2025 The Digital Video Information Network