peterhuh
26th February 2008, 20:49
Hi!
I'm trying to squeeze four eps of my local TV drama onto 1 DVD. This comes to an average bitrate of about 3000 kbps. When viewing the disc with my CRT TV, i notice a slight but irritating problem.
In a scene, areas with fast motion, like people waving their hands around while talking, the motion stays fluid. Just like what 50i suppose to look.
But within the same scene, areas with slow motions, like the cheeks on people faces when they are sitting, the motion seems to judder a little. Very much like what i get when i deinterlace my source to 25p prior to encoding.
This is a little irritating because the areas that judder and those that don't, appear within the very same scene. You know, when you are comparing pictures side-by-side, the difference is very noticeable.
Ok, here are the details:-
video = MPEG2Source("VTS_01_1.d2v").AssumeTFF()
audio = WAVSource("VTS_01_1 T01 2_0ch 384Kbps 48KHz.wav")
AudioDub(video,audio)
Trim(1469,21718)+Trim(26749,42687)+Trim(47438,59512)+Trim(64636,73534)+Trim(78165,90898)
FFT3DGPU(interlaced=true)
Encoder: HCgui 0.22
Avg Bitrate: 3000
Profile: Best
DC Prec: 9
GOP: 15
Interlacing: TFF
Matrix: MPEG
To determine if the problem really lies with HCEnc, I have done four different encodes with the same .avs source. All 2-pass.
-HCEnc @ 9000 kbps
-HCEnc @ 3000 kbps
-CCE @ 3000 kbps
-TMPGEnc @ 3000 kbps
HCEnc @ 9000 kbps - no judder at all
HCEnc @ 3000 kbps - judder, but only in areas with slight motion.
CCE @ 3000 kbps - no judder, but shows more MPEG artifacts like ringing...
TMPGEnc @ 3000 kbps - judder, and shows ringing as well.
Sorry, i'm unable to provide an absolute index of "judder-ness". I don't think PSNR or SSIM will show. Neither can i upload pictures showing the problem, because the problem lies with its motion. I can probably upload a short mpeg clip onto some filesharing website if there is a need to. But you will need to watch them on a CRT TV because, i have difficulty identifying the problem on my computer's monitor.
My best guess is that HCEnc codes two fields with only one motion vector in areas with little motion. I might be wrong.
Thanks for reading. ^^
I'm trying to squeeze four eps of my local TV drama onto 1 DVD. This comes to an average bitrate of about 3000 kbps. When viewing the disc with my CRT TV, i notice a slight but irritating problem.
In a scene, areas with fast motion, like people waving their hands around while talking, the motion stays fluid. Just like what 50i suppose to look.
But within the same scene, areas with slow motions, like the cheeks on people faces when they are sitting, the motion seems to judder a little. Very much like what i get when i deinterlace my source to 25p prior to encoding.
This is a little irritating because the areas that judder and those that don't, appear within the very same scene. You know, when you are comparing pictures side-by-side, the difference is very noticeable.
Ok, here are the details:-
video = MPEG2Source("VTS_01_1.d2v").AssumeTFF()
audio = WAVSource("VTS_01_1 T01 2_0ch 384Kbps 48KHz.wav")
AudioDub(video,audio)
Trim(1469,21718)+Trim(26749,42687)+Trim(47438,59512)+Trim(64636,73534)+Trim(78165,90898)
FFT3DGPU(interlaced=true)
Encoder: HCgui 0.22
Avg Bitrate: 3000
Profile: Best
DC Prec: 9
GOP: 15
Interlacing: TFF
Matrix: MPEG
To determine if the problem really lies with HCEnc, I have done four different encodes with the same .avs source. All 2-pass.
-HCEnc @ 9000 kbps
-HCEnc @ 3000 kbps
-CCE @ 3000 kbps
-TMPGEnc @ 3000 kbps
HCEnc @ 9000 kbps - no judder at all
HCEnc @ 3000 kbps - judder, but only in areas with slight motion.
CCE @ 3000 kbps - no judder, but shows more MPEG artifacts like ringing...
TMPGEnc @ 3000 kbps - judder, and shows ringing as well.
Sorry, i'm unable to provide an absolute index of "judder-ness". I don't think PSNR or SSIM will show. Neither can i upload pictures showing the problem, because the problem lies with its motion. I can probably upload a short mpeg clip onto some filesharing website if there is a need to. But you will need to watch them on a CRT TV because, i have difficulty identifying the problem on my computer's monitor.
My best guess is that HCEnc codes two fields with only one motion vector in areas with little motion. I might be wrong.
Thanks for reading. ^^