Devices > Video Cards, Monitors, Televisions, and Projectors

Bump - Support Request: Playback engine command 28038 cleanup / enhancements

<< < (2/3) > >>

tij:
I am not expert on this at all ... but does not MadVR support this automatically by detecting blackbars (and removing them) ... I vaguely recall seeing this on one of the forums (from what i remember the setting for this was all over the place in MadVR)

EDIT: found that forum ... http://forum.doom9.org/showthread.php?t=173286

Movieman:
Yes it will, but it does so with a delay.  It also doesn't handle situations like a 1.66:1 blu ray that it actually an open matte presentation of a film that was projected theatrically at 1.85:1.

Just for reference, JRiver is the only player I have used with this issue.

Other players (Zoom Player, MPC-BE, MPC-HC, and VLC) all allow zoom presets to be defined with 2 decimal place accuracy.

Hendrik:
We can't really change how these values work since anyone that uses them might otherwise suddenly have their values broken.

They are not meant to match the percentages shown in the UI, since the percentages depend on the video resolution and the window size or screen resolution. These values do not. This is the internal representation of the zoom value as we would also save it into the [Playback Info] field when changed manually - with the same precision, too. This is basically a two digit decimal value multiplied by 100 (so it has two digit decimal precision).

This internal representation may not be very intuitive, but you can change the zoom with the +/- keys during playback, stop playback, and read it out of the [Playback Info] field.

The 1% steps with the keys are definitely bigger then 1 pixel movements, so achieving a pixel accurate zoom at any arbitrary value is not quite the goal for any of these.

Movieman:
Here's what I see

First of all the I/O zoom steps are perfectly acceptable in terms of accuracy. So that piece of the puzzle is working fine.

However:

101% zoom  = 2.99
102% zoom  = 2.98
103% zoom  = 2.98
104% zoom  = 2.97
105% zoom  = 2.96

So, I still maintain the presets do not offer the same granularity as provided by the zoom in and out (I/O) keys as shown by both 102% and 103% zoom being represented by the 2.98 value.

Methinks that a gremlin exists somewhere in there relating to the precision of a variable.

Movieman:

--- Quote ---101% zoom  = 2.99
102% zoom  = 2.98
103% zoom  = 2.98
104% zoom  = 2.97
105% zoom  = 2.96
--- End quote ---

So lets take this one more step:
I play a video and set the the zoom to 103% using the I key.  The resulting value saved in the Playback Info field is 2.98.

Then a week later I play the same video, and the playback engine reads the 2.98 from the playback field.

Now how will it know how to translate the 2.98 to a 103% zoom when that same 2.98 also applies to a 102% zoom?  I suspect it won't and the resulting playback will be at an incorrect 102% zoom. 

This is exactly the same behavior that occurs when setting the 28038 parameter with a hot key.

This is clearly a bug in JRiver, although it is not actually with the 28038 parameter code, and it does need to be addressed.

Thanks again.

Navigation

[0] Message Index

[#] Next page

[*] Previous page