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.

 

Go Back   Doom9's Forum > Video Encoding > VP9 and AV1

Reply
 
Thread Tools Search this Thread Display Modes
Old 20th May 2020, 08:42   #2181  |  Link
stax76
Registered User
 
Join Date: Jun 2002
Posts: 6,506
Quote:
Originally Posted by marcomsousa View Post
I generated one time build for libaom v2.0.0 stable branch.
https://ci.appveyor.com/project/marc...7143/artifacts
Thanks for the build.

Has this encoder something like a github repo?

It seems there is absolutely no version information provided by the encoder.
stax76 is offline   Reply With Quote
Old 20th May 2020, 08:56   #2182  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,292
If you use the media-autobuild suite:
In the media-suite_compile.sh you can read that it is downloaded from https://aomedia.googlesource.com/aom by a helper function do_vcs() in media-suite_helper.sh which handles a variety of methods.

Apparently there is a git repo behind this URL, which appears as website with an own design in a browser. There are branches (MABS uses the "master" branch usually) and tags. Their relation is not very obvious, though. I am not sure but I believe there was an additional shell script which collects required information to store the version information as "tag+updatecount" in a header file...
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid

Last edited by LigH; 20th May 2020 at 09:00.
LigH is offline   Reply With Quote
Old 20th May 2020, 09:55   #2183  |  Link
stax76
Registered User
 
Join Date: Jun 2002
Posts: 6,506
Thanks for the info LigH, so no issue tracker. Maybe a developer reads here and bookmarks this post as feature request, I would like to suggest providing version info, examples:

Code:
Desktop> x265 --help
x265 [info]: HEVC encoder version 3.3+27-g4780a8d99
x265 [info]: build info [Windows][GCC 11.0.0][64 bit] 8bit+10bit+12bit

Syntax: x265 [options] infile [-o] outfile
    infile can be YUV or Y4M
    outfile is raw HEVC bitstream

Executable Options:
-h/--help                        Show this help text and exit
   --fullhelp                    Show all options and exit
-V/--version                     Show version info and exit
Code:
Desktop> nvencc64 --help
NVEncC (x64) 5.01 (r1507) by rigaya, May  7 2020 12:04:16 (VC 1916/Win/avx2)
  [NVENC API v9.1, CUDA 10.1]
 reader: raw, y4m, avi, avs, vpy, avsw, avhw [H.264/AVC, H.265/HEVC, MPEG2, VP8, VP9, VC-1, MPEG1, MPEG4]
Usage: NVEncC.exe [Options] -i <input file> -o <output file>

Input can be avi, avs, raw YUV, YUV4MPEG2(y4m).
When Input is in raw format, fps, input-res is required.

Ouput format will be in raw H.264/AVC or H.265/HEVC ES.

Example:
  NVEncC -i "<avsfilename>" -o "<outfilename>"
  avs2pipemod -y4mp "<avsfile>" | NVEncC --y4m -i - -o "<outfilename>"

Information Options:
-h,-? --help                    print help
-v,--version                    print version info

Last edited by stax76; 20th May 2020 at 09:58.
stax76 is offline   Reply With Quote
Old 20th May 2020, 10:30   #2184  |  Link
marcomsousa
Registered User
 
Join Date: Jul 2018
Posts: 77
Quote:
Originally Posted by stax76 View Post
Thanks for the build.

Has this encoder something like a github repo?
It seems there is absolutely no version information provided by the encoder.
Encoder git repo: https://aomedia.googlesource.com/aom/+/refs/tags/v2.0.0

Build script for vs2019 git repo: https://github.com/marcomsousa/build_aom

In every libaom commit (in master branch) a build is automatically generated: https://ci.appveyor.com/project/marc...ld-aom/history
Now it goes with v2.0.0-255-ge0be17e7f



The version you can see if you perform:
Quote:
aomenc.exe --help
(...)
Included encoders:
av1 - AOMedia Project AV1 Encoder 2.0.0 (default)
Use --codec to switch to a non-default encoder.
Quote:
aomenc.exe --help
(...)
Included encoders:
av1 - AOMedia Project AV1 Encoder 2.0.0-255-ge0be17e7f (default)
Use --codec to switch to a non-default encoder.
__________________
AV1 win64 VS2019 builds
Last build here

Last edited by marcomsousa; 20th May 2020 at 10:40.
marcomsousa is offline   Reply With Quote
Old 20th May 2020, 10:33   #2185  |  Link
hydra3333
Registered User
 
