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

Official RadianceXD support thread - Page 8

post #211 of 1246
9/25/09 at 12:06pm
I have never checked out the "Lumagen Support Forum" (from Lumagen not AVS) until today.

I thought this Lumagen FW priority list might be of interest to people here...
Link

Updated priority of all remaining Radiance planned features (9/22/09):
Grayscale/Gamma (12-point, 21 point parametric)
PiP (additional features)
PoP
Scale 240p as progressive input
Lower latency game mode (Approx 4 mS if genlock on)
Near zero latency pass-through mode (i.e. no scaling).
Ability to configure output as digital pass-through (video only, audio only, both)
Input sub-memory format select (resolution, rate, and interlace)
Programmable audio delay



(Unrelated) questions:
What is PoP and PrePish?

Thanks

Mike
Reply
Reply

Gear mentioned in this thread:

post #212 of 1246
9/25/09 at 7:16pm
Quote:
Originally Posted by Mike_WI View Post

My Oppo BDP83 and XE work ok with Source Direct.
Let us know what you find out. Sorry I can't be more helpful. Mike

Played around with this a lot, got customary excellent support from Lumagen, and have solved the problem. Issue was not getting source direct from the Oppo, rather getting 1080p24 output from the XE. Apparently I had set the input level to 'pc' a long time ago, and even though it worked with earlier versions of the firmware, something in my setup was getting mucked up. Went into service mode, switched the input level to 'video', tweaked the black/white levels and the problem is gone. No idea why, but no matter ....
Reply
Reply
post #213 of 1246
9/26/09 at 11:20am
@Mike_WI

PoP is picture outside picture (i.e. Two inputs displayed next to each other)
PReP is DVDO/Anchor Bay's "Progressive Re-Processing" functionality which takes a progressive input, obtains the original interlaced fields from it, and re-deinterlaces those fields.
Reply
Reply
post #214 of 1246
9/26/09 at 11:57am
Quote:
Originally Posted by VirusKiller View Post

@Mike_WI

PoP is picture outside picture (i.e. Two inputs displayed next to each other)
PReP is DVDO/Anchor Bay's "Progressive Re-Processing" functionality which takes a progressive input, obtains the original interlaced fields from it, and re-deinterlaces those fields.

VirusKiller -

Thanks alot.
With PoP, would you be able to see -- for instance -- two HDTV signals next to each other if you have one cable box.
I assume you will be able to do it with two boxes.

Thanks again.

Mike
Reply
Reply
post #215 of 1246
9/27/09 at 12:17am
You need two sources...
Reply
Reply
post #216 of 1246
10/3/09 at 9:00am
Thread Starter 
Looks like I missed the latest update, I'm guessing it's been up for a few days. First post is updated as well.

XD direct download
XE direct download

Just bug fixes this time around:
Quote:


Turning on/off PiP no longer results in momentary onscreen noise. Bugfix for occasional horizontal line of noise with combing when the "film only" mode is used with 480i in and the output mode is 60 Hz. Bugfix for pressing the wrong key in one menu command which would corrupt an entry in the CMS gamut. Bugfix for going from 11 point to 12 or 21 point grayscale for an issue that occurs if the original points are only 0.5 IRE apart. Bugfix for restoring an ISF configuration that was saved more than a few months ago.
Reply
Reply
post #217 of 1246
10/6/09 at 3:20pm
XD - Production 092209 FW
XE - Production 092209 FW


Production 092209- Some bugfixes for new 12/21 point grayscale/gamma calibration commands. The biggest issue was a bug in the copying of the calibrated data between output configs which could cause either overflow on bright scenes and/or inability to go back and edit the grayscale for an output config that had been copied from another. So if you did an output copy command with revisions 091409 or 092109 you should recopy the output configs (.ie if you had copied config0 CMS data to all other output configs then do that again after loading this update). Also a couple of other small bugfixes unrelated to CMS.
Reply
Reply
post #218 of 1246
10/8/09 at 12:42am
Production 100109- Adds a new command to tweak deinterlacing quality with an "Inter-Frame motion detection" setting. This command can be found under the menu at Input:Video Setup:RES:Controleint:IFMD. The range is 0-15, 0 should minimize combing while 15 maximizes detail according to the chip specification. The default value is 6. Adds the ability to set HDMI input type. This option is found in the menu under Input:HDMI Setup:Type. This was always "Auto" but can now be set manually to RGB, YCbCr422, YCbCr444 as some DVI outputs use these other formats but can't communicate which format they're putting out like an HDMI device can. Default for audio mute was changed to "Long" but this only comes into play if you load factory default values.

XD - Production 100109
XE - Production 100109
XS - Production 100109

I've asked Pat for clarification on the IFMD de-interlacing parameter.
Reply
Reply
post #219 of 1246
10/29/09 at 11:10am
I narrowly missed a Dave G. sighting in Madison last week...

funlvr1965 (Wayne) told me that there is a Radiance setting for making the black sidebars even "blacker".
In a quick perusal of the manual yesterday I didn't see any obvious setting changes.
So, is there?

