or Connect
AVS › AVS Forum › Display Devices › Display Calibration › Lumagen Announces 9-Point Cube Gamut (729 Color Points) for the Radiance 20XX
New Posts  All Forums:Forum Nav:

Lumagen Announces 9-Point Cube Gamut (729 Color Points) for the Radiance 20XX - Page 3

post #61 of 136
Quote:
Originally Posted by Doug Blackburn View Post

So... Radiance 2041. CalMAN 5.2 current release version.

3D LUT Workflow selected

Connects to Radiance with no problem

But there's no setting I see anywhere that lets you tell CalMAN if it is an "old" Radiance that will only do 5x5x5 matrix or a "new" Radiance that will do 9x9x9... I did not actually try running a matrix cal yet, but want to do it. Will it automatically do 9x9x9 matrix for new Radiace processors? What if I just want a 5x5x5 matrix with a new Radiance (not 9x9x9) .

Am I missing something? I see a drop down window in CalMAN but there's nothing in that window...blank.

Have done 5x5x5 matrix with an XE 3D several times with no problem... I was expecting some kind of 5x5x5 / 9x9x9 selector somewhere... or perhaps a way of choosing Radiance 20XX series versus XE, XS, Mini but don't see either of those unless I'm missing them somewhere.

Doug, once the Radiance is connected, under "Display Control" you should see a dropdown "3D LUT Calibration Points". That's where you'll select 5 or 9 points. CalMAN doesn't yet do that automatically. Also, when you get to the "Calibrate 3D Cube LUT" screen and click the autocal button, you'll get the "AutoCal Setup" window, and this is where you do the final 9x9x9 point selection. Do read it before you click OK, because there are several options available, and 9x9x9 isn't the first one in the list.

Have fun!
post #62 of 136
Quote:
Originally Posted by Rolls-Royce View Post

IIRC, CalMAN does its connection to Radiance models at 9600 baud. Perhaps your adapter is not negotiating to that rate as it should. Try setting the port speed manually to 9600 baud in Device Manager > Ports before starting CalMAN. If that fails, try changing flow control to None, with data bits to 8, parity to None, and stop bits to 1. Even if they already are set that way, it's possible one of them is corrupted in the Registry. Won't cost anything to try!

Gawd, I remember having to do all this kind of stuff on the old RS-232 external modems. I'm so glad those days are over!tongue.gif

Thanks, I tried changing but nothing. I'll have to contact lumagen and spectral hopefully they can understand what happening. I've tried on 2 different laptops, same issues display not found or check connections. Though both are able to download the lumagen configuration. Go figure confused.gif
post #63 of 136
Thread Starter 
Quote:
Originally Posted by Franin View Post

Quote:
Originally Posted by Rolls-Royce View Post

IIRC, CalMAN does its connection to Radiance models at 9600 baud. Perhaps your adapter is not negotiating to that rate as it should. Try setting the port speed manually to 9600 baud in Device Manager > Ports before starting CalMAN. If that fails, try changing flow control to None, with data bits to 8, parity to None, and stop bits to 1. Even if they already are set that way, it's possible one of them is corrupted in the Registry. Won't cost anything to try!

Gawd, I remember having to do all this kind of stuff on the old RS-232 external modems. I'm so glad those days are over!tongue.gif

Thanks, I tried changing but nothing. I'll have to contact lumagen and spectral hopefully they can understand what happening. I've tried on 2 different laptops, same issues display not found or check connections. Though both are able to download the lumagen configuration. Go figure confused.gif

Post your question to Lumagen Forum, they have amazing after-sales support.
post #64 of 136
Quote:
Originally Posted by Franin View Post

Thanks, I tried changing but nothing. I'll have to contact lumagen and spectral hopefully they can understand what happening. I've tried on 2 different laptops, same issues display not found or check connections. Though both are able to download the lumagen configuration. Go figure confused.gif

I forgot to mention one more thing to try in Device Manager: Flow Control. Mine is currently set to Off, and I can access the Radiance from CalMAN or the Lumagen configuration app. It probably shouldn't make a difference, but stranger things have happened.
post #65 of 136
OK then, since I wasn't controlling a display, I didn't look at that drop-down! So I did miss something! Thx RR
post #66 of 136
Quote:
Originally Posted by Doug Blackburn View Post

OK then, since I wasn't controlling a display, I didn't look at that drop-down! So I did miss something! Thx RR

I missed it at first, too, Doug. The calibrations were going really fast, but post-calibration measurements were lacking compared to those from the previous beta. Then I discovered that the top item in that dropdown was actually a 5x5x5 cube, not the 9x9x9 I thought I was doing. Duh-oh!
post #67 of 136
Not to get off track, but somewhere along the line, I've managed to set something in a 2041 that causes it to return to the previously active input if you switch the 2041 to an input that has nothing connected to it or that has the source component turned off.

Is there a way to undo that and keep the 2041 on the unused/off input -- I don't want it to switch back to the cable box if I switch to something else on purpose and it doesn't happen to be plugged in or is turned off.
post #68 of 136
Quote:
Originally Posted by Doug Blackburn View Post

