ChanServ changed the topic of #ffmpeg to: Welcome to the FFmpeg USER support channel | Development channel: #ffmpeg-devel | Bug reports: https://ffmpeg.org/bugreports.html | Wiki: https://trac.ffmpeg.org/ | This channel is publically logged | FFmpeg 7.1.1 is released
chandash has quit [Ping timeout: 252 seconds]
Muimi has joined #ffmpeg
finsternis has quit [Read error: Connection reset by peer]
tokyovigilante has quit [Remote host closed the connection]
iive has quit [Quit: They came for me...]
tokyovigilante has joined #ffmpeg
_whitelogger has joined #ffmpeg
sam113101 has quit [Ping timeout: 252 seconds]
dxh_ has quit [Ping timeout: 276 seconds]
dxh_ has joined #ffmpeg
dxh_ has quit [Ping timeout: 248 seconds]
dxh_ has joined #ffmpeg
chandash has quit [Quit: WeeChat 4.4.2]
dxh_ has quit [Read error: Connection reset by peer]
dxh_ has joined #ffmpeg
linuxuser1 has joined #ffmpeg
<linuxuser1>
hi
<linuxuser1>
i am wondering about the dependency of FFMEG on libvdpau in the Linux Ecosystem. libvdpau is a library for NVidia GPU cards. Is FFMEG is run on an system where there is no NVIDIA GPUs then is this library still required
<linuxuser1>
libvdpau is the Nvidia VDPAU library
<linkmauve>
linuxuser1, you can build ffmpeg without vdpau support with ./configure --disable-vdpau, but if it’s been built with it then you have to have the .so availabled in order for ffmpeg to run.
beastd has quit [Ping timeout: 260 seconds]
<linuxuser1>
how can it be checked whether ffmpeg is compiled with vdpau support?
<linuxuser1>
I was under the impression that ffmeg is coded in such a way that there will be a interface or abstraction layer which will determine which library to pickup at run time, based on the HW detected. So for example if AMD Radeon is present the interface or abstraction layer will pick that up. and not Intel or NVidia libraries.
<linuxuser1>
I am not saying that FFMEG is built wrong. Or the developers of FFMEG should have developed in some way. I do not mean to disparage any of the FFMEG team
<linkmauve>
Try using it, and if it doesn’t work then either your driver doesn’t provide it, or it hasn’t been built with vdpau support.
<linuxuser1>
Or belittle their contribution.
<linkmauve>
But in general, you don’t have to care about it, if it’s built in and your system doesn’t support it, you just won’t use it and that’s perfectly fine.
<linkmauve>
You can use other hwaccels, such as vaapi.
<linuxuser1>
Will FFMEG crash if libvdpau is not there? Especially if it has been built/compiled with vdpau support ?
<linkmauve>
It won’t crash, it will just return an error.
dxh_ has quit [Read error: Connection reset by peer]
dxh_ has joined #ffmpeg
beastd has joined #ffmpeg
tokyovigilante has quit [Read error: Connection reset by peer]
tokyovigilante has joined #ffmpeg
maxim_d33 has quit [Ping timeout: 276 seconds]
maxim_d33 has joined #ffmpeg
Fiji has quit [Ping timeout: 248 seconds]
Muimi has quit [Quit: Going offline, see ya! (www.adiirc.com)]
System_Error has quit [Remote host closed the connection]
chiselfuse has quit [Remote host closed the connection]
chiselfuse has joined #ffmpeg
Vonter has joined #ffmpeg
Vonter has quit [Ping timeout: 268 seconds]
Vonter has joined #ffmpeg
Quackdoc has joined #ffmpeg
linuxuser1 has quit [Quit: Client closed]
System_Error has joined #ffmpeg
chair1 has joined #ffmpeg
cantelope has quit [Quit: Connection closed for inactivity]
dxh_ has quit [Remote host closed the connection]
System_Error has quit [Remote host closed the connection]
vincejv has quit [Quit: Bye bye! Leaving for now...]
lavaball has joined #ffmpeg
Quackdoc has quit [Ping timeout: 272 seconds]
phantomics_ has quit [Ping timeout: 276 seconds]
phantomics has joined #ffmpeg
Ingvix has quit [Ping timeout: 252 seconds]
lusciouslover has quit [Remote host closed the connection]
lusciouslover has joined #ffmpeg
vincejv has joined #ffmpeg
foonix has quit [Quit: leaving]
foonix has joined #ffmpeg
emmanuelux has quit [Quit: Leaving]
acryo has quit [Ping timeout: 252 seconds]
grib has quit [Ping timeout: 248 seconds]
alexherbo2 has joined #ffmpeg
afck has quit [Quit: afck]
Blacker47 has joined #ffmpeg
rsx has joined #ffmpeg
user_oreloznog has joined #ffmpeg
acryo has joined #ffmpeg
acryo has joined #ffmpeg
acryo has quit [Changing host]
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #ffmpeg
SuicideShow has quit [Ping timeout: 252 seconds]
alexherbo2 has quit [Remote host closed the connection]
SuicideShow has joined #ffmpeg
kingdomofheaven has quit [Read error: Connection reset by peer]
kingdomofheaven has joined #ffmpeg
Sketch has quit [Remote host closed the connection]
Sketch has joined #ffmpeg
vincejv has quit [Quit: Bye bye! Leaving for now...]
Shine_ has joined #ffmpeg
vincejv has joined #ffmpeg
rsx has quit [Quit: rsx]
grib has joined #ffmpeg
Ingvix has joined #ffmpeg
j45 has quit [Ping timeout: 248 seconds]
Offspring has quit [Read error: Connection reset by peer]
sentriz has joined #ffmpeg
j45 has joined #ffmpeg
j45 has quit [Changing host]
j45 has joined #ffmpeg
Offspring has joined #ffmpeg
averne has quit [Ping timeout: 245 seconds]
<BtbN>
libvdpau _is_ the abstraction layer
<BtbN>
it's just that by now, nvidia is the only thing left it abstracts
<BtbN>
A bunch of mesa drivers used to implement vdpau interfaces as well
<JEEB>
yea
<CounterPillow>
any fellow FFMEG users
<linkmauve>
There is still the gallium-vdpau option in Mesa, so it might still be implemented in some drivers.
<Bombo>
i made screenshots: upper: the command i used+verbose output lower: screenshot of resulting mkv video. why is this scrambled? https://imgur.com/a/JjVaIbh
user_oreloznog has quit [Ping timeout: 272 seconds]
averne has joined #ffmpeg
luser9 has joined #ffmpeg
travisghansen13 has joined #ffmpeg
travisghansen1 has quit [Read error: Connection reset by peer]
travisghansen13 is now known as travisghansen1
ParkerR has joined #ffmpeg
HarshK23 has quit [Quit: Connection closed for inactivity]
Richardcavell_ has quit [Ping timeout: 268 seconds]
lolok has joined #ffmpeg
f0x_30336912710 has quit [Quit: Bye !]
vincejv has joined #ffmpeg
YUiNA_ has joined #ffmpeg
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
YUiNA has quit [Ping timeout: 268 seconds]
YUiNA has joined #ffmpeg
YUiNA_ has quit [Ping timeout: 268 seconds]
fling has joined #ffmpeg
jmcantrell has joined #ffmpeg
minimal has joined #ffmpeg
jmcantrell has quit [Ping timeout: 276 seconds]
Richardcavell_ has joined #ffmpeg
MisterMinister has quit [Ping timeout: 276 seconds]
sam113101 has joined #ffmpeg
usagi_mimi has joined #ffmpeg
tranzistor has joined #ffmpeg
darkmushroom has joined #ffmpeg
<darkmushroom>
Oh man. Didn't expect to see so many people hanging out in the ffmpeg IRC. o/ greetings everybody
<BtbN>
looks like something disagrees about linesizes to me
<BtbN>
i.e. ffmpeg is reading that image with a too small linesize
lavaball has quit [Remote host closed the connection]
hpkn has quit [Remote host closed the connection]
hpkn has joined #ffmpeg
<darkmushroom>
I might as well ask. I'm trying to get ffmpeg to feed a webRTC server. The docs say it supports whip, but when I start the stream it tells me "Requested output format 'whip' is not known" Compiled from source, same error message. Is there some other library I need?
<JEEB>
I think whomever developed that module decided to make it require openssl
<JEEB>
and I think it's properly now flagged as experimental
<JEEB>
check the configure output (ffbuild/config.log) regarding enabled etc modules
<BtbN>
Why does it do any crypto beyond simple tls? oO
<darkmushroom>
Appreciate you JEEB. I'll check it out
<JEEB>
BtbN: I think the dtls implementation pretty much just piggy-backs some openssl impl
<darkmushroom>
Hm. I found a line in config.log that says `whip_muxer=yes`, so that's promising.
<JEEB>
yea I think it has a separate protocol and separate muxer or something
<JEEB>
also do note that it is really unusual for something TLS-related to be specific to one backend
<JEEB>
since FFmpeg supports gnutls, windows schannel, macOS whatever it was called etc etc
<JEEB>
but this dtls implementation is apparently openssl specific
<JEEB>
(and broke building with older versions for a while due to bad checks)
<BtbN>
I could see something as finnicky as DTLS to be harder to abstract, but it's still a weird limitation
<darkmushroom>
It's fun to ponder, but I find I have openssl installed anyways so I, naively, don't assume that was a fail point.
<JEEB>
darkmushroom: I just want to highlight these unusual things in the impl :P so I actually hope it will work against whatever server you want to utilize it against
<darkmushroom>
Oh for sure, and I deffo appreciate it
<JEEB>
it just seems like it was merged without heavy scrutiny with regards to these things
<BtbN>
It for example means I simply won't ever have support for that stuff in my builds, since I won't switch from schannel to openssl
<BtbN>
that'd be stupid, security wise
<JEEB>
yea
<BtbN>
schannel has dtls support
<JEEB>
using OS TLS library that the OS vendor will update makes 100% sense and that's why the different backends exist
<darkmushroom>
./configure --list-muxers specifically lists whip (working from source now), so that's a positive sign.
<JEEB>
the list-blah options list just everything in the build system
<BtbN>
well, configure listing it does not mean it'll enable it
<JEEB>
not what is enabled
<JEEB>
ffbuild/config.log is the log location for build time configure checks, and `ffmpeg -muxers` `ffmpeg -protocols` are the runtime listings with cli
<darkmushroom>
actually running ./configure does not list whip. That makes sense. So whip is in the build system, but config isn't picking it up (I assume).
<JEEB>
required checks do not pass and thus it does not get enabled
<darkmushroom>
Yes. Alright let me crack open the build log again.
<BtbN>
enable it explicitly and configure should bail
<darkmushroom>
Nice call BtbN. Explicitly enabling it did cause config to kill over, with the helpful message. whip_muxer disabled because dependency is not satisfied: dtls_protocol
<BtbN>
it does look like dtls is abstracted
usagi_mimi has quit [Ping timeout: 248 seconds]
coldfeet has joined #ffmpeg
<darkmushroom>
manually enabled dtls protocol, and I get to eat crow. openssl is installed, but configure doesn't see the dependency as being satisfied. I wonder if it needs something from the openssl-devel libray?
<JEEB>
yes, dev(el) packages are required for actually building against those libraries
<JEEB>
since non-dev(el) packages only contain the runtime required bits
<darkmushroom>
Huh. my package manager informs me that openssl-devel is already installed too.
coldfeet has quit [Client Quit]
<JEEB>
then check ffbuild/config.log , that should then contain the checks
<JEEB>
I know it requires some 3.x version of openssl, I did not look into it more
tranzistor has quit [Quit: lahko noč]
cantelope has joined #ffmpeg
System_Error has quit [Ping timeout: 244 seconds]
Richardcavell_ has quit [Ping timeout: 260 seconds]
five618480339176 has quit [Remote host closed the connection]
five618480339176 has joined #ffmpeg
paulk has quit [Ping timeout: 268 seconds]
coldfeet has joined #ffmpeg
K900 has quit [Remote host closed the connection]
paulk has joined #ffmpeg
paulk has joined #ffmpeg
paulk has quit [Changing host]
K900 has joined #ffmpeg
System_Error has joined #ffmpeg
chair1 has joined #ffmpeg
coldfeet has quit [Quit: Lost terminal]
fling has quit [Remote host closed the connection]
fling has joined #ffmpeg
damian101_ has quit [Read error: Connection reset by peer]
<darkmushroom>
I'm still cracking away on this. It looks like my openssl headers are sitting in /usr/include/openssl. I wonder if there's a way I can tell ./configure directly where to find them?
<ePirat>
darkmushroom, what does the configure log say?