02:32 <ToughRockJohnson> Hello

02:35 <aaabbb> hello

02:35 <ToughRockJohnson> If anyone here uses vscode as their IDE for developing ffmpeg, I was wondering if you could give insight on how your set-up is. I'm still somewhat new to vscode and I'm trying to figure out the best way to set up things like the .vscode folder, tasks.json, & launch.json in the same repo directory. Or should I maybe have that in a parent directory with the repo in a folder?

02:36 <ToughRockJohnson> Not really sure, but would like to know.

08:52 <Traneptora> just do code ./ in the ffmpeg directory

08:52 <Traneptora> and develop from the CLI

08:52 <Traneptora> don't bother with tasks.json

08:57 <JEEB> aand he had left >_>

08:57 <JEEB> basically at most I set up the clang compiler commands stuff for the clang C integration

08:57 <JEEB> there was a compiler wrapper which generated the commands file

09:02 <Lynne> for some reason lang servers failed to detect any includes we used when I tried to use it

09:03 <Lynne> I had to put a hidden file to set the clangd include directives in all my ffmpeg dirs, and put a global gitignore

09:08 <Lynne> but then I just switched to emacs, I didn't need a buggy web-based clippy telling me I forgot a semicolon when I know I forgot a semicolon

09:09 <JEEB> Lynne: for me the file that would have had global compiler args didn't work (adding it to the root did nothing), but the commands file did

09:11 <JEEB> for me way too often touching a file means makefile compiles X files before that, so actually knowing I did a dumb mistake before running `make` is good for me.

09:11 <JEEB> uhh, not before but after of course

09:17 <Lynne> ".clangd", right?

09:18 <Lynne> mine just contains "CompileFlags: \nAdd: [-I<exact unshortened unsymlinked path to directory>]"

09:18 <Lynne> hence needing a different one for every single directory

09:20 <JEEB> https://clangd.llvm.org/installation#project-setup the compile_flags.txt thing I think

09:20 <JEEB> compile_commands.json then worked when I got it generated

09:23 <JEEB> could be that as you say, it would work if I had copied the compile_flags.txt to each damn dir

09:23 <JEEB> but no way I would do that :P

09:24 <JEEB> I used to utilize EasyClangComplete with Sublime Text (the completion bit being the least important of it, it running libclang on the file being the main benefit), which had a single file which actually worked :P

09:25 <Lynne> oh, the makefile generated file, I remember looking into it before .clangd, but yeah, no way

09:26 <JEEB> right, this was the tool that generated compile_commands.json https://github.com/rizsotto/Bear

09:26 <JEEB> (clang itself might do it with an env var, not sure)

15:52 <never> hello all this is never new to ffmpeg and want to start contributing to ffmpeg, so there are some resource to get started

15:54 <JEEB> clone the repo, create a build dir and run `path/to/src/configure` and if it succeeds run `make` :)

16:09 <never> JEEB completed

16:09 <JEEB> nice

16:09 <JEEB> https://www.ffmpeg.org/developer.html is one page to keep an eye on

16:09 <JEEB> but I think you can start by attempting to run the FATE test suite

16:10 <JEEB> after normal make finishes, you can do `make fate-rsync SAMPLES=/some/path/for/fate-suite`, it will rsync about 2 gigs of samples

16:10 <JEEB> and after that finishes, you can do `make fate SAMPLES=/some/path/for/fate-suite` and it will then run the tests :)

16:12 <never> JEEB ok

16:15 <Lynne> I got LDPC code generation via PEG to work!

16:16 <Lynne> I have preliminary working error correction for avtransport

16:17 <Lynne> might need some serious compute power to optimize them, but even random variable/check node distribution functions work fine

20:54 <Daemon404> i feel like this idea to dump bytes to the terminal in ffprobe comes up every 1-2 years to support peoples terrible workflows

20:54 <JEEB> showinfo and friends

20:54 <JEEB> when it's "nice" it's ffprobe

20:55 <Daemon404> lol

20:55 <Daemon404> that is sad

20:56 <JEEB> I do wonder how large of a use case gets done if the trace_headers CBS stuff gets exposed as an API as multiple side data or a side data that contains the things within that buffer

20:56 <JEEB> is it just debugging or is there some other use case

20:56 <JEEB> well, debugging + having some ad-hoc code parse something

20:57 <Daemon404> one day i am fully expecting to see someone add raw_frame: [128,121,122,...] to ffprobe

20:57 <Daemon404> because they need decoded frames in json

21:03 <nevcairiel> do they at least dump it hex encoded this time, instead of hoping its a string? :D

21:03 <Daemon404> byte array i think

21:04 <Daemon404> idea: libcaca support for -show_frame

21:06 <cone-520> ffmpeg Stefano Sabatini master:c2ab41b7e0b9: lavfi/overlay: factorize definition of planar and packed blending functions

21:06 <cone-520> ffmpeg Stefano Sabatini master:030e14014512: lavfi: add quirc filter

21:06 <cone-520> ffmpeg Stefano Sabatini master:899302bb5f6a: lavfi: add qrencode source and filter

21:06 <cone-520> ffmpeg Stefano Sabatini master:7769afcab4c2: lavu/eval: add randomi function to compute random value in interval

21:06 <cone-520> ffmpeg Stefano Sabatini master:732fb122e66c: lavfi: introduce textutils

21:06 <cone-520> ffmpeg Stefano Sabatini master:933c7ff0b96f: lavfi/setpts: use macro to access variables array

21:06 <cone-520> ffmpeg Stefano Sabatini master:4d301be9e581: doc/filters/setpts: add random jitter generation example

21:06 <cone-520> ffmpeg Stefano Sabatini master:43042931fb0c: doc/filters/drawtext: apply second level of escaping on colon

21:07 <Lynne> gzip compressed byte array

21:07 <Lynne> ...in yaml

21:07 <Daemon404> im actually pretty suprised nobody added yaml output

21:07 <Daemon404> like, legitimately.

21:07 <JEEB> :D

21:08 <Daemon404> [20:57] < Daemon404> one day i am fully expecting to see someone add raw_frame: [128,121,122,...] to ffprobe

21:08 <Daemon404> [20:57] < Daemon404> because they need decoded frames in json

21:08 <Daemon404> [21:03] <@nevcairiel> do they at least dump it hex encoded this time, instead of hoping its a string? :D

21:09 <Daemon404> [21:03] < Daemon404> byte array i think

21:09 <Daemon404> putty mouse fail

21:09 <Daemon404> [21:04] < Daemon404> idea: libcaca support for -show_frame

21:09 <Daemon404> autocopy -_-

21:09 <Daemon404> fffffffffffff

21:09 <Daemon404> sorry

21:09 <JEEB> it happens

21:09 <JEEB> at least it wasn't too many lines

21:10 <Daemon404> no then at least putty would stop the paste :P

21:10 <Daemon404> er, irssi would