Threaded Mode | Linear Mode

**Syabas** · (04-02-2011)

Please make sure your AVR is HDMI1.4 compliant as well, otherwise it will block
the HDMI1.4 signalling from our device, so you won't see any different.

An update on the buglist:

Reported on betatester Mantis: 500+
Closed: 300+
Open item: 120
Feature request: 66

Of the 120 open items:
- our QA have processed 74 items
- 46 not processed (will be done in due time depending on our QA manpower)
- 13 still under QA verification

- 28 confirmed bugs (1 is a duplicate)

- 33 cannot reproduce on our QA setup
(Werner will communicate with respective beta-tester for offending clip,
or for more details on users setup)

Will discuss the confirmed bugs in beta-tester forum next week, after we
complete our first round of prioritisation.

lostmage · 04-01-2011, 03:24 PM

although not a beta tester this sort of info being shared is great, at least we get an idea of whats happening and that the dev's are working with the community and all the beta testers who dedicate there time so we get a better product at the end of the day,

Padavan · (This post was last modified: 04-01-2011 11:18 PM by Padavan.)

Syabas
Why PCH-C200/A2x0 does not support HDMI output in YCbCr color space??? Huh

I have two another SMP8655-based (WDTV Gen2) and SMP8643-based (Dune Smart-H1) media players, and they use BT.709 YCbCr 4:4:4 output by default. Dune Smart-H1 also support sRGB modes for compatibility with PC monitors. Also they support 8/12 bit depth.

PCH support only sRGB 4:4:4 [0-255] 8 bit and sRGB 4:4:4 [16-235] 8bit. Why? It is very sad Sad

**Willem53** · 04-02-2011, 06:29 AM

(04-01-2011 11:16 PM)Padavan Wrote: Syabas
Why PCH-C200/A2x0 does not support HDMI output in YCbCr color space???

I have two another SMP8655-based (WDTV Gen2) and SMP8643-based (Dune Smart-H1) media players, and they use BT.709 YCbCr 4:4:4 output by default. Dune Smart-H1 also support sRGB modes for compatibility with PC monitors. Also they support 8/12 bit depth.

PCH support only sRGB 4:4:4 [0-255] 8 bit and sRGB 4:4:4 [16-235] 8bit. Why? It is very sad

never thought I do this but +1 from me on this feature.... Rolleyes

**halfelite** · 04-02-2011, 06:31 AM

(04-01-2011 11:16 PM)Padavan Wrote: Syabas
Why PCH-C200/A2x0 does not support HDMI output in YCbCr color space???

I have two another SMP8655-based (WDTV Gen2) and SMP8643-based (Dune Smart-H1) media players, and they use BT.709 YCbCr 4:4:4 output by default. Dune Smart-H1 also support sRGB modes for compatibility with PC monitors. Also they support 8/12 bit depth.

PCH support only sRGB 4:4:4 [0-255] 8 bit and sRGB 4:4:4 [16-235] 8bit. Why? It is very sad

The problem with it to start was the SDK the pch chose to use YcbCR and deep color were broken. the wd and dune used an older firmware where it was ok. Hopefully the next sdk brings use this feature.

accident · 04-02-2011, 06:40 AM

(03-30-2011 04:32 AM)Syabas Wrote: Let us know anything else needed by the community developers.

I appreciate this but it feels off topic for this thread. What is the best way we can all communicate our needs on this topic? It will offer a chance for everyone working on projects to chime in without distracting this discussion.

I do want to point out that those of us who are trying to make apps and use the new api/sdk are feeling like we are on our own except for 1 person behind the scenes who might answer 1-2 questions every couple weeks. We could really use more support in the development website.

deh2k7 · 04-02-2011, 07:04 AM

(04-01-2011 11:16 PM)Padavan Wrote: Syabas
Why PCH-C200/A2x0 does not support HDMI output in YCbCr color space???

I have two another SMP8655-based (WDTV Gen2) and SMP8643-based (Dune Smart-H1) media players, and they use BT.709 YCbCr 4:4:4 output by default. Dune Smart-H1 also support sRGB modes for compatibility with PC monitors. Also they support 8/12 bit depth.

PCH support only sRGB 4:4:4 [0-255] 8 bit and sRGB 4:4:4 [16-235] 8bit. Why? It is very sad