Not to get off track, but somewhere along the line, I've managed to set something in a 2041 that causes it to return to the previously active input if you switch the 2041 to an input that has nothing connected to it or that has the source component turned off.

Is there a way to undo that and keep the 2041 on the unused/off input -- I don't want it to switch back to the cable box if I switch to something else on purpose and it doesn't happen to be plugged in or is turned off.

imo its a bug in the 2041. My 2041 does the same thing plus if I say have CMS memory on CMS 2 it will drop back to CMS 0.

The only way around this issue that I have found is using memory's A.B,C,D for one preset only in each memory. .

I am now back to using the eecolor box for LS 17^3 LUT's, imo PQ is better than a 17^3 profile that is scaled back to a 9^3 LUT to be used in the 2041.

ss
post #69 of 136
ss....are you saying you prefer the radiance LUT over the eecolor 4913pt LUT? I find this interesting. Why?
post #70 of 136
Thread Starter 
Quote:
Originally Posted by 1forsnow View Post

ss....are you saying you prefer the radiance LUT over the eecolor 4913pt LUT? I find this interesting. Why?

SS is telling that he likes better the true 17-Point Cube Profiling loaded to his eecolor.
post #71 of 136
Quote:
Originally Posted by ConnecTEDDD View Post

SS is telling that he likes better the true 17-Point Cube Profiling loaded to his eecolor.

Exactly. smile.gif

ss
post #72 of 136
Quote:
Originally Posted by sillysally View Post

imo its a bug in the 2041. My 2041 does the same thing plus if I say have CMS memory on CMS 2 it will drop back to CMS 0.

The only way around this issue that I have found is using memory's A.B,C,D for one preset only in each memory. .

I am now back to using the eecolor box for LS 17^3 LUT's, imo PQ is better than a 17^3 profile that is scaled back to a 9^3 LUT to be used in the 2041.

ss

Have you reported this to Lumagen?
post #73 of 136
Quote:
Originally Posted by Gordon Fraser View Post

Have you reported this to Lumagen?

Yes I called them, but I think we had "failure to communicant".

ss
post #74 of 136
Quote:
Originally Posted by Doug Blackburn View Post

Not to get off track, but somewhere along the line, I've managed to set something in a 2041 that causes it to return to the previously active input if you switch the 2041 to an input that has nothing connected to it or that has the source component turned off.

Is there a way to undo that and keep the 2041 on the unused/off input -- I don't want it to switch back to the cable box if I switch to something else on purpose and it doesn't happen to be plugged in or is turned off.

MENU>OTHER>AUTOSELECT seems to allow the allocation of automatic input selections....you could look there
post #75 of 136
Thread Starter 
Quote:
Originally Posted by sillysally View Post

Quote:
Originally Posted by Gordon Fraser View Post

Have you reported this to Lumagen?

Yes I called them, but I think we had "failure to communicant".

ss

SS, In a few hours, it will be released a new firmware for 20xx, keep an eye open. wink.gif
post #76 of 136
Quote:
Originally Posted by Rolls-Royce View Post

I forgot to mention one more thing to try in Device Manager: Flow Control. Mine is currently set to Off, and I can access the Radiance from CalMAN or the Lumagen configuration app. It probably shouldn't make a difference, but stranger things have happened.

Thanks for your help Rolls-Royce, I ended up finding what the issue was, which is when controlling your Lumagen 2041 via remote like I do ( still using pronto tsu 9800) you need to turn off delimeters in the lumagen rs232 setup so it's able to communicate with the Calman.
post #77 of 136
Quote:
Originally Posted by ConnecTEDDD View Post

SS, In a few hours, it will be released a new firmware for 20xx, keep an eye open. wink.gif

Thanks for the heads up.

btw, looking forward to receiving your new Calibration disc. Kudos to you.

ss
post #78 of 136
Quote:
Originally Posted by Franin View Post

Thanks for your help Rolls-Royce, I ended up finding what the issue was, which is when controlling your Lumagen 2041 via remote like I do ( still using pronto tsu 9800) you need to turn off delimeters in the lumagen rs232 setup so it's able to communicate with the Calman.

You're very welcome. Glad you got it sorted out!
post #79 of 136
Thread Starter 
Lumagen Radiance XE/XE+/XE3D/XE/XE+/XE3D/Mini-3D/XD/XD3D + Radiance 20XX Series (2021, 2022, 2041, 2042) New 102913 Firmware Update

Release Notes

Added 2 APL patterns to the Gray Window pattern group.

Added a custom window size and a custom window size + APL pattern to the User Color window pattern group.

The 2 new patterns added to the User group use the RGB level that are settable in the first 3 patterns.

The custom sizing allows setting the window size in .1% steps.

The custom size + APL pattern allows setting both the window size and an APL.

As you vary the size of the window the background level is adjusted to give the desired APL.

If it can't meet the requested APL, a greater-than or less-than sign is displayed next to APL to indicate this (.ie setting RGB=240,240,240, the custom size to 90.0% and the APL to 30% would give the greater-than sign next to APL).

