|
|
Post by jaredjaric on Oct 1, 2017 12:23:07 GMT -5
HI Guys , hope someone here can put their valuable input to my problem. Seeking HUlio  After changing to a Lumagen Radiance xe, i have been having scan fail issues. The red led lights up on both the smps board and the H deflection board. Have swapped out both the smps and H boards from a working cinemax with the same setup. This other set up uses the newer radiance 2020 processor, without any issues. Both systems has the HDCP stripper from viewhd. I found out that having an oppo player straight to the cinemax it does not go to scan fail. Meaning the PJ is perfect without the Lumagen xe. with this other PJ, the Lumagen seems to demand more h frequency lines . By the way i am also both using moome's latest barco 1.4 hdmi card. I also found out that decreasing raster width ,(P700 trimpot on the smps) solves the issue.I am now able to enjoy the Lumagen Xe and oppo combinaton for now. But am hating the fact that the screen size or the width is much smaller than before. and am also worried about having raster burns due to the smaller image. Basically this is just a temporary treatment on some hidden issues with in the PJ. am thinking of swapping the controller board from a 909. I think the cinemax controller board software has some bandwidth restrictions versus the 909s. |
|
|
|
Post by stridsvognen on Oct 1, 2017 14:00:05 GMT -5
Did you test that your radiance output the same as you input on a different display.?
Be aware of the power supply to the lumagen might be bad if its a few years old, i have one here that works when connected to the tv, but not with the Marquee/ moome, and if you have HDCP issues you should be able to display the info screen and testpatterns from the radiance, just make sure your not feeding it HDCP protected content while you try that.
The old XE should not need a HDCP stripper, so try remove that one as well
And if you did not do it already its always a good idea to factory reset the radiance.
|
|
|
|
Post by Casethecorvetteman on Oct 1, 2017 16:43:35 GMT -5
Have you tried clearing the memories from the Cine 9?
The limit of the Cine 9 software is far higher than you will need, i have run mine at 2560x1600 60Hz without at issue, so its not a software issue in the projector, unless something is corrupt.
You should be able to run at full width, if you go into the diagnostics section in the menus, see if there was a coincidence error, if so, clear out all memories and do another setup for your source.
I have had mine do strange things when there was two sources that the machine could not pick between, and it gave coincidence error. I had to delete all the memory blocks to fix it.
|
|
|
|
Post by hulio on Oct 1, 2017 17:05:08 GMT -5
Bandwidth wise, both BR909 and Cine 9 (CineMax) are identical (180 MHz).
The software limitations found on Cine 9 (CineMax) are on the maximum horizontal and vertical scan frequencies. 132KHz horizontal (against 180KHz on BR909) and 210Hz vertical (against 240Hz on BR909). That was necessary to be able to make the fans run at lower speed.
You can swap the controller, but I doubt it will behave differently. The trouble-free use of Oppo as a source, proofs that. I think is a timing issue from your Radiance scaler. As I don't have any personal experience with Radiance scalers, i can't comment too much but what Kurt is saying makes sense.
|
|
|
|
Post by hulio on Oct 1, 2017 17:25:36 GMT -5
Ha, didn't noticed that Case replied before me. His advice makes sense too 😀, previously made memory-blocks should always be deleted. Else, the new block will be "guessed" by the interpolation algorithm.
Forgot to mention with regards to P700 on the SMPS. Don't be blinded by the 69V adjustment procedure. Nowadays, we are watching HD (and higher). The way a lot of folks do is this: put your horizontal width at 95 with the remote and tweak the P700 pot till your screen is properly filled, at the highest resolution you will watch your movies. That simple.
|
|
|
|
Post by Casethecorvetteman on Oct 1, 2017 20:13:17 GMT -5
Yes it will be interesting to see if any stored faults show "COINCIDENCE ON", as this is what id guess to be the likely issue at this point. Ive seen it shut down HV on my Cine 9 before, and it was all easily fixed by deleting the one memory block that caused it.
If you need to do a full set up, you should delete all the memory blocks anyway. There is no point starting from a previous setup that does not fit anything. Best way forward is to set all to mid point, then set the first block perfectly, then base everything else after that.
The fact it goes away when you adjust a pot doesnt mean a lot to me, because by adjusting that, you throw the entire setup out the window.
If i were to adjust that, id be setting the source to standard 720p timings and then filling the screen on 90-95 width, this way all sources should fill the screen easily enough.
|
|
|
|
Post by jaredjaric on Oct 1, 2017 21:48:45 GMT -5
Did you test that your radiance output the same as you input on a different display.? Be aware of the power supply to the lumagen might be bad if its a few years old, i have one here that works when connected to the tv, but not with the Marquee/ moome, and if you have HDCP issues you should be able to display the info screen and testpatterns from the radiance, just make sure your not feeding it HDCP protected content while you try that. The old XE should not need a HDCP stripper, so try remove that one as well And if you did not do it already its always a good idea to factory reset the radiance. Yes, sounds good.i will try doing the factory reset. Many thanks for the input. Cheers  |
|
|
|
Post by jaredjaric on Oct 1, 2017 21:52:33 GMT -5
Yes it will be interesting to see if any stored faults show "COINCIDENCE ON", as this is what id guess to be the likely issue at this point. Ive seen it shut down HV on my Cine 9 before, and it was all easily fixed by deleting the one memory block that caused it. If you need to do a full set up, you should delete all the memory blocks anyway. There is no point starting from a previous setup that does not fit anything. Best way forward is to set all to mid point, then set the first block perfectly, then base everything else after that. The fact it goes away when you adjust a pot doesnt mean a lot to me, because by adjusting that, you throw the entire setup out the window. If i were to adjust that, id be setting the source to standard 720p timings and then filling the screen on 90-95 width, this way all sources should fill the screen easily enough. Million Thanks for this Case. Cheers, |
|
|
|
Post by jaredjaric on Oct 1, 2017 21:56:43 GMT -5
Ha, didn't noticed that Case replied before me. His advice makes sense too 😀, previously made memory-blocks should always be deleted. Else, the new block will be "guessed" by the interpolation algorithm. Forgot to mention with regards to P700 on the SMPS. Don't be blinded by the 69V adjustment procedure. Nowadays, we are watching HD (and higher). The way a lot of folks is this: put your horizontal width at 95 with the remote and tweak the P700 pot till your screen is properly filled, at the highest resolution you will watch your movies. That simple. Thanks again,Hulio. I was too focused on the p700 adjustments. This makes a lot of sense, i will try to readjust the amplitude. Cheers, |
|
|
|
Post by jaredjaric on Oct 2, 2017 0:10:39 GMT -5
Ok, factory reset of lumagen worked. It is outputting 720p now on both inputs. I also did Hulio's advice of turning up the width to 95 and reducing the p700 to fit the screen.
Now , i have to readjust the lumagen to output 1080p 60, On the first HDMi input , no scan fail.
Then, (on the Lumagen )after trying to have other inputs copy input 1's adjustments, Barco goes into scan fail.
It seems that switching between different inputs and resolutions on the Lumagen causes the barco to go to scan fail.
BUt, I had experienced that earlier with this PJ also, when switching between input 3(moome card) at 1080p and input 5 at 720p.The pj unit goes into scan fail also.
I can not seem to isolate the problem here.
|
|
|
|
Post by Casethecorvetteman on Oct 2, 2017 0:31:14 GMT -5
Did you delete all memory blocks?
|
|
|
|
Post by stridsvognen on Oct 3, 2017 8:49:38 GMT -5
after the factory reset remember to save it before you turn the unit off again, then try set the lumagen to output 1080P 60hz at all your different input resolutions, it might send out 1080P 24hz as defoult when feeding it 1080P 24hz.
you need to set the output pr input resolution.
|
|
|
|
Post by Casethecorvetteman on Oct 3, 2017 9:13:26 GMT -5
Also ditch the 720p res for now, that was the one the caused my issue, and i cant recall why.
|
|
|
|
Post by jaredjaric on Oct 3, 2017 10:33:09 GMT -5
Also ditch the 720p res for now, that was the one the caused my issue, and i cant recall why. Yes( avoid 720), it seems i read somewhere in the past that you had an almost similar issue with scan fail . I am not near this pj now,but will be going back at it tomorrow. i will take all your advises and also not use Lumagen's second hdmi out( feeding audio receiver). The hdcp stripper has a seperate audio out anyways. Thanks for this , Case |
|
|
|
Post by jaredjaric on Oct 3, 2017 10:36:06 GMT -5
after the factory reset remember to save it before you turn the unit off again, then try set the lumagen to output 1080P 60hz at all your different input resolutions, it might send out 1080P 24hz as defoult when feeding it 1080P 24hz. you need to set the output pr input resolution. I will try to check if it went back to its previous setting, i am going to tweak the pj again tomorrow. Million thanks for this |
|
