View Full Version : Lumagen HDP ... component inputs green or purple ... help!


Michael TLV
12-28-06, 12:08 PM
Greetings

I hope someone here might be able to assist me in trouble shooting this issue. The Visionhdp processor was working fine a week ago ... but then the component video inputs turned purple on 1080i signals from my dish receiver.

Signals from other sources like the HD add on and LG DVD players display as green. All cable connections have been double checked and triple checked and more to make sure no wires are crossed.

The DVI inputs on the unit continue to work fine ... although changing to things like 422 or 444 can simulate the same discoloration effect.

I have cycled the component signals through the S ... H ... RGBS ... RGBHV ... to no avail. Also looked at the user manual for the section on signal type ... M019xx ...

Hope someone can steer me in the right direction to get this fixed.

Regards

dsinger
12-28-06, 01:24 PM
Email support at Lumagen. Their customer service is excellent.

oferlaor
12-31-06, 04:53 AM
sounds like you might have switched color domains from component to RGB...

Are you sure you didn't touch the STB? try connecting it directly to a screen.

Check that the HDP itself (using test patterns) that it is set to RGB output.

Michael TLV
12-31-06, 08:53 PM
Greetings

The unit is outputting dvi

DVI inputs and S-vid and composite work fine ... the component video ones are messed up. Green on input 3 and purple on input 4.

Switching to SD to HD to RGBS to RGB HV etc does nothing to make the color go away.

anything fed component into the lumagen gets the purple treatment ...dvd player ... ps2 ... satellite ...

The test patterns output just fine while on these purple signals. They look normal ...

Still waiting on support ... but it is the holidays so will give them lots of slack.

Thanks

Regards

Barry928
01-01-07, 09:31 AM
I remember this problem from the early days of Lumagen. You need to input a 100 ire WINDOW test pattern from DVE, then key in MENU>0>9>2>6>OK. This calibrates and saves the component input. The instructions say to use input 3.

Michael TLV
01-01-07, 01:18 PM
greetings

Thanks Barry, will give that a try later on today ... (200 miles later)

Regards

Michael TLV
01-01-07, 08:21 PM
Greetings

Barry, ... :( no joy here. It slightly reduced the intensity of the green on input 3 ... but nothing else. No impact on the purple over on input 4 ...

Strange that it ID's both component inputs as RGB signals now ... eventhough the signals are component from the DVD player ...

RGB Y ... Component N ...

Worth a try ... now awaiting a reply from the Lumagen support people.


Thanks

Regards

Barry928
01-01-07, 08:32 PM
Darn, I realy thought that was it. Have you tried going back to factory defaults and/or reloading the software?

Gordon Fraser
01-02-07, 04:26 AM
The 0926 trick is just to calibrate the a to d section of inputs 3 and 4. Generally it never ever needs done. The vast change in colour that Michael sees would more likely be failed hardware. Never seen that happen without some external intervention though. Very strange but I think it's not going to be a firmware fix....

Gordon

jkscherk
01-02-07, 09:17 AM
Wait for the Lumagen guys to get back to you....they're very responsive and helpful. Based on some similar experience I've had, Gordon may be right. Could be the analog input board has gone bad. Please let us know what you find.

oferlaor
01-03-07, 03:43 AM
Back up your settings and try a full factory default.

toadyyy
01-03-07, 09:31 AM
I'd try factory default and cross my fingers. But sounds exactly like someones plugged/unplugged some live cables from either the Lumagen or the source. I know from sore experience connecting a live source to a HDP will give this issue, and will need a complete board replacement to fix.

However it doesn't seem clear about the YUV/RGB thing. The Lumagen never reports back to you what it's getting, you just tell it it's getting HDYPbPr (and make sure the source is also outputting this). It is a manual setting not an automatic thing or a reporting thing so there's a long shot this might help?