The Official Pioneer 9G North American KRP-500M / KRP-600M Owner's Discussion Pt. II - Page 151

Wow, they do native PAL without conversion to 60hz? I had no idea that any US sets offered that.

Pioneer kept PAL under hush but I always knew lol

The Kuros are reasonably international and accept six variations on NTSC, PAL and SECAM. It was probably more about manufacturing simplification than having catholic tastes.

Thank you! The RGB bug is quite a major annoyance for me.

I have two conflicting sources coming through an AVR: HTPC and a BD player. The BD player color space cannot be configured, it is always RGB limited. You would think there would be some way to set the color space in the HTPC, but I haven't found any. I have an ATI video card and it seems that over the years on rare occasion there is a feature in the Catalyst software that lets you set the color space (they call it pixel format), but that setting hasn't been available in newer drivers for quite some time now.

So right now I either put up with incorrect color space or manually change it. I could probably buy a universal remote with macro capability, but I don't think there are discreet codes for the color space, so I'm not sure that would work out.

I just got my pioneer and i made evangelo2 dvd and will be using d-nice
break in settings. i will be using my ps3, what video output settings should
i use on the ps3? thank you

I believe I read in the Master thread that output resolution does not matter, as long as the screen is completely filled.

Welcome to AVS and congratulations on your new Kuro.

As long as the screen is filled the settings are not that critical. Going forward you can probably use the suggested settings in the PS3 FAQ.

Thanks everyone

I haven't found discrete codes for colorspace although I haven't really started looking yet. If they exist then they're nearly a secret. A reasonably simple solution is to get an HDMI splitting device and send the output to port 5 and port 6, configure the ports for the appropriate colorspace and then use input select to change colorspace. I did that at one point in time. As a lark I recently did an IR to IP gateway using a FIT-PC2 and LIRC. Getting a working remote slotted in on my MX-900 was the hardest part.

That may be the case but it used to work just fine.

