Hey OP here, I spend a significant amount of time generating complex FFmpeg filtergraphs for my project. They can get really long and cumbersome, so I made this tool that lets you visualize and edit them, and generates the FFmpeg command string for you.
It sort of became an IDE/LSP for FFmpeg filters. My biggest problems were having to constantly to flip to FFmpeg documentation and errors in my filters. So I added autocomplete and embedded the FFmpeg docs. It also verifies the correctness of filters/arguments, and does an analysis on the graph to verify connections/etc.
I haven't played around much with ffmpeg-python, I used to use fluent-ffmpeg for a bit. They're an improvement over writing raw command strings, but they lack static analysis features to verify the correctness of your command at compile time. There's only so much you can do with the constraints of general programming languages.
I'm going to add the ability to export graphs as ffmpeg-python/fluent-ffmpeg code, and to import a graph from ffmpeg-python/fluent-ffmpeg code as well.
In something like Haskell or OCaml, it would be possible to verify the tree/graph at compile the time. That's why functional languages with powerful (or even dependent) type systems are so popular!
The other day I was thinking that precisely this is needed!
Question:
Why are you offering lifetime access for $39? Makes no sense. Anyone company that needs this can afford $100/month. Any individual who needs it can afford $30 for 3 months access.
Ideas:
It would be good if I could upload my ffmpeg binary and the IDE queries it to work out what libraries and options are compiled in.
Or maybe you could provide a command that I could enter that dumps this information, which I then put into your IDE.
It would be great if I could put my existing ffmpeg command lines into this and have them represented as a graph.
Honestly the pricing was selected kind of on a whim, I actually didn't think anyone would use the project. Will probably update the pricing.
I'm not sure how much information could be extracted from the binary, will need to do some more research. Maybe we could read the strings in the static part of the binary and extract some information.
`ffmpeg -i` prints out the configuration FFmpeg was built with, this mostly will let us know which encoder/decoders/container formats you can use. Will add a feature to parse and interpret that output.
I added an ffmpeg command string parser that converts the command stirng into graph nodes, but I temporarily disabled it to fix an infinite loop bug in my parsing code.
To follow up on this, we did update the pricing now https://ffmpeg.guide/pricing which should be effective from Nov 1st. Gonna try to move some more lifetime deals at a slightly higher price before then
As a hobbyist who doesn't _need_ this, the 6-node free plan feels very reasonable for tinkering around and sanity-checking something.
As someone with a project at work that involves setting up an ffmpeg project in the future, I'm now expecting to talk to my boss about expensing this and I think it's at the perfect price point where it won't take too much effort to get them to budge.
This is so useful! Would you consider adding some way of linking a filter to the ffmpeg documentation/reference for it? Or maybe some way of embedding it on a sidebar when a node is selected?
First of all, I love this. ffmpeg is the closest to magic, with the arguments the closest to Harry Potter-type spells, I've ever seen.
Second... I swear it makes me want something like this for shell commands in general. The amount of time I've wasted trying to fix nightmare quoting and spacing issues when passing arguments (containing spaces) that get to a command that will run ssh to run a command remotely that needs those original arguments...
I swear if there were a visual command-line builder that guaranteed quotes and spaces and variables were always printed and escaped correctly, together with a visual reminder of what the -akxlIEJC flags all mean... in other words, I want this but for way more than just ffmpeg! :)
Copilot changed all this for me. Even using ffmpeg, now I just open a .sh and describe the functions that I want in comments and fiddle with what copilot gives me.
Copilot is at it's best writing dumb little shell scripts. Just today I was asking it to help me extract gps coords from a json with jq. A dream.
Something like this for ImageMagick would be awesome. Its CLI syntax is not quite as arcane as FFmpeg, but the sheer breadth of available options and the power of possible combinations is similarly insane.
Seems like a really great idea, and the few times I used ffmpeg I could have really benefited from this. That being said, I almost exclusively prefer email signup over Google sign-in.
I can understand not wanting to create an email-password login, but imagine for a moment losing your Google account for any reason, and losing all your accounts associated with it.
Will add a email auth provider and ship that in a couple of hours, made it Google only cause it was the fast way to ship. Will probably add Github oauth too
This is a godsend considering I'm just starting an FFMPEG project right now. Do you have any other resources you recommend to fully grasp FFMPEG and even what it's capable of? This website is awesome btw!
practice practice practice. if you're using ffmpeg as a one of project, then you'll never grok it. if you're using ffmpeg as a daily tool doing many things, you'll almost start to think you grok it, but then still learn something new about it. whatever your current need of ffmpeg is right now, it is probably such a small subset of what it can do that you'll forever be amazed at what other people are doing with it.
if you're stuck on something and can't find an answer, keep trying to rephrase your question. i'd put money down that it is highly unlikely you are the first person attempting whatever you are doing, and it is very likely someone else has had issues like you.
sometimes, searching for the exact error message isn't as useful as one would hope, but with enough time you'll start to recognize how/why those errors are what ffmpeg is struggling with but it is actually something related that you need to address.
hopping on to this - i'm interested in doing my own audio waveforms, but the only documentation on this I can find is https://trac.ffmpeg.org/wiki/Waveform
wondering if theres a standard set of tooling for creating audio waveform videos?
This is brilliant. A long time ago when I worked on Windows video apps, I used to use Graph Studio[1] to visualize the video graph comprised of countless DirectShow filters. It occurred to me multiple times that such a tool would be super useful for ffmpeg as well.
It really helps visualize your filter graphs, especially when building complex video processing pipelines. Too bad this is not open source... I'd be more than happy to contribute.
i've been thinking on having an ffmpeg filter object in https://ossia.io for quite some time, which would give the timeline aspect for free (and wouldn't be too hard to integrate as ffmpeg is already used for decoding A/V and we have a very very simple plug-in API which supports audio, video and GPU processing : https://celtera.github.io/avendish ). Just not a priority... but if someone is interested in contributing it I can definitely mentor.
But if that’s rhetorical/curt, then the answer can also be found on the home page of the site: it’s a service with a paid component and the login is to associate the purchase with your account. Very common across the web.
One thing I wish ffmpeg tools - including this one- would do better is account for live inputs and outputs. I’ve come up with the incantations to do live rtsp to hls, webcam to hls and more, but it’s always something I have to relearn.
The main thing I’ve done is take RTMP/RTSP from network cameras (im doing this for traffic cameras) and push to HLS. This is very powerful as you can take a camera that otherwise would require a special viewer and play in any modern browser with no plugins. Also HLS is over HTTP, so it’s cacheable.
I have to craft the ffmpeg arguments fresh each time I do this, but the main reason I commented was because many ffmpeg tools - like handbrake and jmeter load testing plugins etc are geared towards fixed length inputs, not indefinite live streaming cameras.
There are plenty of streaming servers etc, but just seems like there is a missing niche for lightweight ffmpeg tooling that helps do this.
ffmpeg is such a great tool, it’s complex but because video stuff is complex. Shoutout to llogan and gyan in StackOverflow, I don’t think I could’ve done a few things without their help.
It sort of became an IDE/LSP for FFmpeg filters. My biggest problems were having to constantly to flip to FFmpeg documentation and errors in my filters. So I added autocomplete and embedded the FFmpeg docs. It also verifies the correctness of filters/arguments, and does an analysis on the graph to verify connections/etc.