Roles for this - 4:3 movie such as Snow White BR.

Thanks for any ideas...

Mike
Reply
Reply
post #220 of 1246
10/29/09 at 11:48am
Thread Starter 
I think the setting you're referring to is just the sidebar color for 4:3 material. It's grey by default in the XD, you can just make it darker or even black if you want. I don't remember the path for it. It's probably a setting that you'd find in the output configurations though, since it's display specific, but I'm not sure. I'll try to find it tonight and post here.

Or try the manual (again)
Reply
Reply
post #221 of 1246
10/29/09 at 11:56am
Quote:
Originally Posted by Dave G View Post

I think the setting you're referring to is just the sidebar color for 4:3 material. It's grey by default in the XD, you can just make it darker or even black if you want. I don't remember the path for it. It's probably a setting that you'd find in the output configurations though, since it's display specific, but I'm not sure. I'll try to find it tonight and post here.

Or try the manual (again)

Thanks.

Mike
Reply
Reply
post #222 of 1246
10/29/09 at 4:49pm
from pg 20 of current manual:

Quote:


Graybar Intensity
NOTE:
Consult a home theater specialist for assistance setting the graybar intensity.

Some degree of burn-in will occur on any susceptible display, but this command can help minimize it by allowing the intensity of the graybars to be adjusted.

The command format is:
MENU => Output => Configs => [Config] => Other => Graybar => (Sides, Top/bottom)
Reply
Reply
post #223 of 1246
10/30/09 at 8:58am
I assume "burn-in" is for:
- plasmas
- non-black sidebars

Or am I missing something?

Thanks.

Mike
Reply
Reply
post #224 of 1246
10/30/09 at 9:05am
I just read a news in official lumagen forum which shocked me
I read that lumagen radiance (xd,xe,xs) has this problem:
Combing appear with 50H interlaced signal.
I'm quite confused because pal 50Hz interlaced signal is the standard for many european countries....
is it true?
If it is true a solution suggested is to send progressive signal to radiance but using this method means not to use one of the most important and famous lumagen property: de-interlacing.....
Could you explain me better?
Reply
Reply
post #225 of 1246
10/30/09 at 9:08am
Quote:
Originally Posted by spinmar View Post

I just read a news in official lumagen forum which shocked me
I read that lumagen radiance (xd,xe,xs) has this problem:
Combing appear with 50H interlaced signal.
I'm quite confused because pal 50Hz interlaced signal is the standard for many european countries....
is it true?
If it is true a solution suggested is to send progressive signal to radiance but using this method means not to use one of the most important and famous lumagen property: de-interlacing.....
Could you explain me better?

I read that also, and I found it strange. I have no noticeable combing, and I'm in PAL land.
Reply
Reply
post #226 of 1246
10/30/09 at 9:17am
Quote:
Originally Posted by movie_fan View Post

I read that also, and I found it strange. I have no noticeable combing, and I'm in PAL land.

Any official news from lumagen?
Reply
Reply
post #227 of 1246
10/30/09 at 9:42am
With one of the updates this summer Lumagen introduced a fixed 2:2 deinterlacing mode. It's running on the FPGA instead as on the Gennum chip, so you loose a few of the Gennum's postprocessing features (NR?), but it should fix the combing problems. This said, the Gennum processor never had the choice of deinterlacing modi DVDO's FPGA processing offered.
Reply
Reply
post #228 of 1246
10/30/09 at 10:42am
All de-interlacing solutions, that are trying to work out if it's a progressive capture or interlaced, will get it wrong at times. The forced 2:2 mode is to help with problem film sourced material, not video.

There are a lot of Radiance owners in 50hz zones. if this was actually a major issue it'd be all over the newsgroups. In actual fact its not an issue at all, imho. I had another guy contact me about the same stuff before he bought his Radiance. He had a demo of one against his own very, very respected hi-end scaler from another manufacturer (that costs more than a Radiance...) and he was surprised to find that he much preferred the XD! (he now owns one!)

One of the beauties of the Radiance range is the ability to have multiple memories. You can have the same settings for everything except de-interlacing mode...then you can choose memA or memB dependant on what content you are watching
Reply
Reply
post #229 of 1246
10/30/09 at 10:55am
Quote:


if this was actually a major issue it'd be all over the newsgroups.

It has actually come up quite a few times, over here and on the german boards I know as well. I mean we're not talking major screw-ups all the time, but when you move from a 50pro to a Radiance you just miss the mass of deinterlacing options like forced film & video modes.

Quote:


The forced 2:2 mode is to help with problem film sourced material, not video.

Makes me wonder if Lumagen could add a forced Video option as well
Reply
Reply
post #230 of 1246
10/30/09 at 11:33am
Quote:
Originally Posted by Mike_WI View Post

I assume "burn-in" is for:
- plasmas
- non-black sidebars

Or am I missing something?

Thanks.

Mike

plasmas, crt, LCD's can suffer from ghosting which is not technically burn-in. i think DLP is the only technology that is completely immune from these types of effects.
Reply
Reply
post #231 of 1246
10/31/09 at 3:44am
Quote:
Originally Posted by drewski11 View Post