I am wondering if the main display in the Web control console is Java-based - I updated Java 6 on my Mac since I first tried this out (and it worked fine, and I wasn't using IE to access it either).

My KRP-500M is in my bedroom and my seating distance is 12 feet.
The only time I hear a faint buzz from my KRP-500M is when there is no signal being fed to the monitor. For example if I turn on the monitor without also turning on my AVR, bluray player, or cable box/dvr. At this moment I have the monitor on and the AVR on mute, so no sound and the monitor is completely silent.
If yours makes noise, try to get a different unit.

I've used all the browsers you noted (and more) on my Mac last May. None of them properly displayed the background or fonts even if you opened the frame by itself. FF under Windows might have done better but I'm fairly confident that only IE was 100%.

The server uses javascript but I don't think it uses Java or A-X controls. It just has an annoying set of IE dependencies. Fortunately it's completely superfluous.

If you really aren't sending a signal to your display then that's not panel buzz that's a power supply.

This has been discussed at tiresome length here, in the other Kuro threads and of course in the Kuro Buzz Thread. The noise is intrinsic to the technology and it's a bit annoying to those of us who are sensitive to it for people to mischaracterize what they cannot perceive.

In my household I have no trouble hearing the buzz and find it faintly annoying. My wife is completely oblivious to it and if I manage to get her in just the right spot and she does hear it she just goes "meh". It's quite irksome.

It can be done, they should have done it. It makes for unnecessary work-arounds, and more importantly extra cables/equipment, for many owners. This is why they should fix it. That's my story, and I'm stickin' to it.

I am in the process of reading this entire thread from the beginning, lol.

I stumbled upon something that I dont quite understand. I read it on page 2 so maybe pioneer already sent a patch for this I have not got to that part yet if they did.

My question is what the heck is RGB?

I think I may have activated the black crushing effect that is talked about. When I first inspected the set it was perfect, but once I connected my PS3 I noticed that it was almost too black.

I have a very simple setup. One HDMI port is my Directv DVR, my other HDMI port is my PS3.

Do I understand correctly that I need to take my settings off of auto?

Quick question on the 500m which i have had now for about a month.I've had it in FULL the entire time.I've past the 100-150hrs.Should i leave it in FULL or change to something else like AUTO.Or does it even matter.I heard that full does overscan unk if true.

If all I am using right now are my 2 hdmi ports this should not be an issue right?

I suspect most of us use Dot-by-Dot when watching HD material. I use it exclusively since the rare bit of video noise at the edge of the screen doesn't bother me.

I'm a bit lazy though.

Probably not. The DTV sends YUV and, although I understand that the PS3 can be used to perform some media center functions and may send RGB limited with certain video sources, the suggested settings send YUV (for video) or RGB full (for games) which is handled by the KRP in Auto mode.

They must have fixed it then, because early on in this thread I was told there was a glitch in the firmware that when you had the KRP in auto it would not handle the YUV correcty and would crush the blacks.

Many people in this thread has said that you have to leave the KRP in auto and adjust the PS2 manually to YUV when watching movies, and then switch it to RGB when playing games.

I could be wrong, but I could have swore I read that several times.

I apologize for my tiresome post. I only wanted to share my experience with the new owner who asked on this thread about the buzz.

Both of these topics are covered in the FAQ.

(Edited) The KRP handles YUV sources (YCbCr 4:4:4 or 4:2:2) correctly when set to Auto. However, if an RGB source does not have the appropriate RGB quantization bit set in the AVI Infoframe, the KRP may select RGB 0-255 even if the source is RGB Limited. If the source does contain the proper RGB quantization bit it will select Full or Limited based on that bit. Or so it seems..

I agree - they should have assumed an RGB limited default, even if it's a slightly plausible argument that a quasi-"monitor" should default to Full.

With regard to Pioneers failure to handle the quantization bits, it would be interesting to know if this is a industry-wide issue or if some manufacturers got it right. HDMI 1.3a was released in 11/2006 and included an "RGB quantization clarification," which may indicate some confusion on the correct usage. I found an example where a particular device had both YCbCr and Full bits set - not quite a legal combination.

The CEA seems pretty clear on what's CE versus IT equipment and from their perspective a compliant IT monitor should also shift to RGB Limited given a CE resolution.


When my CE friends (I must be a consultant, yeah that's the ticket) checked such things they found the byte was unused so they don't use it either. Since the only new colorspace information in byte 3 is extended colorimetry you can be fully functioning while ignoring it -- if you follow the CE versus IT "requirement". This does imply anyone doing xvYCC (not Pioneer, I got my vendors confused earlier) has to at least parse byte 3 even if they ignore the other bits.

By the way, I'm encouraging them to start setting it. For purely selfish reasons of course, I'd like to know if the KRP will do the right thing with explicit quantization.

My KRP on auto detects 16-235 when the PS3 is on limited, and 0-255 when the ps3 is on full. I can try to video me confirming the settings if no one believes me.

You know, you may be right (In other words...I may be am wrong). I've always noticed what we call the "RGB bug" based on my experience with my SA8300HD DVR and from what others have posted here, and assumed that was the case with all RGB Limited sources with HDMI Auto. After reading your post, I set my Sony S350 BD to RGB and the KRP's input to Auto and viewed a greyscale 0-255 bar pattern. Switched the KRP back and forth between Auto and RGB 16-235 and - surprise - no change in levels. The darn thing works! Which means that the KRP does recognize the RGB quantization bit, and it's the SA8300HD that must be leaving the bit unused. As Bodosom said, "..I'd like to know if the KRP will do the right thing with explicit quantization." I think this may be proof that it does. Now I can only put partial blame on Pioneer for defaulting to 0-255 when the bit is blank.

Was this a direct connection or via your AVR?

It was through a Monoprice switch. Could that be affecting the result?

Any non-direct connection can be tweaked by the repeater. Someone quoted a Monoprice tech as saying even different ports can have subtle variations. I'm not sure I believe that's anything but a bug but you never know with HDMI.

I'll do some poking (yet again) with direct connections. There might be extra monitoring hidden in my AVR behind some debug code that will sniff the descriptors.