Yes, with this SVN build please use the actual refresh rate and not the label used in the display properties. MP communicates directly with the driver under Win7 by using the interface MS supplied. Exact rate should work for now. Anyway this has been fixed and 23 should work again in future builds.Scythe42: The 23.976Hz refresh rate is named "23" in CCC, that's why I use that value. Are you saying that I should put 23.976 in the box instead? If so I will try it tomorrow, writing this from bed
Unfortunately this is how DS graph building in MP works. MP is not using exact match what user has configured in config, but instead relies on the directshows connection behavior. If there are two codecs in the graph (different codec for MPEG2 and H-264 configured and both are able to decode the specific video type) directshow will connect the source filter and video decoder based on the filter merits.When choosing different codecs for MPEG2 and H.264 in "TV Codec" section a different from the selected codec may be used if one of the selected codecs support MPEG2 and H.264.
1.) Select "MPC" for MPEG2 and "Cyberlink Video Devoder (PDVD9)" for H.264.
2.) Select a SD channel on TV an you'll see that the Cyberlink codec is used instead of "MPC".
1.) Select "MPC" for MPEG2 and "ffdshow" for H.264.
2.) Select a SD channel on TV an you'll see that "MPC" is used which is correct.
Please post other logs as well, it could be some 3rd party plugin that causes the stuttering / dropped frames (InfoService is one good canditate, at least it caused huge amount of dropped frames in gemx' testing).A lot of dropped frames and sync glitches
That is queried from Windows itself, not much we can do if it reports wrong refresh rate. I assume you are using 60Hz, where as Windows reports 59.xxx. This could be as well a bug in display drivers if you use DVI/HDMI connection (refresh rate should be exact 60Hz at that case) and if you are using analog connection (s-video, vga) display adapter doesn't usually match the exact requested refresh rate (which is already one source for juddering and dropped frames in worst case).display frequencies are not correct.
|Thread starter||Similar threads||Forum||Replies||Date|
|MediaPortal SVN-Snapshot:-02-06-2010 13-59h - Revision:24975.rar||[untested] MediaPortal 1.1.0 BETA svn-builds||249|
|MediaPortal SVN-Snapshot:-01-08-2010 02-15h - Revision:24669.rar||[untested] MediaPortal 1.1.0 BETA svn-builds||391|
|MediaPortal SVN-Snapshot:-12-24-2009 16-14h - Revision:24553.rar||[untested] MediaPortal 1.1.0 BETA svn-builds||273|
|MediaPortal SVN-Snapshot:-11-30-2009 21-44h - Revision:24281.rar||[untested] MediaPortal 1.1.0 BETA svn-builds||225|
|MediaPortal SVN-Snapshot:-11-14-2009 14-48h - Revision:24102.rar||[untested] MediaPortal 1.1.0 BETA svn-builds||157|
|MediaPortal SVN-Snapshot:-02-06-2010 13-59h - Revision:24975.rar|
|MediaPortal SVN-Snapshot:-01-08-2010 02-15h - Revision:24669.rar|
|MediaPortal SVN-Snapshot:-12-24-2009 16-14h - Revision:24553.rar|
|MediaPortal SVN-Snapshot:-11-30-2009 21-44h - Revision:24281.rar|
|MediaPortal SVN-Snapshot:-11-14-2009 14-48h - Revision:24102.rar|