[bastawhiz]

If you visit the ffmpeg.wasm documentation, the first example on the Usage page does almost exactly this:

https://ffmpegwasm.netlify.app/docs/getting-started/usage

It transcodes a webm file to MP4, but making it speed up the video is trivial: just add arguments to `ffmpeg.exec()`. Your lack of success in this task is trusting an LLM to know about cutting-edge libraries and how to use them, not a lack of progress in the area.

[MrThoughtful]

The problem is that they don't provide the full code that can run in the browser. I have not managed to get the function they show in the first example to run in the browser.

[Matheus28]

You don’t need an LLM to do that. The code in there is almost complete…

[vel0city]

Listen buddy, I need an LLM to tie my shoes, don't be so judgemental.

[bastawhiz]

That's just wrong. The example is live: you can run it right there on the page. If the code isn't working when you write it, you're probably importing something incorrectly (or you're not running it in an environment with React, which is where the `use*` functions come from). You can even click on the source of the log lines when the example is running (on the right edge of the Chrome console) to jump into the hot-loaded code and see the exact code that's running it.

[MrThoughtful]

I think there is some kind of misunderstanding here.

You say "an environment with React". My environment is the browser.

I don't know how one is supposed to run that nameless function on that page. What I am looking for is a simple, complete example in HTML that can run standalone when opened in the browser. Without any server side processing involved.

[jmtulloss]

If you want to copy/paste, try taking the first example and asking the llm to refactor the code to run in a browser with no dependencies. It should be able to strip out the react stuff, or at least get it close and you can fix it from there.

[MrThoughtful]

I have tried that a bunch of times and a bunch of ways and did not get ffmpeg to work.

It might have to do with these two strange comments at the top:

    // import { FFmpeg } from '@ffmpeg/ffmpeg';
    // import { fetchFile, toBlobURL } from '@ffmpeg/util';

The rest of the code seems to assume "FFmpeg", "fetchFile" and "toBlobUrl" are somehow magically available. Neither me nor any LLM have yet managed to get these into existance.

[jmtulloss]

OK to your credit your original request was to get this all working in a single html file. That is not possible with the easy paths documented on ffmpeg.

By default, the build relies on web workers which need to load their code from somewhere (and usually it has to be the same origin as the code making the request)

Through much mastery of JS build systems that I would not wish on my enemies, I bet you could get it working on localhost, but you’ll have a much better time of it if you set up vite or something for a local build. You can still easily do a “serverless” deploy with GitHub pages or similar but you do need an http server correctly configured for asset requests.

[numpad0]

I just threw that prompt into the free ChatGPT, looks like it'll have a few versioning as well as CORS issues...