I think this request goes hand-in-hand with the native resolution video output requests. To me, this and native resolution are critical features in any player of the C200 caliber. This allows the player to output source material without alteration (it's primary domain as a source transport), and let the display devices deal with color space and/or resolution/scaling (their primary domain).

Features like this ensure that Syabas is not just a 'techie' solution, but a solution that is suitable for home theaters and high-end installations.

**chris57** · 04-02-2011, 07:36 AM

(04-02-2011 07:04 AM)deh2k7 Wrote: I think this request goes hand-in-hand with the native resolution video output requests. To me, this and native resolution are critical features in any player of the C200 caliber. This allows the player to output source material without alteration (it's primary domain as a source transport), and let the display devices deal with color space and/or resolution/scaling (their primary domain).

Features like this ensure that Syabas is not just a 'techie' solution, but a solution that is suitable for home theaters and high-end installations.

Any yet again we are back to our own wish lists.

I think by now having diverted many threads onto this subject and having a well supported thread asking for the feature that by doing this you are only going to annoy and do damage to the cause! Syabas get it, we get it, stop it!

Padavan · (04-04-2011)

(04-02-2011 06:31 AM)halfelite Wrote: The problem with it to start was the SDK the pch chose to use YcbCR and deep color were broken. the wd and dune used an older firmware where it was ok. Hopefully the next sdk brings use this feature.

Hmmm.. It is seems true, but I have some doubts:
- PCH never supported YCbCr HDMI output, even on old firmwares (like march 2010)
- PCH now used MRUA SDK 3.7.2 and no YCbCr
- Dune now used MRUA SDK 3.7.2 and YCbCr worked (BT.601/BT.709)
- WDTV G2 now used MRUA SDK 3.7.1rc3 and YCbCr worked
- WDTV Live now used MRUA SDK 3.8.5 and YCbCr worked
- SigmaDesign offers SDK 3.9.x (from July 2010) with support YCbCr and xvYCC, with support MJPEG, DV, FLV decoding.

Huh

**halfelite** · 04-02-2011, 08:18 AM

syabas is switching to 3.9

deh2k7 · 04-04-2011, 01:16 AM

(04-02-2011 07:36 AM)chris57 Wrote:
(04-02-2011 07:04 AM)deh2k7 Wrote: I think this request goes hand-in-hand with the native resolution video output requests. To me, this and native resolution are critical features in any player of the C200 caliber. This allows the player to output source material without alteration (it's primary domain as a source transport), and let the display devices deal with color space and/or resolution/scaling (their primary domain).

Features like this ensure that Syabas is not just a 'techie' solution, but a solution that is suitable for home theaters and high-end installations.

Any yet again we are back to our own wish lists.

I think by now having diverted many threads onto this subject and having a well supported thread asking for the feature that by doing this you are only going to annoy and do damage to the cause! Syabas get it, we get it, stop it!

Chris - what seems to be your issue? You are the only one here complaining about discussing issues and feature requests. The very request for YCbCr and deep color support are personal requests and I see nothing from you complaining about that. I merely supported another user's comment, including my own comments. This thread is already way off-topic, and your negative comments are not helping.

Syabas is willingly discussing with us here. If Syabas has an objection and wishes us to stop, that's one thing, but since he already responded and even committed to looking into the request earlier, I don't see the harm. Why not let Syabas make the call instead?

**chris57** · (This post was last modified: 04-04-2011 07:50 AM by chris57.)

Unbelievable!!!

This is our forum and we moderate it not Syabas. Respect that or face the consequences. You were asked to stop pushing your personal feature (Native Resolution NOT Deep Colour) request nicely and you still push it 'this goes hand in hand with native resolution'. You have been warned.

It is very simple. If everyone takes this topic and diverts it into a shambolic mess of posts about whatever is their number one issue then the thread will go nowhere. We are keeping this thread closely moderated to remain on topic and get the List of Bugs/Features from Syabas. Now and here is NOT the time for your personal crusade!

I will clean the thread shortly of off-topic posts.

**Syabas** · (04-04-2011)

Well, engineering got the YCbCr BT.601 and BT.709 colorspace added in a few hours work today.
It will be in the build after the next. Currently already a build in QA.

Somehow this request seems to have drop out of our radar.

Adrgha · (This post was last modified: 04-04-2011 11:21 AM by Adrgha.)

I just wanted to state my appreciation of the level of communication you've been relaying here at the forums over the last week. It's great, and I hope you plan on continuing with this. This really gives me improved confidence in you as a company and where you're headed in the future. There really is a lot of interesting and relevant information in this thread.

Also, that you got YCbCr support nailed is great news!

**Willem53** · 04-04-2011, 01:55 PM

(04-04-2011 11:14 AM)Syabas Wrote: Well, engineering got the YCbCr BT.601 and BT.709 colorspace added in a few hours work today.
It will be in the build after the next. Currently already a build in QA.

Somehow this request seems to have drop out of our radar.

So who is keeping an eye on the feature requests here and in MANTIS?