[Ffmpeg-devel-irc] ffmpeg.log.20180427

[burek]

[00:00:13 CEST] <GrayShade> This started, so you can report it to the developer
[00:00:30 CEST] <GrayShade> Though I'm not sure he keeps that many versions
[00:00:40 CEST] <Lite> Could it affect the issue with FFmpeg?
[00:01:36 CEST] <Lite> The problem is I can not tell when exactly it worked perfect and when exactly stopped
[00:01:50 CEST] <GrayShade> It shouldn't, but you can install it on the other computer to check
[00:02:11 CEST] <Lite> But yeah at that period of time I installed Charles. And it still is in system
[00:02:34 CEST] <Lite> LOL, nice joke, Gray
[00:03:44 CEST] <Lite> If it's not I can't see any more reasons why something wrong could happened with TLS
[00:04:18 CEST] <Lite> I remember I edited manually via Windows registry values of default TTL
[00:04:24 CEST] <GrayShade> Well, it wasn't a joke, actually
[00:04:40 CEST] <Lite> not sure if TTL and TLS connected somehow
[00:05:53 CEST] <Lite> OK, checking provided URLs will come back with results in ~5 mins
[00:07:24 CEST] <GrayShade> Assuming you didn't decrease it, I'd say it's fine, but if you change registry settings and install a TLS proxy, then ffmpeg stops working.. Yeah.
[00:08:06 CEST] <Lite> TLS proxy?
[00:08:30 CEST] <Lite> no no I changed only TTL :O
[00:10:04 CEST] <GrayShade> Charles
[00:11:42 CEST] <Lite> Well, rolled back last nightly version and tested http URL
[00:12:08 CEST] <Lite> Sir Gray, your theory confirming... HTTP is working
[00:12:47 CEST] <Lite> And....yep! HTTPS stucks
[00:13:08 CEST] <GrayShade> HTTPS would still need to fail to confirm it, and there are a couple of TLS versions, so it might work
[00:13:12 CEST] <GrayShade> Or yeah
[00:13:17 CEST] <Lite> Sir Gray, your theory about HTTP and HTTPS totally confirmed
[00:14:36 CEST] <Lite> But what's the difference in 3.4.2 over nightly build with this TLS (HTTPS)??!!
[00:14:45 CEST] <GrayShade> You could try to remove Charles, but the registry changes would remain
[00:14:49 CEST] <Lite> Why 3.4.2 working?
[00:14:56 CEST] <GrayShade> No idea, I'm not the one to ask
[00:15:03 CEST] <Lite> :D
[00:15:16 CEST] <JEEB> have you actually looked into the traffic to see any differences?
[00:15:21 CEST] <Lite> Ok, deleting Charles
[00:15:22 CEST] <JEEB> 3.4 is quite old by now
[00:15:28 CEST] <Lite> Will come back soon
[00:15:44 CEST] <JEEB> and there's been a lot of changes in various things since 3.4 branch was created
[00:16:08 CEST] <JEEB> a lot of good stuff but also possibly bugs. the only way to debug is to actually dump the network traffic and see WTF is going on
[00:16:32 CEST] <GrayShade> They'd need to add a certificate to decrypt the session and that might be hard with gnutls
[00:17:06 CEST] <JEEB> I'm not sure if libavformat's http by default validates the certificate
[00:17:08 CEST] <JEEB> let me check
[00:18:00 CEST] <GrayShade> And when you already have TLS errors, doing MITM sounds like the last thing you'd want :-D
[00:18:08 CEST] <Lite> >> They'd need to add a certificate to decrypt the session and that might be hard with gnutls - so that could be a decision to exclude users like me faces such issue from devs side in this case?
[00:18:10 CEST] <Lite> :D
[00:18:15 CEST] <Lite> souns nice
[00:18:20 CEST] <Lite> sounds*
[00:18:37 CEST] <GrayShade> "They" would be you
[00:19:03 CEST] <JEEB> {"tls_verify", "Verify the peer certificate",         offsetof(pstruct, options_field . verify),    AV_OPT_TYPE_INT, { .i64 = 0 }, 0, 1, .flags = TLS_OPTFL }, \
[00:19:10 CEST] <JEEB> ok, so the default is zero
[00:19:15 CEST] <JEEB> so MITM should work
[00:19:17 CEST] <JEEB> :P
[00:20:01 CEST] <GrayShade> Sounds like a fun project. I off to sleep, so maybe I'll find out in the morning
[00:20:12 CEST] <GrayShade> I'm*
[00:20:43 CEST] <JEEB> Lite: btw *how* recent is your "nightly"?
[00:20:50 CEST] <JEEB> what git hash?
[00:21:00 CEST] <JEEB> it's the gXXXX you get when you do ffmpeg -version
[00:21:29 CEST] <GrayShade> There was a screenshot above
[00:21:51 CEST] <Lite> https://ffmpeg.zeranoe.com/builds/win64/static/ffmpeg-20180426-8ea8be5-win64-static.zip this one
[00:22:42 CEST] <JEEB> ok, so if it uses the windows internal TLS thing
[00:22:45 CEST] <JEEB> called schannel
[00:22:53 CEST] <JEEB> then it should have all the improvements that was getting
[00:23:13 CEST] <GrayShade> The error seems to be from gnutls
[00:23:22 CEST] <JEEB> ok, so it uses gnutls on windows... interesting)
[00:23:26 CEST] <JEEB> there's no reason to do that
[00:23:31 CEST] <JEEB> windows has a TLS implementation out of the box
[00:23:38 CEST] <JEEB> and we implement that
[00:24:12 CEST] <JEEB> also it could be that the "zero is not EOF" change could still be giving fruit, just with gnutls now
[00:24:30 CEST] <GrayShade> schannel has its fair share of issues. There was a recent thing with tls 1.2 and worried 7 iirc
[00:24:44 CEST] <GrayShade> Windows 7 :-/
[00:25:35 CEST] <JEEB> you might have to enable newer ciphers in registry or something like that because for some reason MS disabled them by default. or we have to enable them explicitly in the schannel code
[00:25:46 CEST] <JEEB> anyways, news for me regarding the issues :P
[00:26:11 CEST] <JEEB> the TLS 1.2 stuff that is
[00:27:02 CEST] <GrayShade> Yeah, there were a lot of people having issues with GitHub in the community of a language I'm following. It seemed that the docs were a bit contradictory on whether the registry change is needed
[00:27:23 CEST] <GrayShade> Does ffmpeg support xp?
[00:28:11 CEST] <klaxa> not anymore
[00:28:32 CEST] <Lite> ok
[00:28:38 CEST] <Lite> deleted Charles...
[00:28:45 CEST] <GrayShade> That's a plus for schannel, I suppose
[00:28:53 CEST] <klaxa> >Dropped support for building for Windows XP. The minimum supported Windows version is Windows Vista.
[00:28:59 CEST] <Lite> will check it out in couple mins
[00:29:15 CEST] <JEEB> considering that XP lost support in april 2014
[00:29:25 CEST] <JEEB> if you are still using it outside of a VM
[00:29:37 CEST] <JEEB> or something else that is not on a network
[00:29:38 CEST] <klaxa> but they patched for wannacry :P
[00:30:29 CEST] <Lite> F*ck thats not affected... maybe needs reboot for more clearance
[00:30:40 CEST] <GrayShade> It must be on a network if you care about tls working :-D
[00:31:22 CEST] <JEEB> that's kind of what I was already pointing towards. those people are fscked
[00:31:31 CEST] <GrayShade> Well, what jeeb said. Use that wireshark to see what's up
[00:31:35 CEST] <Lite> A few days ago I reinstalled Fiddler
[00:32:30 CEST] <Lite> so it affected the issue it should be fixed. Since I also checked for deleting all of it's certs
[00:32:40 CEST] <Lite> if*
[00:33:02 CEST] <Lite> So the issue not affected by Fiddler definately
[00:33:55 CEST] <Lite> because Fiddler installed at System a long time ago and FFmpeg nightly worked perfect
[00:34:38 CEST] <JEEB> if you have access to multiple nightlies of different age, you could start going through them forwards from the last known working one :P
[00:34:48 CEST] <Lite> Moreover, on another device  Fiddler installed too
[00:36:02 CEST] <Lite> Actually I don't believe that's 'update to more actual version' issue
[00:36:37 CEST] <Lite> SInce I faced an issue someday on same version that worked perfect before.
[00:38:43 CEST] <Lite> Yeee Mr. Gray and kepstin are really PRO. To find out a reason just from screenshot (https://Drive.Google.Com/uc?id=1h6CyKvQ25ztx9FNo7YBqH-vUyHm4bEt-) shows for me almost nothing :D
[00:43:38 CEST] <Lite> :'C
[00:44:01 CEST] <Lite> @D-ion A5 at LQ7=>?
[00:44:12 CEST] <Lite> 8;09=?
[00:44:26 CEST] <Lite> 4>@>20
[00:45:54 CEST] <Lite> I'm sorry it was russian language :|
[00:46:39 CEST] <Anonrate> To compile ffmpeg with lzma, you need to install the lzma sdk from 7-zip, ya?
[00:49:48 CEST] <furq> no
[00:50:20 CEST] <furq> you want liblzma from xz-utils
[00:50:54 CEST] <Anonrate> I want to compile from source though.  So that would be from kobolabs?
[00:51:02 CEST] <furq> still no
[00:51:57 CEST] <Anonrate> Tukaani?
[00:53:08 CEST] <furq> yes
[00:53:15 CEST] <Lite> found a path affected to schannel setting in Windows 10 registry...
[00:53:27 CEST] <Lite> But nothing intersting there
[00:53:47 CEST] <Lite> Even no any empty folder fro any TLS
[00:54:16 CEST] <Lite> :'(
[00:54:47 CEST] <Anonrate> Thank you.
[00:56:51 CEST] <D-ion> Lite: Da. Tovarisch.
[01:13:28 CEST] <kepstin> Lite: i was mistaken about th eschannel stuff, both builds should be gnutls
[01:14:07 CEST] <kepstin> Lite: at least according to the readme zeranoe provides
[01:15:21 CEST] <Lite> I see
[01:16:33 CEST] <Lite> But it was confirmed that 3.4.2 works how nightly should; ATM nightly works at "i" parameter with HTTP URLs and not working with HTTPS
[01:17:01 CEST] <Lite> isn't that a good reason to tell I should fix something with TLS?
[02:17:51 CEST] <Nanashi> When creating a gif from transparent frames how do I keep the first frame's transparency instead of having black background?
[02:40:10 CEST] <Nanashi> nvm got it, used latest version but slightly different commands, gonna recheck old commands
[02:44:06 CEST] <Nanashi> exactly same result, no issues
[02:56:42 CEST] <Nanashi> but what's the flag to tell it to replace frame instead of combine
[03:09:17 CEST] <Nanashi> since with transparent frames it's stacking on top of each other...
[03:10:40 CEST] <klaxa> would help to know what you are already doing
[03:10:48 CEST] <klaxa> as in, what command you are running
[03:11:15 CEST] <klaxa> not sure if i can help, but if someone else can they can help better and faster
[03:14:11 CEST] <Nanashi> the basic, ffmpeg -i input%d.png -vf palettegen palette.png then ffmpeg -i input%d.png -i palette.png -lavfi paletteuse output.gif
[03:17:26 CEST] <klaxa> maybe your input images need to have their alpha removed?
[03:18:42 CEST] <Nanashi> the point is to have a transparent gif
[03:19:24 CEST] <klaxa> ah
[03:19:55 CEST] <klaxa> oh you don't want it stacking right you said, hmm have you tried -gifflags -transdiff ?
[03:20:21 CEST] <klaxa> not sure if it works that way exactly, but if it is on by default - should disable it
[03:30:54 CEST] <Nanashi> strangely not doing anything
[03:50:37 CEST] <Nanashi> wow my workaround solution is to output each frame, essentially just applying the palette, then assemble the gif in gimp... extra work tho
[03:51:17 CEST] <klaxa> hmm i would have probably done the same :/
[03:51:23 CEST] <klaxa> might be worth a ticket
[03:51:34 CEST] <furq> it's cool that gifflags doesn't appear anywhere in the docs
[03:51:58 CEST] <furq> also yeah if you're going to just write out every frame then just use gifsicle to assemble it
[03:52:01 CEST] <Nanashi> Is there a flag to create unoptimized gif?
[03:52:09 CEST] <furq> i don't know, it's not documented
[03:52:39 CEST] <klaxa> hmm i got it from ffmpeg -help encoder=gif
[03:53:15 CEST] <furq> yeah it shows up in -h full but that's it
[03:53:19 CEST] <furq> it's not in man ffmpeg-all or on the site
[03:53:54 CEST] <furq> i vaguely remember there being some unresolved issue in the gif encoder but i forget what it was now
[03:54:06 CEST] <furq> but yeah just use gifsicle
[05:13:01 CEST] <hotbobby> by what method does -ac 2 downmix 5.1 to stereo audio
[05:20:21 CEST] <hotbobby> also, there is not any kind of -loglevel that lets me ignore errors but also see stream statistics like fps and bitrate
[05:23:00 CEST] <furq> -v error -stats
[05:24:58 CEST] <hotbobby> it still shows nonfatal errors
[05:29:15 CEST] <Nanashi> fuckit, I notice ffmpeg is adding red to palette when there is no red in images
[06:11:35 CEST] <tdr> pick a better color pallet or encoding codec
[06:20:08 CEST] <hotbobby> is there any way to show stats but not errors?
[06:20:19 CEST] <furq> -v quiet
[06:21:04 CEST] <hotbobby> -v quiet -stats works. i didnt think of combining them
[06:21:05 CEST] <hotbobby> thanks
[09:26:21 CEST] <styler2go> Good Morning. I'm trying to make a small script which records my security camera. Now i am stuck on even the simplest step. Problem is it says: "Nothing was written into output file 0 (log.mp4), because at least one of its streams received no packets." What could cause this?
[09:27:08 CEST] <styler2go> full output: https://p.styler2go.de/3306680
[09:48:03 CEST] <Diag> styler2go: are your streams receiving packets?
[09:49:59 CEST] <styler2go> well i can watch the stream in vlc player if that counts?
[10:24:07 CEST] <styler2go> I don't really get any video output, any ideas? https://p.styler2go.de/6864679
[10:25:33 CEST] <sfan5> >Consider increasing the value for the 'analyzeduration' and 'probesize' options
[10:25:36 CEST] <sfan5> have you tried?
[10:25:54 CEST] <sfan5> also why yuva420p instead of yuv420p?
[10:28:08 CEST] <styler2go> sfan5, i just tried, no changes
[10:28:55 CEST] <sfan5> try -probesize 50M -analyzeduration 100M
[10:30:39 CEST] <styler2go> Still the same problem sadly
[12:18:29 CEST] <oerg866> hello again
[12:19:09 CEST] <oerg866> I'm trying to mux some vob files with high quality wav files into a new file, ffmpeg doesn't support lossless or uncompressed audio for TS so I tried muxing to a VOB file instead
[12:19:20 CEST] <oerg866> I get a lot of these: [svcd @ 00000000001ce400] packet too large, ignoring buffer limits to mux it
[12:19:20 CEST] <oerg866> [svcd @ 00000000001ce400] buffer underflow st=1 bufi=2608 size=2728
[12:19:28 CEST] <oerg866> the resulkting file plays fine in MPC-HC
[12:19:37 CEST] <oerg866> but is it always safe to ignore these warnings?
[12:19:41 CEST] <oerg866> they're red and look scary ;-)
[13:10:07 CEST] <Lite> Hello!
[13:10:27 CEST] <Lite> Still couldn't fix TLS/HTTPS issue at my PC....
[13:13:33 CEST] <Lite> ATM, deleted Charles, created 'Clent' and 'Server' paths at each of also created 'TLS 1.0', 'TLS 1.1' 'TLS 1.2', 'SSL 2.0', 'SSL 3.0' Paths here at Windows Registry ><?LNB5@\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SecurityProviders\SCHANNEL Path which was totally empty before
[13:17:09 CEST] <Lite> everywhere at 'Client' and 'Server' paths created 'DWORD' parameters called 'DisableServerExtendedMasterSecret' with value=0 and 'Enabled' with value=1
[13:17:30 CEST] <Lite> Like it said here https://Docs.Microsoft.Com/En-US/windows-server/identity/ad-fs/operations/manage-ssl-protocols-in-ad-fs
[13:18:22 CEST] <Lite> Also did it with RC4 at totally empty before path '><?LNB5@\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SecurityProviders\SCHANNEL\Ciphers'
[13:19:18 CEST] <Lite> restarted my PC, saw how it applies some updates (maybe meaning settings changes I made),
[13:19:36 CEST] <Lite> But even after all of it nothing successfull
[13:19:45 CEST] <Lite> :'C
[13:20:39 CEST] <Lite> Any ideas? What else could be edited to fix this TLS/HTTPS issue?
[13:21:15 CEST] <Lite> :'C
[13:31:03 CEST] <styler2go> Hey there, i am still trying to save a stream to a file but it doesn't seem to save anything.. Any ideas? https://p.styler2go.de/9368806
[13:37:07 CEST] <kepstin> Lite: the ffmpeg builds you have use gnutls not schannel, so changing schannel stuff should change nothing.
[13:38:09 CEST] <kepstin> styler2go: I'm not that familiar with rtsp, but it looks like the issue is that it's not receiving an IDR frame in the video before it times out. maybe there's a timeout you can adjust.
[13:41:19 CEST] <styler2go> kepstin, didn't seem to work with increased timeouts
[13:42:18 CEST] <Lite> @Kepstin, so what's this issue 'stucking, crashing at HTTPS requests with -i parameter' or 'impossibility to produce HTTPS requests with -i parameter' about??!! :O
[13:43:18 CEST] <Lite> Is there any way to find out and fix a reason?
[13:46:58 CEST] <kepstin> Lite: need to debug the issue. maybe look at the network traffic in wireshark to see if there's a difference between the versions, or try on a few more different windows systems to see if it's only the one computer.
[13:49:00 CEST] <Lite> I already confirmed it is only one computer
[13:50:22 CEST] <Lite> Where everything was workinmg perfect before someday when some unknown event or user's action became a reason of this unsolved for now issue
[13:52:15 CEST] <Lite> Only one detail I could add to this IS that issue started at Windows 10 1703 Build. Was hoping for upgrading to current 1709 build will fix the issue... But it did not
[13:52:42 CEST] <Lite> How can I debug the issue?
[13:53:12 CEST] <Lite> Could you provide me step-by-step please?
[13:59:58 CEST] <Lite> And also what, in your mention, could be found in Wireshark as soon as at HTTPS requests FFmpeg just stucks and crashes?
[14:00:13 CEST] <Lite> It is not proceeding these URLs
[14:00:31 CEST] <Lite> even if URL not existing/availiable
[14:00:53 CEST] <Lite> It is just NOT proceeding it at all
[14:01:08 CEST] <Lite> As I showed it at screenshot
[14:02:21 CEST] <Lite> difference between the versions? LOL sure there is. 3.4.2 version works and proceeds HTTPS URLs successfully
[14:25:17 CEST] <Lite> OMG
[14:25:19 CEST] <Lite> Ah
[14:25:20 CEST] <Lite> Ok
[14:25:38 CEST] <Lite> I lied you a little bit, dear colleagues....
[14:25:47 CEST] <Lite> Mr. kepstin
[14:26:33 CEST] <Lite> As I told I faced an issue in ~november or december 2017 - jan. 2018
[14:27:01 CEST] <Lite> Now exchanged current latest nightle build to different nightly build
[14:27:20 CEST] <Lite> https://ffmpeg.zeranoe.com/builds/win64/static/ffmpeg-20171030-05beee4-win64-static.zip this one works perfect
[14:29:09 CEST] <kepstin> october 2017, eh. that's not really all that much newer than 3.4, really. It might be helpful to try a few inbetween builds to figure out when it stopped working
[14:32:06 CEST] <Lite> This one already not working https://ffmpeg.zeranoe.com/builds/win64/static/ffmpeg-20171128-86cead5-win64-static.zip
[14:36:03 CEST] <kepstin> hmm. https://git.videolan.org/?p=ffmpeg.git;a=commit;h=eb061ad6fd0e3cea7cf7cfbff0749bc90dd7d888 was merged between those two builds, i wonder if it had some fallout on windows.
[14:36:45 CEST] <Lite> YES!
[14:36:48 CEST] <Lite> FOUND IT!
[14:36:59 CEST] <Lite> Well.... Not so good news for me...
[14:37:10 CEST] <kepstin> that is not necessarily the problem, it's just a guess
[14:37:35 CEST] <kepstin> you'd want to narrow it down more and maybe even try a custom build with that reverted to see if it's really the problem.
[14:43:40 CEST] <Lite> Last Nightly build (version) which is working well on my issued [for latest-for-now Nightly build (version) of FFmpeg working] machine is N-88428-g88c7aa13dd [released (published) 31.10.2017] [URL: HTTPS://FFmpeg.Zeranoe.Com/builds/win64/static/ffmpeg-20171031-88c7aa1-win64-static.zip] Nightly build (version) N-88514-gd5995c531d which has been released 02.11.2017 already stopped working as well. [URL: HTTPS://FFmpeg.Zeranoe.Com/builds/
[14:43:51 CEST] <Lite> oops
[14:44:01 CEST] <Lite> Last Nightly build (version) which is working well on my issued [for latest-for-now Nightly build (version) of FFmpeg working] machine is N-88428-g88c7aa13dd [released (published) 31.10.2017]
[14:44:11 CEST] <Lite> [URL: https://FFmpeg.Zeranoe.Com/builds/win64/static/ffmpeg-20171031-88c7aa1-win64-static.zip]
[14:44:18 CEST] <Lite> Nightly build (version) N-88514-gd5995c531d which has been released 02.11.2017 already stopped working as well.
[14:44:27 CEST] <Lite> [URL: https://FFmpeg.Zeranoe.Com/builds/win64/static/ffmpeg-20171102-d5995c5-win64-static.zip]
[14:44:34 CEST] <Lite> That's it :'C
[14:45:11 CEST] <Lite> What has been changed there??
[14:46:03 CEST] <Lite> Anyway. It's a good reason to provide an issue directly to Developers
[14:46:31 CEST] <Lite> Because in it's issued machine it has been installed and staying for now a lot of Cryptography software for work
[14:46:51 CEST] <Lite> Which is not installed at all on second machine
[14:48:33 CEST] <Lite> As I understand, any of this software can be affected bad for builds of FFmpeg which are published since 02.11.2017 up to current time
[14:49:48 CEST] <Lite> kepstin? Any ideas?
[14:49:53 CEST] <Lite> :'C
[14:51:22 CEST] <kepstin> I've stepped away from my computer, have some things to do. Later.
[14:51:48 CEST] <Lite> Ah. I'm just going away too...
[14:52:27 CEST] <Lite> Please note my email address to contact me: DEgorkin22 at GMail.Com. Will wait for your reply, sir...
[14:53:04 CEST] <Lite> Also, going to come back here over~ 5 hours
[15:04:30 CEST] <Lite> For comfortable navigating for changes:
[15:05:25 CEST] <Lite> ReadMe for version N-88428-g88c7aa13dd [released (published) 31.10.2017]: https://FFmpeg.Zeranoe.Com/builds/readme/win64/static/ffmpeg-20171031-88c7aa1-win64-static-readme.txt
[15:06:56 CEST] <Lite> ReadMe for version N-88514-gd5995c531d [released (published) 02.11.2017]: https://FFmpeg.Zeranoe.Com/builds/readme/win64/static/ffmpeg-20171102-d5995c5-win64-static-readme.txt
[15:12:00 CEST] <Lite> :'C
[15:28:17 CEST] <Lite> What I definately believe is that any tsable or even beta version of FFmpeg after 3.4.2 shoudn't be released/published since we found an issue which should be definately fixed.
[15:28:54 CEST] <Lite> Or without a release about incompatible software wich could affect the issue
[15:28:56 CEST] <JEEB> 4.0 was released ages ago :P
[15:29:04 CEST] <JEEB> as in more than a week ago
[15:30:35 CEST] <Lite> @ JEB, 1) as soon as I faced(ing) an issue at Nigtly build released since 02.11.2017, will I face an issue at 4.0?
[15:30:44 CEST] <JEEB> fuck if I know
[15:30:51 CEST] <JEEB> also those builds are not official and are using gnutls?
[15:30:56 CEST] <Lite> 2) Why isn't it published here https://ffmpeg.zeranoe.com/builds/ then?
[15:31:01 CEST] <JEEB> ask zeranoe?
[15:31:06 CEST] <JEEB> there are no official binaries of FFmpeg
[15:31:19 CEST] <JEEB> but try with a build that uses SChannel on Windows
[15:31:20 CEST] <JEEB> for TLS
[15:31:48 CEST] <Lite> :C
[15:31:52 CEST] <JEEB> most people who build for windows use schannel because that's the system TLS library
[15:32:00 CEST] <JEEB> also if you have a clear issue that you can replicate
[15:32:03 CEST] <JEEB> post it on trac
[15:32:10 CEST] <JEEB> since at this point you've spammed a lot already
[15:32:11 CEST] <JEEB> :)
[15:32:14 CEST] <Lite> But we found already that's not GnuTLS or TLS issue
[15:32:15 CEST] <JEEB> better put it in one place
[15:32:17 CEST] <JEEB> ok
[15:32:22 CEST] <JEEB> then post all that in an issue on trac
[15:32:25 CEST] <JEEB> trac.ffmpeg.org
[15:32:31 CEST] <Lite> LOL
[15:32:46 CEST] <Lite> Thats why Im here and not there at trac
[15:32:52 CEST] <JEEB> or do you expect any developer to just read your fucking long log here?
[15:32:53 CEST] <Lite> can't register there
[15:33:03 CEST] <Lite> spam filter and not working captcha
[15:33:25 CEST] <JEEB> well I don't know, someone is maintaining that thing. but putting all this stuff here is not going to make it easier for people to test your issue
[15:33:35 CEST] <JEEB> or get your issue fixed
[15:33:36 CEST] <JEEB> :P
[15:33:46 CEST] <JEEB> because f.ex. I just look at this wall of text
[15:34:00 CEST] <JEEB> and you have no idea where to start or where the actually meaningful parts end
[15:34:01 CEST] <JEEB> :P
[15:34:45 CEST] <Lite> :'C
[15:38:36 CEST] <Lite> Hoping for sir's @kepstin help...
[15:38:57 CEST] <Lite> He knows for now about my issue almost everything
[15:39:25 CEST] <kepstin> well, i'm not a core ffmpeg dev, i'm not a windows dev, i'm just a person on irc trying to help you narrow down your issue so you can report it properly
[15:40:51 CEST] <Lite> And we found out it :D
[15:41:51 CEST] <Lite> Next task is to try to found out a real reason depends on what changed between those 2 builds -> which one software could be affect provided in details issue.
[15:42:09 CEST] <Lite> Is it possible here ? :D
[15:42:50 CEST] <Lite> Fiddler is excluded. It installed on both machines
[15:43:33 CEST] <Lite> Wireshark?... dunno, don't believe it. You recommended me to use it to check details
[15:43:54 CEST] <Lite> So, some of cryptographic softwarte.
[15:45:48 CEST] <Lite> Just wanna use actual version of FFmpeg :C
[15:45:51 CEST] <Lite> :'C
[15:46:23 CEST] <Lite> Still hoping you will provide me something more specific
[15:46:45 CEST] <Lite> Or tell me which one logs/diags should I make and provide
[16:22:53 CEST] <lightbulb6> how can i access frame metadata in a ffmpeg expression?
[16:24:20 CEST] <lightbulb6> for example, the aphasemeter filter sets the value of lavfi.aphasemeter.phase frame metadata key; how can i use that value in another filter further down the filterchain, for example the zoompan filter's "zoom" parameter?
[16:26:55 CEST] <durandal_1707> lightbulb6: you can not, zoompan filter does not accepts filter metadata
[16:27:15 CEST] <durandal_1707> but you can with other filters, like drawtext
[16:28:04 CEST] <lightbulb6> hmm, so the metadata cannot be retireved with some expression trickery? i'm thinking https://ffmpeg.org/ffmpeg-utils.html#Expression-Evaluation
[16:28:33 CEST] <lightbulb6> i thought i could st() the value using the ametadata filter first, then ld() it in the zoompan expression
[16:29:10 CEST] <lightbulb6> but it looks like the variables set with st() don't persist between different expressions
[16:30:26 CEST] <lightbulb6> or maybe sendcmd/asendcmd could be used in some way?
[16:59:14 CEST] <durandal_1707> lightbulb6: why you need to set zoompan parameters from aphasemeter?
[17:23:58 CEST] <Lite> any news for me :D
[17:23:59 CEST] <Lite> ??
[17:28:18 CEST] <benguitar> Hello, what is the best way to add "eta" functionality to ffmpeg on macOS?
[17:28:53 CEST] <durandal_1707> there is no way
[17:30:29 CEST] <benguitar> It appears that assumption is incorrect, as others have seem to have added that functionality. https://prupert.wordpress.com/2010/05/11/finally-a-bash-progress-indicator-for-ffmpeg-that-works/
[18:08:57 CEST] <BtbN> Not everything ffmpeg does has a given duration/number of frames
[18:09:04 CEST] <BtbN> so a generic progress indicator is impossible
[18:09:29 CEST] <BtbN> If you know the length of your input, you can already just look at the processed duration yourself
[18:30:41 CEST] <Lite> I created MS-info diagnostic file. Which includes list of software installed on my PC and services
[18:30:52 CEST] <Lite> But it's russian language
[18:30:55 CEST] <Lite> :'C
[18:31:22 CEST] <Lite> Should I provide it with my issue to trac?
[18:32:02 CEST] <Lite> Mr. Kepstin, do you have any news for me?
[19:00:09 CEST] <AJ_> \list
[19:02:05 CEST] <AJ_> anyone familiar with ffprobe?
[19:03:04 CEST] <AJ_> i am using it to check the health of mpeg-DASH streams
[19:03:42 CEST] <AJ_> but the bitrate seems inaccurate
[19:03:45 CEST] <lightbulb6> durandal_1707: zoompan was just an arbitrary example, i'd like to create some nice visual effects to accompany the music, i noticed the output of aphasemeter corresponds to the overall volume of music at any given frame, with that data i could make the video into something more entertaining to watch than a barebones album cover, etc.
[19:05:09 CEST] <utack> vmaf has been nothing but a big segfault for me. is that expected?
[19:08:30 CEST] <Lite> Help me please somebody: how can I set up this IRC chat via Trillian (look at screenshot: https://Drive.Google.Com/uc?id=1VxbpOsTjxMp8OBgNRpmSRZEvIYYMnE8E). What exactly should I type in each of these 3 fields?
[19:08:33 CEST] <AJ_> anyone familiar with ffprobe?
[19:10:29 CEST] <AJ_> Does anyone know if FFPROBE does work with DASH? I have done multiple tests, but the reported bitrate is off
[19:15:50 CEST] <lightbulb6> AJ_: the actual bitrate may be different than the value specified in the manifest
[19:34:18 CEST] <AJ_> Does anyone know if FFPROBE does work with DASH? I have done multiple tests, but the reported bitrate is off
[19:43:22 CEST] <utack> turns out aptx has no bitrate setting...just patents. what a stupid codec
[19:48:29 CEST] <Lite> Mr. Kepstin, you here?
[19:48:45 CEST] <kepstin> Lite: I am not your personal support agent.
[19:48:55 CEST] <Lite> I'm sorry.
[19:49:00 CEST] <Lite> I understand
[19:49:09 CEST] <Lite> :'C
[19:49:40 CEST] <kepstin> I've helped you out as much as I can, your next task is to file a bug report with as much as you know about the problem and how to reproduce it.
[20:49:30 CEST] <AJ_> Does anyone know if FFPROBE does work with DASH? I have done multiple tests, but the reported bitrate is off
[21:21:29 CEST] <SpeakerToMeat> Can quicktime files have plain xml inside?
[21:23:56 CEST] <oblio> halo, having some issues concatenating webm/avc/opus uploaded from chrome into mp4/aac, anyone have any experience or pointers with that?
[21:25:52 CEST] <SpeakerToMeat> I explain, somebody wants help with non playing "undeleted" video files. I suspect simply sectors of the file where overwriten after deletion, or it was non contiguous and somehow a contiguous block was recovered. the file has the moov at the start so mediainfo and ffprobe show its data, but nothing plays it. simply editing the file in an editor to check it "looks ok" (a.k.a. human giberish) I find in th
[21:25:54 CEST] <SpeakerToMeat> emidle a short but complete xml, but the xml contents are congruent with camera metadata so I wonder if it's a sign of corruption, or if .mov is capable of having textual metadata inside in the form of human readable xml.
[21:27:52 CEST] <SpeakerToMeat> Well actually itr's a .mp4... almost the same thing but there might be an important distinction
[21:28:02 CEST] <SpeakerToMeat> it does have a moov at the header though
[23:05:26 CEST] <greentea> Can we ask question about AAC encoding such as the transcode_aac.c example not working for me and i am trying to get audio encoding to work for at the least the example
[23:08:19 CEST] <rindolf> hi all! how can i get this cli to work in ffmpeg 4.0? << ffmpeg -i "audiodump.wav" -i pysolfc-bhs.ogv -map 0:0 -map 1:1 -shortest -c:a libvorbis -q:a 7 -c:v copy pysolfc-bhs-with-audio.ogv >> ?
[23:08:44 CEST] <furq> rindolf: you probably want -map 1:v
[23:08:44 CEST] <greentea> i just got a mp3 file as the input and trying to save the output such as "transcode_aac.exe filename.mp3 filename.mp4"  and i am getting that it cannot open the file (i double checked the paths), anyone let me know
[23:08:55 CEST] <furq> and you probably also want that to come before -map 0:0
[23:09:05 CEST] <furq> unless ogv typically orders streams backwards
[23:09:13 CEST] <rindolf> furq: ah
[23:18:32 CEST] <rindolf> furq: ffmpeg -i "006 - David Amber - Gnarly _feat. Devyn Rush_.ogg" -i pysolfc-bhs.ogv -map 1:v -map 0:a -shortest -c:a libvorbis -q:a 7 -c:v copy pysolfc-bhs-with-audio.ogv ==> with this i get a zero-length file
[23:18:56 CEST] <rindolf> also tried w -map 0:0 and before
[23:19:22 CEST] <furq> pastebin the full command and output
[23:19:39 CEST] <rindolf> furq: ok.
[23:22:12 CEST] <rindolf> furq: see http://www.shlomifish.org/Files/files/text/f.txt
[23:24:23 CEST] <rindolf> furq: thanks for your help
[23:24:49 CEST] <furq> that doesn't look fun
[23:25:00 CEST] <furq> try adding -af asetpts=PTS-STARTPTS
[23:26:40 CEST] <rindolf> furq: doesnt help
[23:26:53 CEST] <rindolf> furq: same result
[23:32:26 CEST] <Lite> hello :D
[23:33:17 CEST] <rindolf> Lite: hi
[23:33:50 CEST] <Lite> Tell me please, which one parameter should I try to use to add some cpesific supported ...how it called ...protocol? which is not included at whitelist by default
[23:34:01 CEST] <Lite> That whitelist where included 'http,https,tls,rtp,tcp,udp,crypto,httpproxy'
[23:34:16 CEST] <Lite> I remember I did it somehow
[23:34:26 CEST] <Lite> forgot how exactly :C
[23:34:44 CEST] <rindolf> Lite: do you mean at ./configure?
[23:35:25 CEST] <rindolf> furq: any idea?
[23:36:09 CEST] <Lite> I mean...
[23:36:26 CEST] <Lite> For example by default I'm using string: FFMPEG -i "<Input_file>" -c copy -crf 0 -preset placebo C:\<Output_file_path>.MP4
[23:37:12 CEST] <Lite> But I wish also to set specific parameter to access it's proceeding with what not included at whitelist
[23:37:47 CEST] <Lite> 'file' for example
[23:38:41 CEST] <Lite> So I'm adding to this string something like that: 'FFMPEG -<???> file -i "<Input_file>" -c copy -crf 0 -preset placebo C:\<Output_file_path>.MP4'
[23:39:16 CEST] <Lite> how correctly should I exchange '<???>' which one parameter is it?
[23:44:22 CEST] <rindolf> furq: any idea?
[23:47:05 CEST] <Lite> looks like almost found that! Here you go: https://blog.yo1.dog/fix-for-ffmpeg-protocol-not-on-whitelist-error-for-urls/ that's what I told about https://blog.yo1.dog/fix-for-ffmpeg-protocol-not-on-whitelist-error-for-urls/
[23:47:20 CEST] <Lite> Ah sorry for duplicating URLs
[23:50:08 CEST] <Lite> yes, that's definately it. '-protocol_whitelist'
[23:52:28 CEST] <rindolf> Lite: thanks for letting us know
[23:53:43 CEST] <Lite> NP :D
[23:58:19 CEST] <rindolf> anyone?
[00:00:00 CEST] --- Sat Apr 28 2018