Join Date: Oct 2009
Location: crow-land
Posts: 540
Quote:
Originally Posted by stax76 View Post
no issue tracker.
is this it ?
https://bugs.chromium.org/p/aomedia/issues/list
google look at and respond in it, eg by addressing a couple of very trivial things I may have raised.

Last edited by hydra3333; 20th May 2020 at 10:38.
hydra3333 is offline   Reply With Quote
Old 20th May 2020, 15:17   #2186  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,292
There must have been a merge in the meantime.

AOM v2.0.0-255-ge0be17e7f

And yes, the bug tracker should match.
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid

Last edited by LigH; 20th May 2020 at 15:19.
LigH is offline   Reply With Quote
Old 21st May 2020, 22:35   #2187  |  Link
benwaggoner
Moderator
 
Join Date: Jan 2006
Location: Portland, OR
Posts: 3,432
Quote:
Originally Posted by nevcairiel View Post
AV1 support was added to DXVA (Microsofts hardware acceleration API) in the Windows 10 2004 SDK update, hence where those come from. But no indication of hardware that uses them quite yet.
The other typical structures to convey codec information to the hardware are still suspiciously absent however, so it may not be fully finalized.
There aren't any GPUs out or (IIRC) announced with HW AV1 decode. I'm confident they're being worked on, of course, although it's speculation as to when, which, and how universally across product lines.
__________________
Ben Waggoner
Principal Video Specialist, Amazon Prime Video

My Compression Book
benwaggoner is offline   Reply With Quote
Old 22nd May 2020, 16:04   #2188  |  Link
birdie
.
 
birdie's Avatar
 
Join Date: Dec 2006
Posts: 170
Looks like Tiger Lake will be the first x86 uArch to support AV1 HW decoding:

https://pbs.twimg.com/media/EYn7NM0V...=png&name=orig
https://pbs.twimg.com/media/EYn7f9BU...=png&name=orig
https://pbs.twimg.com/media/EYn72cxU...=png&name=orig
https://pbs.twimg.com/media/EYn8WKXU...=png&name=orig


I do hope NVIDIA will support it as well in Ampere.

Last edited by birdie; 22nd May 2020 at 16:07.
birdie is offline   Reply With Quote
Old 22nd May 2020, 16:50   #2189  |  Link
Yups
Registered User
 
Join Date: Sep 2011
Posts: 225
I was hoping for encoding as well but it seems not so easy to implement. Is it correct that Gen12 only supports 4K video decoding?
Yups is offline   Reply With Quote
Old 22nd May 2020, 18:05   #2190  |  Link
Blue_MiSfit
Derek Prestegard IRL
 
Blue_MiSfit's Avatar
 
Join Date: Nov 2003
Location: Los Angeles
Posts: 5,762
Source for those captures?
Blue_MiSfit is offline   Reply With Quote
Old 22nd May 2020, 18:32   #2191  |  Link
Yups
Registered User
 
Join Date: Sep 2011
Posts: 225
Momomo_us posted this: https://twitter.com/momomo_us/status...18639423074304

He didn't reveal the original source.
Yups is offline   Reply With Quote
Old 22nd May 2020, 18:56   #2192  |  Link
benwaggoner
Moderator
 
Join Date: Jan 2006
Location: Portland, OR
Posts: 3,432
Quote:
Originally Posted by birdie View Post
Looks like a good media unit for a non-discreet GPU. I think 12-bit HEVC decode is new as well. I wonder what use cases the 12-bit support is; NVidia has had it for a few years as well. I can see it being used for high-bitrate mezzanine files or something. Can't imagine a 12-bit VP9 scenario, though.

I note they don't list bit depths for AV1. Does that imply 8-bit only? They don't list it for AVC either, does Intel support >8-bit AVC decode, or only with more advanced codecs.
__________________
Ben Waggoner
Principal Video Specialist, Amazon Prime Video

My Compression Book
benwaggoner is offline   Reply With Quote
Old 22nd May 2020, 19:07   #2193  |  Link
Yups
Registered User
 
Join Date: Sep 2011
Posts: 225
Quote:
Originally Posted by benwaggoner View Post
I note they don't list bit depths for AV1. Does that imply 8-bit only? They don't list it for AVC either, does Intel support >8-bit AVC decode, or only with more advanced codecs.

