Originally Posted by giomania
Thanks for the info, Larry. I don't think I am explaining my issue correctly, so let me try again:
Here is the background on the issue I am having:
Last week, I installed firmware 2.5 on my XA2 using a burned ISO disc. Both steps of the update process were performed, and I initiated the player after the update. I have a Lumagen Vision Pro HDP video processor, and a JVC HD2K projector; both devices are DVI.
I could not see BTB before or after firmware 2.5 with the XA2 picture controls at their default settings. When I adjust the XA2 brightness control, then I can see BTB, but I decided not to muck around with the XA2 picture control settings.
Instead, I just calibrated using the Lumagen controls with the two other bars in the PLUGE pattern. I was adjusting the brightness and contrast settings on the Lumagen only, as my projector has no such controls.
Now, the problem is: After updating the XA2 to firmware 2.5, I can no longer calibrate that way, as I can barely see any of the bars on the PLUGE pattern! When I adjust the controls in the Lumagen, there is very little perceptible change in the picture levels when viewing the PLUGE pattern. Believe me, I'm not going crazy.
Note, that I when I first noticed this issue, I had made no changes to my settings except for updating the XA2 to firmware 2.5 and initializing the player. Further, I was not using the picture controls in the XA2 prior to the update, so they were at the default settings both before and after updating the firmware. Based on these facts, I am convinced the cause of this issue was the 2.5 firmware update.
Now, I can fix this issue by adjusting the picture controls in the XA2, but I would rather not. The question remains, what did Toshiba change in firmware 2.5 that so adversely effected my setup?
The things I tried to rectify this issue, with no difference: I tried both RGB settings on the XA2. I tried switching the DVI Level settings on the Lumagen from PC to Video. The only thing that made the Lumagen controls work properly (giving me some range of control back) was when I adjust the XA2's brightness control up from "0", so I have a suspicion that lowered brightness is the culprit.
Since I did not have this problem before firmware 2.5 and I made no changes to my setup parameters before I noticed the issue, the logical conclusion is that the firmware update is the cause of my issue. Am I crazy?
I just want to get to the bottom of this issue, so if anyone has any suggestions of things to try, I'm all ears.
Unless I can find another explanation, the culprit is the XA2.