Earlier quoted context omitted.
At 2m15s you even mention HN. :)
This is very nice. I've been surprised how many people don't know HN, it can definitely use some promotion.
We'd need way more dangs than are available.
101–110 of 210 posts
Earlier quoted context omitted.
It really works! With few interactions, ChatGPT was able to create a not so obvious -filter_complex pipeline, like: ffmpeg -ss 00:01:00 -t 00:02:00 -i input1.mp4 -ss 00:03:00 -t 00:02:30 -i input2.mp4 -filter_complex "[0:v][0:a][1:v][1:a]concat=n=2:v=1:a=1[v][a];[v]eq=brightness=0.3[outv]" -map "[outv]" output.mp4
And what does all that filter_complex do?
But I also understand my sister doesn't need to know how her phone does any of what it does to play candy crush or read her emails.
Just like she doesn't need to know how a microwave works to reheat her meal.
If you want to know how things are done, of course get yourself involved in the details, but for most things in life you just want to use it without bothering with the details, so you can focus of the parts that are of interests to you.
(I know some people like to know the details of everything, and maybe you are one of them, and that's great, but the vast majority of people do not)
Earlier quoted context omitted.
This bsf was done to fix the following ticket https://trac.ffmpeg.org/ticket/502
Thanks. Looks like the input in question was an .avi file. That's a container format I don't know anything about (and don't particularly care to). I suspect then it's not relevant for anything more modern.
It’s sort-of optional for most playback stacks because they leave frame reordering to individual decoders as a codec-specific implementation detail, but Apple’s stack actually cares about frame-accurate random access so it relies on the codec-independent container timestamps.
The inaccurate seeking you get without container pts is okay for playback but it falls apart with editing or stuff like av1an.
I absolutely love ffmpeg, but for the life of me I cannot understand how its pipeline system works. Each time I need to use it, I attempt to construct the command myself, but end up giving up and consulting StackOverflow. Amazingly, someone has usually done the exact thing I need to do and posted their command line to StackOverflow, so I'm never out of luck! How do I actually start understanding how ffmpeg works? I w…
Use ChatGPT, prompt: ffmpeg pipeline capture webcam to mp4 ChatGPT: >>> ffmpeg -f v4l2 -framerate 30 -video_size 640x480 -i /dev/video0 -c:v libx264 -preset veryfast -crf 28 -pix_fmt yuv420p output.mp4 Here's a brief explanation of what each part of the command does: - `f v4l2`: specifies that the input device is a V4L2 (Video for Linux 2) device, which is typically what webcams use. - `framerate 30`: sets the framer…
Let me translate: the AI might or might not be bullshitting, I have no way to know but I decide to believe in it. Why ?
Earlier quoted context omitted.
It really works! With few interactions, ChatGPT was able to create a not so obvious -filter_complex pipeline, like: ffmpeg -ss 00:01:00 -t 00:02:00 -i input1.mp4 -ss 00:03:00 -t 00:02:30 -i input2.mp4 -filter_complex "[0:v][0:a][1:v][1:a]concat=n=2:v=1:a=1[v][a];[v]eq=brightness=0.3[outv]" -map "[outv]" output.mp4
And what does all that filter_complex do?
Fun fact of the day: ffmpeg is written by Fabrice Bellard, who among other impressive things, wrote the JS PC emulator capable of running windows 2000 in a browser over 10 years ago that got me fascinated with emulators in general. https://bellard.org/jslinux/tech.html
He also wrote QEMU, which is probably far more impressive.
If you want to know a bit more about what is important in this major release, you can watch my presentation about FFmpeg 6.0 at Fosdem: https://fosdem.org/2023/schedule/event/om_vlc/ (Video + Slides) It’s a bit less dry than the changelog, notably for the evolutions of the APIs. What’s also important is the changes about the release schedule that we’ve been pushing with the community. Major version every year at the…
Earlier quoted context omitted.
Huh, I never really thought about it, but I guess that's one thing that GPL kinda fails at: if your server does all the work, you can leverage open source technology to do all sorts of stuff for your clients, so long as all the work the code you serve them does is collect and present data to the server. Like, they get to see the code they run, but there's no insight to the code you run to deliver whatever service you…
This is known as "Tivoisation" (after a dead set top box company), and is the driving motivation behind GPLv3 and some other licenses adding terms to cover this.
So the end user can have all the source code they want and still be helpless.
That issue with the GPLv2 was fixed with V3.