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. |
30th September 2015, 11:47 | #21 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
Dolby Vision is annoying, they should stick to the HDR metadata that UHD Blu-ray favors (SMPTE ST- 2084/2086). It needs far less decoder changes.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
4th February 2016, 16:41 | #23 | Link |
Registered User
Join Date: Aug 2009
Posts: 201
|
Apparently work has begun:
https://chromium.googlesource.com/webm/aom/ https://chromium-review.googlesource...oject:webm/aom Mostly based on VP9/10 to start with. |
6th February 2016, 00:24 | #24 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,770
|
Quote:
And it's really not that valuable. A single flash frame from a camera flash can double the MaxFALL the whole rest of the title would use, and thus be very misleading for a tone mapper. |
|
5th April 2016, 22:01 | #25 | Link |
Registered User
Join Date: Nov 2009
Location: Northeast Ohio
Posts: 447
|
AMD, ARM, and Nvidia have joined, and because it apparently wasn't established before, this new upcoming in-development video codec will be an open-source project:
http://aomedia.org/press-release/the...and-announces/ Hopefully AMD will finally implement VP9 hardware decoding on their upcoming APUs and GPUs... Last edited by Nintendo Maniac 64; 5th April 2016 at 22:06. |
5th April 2016, 22:18 | #26 | Link |
Registered User
Join Date: Jan 2007
Posts: 729
|
All reference encoders/decoders are open source (H.264, H.265, VP8/9), so that was obvious. The distinction was never in open versus closed source anyway.
After all the development model is more or less the same, but probably with faster development and less testing/reviewing than the MPEG guys do, if libvpx traditions are any sign. So possibly there will again be few bugs in the frozen specification, like VP9/VP8 had The only difference between these "libre" (or whatever term is currently in) codecs and H.264/H.265/... is really in the patent licensing requirements and usage royalties. |
6th April 2016, 12:55 | #27 | Link |
Registered User
Join Date: Aug 2009
Posts: 201
|
I don't think they're announcing that it's open source, but that it is available and mentioning in passing that it's open source. Though I think it's actually been available already, so this is just an official announcement that it's available.
In other oddities, the new members are being given "founder member" status, even though they're joining a while after the others. Finally, the link seems to point just to the patent licence info (possibly the page will be updated to point to the actual code) but it appears to live here: https://aomedia.googlesource.com/aom/ A notably non-impartial place to host the code I would have thought, though it's all git in the end. |
7th April 2016, 01:08 | #28 | Link | |
Registered User
Join Date: Nov 2009
Location: Northeast Ohio
Posts: 447
|
Quote:
In other words, maybe because Intel was previously the only chip hardware designer, the group as a whole left the door open for other chip hardware designers? |
|
13th April 2016, 13:44 | #30 | Link | |
Registered User
Join Date: Jan 2007
Posts: 729
|
http://www.streamingmedia.com/Articl...ticleID=110383
Quote:
|
|
13th April 2016, 18:34 | #31 | Link | |
Registered User
Join Date: Apr 2016
Posts: 61
|
Quote:
https://arewecompressedyet.com/?r%5B...&s=ntt-short-1 Also, the VP10 basis it is built upon does not seem to take all development happening in the nextgenv2 branch. So they could potentially add more feat. already developed from VP10 later. I'm more concerned at the processing power needed for encoding. |
|
13th April 2016, 21:20 | #32 | Link |
Registered User
Join Date: Jan 2007
Posts: 729
|
Speed is inconsequential IMHO, even if it was 2-4x+ as slow as optimised HEVC or VP9 encoder, that would be soemthing that would be solvable - if by nothing else, by throwing more CPU cores there.
My fear is that the problems are going to be the same as with VP8/VP9 and (to a lesser degree, it has matured somewhat) x265: the encoder will be too fresh, too crude, without good rate control and lacking in utilisation of the new compression tools. The advances of format will be probably negated by poor quality encoder. This problem is hard and practice shows it takes years to improve. I think CPU requirements are nothing compared to that. |
25th April 2016, 19:53 | #33 | Link |
Registered User
Join Date: Jul 2003
Location: somewhere north
Posts: 260
|
did some testing
https://nwgat.ninja/test-driving-aomedias-av1-codec/ http://screenshotcomparison.com/comparison/170492
__________________
Woah! Ninja?! http://nwgat.ninja/ (AV1 Overview) "Not available in your region" has now been redefined as "Go Pirate, you filthy scum" Nwgat Last edited by wiak; 25th April 2016 at 19:57. |
26th April 2016, 16:20 | #35 | Link | |
Registered User
Join Date: Jul 2003
Location: somewhere north
Posts: 260
|
Quote:
https://github.com/nwgat/aom/search?...r+Quantization https://github.com/nwgat/aom/search?...=PVQ&type=Code
__________________
Woah! Ninja?! http://nwgat.ninja/ (AV1 Overview) "Not available in your region" has now been redefined as "Go Pirate, you filthy scum" Nwgat |
|
29th April 2016, 13:40 | #37 | Link |
Registered User
Join Date: Aug 2009
Posts: 201
|
The main repo is currently here:
https://aomedia.googlesource.com/aom/ which has more recent commits, though nothing in the last couple of weeks |
3rd May 2016, 11:04 | #39 | Link | |
Registered User
Join Date: Jun 2013
Posts: 98
|
Quote:
Also there are a lot of different branches where work is being done, here is a branch with Daala techniques being tested: https://chromium-review.googlesource...oject:webm/aom Here is what I believe is the official AOM branch: https://aomedia.googlesource.com/aom/ And here is the 'nextgenv2' branch, where there's a lot of work done at a rapid pace: https://chromium.googlesource.com/we...+log/nextgenv2 |
|
|
|