There are bit depths listed but it's not clear to me. One the left it says profile0 (8 bit and 10 bit 4:2:0) 4k60 video, 16K still. The text on the right side is confusing. Intel only supports 8 bit for AVC by the way.
Yups is offline   Reply With Quote
Old 22nd May 2020, 19:37   #2194  |  Link
hajj_3
Registered User
 
Join Date: Mar 2004
Posts: 985
Quote:
Originally Posted by benwaggoner View Post
Looks like a good media unit for a non-discreet GPU. I think 12-bit HEVC decode is new as well. I wonder what use cases the 12-bit support is; NVidia has had it for a few years as well. I can see it being used for high-bitrate mezzanine files or something. Can't imagine a 12-bit VP9 scenario, though.

I note they don't list bit depths for AV1. Does that imply 8-bit only?
12bit av1 with rocket lake, tiger lake and their standalone graphics card:

hajj_3 is offline   Reply With Quote
Old 22nd May 2020, 19:50   #2195  |  Link
Yups
Registered User
 
Join Date: Sep 2011
Posts: 225
Quote:
Originally Posted by hajj_3 View Post
12bit av1 with rocket lake, tiger lake and their standalone graphics card:

This is an RKL-S slide, you can never know if there is a newer decoder build in for RKL-S because it comes about half a year later than TGL-U. Also this slide isn't as detailed as today's leak, it could be a mistake there. 12 bit HEVC but not for AV1, it could be.
Yups is offline   Reply With Quote
Old 22nd May 2020, 20:21   #2196  |  Link
GTPVHD
Registered User
 
Join Date: Mar 2008
Posts: 199
https://github.com/intel/media-drive...media-features

HEVC and VP9 12-bit and 4:4:4 fixed-function hardware decoding support in Gen12/Xe GPU is old news, Intel already revealed that info since December 26 last year in their Media Driver updates.

Intel is still unclear about AV1 fixed-function hardware decoding capabilities, it would be disappointing if they didn't support 8K, 12-bit and 4:4:4 like VP9 hardware decoder does in Gen12/Xe.

Last edited by GTPVHD; 22nd May 2020 at 20:24.
GTPVHD is offline   Reply With Quote
Old 22nd May 2020, 20:41   #2197  |  Link
Yups
Registered User
 
Join Date: Sep 2011
Posts: 225
10 bit sure but do we really need 12 bit?
Yups is offline   Reply With Quote
Old 23rd May 2020, 00:09   #2198  |  Link
Beelzebubu
Registered User
 
Join Date: Feb 2003
Location: New York, NY (USA)
Posts: 80
Quote:
Originally Posted by GTPVHD View Post
it would be disappointing if they didn't support 8K, 12-bit and 4:4:4 like VP9 hardware decoder does in Gen12/Xe.
It says profile 0 only, which is 4:2:0 and 8+10bit only. 4:4:4 is profile 1, 12-bit is profile 2 (along with 4:2:2 for 8+10bit).
Beelzebubu is offline   Reply With Quote
Old 23rd May 2020, 01:43   #2199  |  Link
benwaggoner
Moderator
 
Join Date: Jan 2006
Location: Portland, OR
Posts: 3,432
Quote:
Originally Posted by Yups View Post
10 bit sure but do we really need 12 bit?
Dolby Vision is internally 12-bit, and does tricks with dual layers or a non-backwards compatible base layer and metadata to reconstruct the video in an internal 12-bit format. If we had 12-bit decoders when DoVi was coming out, we'd probably just have a HDR-12 base layer + metadata.

Only current use of 12-bit for anything I can think of is in intermediate post production or high end mezzanine formats like J2K IMF.
__________________
Ben Waggoner
Principal Video Specialist, Amazon Prime Video

My Compression Book
benwaggoner is offline   Reply With Quote
Old 23rd May 2020, 08:10   #2200  |  Link
soresu
Registered User
 
Join Date: May 2005
Location: Swansea, Wales, UK
Posts: 170
Quote:
Originally Posted by benwaggoner View Post
Dolby Vision is internally 12-bit, and does tricks with dual layers or a non-backwards compatible base layer and metadata to reconstruct the video in an internal 12-bit format. If we had 12-bit decoders when DoVi was coming out, we'd probably just have a HDR-12 base layer + metadata.

Only current use of 12-bit for anything I can think of is in intermediate post production or high end mezzanine formats like J2K IMF.
Isn't all this pointless when hardly any TVs actually support 12 bit though?
soresu is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 03:54.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.