weightp incompliant Blu-ray standalone players?

[A.Fenderson]

I was under the impression that most weightp-noncompliant BD players had resolved this issue via available firmware updates, but some people are still using and recommending --weightp 0 for BD-intended encodes.

Does anyone have any examples of actual BD player hardware devices with no native or firmware-update enabled support for weightp?

Bonus question: what software players still have problems with this other than when using CoreAVC versions prior to 2?

Thanks.

[kieranrk]

If it was a professional BD-release the fact that there are firmware updates to fix weightp issues is irrelevant since a significant proportion of people would not have updated their firmware.

[laserfan]

Does anyone have any examples of actual BD player hardware devices with no native or firmware-update enabled support for weightp?

Bonus question: what software players still have problems with this other than when using CoreAVC versions prior to 2?I have an LG BH200, which uses old firmware from early 2008, and it plays my homebrew x264 BDs with weightp at default (iirc is 2/auto) and opengop as well. No problems whatsoever (all other settings are to strict BD-compliance).

My Arcsoft TMT 3.0 b160 (I think, it's a couple behind from current 180) does not play these without glitches: if HW Acceleration is on, they are completely unwatchable, with HW Acceleration off, they are watchable but can be blocky--I only use the sw to check my structures.

[LoRd_MuldeR]

Does anyone have any examples of actual BD player hardware devices with no native or firmware-update enabled support for weightp?

Apple TV was one of the prominent examples for hardware players that are broken with respect to Weight-P.

Don't think it was ever fixed. Was it? :confused:

[Ghitulescu]

I was under the impression that most weightp-noncompliant BD players had resolved this issue via available firmware updates, but some people are still using and recommending --weightp 0 for BD-intended encodes.

Does anyone have any examples of actual BD player hardware devices with no native or firmware-update enabled support for weightp?

If it was a professional BD-release the fact that there are firmware updates to fix weightp issues is irrelevant since a significant proportion of people would not have updated their firmware.
I think this is an x264-related issue. Most if not all commercial BD releases are now VC-1 (MPEG-2 started to fade away, used mostly in demos). I don't say there are no commercial H.264, just that I haven't seen one myself.

So, why would a company invest time in modifying a FW for a thing that is not used in praxis other than by a few hobbists (read damn pirates :p), while burning issues (new BD+ variants, ineffective BD-J programming etc., old bugs) plague the players?

Besides, one of the requirements for players is to be updatable, so new FW versions will appear and some disks (Avatar) may force you to upgrade.

In a horror scenario, the next playing platform may use media that automatically update your player ... one of the reasons BD-live was created.

[Dark Shikari]

I think this is an x264-related issue. Most if not all commercial BD releases are now VC-1 (MPEG-2 started to fade away, used mostly in demos). I don't say there are no commercial H.264, just that I haven't seen one myself.

So, why would a company invest time in modifying a FW for a thing that is not used in praxis other than by a few hobbistsAsk MediaTek, who worked quite hard to fix this issue.

[nurbs]

Probably because he is wrong. From what I found through google about half of currently released blu-ray discs use AVC and checking upcoming releases it doesn't look much different.

[Ghitulescu]

You're might be right that most BluRays are today AVC (I've checked with de.blu-ray.com minutes ago), but in those about 100-150 BDs I've seen, none was AVC, only VC-1 (and MPEG-2 for demos). My mistake to draw rapid conclusions from such a small base ... :( Sorry for that.

Anyway, should have been problems with weightp and BD players, it would have been a huge outcry in the community, I assume then that it weightp is 0 for commercial blurays.

[laserfan]

My Arcsoft TMT 3.0 b160 (I think, it's a couple behind from current 180) does not play these without glitches: if HW Acceleration is on, they are completely unwatchable, with HW Acceleration off, they are watchable but can be blockyNote that Arcsoft appears now to have fixed all problems, with build 185.

[shon3i]

Blu-Code (as default) and CEE-HDe use weight p prediction, and probably is on most retail encodes.

[sneaker_ger]

But they don't utilize it the same way x264's --weightp 2 utilizes it, do they?

[shon3i]

CoreAVC pre 2.0 aslo fail with Blu-Code weight p. Aslo Blu-Code's weight make fades very smooth/natural, more than x264.

Aslo new cinevision beta (MVC) uses weight p from recent mainconcept sdk.