I have a question regarding the 1080p24hz setting in playing mkv files be it 720 or 1080p. The problem is there's judder everytime i set the wdtv to the said resolution when playing mkv files. Is this a software problem? I thought the judder had something to do with my lcd before which was a bravia 32s400, but it still happens with the pv8 i have right now. Ok naman na pag 720p60hz or 1080p60hz ang setting, the judder only becomes apparent with the 1080p24hz. Help guys. Thanks.
This is a known WD issue that should get a fix in future firmware updates. Medyo mahirap ang explanation nito, but I'll try to make it as clear as possible.
The problem is caused by 2 things:
1. The difference between 24p (or 24fps or 24 frames per second) and 23.976p; and
2. Amateur encoders.
The frequency of 24p (24 progressive frames per second) is often confused with 23.976p because usually, the latter is also referred to as "24p" for convenience.
In reality, film has a frame rate of true 24p, not 23.976. For NTSC compatibility, film's 24p is usually converted to 23.976p for video. That's because 23.976 will give 24 a common denominator of 100.1% with NTSC's 29.97 frames from 30 frames.
If NTSC's 29.97 fps is 30 fps divided by 1.001, then celluloid's 24 fps divided by the same denominator of 1.001 will give us 23.976 fps, for better NTSC compatibility.
http://en.wikipedia.org/wiki/24p#23.976pThose amateur encoders should encode at 24p, not 23.976p, to avoid problems with some media players and HTPCs.
The WD can handle a 24p source, but it will have stutter problems with a 23.976p source. Here's the description on the unofficial WD Bug List:
In "1080p 24Hz" display resolution mode, 23.976 fps video files (e.g. .M2TS) suffer a short stuttering/juddering in an exactly 40-seconds cycle. This juddering usually occurs, if the device outputs fixed 24.000 fps whereas it should output 23.976 fps.
In "1080p 24Hz" display resolution mode, 23.976 fps video files in .MKV containers stutter extremely hard every ~25 seconds for about 10 seconds. Remuxing to the .M2TS container temporary solves the issue, but the 40-seconds-cycle juddering is still present then. (Please take a look at the other bug report where the 40-seconds-cycle juddering is described in detail) http://www.avsforum.com/avs-vb/showthread.php?t=1100499