or Connect
AVS › AVS Forum › Video Components › Video Processors › Official RadianceXD support thread
New Posts  All Forums:Forum Nav:

Official RadianceXD support thread - Page 29

post #841 of 1347
Quote:
Originally Posted by amt View Post

It's been a long time since I have done a color gamut calibration, but if memory serves, in order to fix a low luminance problem, one has to lower the luminance of the white-point. This way all of the colors in comparison have more luminance (and in this case yellow might have just enough).

amt has answered your question....change the luminance of white IN THE CMS not in the gamma adjustment points.
post #842 of 1347
^^^
Will try that. Thanks.
post #843 of 1347
So just to confirm there is no passthrough mode on this?

Only game mode?
post #844 of 1347
Quote:
Originally Posted by NxNW View Post

Anyone have any ideas for my auto input issue?

When a device turns off, I want the Radiance to switch to the input of a device that has been on the whole time.

Is this not possible?

I am a big believer in leaving useful information behind for those who may stumble across my posts (say, via search engine) in the future, so, even though no one in this thread had an answer, future visitors deserve to know there may be a fix for this issue according to the last four posts at http://www.convergent-av.co.uk/forum...2c315ac46cd7b9

I won't be able to test this, but at least there's hope for others.
post #845 of 1347
Quote:
Originally Posted by Murilo View Post

So just to confirm there is no passthrough mode on this?

Only game mode?

Anyone? No pass through mode?
post #846 of 1347
Quote:
Originally Posted by Murilo View Post

Anyone? No pass through mode?

There is no absolute complete physical pass through mode......

the game mode by-passes the gennum/sigma de-interlacing and image enhancement chip. That leaves the signal to go through lumagens proprietry processes. If incoming signal and outgoing resolutions are the same then you can also turn off scaling part of that circuit. The delay in game mode is very short....i can't imagine that it wont be fast enough for any gamers...at least I cannot recall ever seeing anyone complaining it wasn't fast enough here or on other forums.
post #847 of 1347
Quote:


Originally Posted by NxNW
Anyone have any ideas for my auto input issue?

When a device turns off, I want the Radiance to switch to the input of a device that has been on the whole time.

Is this not possible?

There was a bug fixed for an auto input select problem in 122211 firmware and you're on older firmware than this, so update to the latest. It should work, I just tried it here. If not then email support@lumagen and send us your config file.
post #848 of 1347
Quote:
Originally Posted by Gordon Fraser View Post

There is no absolute complete physical pass through mode......

the game mode by-passes the gennum/sigma de-interlacing and image enhancement chip. That leaves the signal to go through lumagens proprietry processes. If incoming signal and outgoing resolutions are the same then you can also turn off scaling part of that circuit. The delay in game mode is very short....i can't imagine that it wont be fast enough for any gamers...at least I cannot recall ever seeing anyone complaining it wasn't fast enough here or on other forums.

More so for my pc using a mouse through it i want no delay.

Likely I might just go the route of a mini and use a seperate hdmi switch and run my pc through that. Its to bad you cant just turn processing off, even my denon vp which is sparse on features has that.
post #849 of 1347
Quote:
Originally Posted by patrick harkin View Post

There was a bug fixed for an auto input select problem in 122211 firmware and you're on older firmware than this, so update to the latest. It should work, I just tried it here. If not then email support@lumagen and send us your config file.

Thank you very much for responding!

As I hinted previously, I won't be able to test the results of any new firmware versions any time soon - I currently don't have any PC based computers available to me.

Anyways, thank you again. I'll report back if I'm able to accomplish the update at some point in the future.
post #850 of 1347
I'm confused about how to add a 2nd output to the Radiance.
So far, I have Out1 going to my projector and Out2 going back to the AVR for audio. I want to add a 2nd display (TV). Can it be done without an hdmi extender?
post #851 of 1347
Quote:
Originally Posted by mouradb View Post

I'm confused about how to add a 2nd output to the Radiance.
So far, I have Out1 going to my projector and Out2 going back to the AVR for audio. I want to add a 2nd display (TV). Can it be done without an hdmi extender?

