Dave Blackhurst
August 15th, 2011, 02:11 PM
I know this is more for the NX70 (someday...), but it's as good a place as any since DVi doesn't have any forums for the smaller P&S and handycams that now shoot 60p...
Just picked up a DSC TX100 that does 60p (for about 1/10th the cost of the NX70), running into some "issues" with 60p... doing some "stress testing", some shots of a ceiling fan in room light (fan has lights on it), running of course. This throws shadows, has whirring blades, all sorts of stuff to wreak havoc on the video/codec!
ANYHOW, video shot with a TX10 (TX100's rugged baby bro) in 1080i looks quite good - pausing the video in PMB or Vegas Pro 10e (or displayed direct to an HD big screen) looks pretty good, no painfully obvious artifacts, only slightly softer than the same scene shot with CX500.
HOWEVER, either 1080i or 1080p shot with the TX100 shows substantial blocky banding and other nastyness... Since the CMOS and general design of the two cameras is so similar, I was caught off guard by the differences, beginning to suspect that there is a diferent encoding chip in the two cameras.
I've still got more testing to do, but trying to figure out if there is some trick I missed for proper handling of 60p clips. I know I've seen samples shot with some of the new Sony P&S cams (TX100 included) that shoot progressive, and they looked great! Trying to figure out what it is I might be doing wrong, or did I just "overstress the encoder" with this particular shot?
FWIW, same scene shot with a CX500 (60i) showed a little bit of similar blocking/banding on a FEW pauses, where the TX100 was pretty much banding on every pause... the TX10 showed no banding/blocking?!
I was expecting a bit sharper and cleaner results, given 60 progressive frames, but the 60i looks almost as good if not better, so either the implementation still needs some work, or I'm missing something...
Any thoughts, suggestions, etc? Was really hoping to start to integrate 60P into the workflow, sticking my toe into the water as it were, now I'm not so sure...
Certainly more testing is in order, but want to get the image quality question sorted out. Wondered if anyone else had hit this snag...
Just picked up a DSC TX100 that does 60p (for about 1/10th the cost of the NX70), running into some "issues" with 60p... doing some "stress testing", some shots of a ceiling fan in room light (fan has lights on it), running of course. This throws shadows, has whirring blades, all sorts of stuff to wreak havoc on the video/codec!
ANYHOW, video shot with a TX10 (TX100's rugged baby bro) in 1080i looks quite good - pausing the video in PMB or Vegas Pro 10e (or displayed direct to an HD big screen) looks pretty good, no painfully obvious artifacts, only slightly softer than the same scene shot with CX500.
HOWEVER, either 1080i or 1080p shot with the TX100 shows substantial blocky banding and other nastyness... Since the CMOS and general design of the two cameras is so similar, I was caught off guard by the differences, beginning to suspect that there is a diferent encoding chip in the two cameras.
I've still got more testing to do, but trying to figure out if there is some trick I missed for proper handling of 60p clips. I know I've seen samples shot with some of the new Sony P&S cams (TX100 included) that shoot progressive, and they looked great! Trying to figure out what it is I might be doing wrong, or did I just "overstress the encoder" with this particular shot?
FWIW, same scene shot with a CX500 (60i) showed a little bit of similar blocking/banding on a FEW pauses, where the TX100 was pretty much banding on every pause... the TX10 showed no banding/blocking?!
I was expecting a bit sharper and cleaner results, given 60 progressive frames, but the 60i looks almost as good if not better, so either the implementation still needs some work, or I'm missing something...
Any thoughts, suggestions, etc? Was really hoping to start to integrate 60P into the workflow, sticking my toe into the water as it were, now I'm not so sure...
Certainly more testing is in order, but want to get the image quality question sorted out. Wondered if anyone else had hit this snag...