Reply to thread

Message

I haven't much use for this feature myself. Probably why it takes forever.

I did just think about how this could look in the XML file.

ex.

<entry name="refreshrate01_ext">C:\\Program Files\\displaychanger\\dc.exe -refreshrate=60 -apply -quiet</entry>
<entry name="refreshrate01_name">NTSC</entry>
<entry name="ntsc_fps">29.97;30</entry>
<entry name="ntsc_hz">60</entry>

<entry name="refreshrate02_ext">C:\\Program Files\\displaychanger\\dc.exe -refreshrate=24 -apply -quiet</entry>
<entry name="refreshrate02_name">CINEMA@24</entry>
<entry name="cinema@24_fps">24</entry>
<entry name="cinema@24_hz">24</entry>

<entry name="refreshrate03_ext">C:\\Program Files\\displaychanger\\dc.exe -refreshrate=23.976 -apply -quiet</entry>
<entry name="refreshrate03_name">CINEMA@23.976</entry>
<entry name="cinema@23.976_fps">23.976</entry>
<entry name="cinema@23.976_hz">23.976</entry>

the XML keys will be named : refreshrate01_ext etc.
so there can be an almost infinite nr. of refreshrate settings.
each refreshrateXY section has a corresponding _name, _fps and _hz section mapped to it.
The name defined in "refreshrate01_name" will be used in the notification dialogue (if enabled) as well as the name for the mappings to the "ntsc_fps" and "ntsc_hz" keys.
So this name is user definable.
Mp config will handle the reading and writing to the XML of course.

In my example we have the NTSC configuration. It will map any material with a FPS of either 29.97 or 30 to a RR of 60hz.

The Cinema section is now divided into a 24 and a 23.976 section.

If there are not any improvements to this way of configure it, then I'll go ahead and code it.

I'll provide a path at some stage I think.

/gibman

<blockquote data-quote="gibman" data-source="post: 412404" data-attributes="member: 25430">I haven't much use for this feature myself. Probably why it takes forever.I did just think about how this could look in the XML file.ex.&lt;entry name=&quot;refreshrate01_ext&quot;&gt;C:\\Program Files\\displaychanger\\dc.exe -refreshrate=60 -apply -quiet&lt;/entry&gt;&lt;entry name=&quot;refreshrate01_name&quot;&gt;NTSC&lt;/entry&gt;&lt;entry name=&quot;ntsc_fps&quot;&gt;29.97;30&lt;/entry&gt;&lt;entry name=&quot;ntsc_hz&quot;&gt;60&lt;/entry&gt;&lt;entry name=&quot;refreshrate02_ext&quot;&gt;C:\\Program Files\\displaychanger\\dc.exe -refreshrate=24 -apply -quiet&lt;/entry&gt;&lt;entry name=&quot;refreshrate02_name&quot;&gt;CINEMA@24&lt;/entry&gt;&lt;entry name=&quot;cinema@24_fps&quot;&gt;24&lt;/entry&gt;&lt;entry name=&quot;cinema@24_hz&quot;&gt;24&lt;/entry&gt;&lt;entry name=&quot;refreshrate03_ext&quot;&gt;C:\\Program Files\\displaychanger\\dc.exe -refreshrate=23.976 -apply -quiet&lt;/entry&gt;&lt;entry name=&quot;refreshrate03_name&quot;&gt;CINEMA@23.976&lt;/entry&gt;&lt;entry name=&quot;cinema@23.976_fps&quot;&gt;23.976&lt;/entry&gt;&lt;entry name=&quot;cinema@23.976_hz&quot;&gt;23.976&lt;/entry&gt;the XML keys will be named : refreshrate01_ext etc.so there can be an almost infinite nr. of refreshrate settings.each refreshrateXY section has a corresponding _name, _fps and _hz section mapped to it.The name defined in &quot;refreshrate01_name&quot; will be used in the notification dialogue (if enabled) as well as the name for the mappings to the &quot;ntsc_fps&quot; and &quot;ntsc_hz&quot; keys.So this name is user definable.Mp config will handle the reading and writing to the XML of course.In my example we have the NTSC configuration. It will map any material with a FPS of either 29.97 or 30 to a RR of 60hz.The Cinema section is now divided into a 24 and a 23.976 section.If there are not any improvements to this way of configure it, then I'll go ahead and code it.I'll provide a path at some stage I think./gibman</blockquote>

[QUOTE="gibman, post: 412404, member: 25430"] I haven't much use for this feature myself. Probably why it takes forever. I did just think about how this could look in the XML file. ex. <entry name="refreshrate01_ext">C:\\Program Files\\displaychanger\\dc.exe -refreshrate=60 -apply -quiet</entry> <entry name="refreshrate01_name">NTSC</entry> <entry name="ntsc_fps">29.97;30</entry> <entry name="ntsc_hz">60</entry> <entry name="refreshrate02_ext">C:\\Program Files\\displaychanger\\dc.exe -refreshrate=24 -apply -quiet</entry> <entry name="refreshrate02_name">CINEMA@24</entry> <entry name="cinema@24_fps">24</entry> <entry name="cinema@24_hz">24</entry> <entry name="refreshrate03_ext">C:\\Program Files\\displaychanger\\dc.exe -refreshrate=23.976 -apply -quiet</entry> <entry name="refreshrate03_name">CINEMA@23.976</entry> <entry name="cinema@23.976_fps">23.976</entry> <entry name="cinema@23.976_hz">23.976</entry> the XML keys will be named : refreshrate01_ext etc. so there can be an almost infinite nr. of refreshrate settings. each refreshrateXY section has a corresponding _name, _fps and _hz section mapped to it. The name defined in "refreshrate01_name" will be used in the notification dialogue (if enabled) as well as the name for the mappings to the "ntsc_fps" and "ntsc_hz" keys. So this name is user definable. Mp config will handle the reading and writing to the XML of course. In my example we have the NTSC configuration. It will map any material with a FPS of either 29.97 or 30 to a RR of 60hz. The Cinema section is now divided into a 24 and a 23.976 section. If there are not any improvements to this way of configure it, then I'll go ahead and code it. I'll provide a path at some stage I think. /gibman [/QUOTE]