Suggestion: Route your video sources to the receiver first for audio and HDMI switching, then connect the receiver to the Radiance. That frees up both outputs on the Radiance, one for each of your displays.
post #852 of 1347
That's what I have for most my sources except that I run out of HDMI inputs on the AVR and ended up needing 2 on the Radiance.
post #853 of 1347
The Atlona AT-HD-V12 (Amazon.com has it - I just ordered one for the same purpose)
takes in 2 HDMI and outputs 1 HDMI. I don't do 3D so its HDMI 1.3 is good enough for me. There are some cheaper ones like this at www.monoprice.com, too.
post #854 of 1347
Thanks Steve. I ended up cherry picking my components to make them all connected to the AVR.
I found out too that I can connect all the inputs to the Radiance and then from the Radiance run Out1 with Audio+Video to the AVR and connect the 1st display to the AVR, and run Out2 with Audio only to the 2nd display. Only issue with this setup is that I don't get the AVR OSD on the 2nd display. On the other hand, the advantage is that I get more flexibility in the settings : I would have 32 memories (using 8 inputs with 4 memories each) while when connected to the AVR, I have only 4.
post #855 of 1347
Can anybody shed some light on how to use the Radiance with a 2.35 screen and no anamorphic lenses) ? Tried to follow-up on previous threads (here and on the Lumagen forum) but all reference the older menus in Radiance that don't make sense anymore.

I'm assuming that it is better to implement the shifting between 2.35 & 16:9 material thru the Radiance to save on wearing the JVC's lenses.
post #856 of 1347
Quote:
Originally Posted by mouradb View Post

Can anybody shed some light on how to use the Radiance with a 2.35 screen and no anamorphic lenses) ? Tried to follow-up on previous threads (here and on the Lumagen forum) but all reference the older menus in Radiance that don't make sense anymore.

I'm assuming that it is better to implement the shifting between 2.35 & 16:9 material thru the Radiance to save on wearing the JVC's lenses.

Randy commented on the mini forum that they will have a better way to do this in the next FW and will have a tech tip to document how to do 2.35 zoom on a 2.35 screen, and top-mask displaying 2.35 image with 16:9 screen.
post #857 of 1347
Saw that. Very good news and perfect timing.
The constant support from Lumagen is incredible and proves to me over and over again that I made the right choice.
Thanks.
post #858 of 1347
Quote:
Originally Posted by mouradb View Post

Thanks Steve. I ended up cherry picking my components to make them all connected to the AVR.
I found out too that I can connect all the inputs to the Radiance and then from the Radiance run Out1 with Audio+Video to the AVR and connect the 1st display to the AVR, and run Out2 with Audio only to the 2nd display. Only issue with this setup is that I don't get the AVR OSD on the 2nd display. On the other hand, the advantage is that I get more flexibility in the settings : I would have 32 memories (using 8 inputs with 4 memories each) while when connected to the AVR, I have only 4.

If you use only an AVR/Switch output to drive a Radiance you can use our "virtual Input" feature to have more available memories. For example on teh Mini there are six "virtual" inputs. You can setup all to use physical input 1. This gives you 24 memories for sources from the AVR.
post #859 of 1347
Before throwing in the towel...

Radiance XE-3D running firmware from July 2011... I can't update the firmware any more. The update exe fails to communicate with the Radiance so the update never starts.

Bought a second USB-to-serial adapter just to be sure that wasn't the problem and have the same issue with the new one (different brand with the highly compatible chip-set in it, can't recall the brand off the top of my head). That July update and many earlier updates worked fine with the same computer and same serial cable. Tried the extra steps recommended in the update instructions to see if that would force an update with no help.

Also tried disconnecting from power for 15 minutes a couple of times just to see if that sort of "hard" reboot would resolve the issue -- no help.

Anything else I should try before giving up? Luckily the only problem I'm having is occasional long sync times for audio (video goes into Radiance, one output of Radiance goes to surround processor, other output goes to projector). Switching inputs or turning Radiance off/on usually gets the audio back much more quickly than waiting for it (if you wait long enough, it always comes back, but sometimes the waits are over 5 minutes unless I force a re-handshake by switching inputs or off/on).
post #860 of 1347
^^^
I had problem updating when my COM port was a high number. Following Randy's advice (Lumagen), I changed to #2 and it worked perfectly since. What COM port are you using?
post #861 of 1347
Production 011612 FW Updates:

XD/XD3D
XE/XE+/XE3D
XS/XS+/XS3D


Production 011612
Modified the newly added Lbox Crop command from previous release such that the setting is common to all input resolutions for a given input & memory.
The command was also renamed to LBox Zoom and you can now easily set it for all inputs/memories within the command.
Fix for PC input level setting causing video to flash off/on.
Improvements to switching input resolutions on a source.
Bugfix for issue with video judder under certain conditions.
Some improvements to Pip functionality.
post #862 of 1347
Quote:
Originally Posted by mouradb View Post

^^^
I had problem updating when my COM port was a high number. Following Randy's advice (Lumagen), I changed to #2 and it worked perfectly since. What COM port are you using?

The first USB-serial adapter would consistently install itself as Com7 or Com12 and it worked fine for 2 years of updating. The new USB-serial adapter installs itself as Com3 with no change in ability to communicate with the Radiance.
post #863 of 1347
Quote:
Originally Posted by Doug Blackburn View Post

Before throwing in the towel...
Anything else I should try before giving up?