plasmas, crt, LCD's can suffer from ghosting which is not technically burn-in. i think DLP is the only technology that is completely immune from these types of effects.

Right.
But making the sidebars "black" (vs. grey) shouldn't result in burn in, or should it?

Thanks

Mike
Reply
Reply
post #232 of 1246
10/31/09 at 11:25pm
Quote:
Originally Posted by Mike_WI View Post

But making the sidebars "black" (vs. grey) shouldn't result in burn in, or should it?

Not persistent burn-in, per se. It's more that the black bars don't get "run in" to the same degree as the rest of the screen, which can be a problem for a new screen. The last thing you want are bars visible in 16:9 material because the widescreen bits of the display haven't been used as much as the 4:3 bits.
Reply
Reply
post #233 of 1246
11/1/09 at 3:01am
Quote:
Originally Posted by VirusKiller View Post

Not persistent burn-in, per se. It's more that the black bars don't get "run in" to the same degree as the rest of the screen, which can be a problem for a new screen. The last thing you want are bars visible in 16:9 material because the widescreen bits of the display haven't been used as much as the 4:3 bits.

Thanks.
So, basically an "inverted" burn in showing the black standing out from the rest.
If I do it, it would likely be okay for the few 4:3 AR 2 hr movies I use, correct?

Mike

MENU => Output => Configs => [Config] => Other => Graybar => (Sides, Top/bottom)
Reply
Reply
post #234 of 1246
11/1/09 at 4:17am
If the screen isn't brand new, then watching the occasional 4:3 movie shouldn't cause any problems. I used "medium" gray side-bars on my new plasma for the first 200 hours or so. Then I set them back to black.
Reply
Reply
post #235 of 1246
11/1/09 at 4:53am
Quote:
Originally Posted by VirusKiller View Post

If the screen isn't brand new, then watching the occasional 4:3 movie shouldn't cause any problems. I used "medium" gray side-bars on my new plasma for the first 200 hours or so. Then I set them back to black.

I think this is more important for plasmas (I have a JVC RS20 projector), but points well taken.
Thanks.

Mike
Reply
Reply
post #236 of 1246
11/1/09 at 10:16am
Agreed. I didn't worry about this with my HD1 (RS1).
Reply
Reply
post #237 of 1246
11/3/09 at 4:42pm
Thread Starter 
New firmware is up. Direct download links:

XD firmware (102509)
XE firmware (102509)

Quote:


Production 102509

* Added PiP for analog inputs with the limitation that if the main window is an analog source then the PiP can either be the same analog source or an HDMI source. If the main window is an HDMI source then the PiP can be any source.
* Added a new "Memory Usage" option in the menu under Other:Memory Usage. Previously when you select a memory (A-D) you are using it across all inputs, .ie if you're on input 1A, change to input 2 and press 'MemB' and change to input 1, you'll be using 1B. We've called this the 'common' memory usage mode since the memory in use is common across all inputs. Now you can set the memory usage to be per-input, so if you're on input 1A and change to input 2 then press 'MemB' and change back to input 1, you'll go back to 1A---it remembers the memory you're on for each input. Either mode can be used and it depends on what you use the memories for as to which you might prefer. For example, if you're using memA for settings adjusted to daytime ambient settings and memB for nighttime then you'll probably want to stick with the default 'common' mode.
* Added aspect and memory control for the PiP window. Now pressing the aspect or memA-D buttons after PiP select or mode have been pressed sets the aspect or memory for the PiP window--note that if you're not using the new per-input memory usage setting then changing the PiP memory also changes the main windows memory. Auto-aspect also works for the PiP now. Note that for the PiP window the 'Letterbox' aspect, which is defined to be an aspect greater than 4:3 within a 4:3 aspect, is just treated as 4:3 (so you'll see bars on top and bottom) and similarly the '2.35' aspect, which is defined to be 2.35 inside a 16:9 aspect, is just treated as 16:9 (so again top/bottom bars are visible).
* Added a label to the PiP window that displays it's input name for a few seconds when the PiP is accessed with PiP remote buttons like PiP select, mode, etc..
* Added a power on input selection option to the menu under Other:OnOff Setup:Input Select. With this you can control which input the unit powers up on after either power is removed or after standby.
* Added a small reminder in the menu when settings have been changed to help remember if you should 'Save' before powering down.
* Several bugfixes and some minor additional menu enhancements.
Reply
Reply
post #238 of 1246
11/5/09 at 12:10pm
Anyone upload the new FW yet?
Any bugs/issues?

Mike
Reply
Reply
post #239 of 1246
11/5/09 at 5:37pm
Uploaded firmware last night everything seem's fine. Checked out new functions all seem to work and make sense. Keep up the good work Jim.
Reply
Reply
post #240 of 1246
11/9/09 at 2:19pm
Question: Can the Radiance products accept 480p/24 over HDMI? (assuming there was a device that could send that)
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Video Processors

Gear mentioned in this thread:

AVS › AVS Forum › Video Components › Video Processors › Official RadianceXD support thread