It would be nice if computers only had exactly one video and image format. Like for better or for worse, this is what you get. Everything would just work.
That would be very inefficient in terms of data size, energy consumption and CPU time.
2 years ago
Anonymous
internet is meant for white man and white man only, no need to support street shitters, we could live in properity, instead we choose to let them poison our minds
>webm >one video format >meanwhile >vp8 >vp9 >vp10 >vp11 >vp12 >vp13 >vp14 >vp15 >etc.
2 years ago
Anonymous
VP9 was released NINE YEARS AGO
VP10 isn't happening, google went all in on AV1 instead.
2 years ago
Anonymous
IIRC AV1 is largely based on Xiph's DAALA.
2 years ago
Anonymous
Wikipedia (I know, I know) says it's both: >However, Google decided to incorporate VP10 into AOMedia Video 1 (AV1). The AV1 codec was developed based on a combination of technologies from VP10, Daala (Xiph/Mozilla) and Thor (Cisco).[106][107][108] Accordingly, Google has stated that they will not deploy VP10 internally nor officially release it, making VP9 the last of the VPx-based codecs to be released by Google.
>It would be nice if computers only had exactly one video [...] format. Like for better or for worse, this is what you get.
I don't think you'd say that if you were familiar with the shit codecs we started out with.
>image format
This is basically already the case, with jpg, which is ubiquitous. Of course png also exists and svg also exist, but for good reasons; jpg is specifically optimized for photography, not vector graphics.
>It would be nice if computers only had exactly one video and image format
BMP.
also we should make MJPEG alternative but with BMPs, mjpeg is just jpeg files in zip
2 years ago
Anonymous
>mjpeg is just jpeg files in zip >in zip
I don't think that part is true. I don't think the container for motion jpegs is specified anywhere. From what I understand, there is no standard for how to store an mjpeg stream but AVI is commonly used.
2 years ago
Anonymous
>also we should make MJPEG alternative but with BMPs
Uncompressed .AVI with PCM .WAV audio.
The WebM container itself is a subset of Matroska though. And Google has nothing to do with Vorbis or Opus so that's far from ~~*everything*~~ in my book.
It's open so I have no issue with it. If Google let their engineers work on something worthwhile for once then why not use it? You're like a mathematican saying that you won't accept some guy's proof and won't use his super innovative formula, because he used a calculator
AV1 only offers around 10-20% better compression efficiency compared to 10-bit VP9/HEVC while at the same time takes 10X longer to encode. If efficiency jumps to 30-40% then the sub-1 FPS encode times will be worth it.
Because as much as everyone hates the borg there's a far more insidious and utterly evil entity: mpeg la. They've been known to go after individual users for uploading H264/HEVC content on the internet without paying ~~*royalty*~~ fees. VP9 is open sores, royalty free, and encodes 10X faster compared to AV1.
What part of >AV1 only offers around 10-20% better compression efficiency compared to 10-bit VP9/HEVC while at the same time takes 10X longer to encode.
did you not understand?
2 years ago
Anonymous
You stupid fricking Black person. svt-av1 is faster than libvpx-vp9 while offering superior compression.
have a nice day
2 years ago
Anonymous
>svt-av1 is faster than libvpx-vp9
Prove it.
2 years ago
Anonymous
>SVT
lower quality than AV1 AOM, you know the encoder required to achieve 10-20% better compression efficiency than 10-bit VP9?
2 years ago
Anonymous
what does that even mean
2 years ago
Anonymous
AV1 still remains a BETA codec for personal use.
2 years ago
Anonymous
Yeah, but SVT-AV1 looks very promising. And it's plenty usable already, much more than libvpx at least.
2 years ago
Anonymous
(Checked)
Good enough for youtube, good enough for me.
AV1 is still only suitable for giant tech companies like youtube not for consumers. Only a small portion of the population know that handbrake exists (no AV1 option yet, SVT-AV1 unlikely). Even less know how to use ffmpeg.
2 years ago
Anonymous
That depends on your definition of suitability. The support isn't quite there yet, but its performance profile is good enough for encoding in home environment.
ffmpeg spits out the encoding speed btw.
libvpx-vp9 is around 0.2 something on my machine. >transcoding 1080p h264 3051 kb/s, 29.97 fps >to svta1 at -qp 30
You have to add "-row-mt" for multithreading. Also set "-cpu-used" to ~4.
2 years ago
Anonymous
It'll remain an obscure codec until the multi-threading aspect of SVT-AV1 can be ported to AOM AV1 and judging by how piss poor VP9 multi-threading is, it's going to be a while.
There's not a lot of encoding options in ffmpeg yet for libsvtav1.
You could find a patched version if your impatient.
$ ffmpeg -h encoder=libsvtav1
Encoder libsvtav1 [SVT-AV1(Scalable Video Technology for AV1) encoder]:
General capabilities: delay threads
Threading capabilities: other
Supported pixel formats: yuv420p yuv420p10le
libsvtav1 AVOptions:
-hielevel <int> E..V....... Hierarchical prediction levels setting (from 3 to 4) (default 4level)
3level 3 E..V.......
4level 4 E..V.......
-la_depth <int> E..V....... Look ahead distance [0, 120] (from -1 to 120) (default -1)
-preset <int> E..V....... Encoding preset [0, 8] (from 0 to 13) (default 13)
-tier <int> E..V....... Set operating point tier (from 0 to 1) (default main)
main 0 E..V.......
high 1 E..V.......
-rc <int> E..V....... Bit rate control mode (from 0 to 2) (default cqp)
cqp 0 E..V....... Constant quantizer
vbr 1 E..V....... Variable Bit Rate, use a target bitrate for the entire stream
cvbr 2 E..V....... Constrained Variable Bit Rate, use a target bitrate for each GOP
-qp <int> E..V....... Quantizer to use with cqp rate control mode (from 0 to 63) (default 50)
-sc_detection <boolean> E..V....... Scene change detection (default false)
-tile_columns <int> E..V....... Log2 of number of tile columns to use (from 0 to 4) (default 0)
-tile_rows <int> E..V....... Log2 of number of tile rows to use (from 0 to 6) (default 0)
-rc 0 is the default, so you just need to apply a -qp factor. If you want to specify a bitrate, you'd need to apply -rc 1 or -rc 2. >and that's about all the characters you can use in a IQfy comment
That makes things significantly worse, ffmpeg devs sure like taking their sweet sweet time with things.
2 years ago
Anonymous
You could use the encoding commands that are part of the svt-av1 package.
But you can only work on y4m and yuv files as input. >/usr/bin/SvtAv1EncApp
No shortage of options tho. >SvtAv1EncApp --help
I saw on their wiki you can pipe from ffmpeg to SvtAv1EncApp as well.
2 years ago
Anonymous
>-row-mt
no such thing >-cpu-used 4
unacceptable quality drop over 0
2 years ago
Anonymous
>no such thing
https://trac.ffmpeg.org/wiki/Encode/VP9#rowmt
people have also said to try -tile-columns 1 but i haven't played with that much. seems like more tiles lowers quality so 1 or 0 might be good. don't know the cost of quality vs encoding speed.
https://developers.google.com/media/vp9/settings/vod
2 years ago
Anonymous
There's not a lot of encoding options in ffmpeg yet for libsvtav1.
You could find a patched version if your impatient.
$ ffmpeg -h encoder=libsvtav1
Encoder libsvtav1 [SVT-AV1(Scalable Video Technology for AV1) encoder]:
General capabilities: delay threads
Threading capabilities: other
Supported pixel formats: yuv420p yuv420p10le
libsvtav1 AVOptions:
-hielevel <int> E..V....... Hierarchical prediction levels setting (from 3 to 4) (default 4level)
3level 3 E..V.......
4level 4 E..V.......
-la_depth <int> E..V....... Look ahead distance [0, 120] (from -1 to 120) (default -1)
-preset <int> E..V....... Encoding preset [0, 8] (from 0 to 13) (default 13)
-tier <int> E..V....... Set operating point tier (from 0 to 1) (default main)
main 0 E..V.......
high 1 E..V.......
-rc <int> E..V....... Bit rate control mode (from 0 to 2) (default cqp)
cqp 0 E..V....... Constant quantizer
vbr 1 E..V....... Variable Bit Rate, use a target bitrate for the entire stream
cvbr 2 E..V....... Constrained Variable Bit Rate, use a target bitrate for each GOP
-qp <int> E..V....... Quantizer to use with cqp rate control mode (from 0 to 63) (default 50)
-sc_detection <boolean> E..V....... Scene change detection (default false)
-tile_columns <int> E..V....... Log2 of number of tile columns to use (from 0 to 4) (default 0)
-tile_rows <int> E..V....... Log2 of number of tile rows to use (from 0 to 6) (default 0)
-rc 0 is the default, so you just need to apply a -qp factor. If you want to specify a bitrate, you'd need to apply -rc 1 or -rc 2. >and that's about all the characters you can use in a IQfy comment
2 years ago
Anonymous
Use the latest git, not release. It allows you to set everything with -svtav1-params. Multi pass is not supported, though. But I had better results with surgical crf, so maybe it isn't a big loss.
It'll remain an obscure codec until the multi-threading aspect of SVT-AV1 can be ported to AOM AV1 and judging by how piss poor VP9 multi-threading is, it's going to be a while.
[...]
That makes things significantly worse, ffmpeg devs sure like taking their sweet sweet time with things.
>It'll remain an obscure codec until the multi-threading aspect of SVT-AV1 can be ported to AOM AV1
Why? AOMedia considers SVT-AV1 their production-ready encoder.
https://aomedia.org/press%20releases/aomedia-software-implementation-working-group-to-bring-av1-to-more-video-platforms/
I don't know how many web browsers support svtav1 so far.
Plays on the latest firefox fine.
Encoder doesn't matter. They all produce streams compatible with av1 spec.
2 years ago
Anonymous
(Checked)
Good enough for youtube, good enough for me.
2 years ago
Anonymous
>lower quality than AV1 AOM
Still better than VP9.
No it isn't you fricking donkey. You only get a few FPS with preset 4 just to match compression efficiency of the quality preset of SVT-VP9. To get the additional 10-20% you need to drop down to preset 0 which encodes at LESS than 1 FPS.
2 years ago
Anonymous
>SVT-VP9
Can you run this thing with ffmpeg? Most people are going to use libvpx, which is quite horrible.
Encode time doesn't matter
If someone wants to take the time to produce the better encode, IQfy should allow it
Then again I don't think support for av1 stream in webm container is finalized yet
Because as much as everyone hates the borg there's a far more insidious and utterly evil entity: mpeg la. They've been known to go after individual users for uploading H264/HEVC content on the internet without paying ~~*royalty*~~ fees. VP9 is open sores, royalty free, and encodes 10X faster compared to AV1.
my ssr profile for libsvtav1 screencapture.
The libvpx-vp9 profile has speed=16 so I don't have to wait 30 seconds for my screencapture to finish encoding before I watch it.
libsvtav1 is waaaaaaaaaay faster.
vp9 is slower than vp8 but offers better compression at equal quality. >ffmpeg 5.0.1 doesn't give you a lot of libsvtav1 encoding options.
>How long until we reach the limits of video compression?
Define limits?
You can transmit 80TB of video data with like 200MB of information, losslessly, it all depends on CPU resources and video complexity.
For example if I wanted a video at 16K resolution of a rainbow shifting starburst style dot moving around on the screen that can be extremely compressed but remain lossless. We're pretty close to the limit for lossy general purpose video encoding though and any more... isn't worth it. Literally.
It's more economical and efficient to use codecs that do 95% compression for 80% quality than codecs doing 97% for 75% quality with 5x the CPU decoding requiement.
I saw a vp9-vaapi option for encoding when I ran
ffmpeg -codecs | grep vp9
Did a little web search and it seems ffmpeg can create a /dev/ entry you can then use on the ffmpeg cli.
Just kinda skimmed over it, tho.
Not sure, but I think vaapi is an AMD thing.
ffmpeg spits out the encoding speed btw.
libvpx-vp9 is around 0.2 something on my machine. >transcoding 1080p h264 3051 kb/s, 29.97 fps >to svta1 at -qp 30
To add onto this post, speed is relative to realtime.
1.2x means if you're watching the video on 1x speed it'll keep encoding ahead of wher you're watching,
less than 1x and watching will get to buffering where it's not encoded yet.
>hating VP9 >when the only alternative is moronic proprietary format with awful licensing and royalties
Why are people doing this apart from paid shilling?
>the encoding time is astronomical
Have you tried SVT-AV1? It's plenty fast.
And yes, VP9 is now supported save for single GOP encodes which are apparently rejected by embed detection.
2 years ago
Anonymous
I will try it.
Yes, I just noticed VP9 is now supported here, great news!
>Or maybe a GPU accelerated encode is out now?
Only in software for Teams Green and Red afaik. Blue has hardware AV1 media encoders in their dGPUs
Well, let's hope SVT-AV1 is faster then.
My CPU is quite old...
2 years ago
Anonymous
SVT is flexible, and it can still be much slower than VP9 in the worst case. Anything below preset 2 seems like a waste of time, and you might as well use libaom for minmax masturbation.
I literally just modified the WebM header duration value, and I assume that's what you are doing too. Not sure how you have cursed it to not work.
2 years ago
Anonymous
it's probably is doing some check on the video stream that I can't figure out.
if you look at your webm with mkvinfo you will see it is much more complex.
Filenames describe the settings used for encoding. All are with -lossless 1, and some frames are duplicated to bypass a check, so size is inflated. This one here is just regular yuv420p with nothing fancy.
Realtime on non recording or streaming is utter moronic and hurts both quality and encoding time
Encoding vp9 takes so fricking long
damn, anyway to improve? already using row-mt 1
Go for slicing since you already have row-mt 1
doesnt that reduce video quality?
Yes, use 4 if anything
Why cant we upload mp4's? if they allow them with an HEVC the file size would be half and look twice as good and why cant we have sound on every board?
Only free codec contained by mp4 is AV1 and is not yet available
At any case mkv should be allowed
>Have a computer that isn't complete shit? I could encode vp9 in the 8ch days real quick even on an i5 3570k.
What are your speeds and cpu?
post your ffmpeg
No, I don't think I will. I haven't bothered encoding weebums in a long time because this shithole has a pitiful file size limit and no sounds outside two otherwise completely irrelevant board, so I haven't had a need to.
2 years ago
Anonymous
2 years ago
Anonymous
I've gone through two processor upgrades and one replacement since then. Even then, I was getting encode times in minutes for minutes-long videos. The only thing faster was NVENC h.264 encodes. Just stop complaining about things being "inefficient" because your hardware is insufficient.
2 years ago
Anonymous
Do you know about 8ch dot moe and the "webring" of ex-8ch boards like zzzchan.xyz?
2 years ago
Anonymous
Of course I do. I used them enough to know 2 things:
1: They fricking suck and are dead as shit, full of people who stuck with the site post-sunshine aka 99% /misc/ crossboarders; the biggest benefits being fewer redditjaks
2: I know better than to name living altchans on this site. They aren't nerdfiltered like butthurt hiro did for 8ch, but its' better not to give even the slightest idea to the homosexuals that infest this site to shit up other places.
8ch is a corpse and I couldn't give less of a frick about jimbo watkins' Q grift 8kunt, so I don't mind mentioning them specifically. Webring has a bad problem of being infested with bottom feeder drama as well.
Why cant we upload mp4's? if they allow them with an HEVC the file size would be half and look twice as good and why cant we have sound on every board?
it's an imageboard not an a video board so we don't need sound. mp4's are not allowed because you need to pay royalties to mpegla if you want to use avc or hevc video codecs.. other chan sites might use them because they're too small for mpegla to care, but 4chins is pretty big
everything webm is developed by google
webm and webp is gayets
It would be nice if computers only had exactly one video and image format. Like for better or for worse, this is what you get. Everything would just work.
That would be very inefficient in terms of data size, energy consumption and CPU time.
internet is meant for white man and white man only, no need to support street shitters, we could live in properity, instead we choose to let them poison our minds
dilate
>webm
>one video format
>meanwhile
>vp8
>vp9
>vp10
>vp11
>vp12
>vp13
>vp14
>vp15
>etc.
VP9 was released NINE YEARS AGO
VP10 isn't happening, google went all in on AV1 instead.
IIRC AV1 is largely based on Xiph's DAALA.
Wikipedia (I know, I know) says it's both:
>However, Google decided to incorporate VP10 into AOMedia Video 1 (AV1). The AV1 codec was developed based on a combination of technologies from VP10, Daala (Xiph/Mozilla) and Thor (Cisco).[106][107][108] Accordingly, Google has stated that they will not deploy VP10 internally nor officially release it, making VP9 the last of the VPx-based codecs to be released by Google.
>It would be nice if computers only had exactly one video [...] format. Like for better or for worse, this is what you get.
I don't think you'd say that if you were familiar with the shit codecs we started out with.
>image format
This is basically already the case, with jpg, which is ubiquitous. Of course png also exists and svg also exist, but for good reasons; jpg is specifically optimized for photography, not vector graphics.
>It would be nice if computers only had exactly one video and image format
BMP.
also we should make MJPEG alternative but with BMPs, mjpeg is just jpeg files in zip
>mjpeg is just jpeg files in zip
>in zip
I don't think that part is true. I don't think the container for motion jpegs is specified anywhere. From what I understand, there is no standard for how to store an mjpeg stream but AVI is commonly used.
>also we should make MJPEG alternative but with BMPs
Uncompressed .AVI with PCM .WAV audio.
No, at least give me a lossy, lossless and uncompressed format for each.
The WebM container itself is a subset of Matroska though. And Google has nothing to do with Vorbis or Opus so that's far from ~~*everything*~~ in my book.
would be nice if we could just use x265
No h265 decoding support in browsers. I would love to have h264 though.
h264 is obsolete, and AV1 is at least as good as h265. No reason for either.
264/265
gpu encoding
GPU encoding tends to be inefficient. You use it as an intermediate format and compress down to 3MB for IQfy.
Also, Intel stuff can encode VP9 anyway.
>>GPU encoding tends to be inefficient.
By space? Yes. By power and performance? No.
>intel
so that's how they're forcing you upgrade from threadripper?
googlan:
>Intel Quick Sync, Kaby Lake and later
>reddit: This setup with that command encodes at ~126 fps. This compares to about 10 fps using libvpx-vp9 encoder!
>obsolete
It's still a very good, fast codec with ubiquitous support.
webm is alright
webp on the other hand needs to fricking die, or at least be supported by photoshop and the likes.
It's open so I have no issue with it. If Google let their engineers work on something worthwhile for once then why not use it? You're like a mathematican saying that you won't accept some guy's proof and won't use his super innovative formula, because he used a calculator
Linux is made by google
Should have added AV1 while they were at it
AV1 only offers around 10-20% better compression efficiency compared to 10-bit VP9/HEVC while at the same time takes 10X longer to encode. If efficiency jumps to 30-40% then the sub-1 FPS encode times will be worth it.
>what is svt-av1
What part of
>AV1 only offers around 10-20% better compression efficiency compared to 10-bit VP9/HEVC while at the same time takes 10X longer to encode.
did you not understand?
You stupid fricking Black person. svt-av1 is faster than libvpx-vp9 while offering superior compression.
have a nice day
>svt-av1 is faster than libvpx-vp9
Prove it.
>SVT
lower quality than AV1 AOM, you know the encoder required to achieve 10-20% better compression efficiency than 10-bit VP9?
what does that even mean
AV1 still remains a BETA codec for personal use.
Yeah, but SVT-AV1 looks very promising. And it's plenty usable already, much more than libvpx at least.
AV1 is still only suitable for giant tech companies like youtube not for consumers. Only a small portion of the population know that handbrake exists (no AV1 option yet, SVT-AV1 unlikely). Even less know how to use ffmpeg.
That depends on your definition of suitability. The support isn't quite there yet, but its performance profile is good enough for encoding in home environment.
You have to add "-row-mt" for multithreading. Also set "-cpu-used" to ~4.
It'll remain an obscure codec until the multi-threading aspect of SVT-AV1 can be ported to AOM AV1 and judging by how piss poor VP9 multi-threading is, it's going to be a while.
That makes things significantly worse, ffmpeg devs sure like taking their sweet sweet time with things.
You could use the encoding commands that are part of the svt-av1 package.
But you can only work on y4m and yuv files as input.
>/usr/bin/SvtAv1EncApp
No shortage of options tho.
>SvtAv1EncApp --help
I saw on their wiki you can pipe from ffmpeg to SvtAv1EncApp as well.
>-row-mt
no such thing
>-cpu-used 4
unacceptable quality drop over 0
>no such thing
https://trac.ffmpeg.org/wiki/Encode/VP9#rowmt
people have also said to try -tile-columns 1 but i haven't played with that much. seems like more tiles lowers quality so 1 or 0 might be good. don't know the cost of quality vs encoding speed.
https://developers.google.com/media/vp9/settings/vod
There's not a lot of encoding options in ffmpeg yet for libsvtav1.
You could find a patched version if your impatient.
$ ffmpeg -h encoder=libsvtav1
Encoder libsvtav1 [SVT-AV1(Scalable Video Technology for AV1) encoder]:
General capabilities: delay threads
Threading capabilities: other
Supported pixel formats: yuv420p yuv420p10le
libsvtav1 AVOptions:
-hielevel <int> E..V....... Hierarchical prediction levels setting (from 3 to 4) (default 4level)
3level 3 E..V.......
4level 4 E..V.......
-la_depth <int> E..V....... Look ahead distance [0, 120] (from -1 to 120) (default -1)
-preset <int> E..V....... Encoding preset [0, 8] (from 0 to 13) (default 13)
-tier <int> E..V....... Set operating point tier (from 0 to 1) (default main)
main 0 E..V.......
high 1 E..V.......
-rc <int> E..V....... Bit rate control mode (from 0 to 2) (default cqp)
cqp 0 E..V....... Constant quantizer
vbr 1 E..V....... Variable Bit Rate, use a target bitrate for the entire stream
cvbr 2 E..V....... Constrained Variable Bit Rate, use a target bitrate for each GOP
-qp <int> E..V....... Quantizer to use with cqp rate control mode (from 0 to 63) (default 50)
-sc_detection <boolean> E..V....... Scene change detection (default false)
-tile_columns <int> E..V....... Log2 of number of tile columns to use (from 0 to 4) (default 0)
-tile_rows <int> E..V....... Log2 of number of tile rows to use (from 0 to 6) (default 0)
-rc 0 is the default, so you just need to apply a -qp factor. If you want to specify a bitrate, you'd need to apply -rc 1 or -rc 2.
>and that's about all the characters you can use in a IQfy comment
Use the latest git, not release. It allows you to set everything with -svtav1-params. Multi pass is not supported, though. But I had better results with surgical crf, so maybe it isn't a big loss.
>It'll remain an obscure codec until the multi-threading aspect of SVT-AV1 can be ported to AOM AV1
Why? AOMedia considers SVT-AV1 their production-ready encoder.
https://aomedia.org/press%20releases/aomedia-software-implementation-working-group-to-bring-av1-to-more-video-platforms/
Encoder doesn't matter. They all produce streams compatible with av1 spec.
(Checked)
Good enough for youtube, good enough for me.
>lower quality than AV1 AOM
Still better than VP9.
>>what is svt-av1
Shit nobody ever heard of
SVT-AV1 is much better than VP9 *and* faster.
It also has documentation that isn't dogshit.
No thanks cabalBlack person/madshit shill
Both codecs are googleshit, but AV1 isn't exclusively googleshit and it shows.
You will never be Japanese, 10 bit is a shit meme and your cabal is dead.
Not quite
No it isn't you fricking donkey. You only get a few FPS with preset 4 just to match compression efficiency of the quality preset of SVT-VP9. To get the additional 10-20% you need to drop down to preset 0 which encodes at LESS than 1 FPS.
>SVT-VP9
Can you run this thing with ffmpeg? Most people are going to use libvpx, which is quite horrible.
moron
Why not push the SVT-VP9 patch to ffmpeg instead? As we currently gotten vp9 support, not AV1.
Has anyone even tested how good it is? The development was halted 2 years ago, it only works in 8bit and has no crf support.
Encode time doesn't matter
If someone wants to take the time to produce the better encode, IQfy should allow it
Then again I don't think support for av1 stream in webm container is finalized yet
>VP9
>patented
no, thanks
Because as much as everyone hates the borg there's a far more insidious and utterly evil entity: mpeg la. They've been known to go after individual users for uploading H264/HEVC content on the internet without paying ~~*royalty*~~ fees. VP9 is open sores, royalty free, and encodes 10X faster compared to AV1.
>Why are you all so excited about VP9?
It was released almost a decade ago.
It doesn't matter who made it; the codecs are open source and freely available. You can use them without google getting a single cent from you.
2 minutes of 1920x1080
>speed 10
holy frick, you might as well just fall back on VP8. Probably get better quality too.
Quality seems not bad if you view it full screen.
>I showed you mine. Show me yours.
>you might as well just fall back on VP8. Probably get better quality too.
Foolish. Try it and see how well it works.
>most of the image is completely static
heh. I can already see that vp9 will be used as an excuse for forego proper cropping and editing.
ssr lets you select a window or draw a rectangle with you're mouse [first screen of options in the vid].
>ssr
Looks nice, thanks for the suggestion.
my ssr profile for libsvtav1 screencapture.
The libvpx-vp9 profile has speed=16 so I don't have to wait 30 seconds for my screencapture to finish encoding before I watch it.
libsvtav1 is waaaaaaaaaay faster.
vp9 is slower than vp8 but offers better compression at equal quality.
>ffmpeg 5.0.1 doesn't give you a lot of libsvtav1 encoding options.
How long until we reach the limits of video compression? How much better than AV1 can we get?
It has to jump around patents as ancient as h264, so I guess plenty.
>How long until we reach the limits of video compression?
Define limits?
You can transmit 80TB of video data with like 200MB of information, losslessly, it all depends on CPU resources and video complexity.
For example if I wanted a video at 16K resolution of a rainbow shifting starburst style dot moving around on the screen that can be extremely compressed but remain lossless. We're pretty close to the limit for lossy general purpose video encoding though and any more... isn't worth it. Literally.
It's more economical and efficient to use codecs that do 95% compression for 80% quality than codecs doing 97% for 75% quality with 5x the CPU decoding requiement.
I saw a vp9-vaapi option for encoding when I ran
ffmpeg -codecs | grep vp9
Did a little web search and it seems ffmpeg can create a /dev/ entry you can then use on the ffmpeg cli.
Just kinda skimmed over it, tho.
Not sure, but I think vaapi is an AMD thing.
ffmpeg spits out the encoding speed btw.
libvpx-vp9 is around 0.2 something on my machine.
>transcoding 1080p h264 3051 kb/s, 29.97 fps
>to svta1 at -qp 30
To add onto this post, speed is relative to realtime.
1.2x means if you're watching the video on 1x speed it'll keep encoding ahead of wher you're watching,
less than 1x and watching will get to buffering where it's not encoded yet.
I don't know how many web browsers support svtav1 so far.
Plays on the latest firefox fine.
libsvtav1 is the cat's pajama's.
she makes me compressed carbon
I don't want to see her get old 🙁
It saddened me to see pics of her wearing the cellulite concealing hosiery on stage in recent /b/cel threads.
A new way to waste bandwidth.
>hating VP9
>when the only alternative is moronic proprietary format with awful licensing and royalties
Why are people doing this apart from paid shilling?
The alternative is AV1, and it's better in every way.
AV1 is not an alternative but successor. Hating VP9 because of AV1 is like hating h264 because h265 exists.
Yeah it'll just be another 9 years before 4chins lets us upload AV1 webms.
I absolutely love AV1 quality, but the encoding time is astronomical.
Or maybe a GPU accelerated encode is out now?
I don't think so.
>the encoding time is astronomical
Have you tried SVT-AV1? It's plenty fast.
And yes, VP9 is now supported save for single GOP encodes which are apparently rejected by embed detection.
I will try it.
Yes, I just noticed VP9 is now supported here, great news!
Well, let's hope SVT-AV1 is faster then.
My CPU is quite old...
SVT is flexible, and it can still be much slower than VP9 in the worst case. Anything below preset 2 seems like a waste of time, and you might as well use libaom for minmax masturbation.
>Or maybe a GPU accelerated encode is out now?
Only in software for Teams Green and Red afaik. Blue has hardware AV1 media encoders in their dGPUs
so 4chins now support vp9?
When will subtitles stream be supported?
never because google dropped it for av1
Good morning sir!
I think it's a little early for morning, anyway about the time limit. What do you know about it?
Works on my machine 🙂
why doesn't this one work?
this one seems to break skipping somehow
but mine does not
what do you know about this?
I literally just modified the WebM header duration value, and I assume that's what you are doing too. Not sure how you have cursed it to not work.
it's probably is doing some check on the video stream that I can't figure out.
if you look at your webm with mkvinfo you will see it is much more complex.
Test
Last one.
Filenames describe the settings used for encoding. All are with -lossless 1, and some frames are duplicated to bypass a check, so size is inflated. This one here is just regular yuv420p with nothing fancy.
This is the only one that works for me (Firefox on Android).
Source PNG. Should be identical to the RGB encoding.
I may have done some of them a disservice. Here's the 10-bit one without using zscale, and the colors are more accurate.
Looks like that filter is not reliable.
It's the other way around for me until I disable acceleration. Is Chrome fricked?
for me as well
displays like the png
has darker darks / brighter brights
firefox wayland w/ + w/o AMD HW accel
Where did they announce that VP9's now supported? Or did someone just discover it was and the news spread?
Think the guy who made is still alive and lurking?
why dont we ask him?
HEY ANON, ARE YOU STILL THERE?!
Someone reposted it in better quality, but it's loosing it's charm.
>loosing
Come on, the gif emulation was way better on the original.
he was just being pedantic about your spelling
Oh, that.
Yes, sorry.
What? It's loosing up alright, like how a vegana looses up and becomes worthless.
Lost
Which is has the better encoder nvidia, AMD or Intel?
How do you use them in ffmpeg anyway?
I lack one so I never learned but it's possible. Read the manual.
>you all
Encoding vp9 takes so fricking long
damn, anyway to improve? already using row-mt 1
-deadline realtime -cpu-used 5
doesnt that reduce video quality?
I just tested it, and that's a big YES
You either get speed or quality, no in-between.
Realtime on non recording or streaming is utter moronic and hurts both quality and encoding time
Go for slicing since you already have row-mt 1
Yes, use 4 if anything
Only free codec contained by mp4 is AV1 and is not yet available
At any case mkv should be allowed
Who cares? Whining about the creators of something free and oben sores is a waste of time.
Have a computer that isn't complete shit? I could encode vp9 in the 8ch days real quick even on an i5 3570k.
>Have a computer that isn't complete shit? I could encode vp9 in the 8ch days real quick even on an i5 3570k.
What are your speeds and cpu?
post your ffmpeg
No, I don't think I will. I haven't bothered encoding weebums in a long time because this shithole has a pitiful file size limit and no sounds outside two otherwise completely irrelevant board, so I haven't had a need to.
I've gone through two processor upgrades and one replacement since then. Even then, I was getting encode times in minutes for minutes-long videos. The only thing faster was NVENC h.264 encodes. Just stop complaining about things being "inefficient" because your hardware is insufficient.
Do you know about 8ch dot moe and the "webring" of ex-8ch boards like zzzchan.xyz?
Of course I do. I used them enough to know 2 things:
1: They fricking suck and are dead as shit, full of people who stuck with the site post-sunshine aka 99% /misc/ crossboarders; the biggest benefits being fewer redditjaks
2: I know better than to name living altchans on this site. They aren't nerdfiltered like butthurt hiro did for 8ch, but its' better not to give even the slightest idea to the homosexuals that infest this site to shit up other places.
8ch is a corpse and I couldn't give less of a frick about jimbo watkins' Q grift 8kunt, so I don't mind mentioning them specifically. Webring has a bad problem of being infested with bottom feeder drama as well.
testt
its so much better than VP8
>be brain dead
>use cloud convert to make webms quickly
>45 second videos on the lowest setting are only using 2.2 MB.
And im sure you could get better quality and more length if you played around with it more.
Why cant we upload mp4's? if they allow them with an HEVC the file size would be half and look twice as good and why cant we have sound on every board?
it's an imageboard not an a video board so we don't need sound. mp4's are not allowed because you need to pay royalties to mpegla if you want to use avc or hevc video codecs.. other chan sites might use them because they're too small for mpegla to care, but 4chins is pretty big
HEVC doesn't have decoding support in browsers man. VP9 is comparable anyway.
Not having AV1 and sound hurts however.
How come HEVC never received support when AVC did? Aren't they both patented up the ass?