March 07, 2021, 08:37:19 PM

News:

--


AV1 support

Started by rolandpisano, January 09, 2019, 09:04:02 PM

Previous topic - Next topic

eumagga0x2a

Quote from: phaolo on October 14, 2020, 08:34:46 PMthe few times I tried them I always had problems.

Dev builds are better than releases most of the time, but sometimes they can be terrible. As can be releases.

Nightlies not being tested by a sufficiently large crowd means bugs making it into releases unnoticed.

phaolo

Ono, I finally tried the latest nighly (v277 VC 21-03-03) but.. it still shows the "Too short" error with AV1 :(

eumagga0x2a

Quote from: phaolo on March 05, 2021, 02:35:10 AMit still shows the "Too short" error with AV1

I just tried with a random AV1 video from YT (id fH921fbPB-g) as well as with the stream 399 from the video you mentioned earlier (id vKDQGcQWt9Q) and didn't experience any difficulties cutting the AV1 varieties in copy mode. I conclude from that that the problem is likely not on our side. Maybe you use a broken tool to obtain the videos in the first place, please try one which works (e.g. youtube-dl).

phaolo

March 05, 2021, 07:14:15 AM #18 Last Edit: March 05, 2021, 07:28:10 AM by phaolo
But I'm exactly using youtube-dl.
I made a script for it, but these are the resulting (simplified) parameters I use:

--merge-output-format mkv -f "(bestvideo[vcodec^=av01][height=1080]/bestvideo[vcodec^=vp9][height=1080]) + bestaudio[ext=webm][abr>=90]"

And here is the (simplified) Mediainfo data for the downloaded file for "vKDQGcQWt9Q":

Format                                   : Matroska
Format version                           : Version 4
File size                                : 254 MiB
Duration                                 : 12 min 17 s
Overall bit rate                         : 2 884 kb/s
Writing application                      : Lavf58.12.100

Video
Format                                   : AV1
Format/Info                              : AOMedia Video 1
Format profile                           : Main@L4.1
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 60.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits

Audio
Format                                   : Opus
Channel(s)                               : 2 channels
Sampling rate                            : 48.0 kHz
Bit depth                                : 32 bits
Compression mode                         : Lossy

I don't want to insist too much, but it's so strange that you aren't getting the error like me.  :-\

eumagga0x2a

Not insisting too much is the problem  :)

Which FFmpeg version is your youtube-dl using?

eumagga0x2a

It might be also helpful to know the segment layout i.e. where do you cut. Saving from the start of the video to e.g. 00:03:27.766 works impeccably for me, the MKV loaded by Avidemux was muxed from streams 399+251 with FFmpeg 4.3.2.

phaolo

March 05, 2021, 07:46:30 AM #21 Last Edit: March 05, 2021, 07:50:03 AM by phaolo
Mm.. I installed it from this archive:
ffmpeg- v0431_25 2020_11_15 win64- gpl shared.zip
It's not that old, but I'll try updating it.
(ffmpeg's multiple builds are confusing for me btw)

Btw your stream codes seem correct, and my test cuts were random (but on keyframes).

eumagga0x2a

4.3.1 is for sure recent enough, I didn't have any issues to cut with MKV created by 4.2.x at least (or maybe even 4.1.x). edit: obviously, on Linux.

phaolo

It didn't work :(
I updated ffmpeg to the latest version (v0432_160 2021_03_04 win64- gpl shared) and cut your video at your time and I'm still getting the error.

I'm on Windows 7 Pro x64 here instead.

eumagga0x2a

Quote from: phaolo on March 05, 2021, 07:46:30 AMffmpeg- v0431_25 2020_11_15 win64- gpl shared.zip

By the way, would you mind trying a static build?

eumagga0x2a

Another thing to try: don't use your youtbue-dl command line and obtain just the video track (i.e. 399), no audio. Try to cut it.

phaolo

March 05, 2021, 08:25:05 AM #26 Last Edit: March 05, 2021, 08:46:15 AM by phaolo
Quote from: eumagga0x2a on March 05, 2021, 08:06:40 AMBy the way, would you mind trying a static build?
Which one do you mean exactly?
As I mentioned, I don't understand those build names at all.

I followed the link "Windows builds by BtbN" and there are like 10 archives..

Quote from: eumagga0x2a on March 05, 2021, 08:09:30 AMAnother thing to try: don't use your youtbue-dl command line and obtain just the video track (i.e. 399), no audio. Try to cut it.
Ok, I tried "-f 399" and I can cut the resulting .mp4 mute file.
If I do "-f 399+251" instead, the resulting .mkv file gives the same error as before when cut.
I also tried VP9+Opus with "-f 303+251" and cutting the .webm didn't give me problems.

eumagga0x2a

March 05, 2021, 08:31:20 AM #27 Last Edit: March 05, 2021, 08:33:01 AM by eumagga0x2a
I meant ffmpeg-n4.3.2-160-gfbb9368226-win64-gpl-4.3.zip (no "shared" in the name).

(this simple machines forum software stupidly makes URLs out of anything with a period followed by three letters)

Quote from: phaolo on March 05, 2021, 08:25:05 AMIf I do "-f 399+251" instead, the resulting .mkv file gives the same error as before when cut.

The problem is obviously with the muxing step.

phaolo

Nope, the static builds gave me the same error.

Quote from: eumagga0x2a on March 05, 2021, 08:31:20 AMThe problem is obviously with the muxing step.
But why.. could it be a FFmpeg problem just on Windows?
Also damn, this means I downloaded a bunch of faulty AV1 files -_-

eumagga0x2a

Quote from: phaolo on March 05, 2021, 08:58:06 AMBut why.. could it be a FFmpeg problem just on Windows?

Difficult to tell with certainty at this stage of problem assessment. Could be also a Matroska demuxer problem in Avidemux (on Windows only, of course). Could you eventually provide such a presumably faulty MKV as a sample via WeTransfer, Mega, Dropbox or Google Drive, please?