Robust video/audio merge solution?

Questions
1

Has anyone found a robust way to merge video and audio?

I’m running n8n latest on a Hostinger VPS

I’ve tried:

  • Supplying video/audio as Google Drive URLs (files are set to viewable)
  • Data binary from downloaded Google Drive / Audio provider files
  • URLs to the files hosted on my website

I’ve tried these services:
0Code: their “temporary storage” node returns a 3-byte file, their API (either their node or an HTTP Request) returns a 500 error, even from their API playground
kie.ai: HTTP Request times out
Segmind: HTTP Request times out
Using ffmpeg installed locally, I have added ffmpeg to my docker-compose, can confirm it’s installed and n8n has all the right permissions from the Hostinger console… but from the workflow the Read/Write Files from Disk node always throws a “The file “file.mp4” is not writable.” error…

Has anyone got a working workflow?

Information on your n8n setup

  • n8n version: 1.116.2
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker via Hostinger VPS
  • Operating system: Ubuntu 24.04
2

If you are okay with paying fees, you can use the AWS Media Services APIs, and you don’t have to worry about your infrastructure.

I do not know how your Hostinger setup is configured at the moment. For example, did you add ffmpeg directly into your n8n Docker Compose? If so, that may not be the best approach.

Ideally, you want an API that runs ffmpeg for you. For example, maybe your n8n workflow calls an API you wrong at “/combinemedia” that sends an array of media files from Google Drive (e.g., a Google Drive “Target Production Videos” folder). Then, that API processes the media and places it in the resulting file in the Google Drive. The API will use ffmpeg locally.

To do that, you could create a simple Docker container with Django, FastAPI, or another service, install ffmpeg in that container, and roll your own API. That option gives you the flexibility to expand and use other ffmpeg features if you want to do even more with the service.

I do not know which plan you are on with Hostinger, but keep in mind that you likely have limited CPU/GPU resources, so performance might be limited.

Once you have your API or AWS job working, connect it via the HTTP Request node in n8n and handle the callback or output upload automatically.

I hope this helps,

-Bill

3

Thanks Bill, that’s really helpful. I’m quite happy to pay and outsource it, so I’ll check out AWS… thanks!

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.