Originally Posted by ADU
Perhaps I should have mentioned these adjustments earlier when you were having some of your Brightness dilemmas. But I figured you were probably already aware of this, and wanting to find a way to get Brightness in the SM to work with the existing slider configs in the User Menu.
1st off, please stay with me here until the next section and attached screenshot ....
No, there was no need for you to mention those, but thanks. I'm afraid you are still misunderstanding the issue I had with getting the "picture" slider centered, instead of using it at "24" which worked just perfectly, all I was trying to do was to get the picture slider to read "31"(32 ticks) and achieve the same results as was the case with "24"(25 ticks). I didn't have any problem "issues" whatsoever with brightness, or "contrast" or balancing those(or the "sharpness slider either for that matter) among inputs/etc, just wanted to center the Picture slider at "31".
I perhaps used the wrong terminology --- In those posts I was talking about "brightness" as it relates to "white balance" and "contrast", NOT brightness as it refers to the "brightness" slider, or "black levels", the latter I took care of long ago with 2170P-3 UBOF and 2170P-1 SBRT.
It's all water under the bridge, now though, as I've already explained I was able to figure it out using a lower value for 2170P4 SPIO (and, long ago I had already used 2170P-4/SPIC to balance contrast among inputs, although I touched those up a bit anyway when I was working on this). Sorry, I probably did not do a good job explaining that, but I can't think of a better way to say it than I already have(along the lines of what Ken said, sometimes it is awfully difficult for me to talk about these issues and know that my comments are "understandable" by others), and I'm afraid going into that again and repeating it again won't be useful.
Originally Posted by ADU
Interesting.Actually that sounds pretty much the same as on the XBR800. On the XBR800, 2170P-4/UPIC through UTMP configure the default positions of the sliders and temp settings for each picture mode in the User Menu. For slider controls, the numbers correspond to ticks, with 0 representing the first tick, and 31 representing 32 ticks. If, for example, you wanted the Brightness slider to default to say 27 ticks instead of the usual 32 in Pro mode, you could change that by making UBRT=26. Same for Sharpness, Contrast, etc.
So why use this approach to reconfigure Sharpness? Well, because the 2170P-3/SHOF sharpness offset is already at it's lowest setting for the DVI signal/input I'm using on my XBR800, and Sharpness is still not "optimal" w/o further reducing the slider in the User menu.
Interesting. I don't think it's quite working the same, at least with "mode memory" turned on on 34XBR960 in as "useful" a manner.
Fom what I recall from checking this, On KD34XBR960, QM UPIC~UTMP do nothing to actually "configure" the sliders(update: except to allow you to hit "reset" button to return to a certian set of default values as Ken mentions below/End update) , other than if you use the little "dots" shown in the slider menu as a reference to return the values for the sliders back to factory defaults for any given pic mode, or if you change the values for UPIC~UTMP, your "new" values would correspond to new posistions for these "little dots", which otherwise mark the factory defaults for the sliders for the different pic modes.
They only SHOW you [update again : or let you use the reset button to return to a certian set of "defaults" - either the factory, or values you've set up ; end update], in the "video" user menu what those factory defaults were, with little "dots". They don't effect what happens to the picture, you do that by changing the slider yourself, which you can do on KD34XBR960 in a Input specific manner(in other words you can use different slider values for different inputs(or pic modes for that matter with "mode memory/On) by turning "mode memory" on in user menu, or you can use the same slider "settings" for all inputs by turning "mode memory" to : off.
Again, as noted in my reply to Ken farther below - sorry ADU for my "misunderstanding" of what you were talking about on this -- Entirely my fault, but, rather than editing them except for these updates as noted, I think I'll go ahead and leave my comments as they were in this post, if nothing other than a demonstration of how easy it can be to "misread", or "misinterpet" things - again, in this case, entirely MY fault.
Because of the availability "mode memory: On" function and different slider settings(or other input/scan rate/etc. offset controls available in SM - such as "UBOF") for all the different sources I use, I've never really thought of a reason to make use of the reset button, or to define a certian set of "defaults" with QM UPIC~UTMP settings for the User mode "sliders" ... Although, thinking about it more, it could perhaps be useful for me in order to more quickly "switch" to a "default" set of slider settings when "checking" things, or, perhaps to set the sliders quickly back to my "normal" mid range settings after adjusting to preference to compensate for "differences in programming material."
Perhaps a picture is worth 1,000 words. So, attached is screenshot "sliderdots.jpg"(pardon the quality of the shot and the reflection from a lamp in the room) -- I've adjusted the sliders(this is NOT what I use them at, LOL) so you can see all the "little white dots" which UPIC~UTMP correspond to for "factory Mode" for each slider. For instance -- UBRT for this Pic mode = 32, and that's right where the little white dot is for the "brightness" slider that shows the "brightness" slider factory default for this pic mode. The "brightness" slider would JUST "cover up" the little white dot if I had the slider set at "31" as I normally do. If I change QM/UBRT to "45" for this pic mode, the little white dot will move up to correspond with the "44" value for the slider itself, but, it doesn't effect the actual value of the slider itself in any way shape or form -- nothing else will change except the posistion of that little white dot. Perhaps it may behave differently however if I wasn't using "mode memory" set to "on" - I didn't try that.