If you could actually read and study those two solutions, you could notice that the grok has moved that stuff into separate file.
"I want to use blue and red on my multicolor pen at the same time and it's not working so clearly the pen is broken might fit in your head but the pen still isn't the problem...
Quote Gemini:
This error is the "smoking gun." It confirms that no matter how we quote the command, your shell is treating the comma as a separator for the FFmpeg command itself rather than a character inside the filter.You: "I would like to remove blurry frames with ffmpeg. I think I want to use xyz method. Can anybody please help me craft the command?"
Them: "yes, here's the command" (and maybe it's exactly what the LLM output)
You: "it's giving this error code. Here's a snippet of my input file. Can you please check if that works on your end?"
Them: "oh wow you're absolutely right, this doesn't work, I'll put in the issue ticket"
This is a lot nicer than "something else told me how to use your tool and it's broken".
Watching the zombifying effects of AI "think" for others in real time is depressing.
"I thought about improving old video-8 by discarding fuzzy frames and interpolating between sharp ones. Can ffmpeg do that?"
Gemini produced this:
ffmpeg -i input_video8.mp4 -vf " blurdetect=block_width=32:block_height=32, select='gt(metadata(lavfi.blurdetect.blur), 0.15)', setpts=N/FRAME_RATE/TB, minterpolate=fps=30:mi_mode=mci:mc_mode=aobmc" -c:v libx264 -crf 18 output_clean.mp4
After couple of hours back-and-forth Gemini gave up. Syntax problems seemed unsolvable. Something to do how different layers of FFmpeg interpret quote-characters?
After couple of more hours Grok solved the problem: https://github.com/timonoko/Skipperi
Unfortunately results in improving shitty old videos were not too impressive. :-/