Have you tried changing your null cable? I had a similar problem as you describe and thought I had tried everything. I changed the null modem cable and everything worked again, even though I had been using the prior cable for many, many Radiance updates. I threw the old cable away; must have worn out the connection somewhere. Worth a try if you haven't tried it. Also, have you physically inspected the pins on the Radiance's RS232 connector? With so much use, it could be that a pin has been pushed in so that it no longer makes contact.
post #864 of 1347
I did try 3 different serial cables with the first usb-serial adapter that had been working fine for 2 years, but I didn't try the other 2 serial cables with the newer USB-serial adapter. I should probably do that. I don't connect and disconnect the serial cable very often... maybe 1 or 2 times in 2 years. I leave the cable connected all the time and just connect and disconnect the USB-serial adapter to the laptop when I need to do an update.
post #865 of 1347
Production 011812 FW Updates:

XD/XD3D
XE/XE+/XE3D
XS/XS+/XS3D


Production 011812
Some minor fixups and improvements to input EDID functions.
Now allowed to set up different video EDID on input memories to aid with some multimedia PC issues.
This enables the user to change memories on the Radiance in order to direct the PC to change video modes.
Added "menu 7" shortcut for quicker access to Quick Keys menu.
Other minor menu fixups and clarifications.
post #866 of 1347
Quote:
Originally Posted by fight4yu View Post

Randy commented on the mini forum that they will have a better way to do this in the next FW and will have a tech tip to document how to do 2.35 zoom on a 2.35 screen, and top-mask displaying 2.35 image with 16:9 screen.

Any tech tips available?
I use zoom on the 2.35 screen, and then vertical shift to get the 2.35 image on the 2.35 screen. By pressing 2.35 AR button, this is done easily.
My problem is with 16:9 image. I need this to "zoom in" so I can have black bars and keep the aspect ratio. However, there is no zoom option in the same aspect ratio menu. The zoom is part of the STYLE and that means I need to use a memory slot. Can this be done by not using memory slot?
post #867 of 1347
Sincerely I don't see clearly the differences between them.

Taking into account that I'm watching mostly PAL DVDs (576i) and BD what would be the preferred setup for both choices?

I do currently have the default values for both.

Perhaps someone could explain it in a a precise way?

Forgot to mention that my video device (front projector) doesn't support 1080p24 but support 1080p48 flawlessly.
post #868 of 1347
Quote:
Originally Posted by WildBoar View Post

Sincerely I don't see clearly the differences between them.

Taking into account that I'm watching mostly PAL DVDs (576i) and BD what would be the preferred setup for both choices?

I do currently have the default values for both.

Perhaps someone could explain it in a a precise way?

Forgot to mention that my video device (front projector) doesn't support 1080p24 but support 1080p48 flawlessly.

Genlock is usefull with 1080i60 film or 1080p24 input when radiance outputs 1080p24 or p48 or p72 output.

Rate match works only with 1080p23.976 or 1080p24.00 input. When it is set at ON then Radiance does automatically the following:

if 1080p23.976 input then it outputs 1080p23.976 (or 1080p47.952 or 1080p71.928)
if 1080p24.000 input then it outputs 1080p24.000 (or 1080p48.000 or 1080p72.000)

Hope that helps.
post #869 of 1347
Since we're on the topic of genlock, I want to talk about how to get the best performance when attempting to convert 480i DVD content to 1080p24 output.

If I'm understanding correctly, genlock is not configurable in this scenario - it is forced "on".

I am now (finally!) running the latest firmware, but I'm still not really satisfied with the performance of the "frame rate conversion" feature.

I set my DVD player to output 480i over HDMI.

I then set my Radiance to out put 1080p24 to my 24p-capable display.

For 99% of program material this works great.

But in scenes where there is only a small amount of movement within the frame (especially if it is a dark scene with low APL) , the cadence detection algorithm fails and the motion becomes very choppy. Occasionally the condition persists and the movie will continue to play in something resembling 12 or 15 fps even after the scene changes to one where movement is easier to detect.

This has occurred with many different titles.

It never used to occur with my old VP (I don't want to be "that guy" who talks about other brands, but since someone will probably ask, it was a DVDO product).

Am I missing some other way of setting up the Radiance to improve the performance of this feature?
post #870 of 1347
Set the Radiance deinterlacing to film mode. Press "Input, Video Setup, [resolution], Control, Deinterlace, Mode, Film, Ok". Make sure that you "Save" the new setting.

By default the video enhancement settings are all set to zero. If you use the enhancement settings, especially if you have higher numbers in these settings, it could have some impact on film deinterlacing in dark scenes.

Randy Freeman
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Video Processors
AVS › AVS Forum › Video Components › Video Processors › Official RadianceXD support thread