Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
24th January 2013, 20:36 | #41 | Link | |
Registered User
Join Date: Dec 2012
Posts: 197
|
Quote:
I've also noticed in the draft text that they added grain flags as an option for the bitstream and that those flags also existed in AVC. Anyone know if there were ever any h264 products that took advantage of those flags? It seems that almost all of AVC's growing pains in the marketplace (plasticky encodes) would have been alleviated with some smart decoding action. |
|
25th January 2013, 16:04 | #42 | Link | ||
Registered User
Join Date: Mar 2010
Location: Ukraine
Posts: 50
|
Quote:
Edit: http://wiki.videolan.org/SoC_x264_2008 Quote:
__________________
blendhater Last edited by D3C0D3R; 25th January 2013 at 16:07. |
||
25th January 2013, 16:16 | #46 | Link | |
Guest
Posts: n/a
|
Quote:
Now it's more than possible he's changed his mind since then, but I've found nothing from him through searching that has him saying it's useless. Last edited by paradoxical; 25th January 2013 at 16:41. |
|
25th January 2013, 17:13 | #47 | Link |
もこたんインしたお!
Join Date: Jan 2008
Location: Finland / Japan
Posts: 512
|
FGM wasn't useless indeed, but its implementation was so limited it was generally very hard to implement it and see if it worked at all. Now-dead HD-DVD did contain support for it, but I'm not sure if any discs actually used it, or if any decoders bundled with HD-DVD players supported it.
JM not supporting it was also a large thing against it, as it often is used to test an implementation. The fact that JM was broken with lossless encoding for ages (the newer thing in High 4:4:4 Profile), and the fact that the specification was (not on purpose) readable in a way that was not meant by the creators of the specification, were the reasons that led to the lossless encoding mode of x264 to be out-of-spec. It still is, and nothing will be done about it because everything else that implements it (libavcodec, CoreAVC etc.) implements it in the way that x264 implemented it (I think it was either in 2010 or 2011 that someone actually found out about the difference in implementation compared to the specification).
__________________
[I'm human, no debug]
|
26th January 2013, 07:11 | #48 | Link | |
Swallowed in the Sea
Join Date: Oct 2002
Location: Aix-en-Provence, France
Posts: 5,191
|
ITU has approved this codec...
Quote:
|
|
26th January 2013, 12:23 | #50 | Link | |
もこたんインしたお!
Join Date: Jan 2008
Location: Finland / Japan
Posts: 512
|
Quote:
__________________
[I'm human, no debug]
|
|
26th January 2013, 12:34 | #51 | Link | |
Life's clearer in 4K UHD
Join Date: Jun 2003
Location: Notts, UK
Posts: 12,227
|
Quote:
__________________
| I've been testing hardware media playback devices and software A/V encoders and decoders since 2001 | My Network Layout & A/V Gear |
|
|
26th January 2013, 17:56 | #53 | Link |
Registered User
Join Date: Mar 2004
Posts: 1,125
|
Nearly ratified then Lets hope that nvidia and AMD add decoding support into the programmable areas of their gpus like they did with h264 before they created dedicated silicon in their gpu's for h.264. I reckon intel will probably have dedicated silicon in their chips within 18 months as they have a lot of cash to throw at it.
Now someone go do an in-depth test on how good it's compression is at 720x400, 1280x720, 1920x1080 Last edited by hajj_3; 26th January 2013 at 18:07. |
28th January 2013, 10:13 | #55 | Link | |
Swallowed in the Sea
Join Date: Oct 2002
Location: Aix-en-Provence, France
Posts: 5,191
|
Looks like x265 project (not related to x264 though) has been updated few days ago...
Quote:
|
|
28th January 2013, 10:32 | #56 | Link | |
Registered User
Join Date: Dec 2005
Posts: 106
|
Quote:
Code:
hm_9.2_r3282_release>TAppDecoder.exe -b ChinaSpeed_1024x768_30_qp37.bi n -o 123.yuv HM software: Decoder Version [9.2rc1][Windows][VS 1600][32 bit] Assertion failed: uiCode == 3, file ..\..\source\Lib\TLibDecoder\TDecCAVLC.cpp, line 657 |
|
28th January 2013, 14:12 | #57 | Link | |
もこたんインしたお!
Join Date: Jan 2008
Location: Finland / Japan
Posts: 512
|
Quote:
Code:
TAppDecoder.exe -b zeroma_HM9.2.hevc -o zeroma_HM9.2.yuv HM software: Decoder Version [9.2rc1][Windows][VS 1600][32 bit] TDecCavlc::parsePPS(): m_bUseWeightPred=0 m_uiBiPredIdc=0 POC 0 TId: 0 ( I-SLICE, QP 20 ) [DT 0.006] [L0 ] [L1 ] [:,,,(unk)] ...
__________________
[I'm human, no debug]
|
|
28th January 2013, 20:46 | #58 | Link | |
Registered User
Join Date: Dec 2012
Posts: 197
|
Quote:
|
|
29th January 2013, 19:41 | #60 | Link | |
もこたんインしたお!
Join Date: Jan 2008
Location: Finland / Japan
Posts: 512
|
No idea about exact details, but smarter did note that the OpenHEVC folk were also making their own decoder, and using HM + smarter's decoder to test results against.
Quote:
__________________
[I'm human, no debug]
|
|
Tags |
hevc. h.265 |
Thread Tools | Search this Thread |
Display Modes | |
|
|