Added rs232 access to the new patterns.

The rs232 format for the new User size pattern is "ZY7TsSSSRRRGGGBBB" with SSS being 3 digits (000-999) for 0-99.9% area of screen.

The rs232 format for the user defined size + APL pattern is "ZY7TsSSSAAARRRGGGBBB" with AAA being 3 digits to be set to 000-100 for 0-100% APL.

Download Link
post #80 of 136
Thank you
post #81 of 136
Quote:
Originally Posted by sotti View Post

Our handling of larger LUTs, is all new as of the build we put up on friday. It's a substantial difference and should be evaluated with a fresh eye.

So you are saying I should look at it only with my new cataract eye and not with both eyes? Gotcha. Thanks for the help.
post #82 of 136
Thread Starter 
Lumagen.jpg

LightSpace Development Team is working to add the new Production 102913 firmware features to their software.

Here is a build preview with Lumagen custom window pattern size selector, that i'm currently using.
Edited by ConnecTEDDD - 11/6/13 at 5:18am
post #83 of 136
Quote:
Originally Posted by ConnecTEDDD View Post

Lumagen.png

LightSpace Development Team is working to add the new Production 102913 firmware features to their software.

Here is a build preview with Lumagen custom window pattern size selector, that i'm currently using.

Ted, prince of the calibration disc.smile.gif

You got to hand it to the LightSpace team. I posted on LS forum yesterday about adding window sizing for the Lumagen, and today I see Steve sent me a beta to test. cool.gif



My new toy showed up today, so I first want to run a full 17^3 profile using the non beta firmware to check it out.

ss
post #84 of 136
Thread Starter 
The LightSpace's Build that will be ready tonight will include the Lumagen 'Fixed APL' option wink.gif
post #85 of 136
Thread Starter 


Ok, I have just installed the new LightSpace Build which features Lumagen Custom Sized Window Patterns with Custom APL Percentance. wink.gif

If anyone is interesting for this build test drive, I can send the download link with a PM. I have the approval of Light Illusion on this. wink.gif
Edited by ConnecTEDDD - 11/6/13 at 11:47am
post #86 of 136
Just ran a quick profile using the above Beta, also went back into the upload window change the size and APL to 0.

All worked very well, I am running a full 17^3 profile right now using a 5.5% window and no ALP.

Steve and Team, looks like you have a winner with this Beta.
What great customer support, I posted on LightSpace forum two days ago if they would incorporate this new feature in there software for the new Lumagen window sizing. Two days later not only does it seem to work well but you also added the APL.%

Thanks,
Team LightSpace.

ss

Update, all went as it should when I ran a 17^3 Profile. smile.gif
Edited by sillysally - 11/6/13 at 11:28pm
post #87 of 136
I have a Lumagen 2042 and I'm having a problem with YCbCr422 output from the Lumagen when a 3x17 from LightSpace is uploaded to the current CMS (set for 3x9). Everything looks great when the Lumagen output is set to RGB or YCbCr444. Also with Oppo set to RGB or YCbCr. But when I set the Radiance 2042 output to YCbCr422 the low grayscale goes to pot - but only on the CMS that has a 3x9 uploaded to it. Another memory with its CMS set to 3X9 but loaded with its default settings looks fine. I've tried the 10/29 and the 10/1 Radiance firmwares and the problem is the same. Anybody see this problem? I don't know whether it's a Lumagen or LS problem, or maybe cockpit error on my part. By the way, I'm observing this problem using Ted's CMS disk as well as the AVS disk - both show the problem. Help?
Edited by Citation4444 - 11/7/13 at 6:05am
post #88 of 136
I can't directly answer the question, but I can say this is not a LightSpace problem.

There must be something happening within the Lumagen, but I really do not know what.

Have you tried asking the same question on the Lumagen forums?

Steve
post #89 of 136
Quote:
Originally Posted by Light Illusion View Post

I can't directly answer the question, but I can say this is not a LightSpace problem.

There must be something happening within the Lumagen, but I really do not know what.

Have you tried asking the same question on the Lumagen forums?

Steve
Yes, but no answer yet as it's early in Oregon. smile.gif
post #90 of 136
Quote:
Originally Posted by Citation4444 View Post

Yes, but no answer yet as it's early in Oregon. smile.gif

fwiw, I have a 2041 and use 4:2:2. I din't see what you are describing using a 17^3 profile. I would ask if maybe you did a video scale (only use for eecolor box) in LS edit, then transferred the file to your 2042.
But it seems that if RGB and 4:4:4 are fine I don't think that is the problem.

I ended up using my eecolor box for a 17^3 LUT. I thought the 9^3 was good, but the 17^3 LUT is better.

ss

Correction, it should read edit not tools.
Edited by sillysally - 11/7/13 at 9:07pm
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Display Calibration
AVS › AVS Forum › Display Devices › Display Calibration › Lumagen Announces 9-Point Cube Gamut (729 Color Points) for the Radiance 20XX