The ffmpeg node is ready for testing. It is similar to the exec node to spawn ffmpeg, with additional features. An example flow doing way more than a regular human needs to do: [{"id":"93d74c4e.4c8fe","type":"ffmpeg-spawn","z":"5967c855.68b978","name":"","outputs":5,"migrate":1e-9,"cmdPath":"ffmpe…

@thejollypop Added a new feature where you can define the ffmpeg path in settings.js Firstly, install the dependency that will have the ffmpeg that you desire. At the top of settings.js, require the selected lib to get the path. Add the value to ffmpegSpawn.cmdPath. excerpt from settings.js sho…

Accidentally posted this to wrong thread a minute ago. oops. When tweaking your ffmpeg command, its always good to know what type of cpu load it is using. Uses top in batch mode to get the stdout. top -b -p <pid> [Screen Shot 2021-04-27 at 8.01.32 PM] [{"id":"fc058328.2af29","type":"exec","z":"…

[image] kevinGodell: probably a bunch of ways to do this better A bit of advertisment for my nodes can never be harmful: node-red-contrib-cpu

I was actually looking at your node with intentions to use it, but didnt see an option to get an individual PID's data. Would be a nice feature, but I could not find any node.js way of getting the value and had to resort to the system command.

[image] kevinGodell: const ffmpegPath2 = require('ffmpeg-for-homebridge'); Thanks @kevinGodell , now it's compatible with docker as well! I'm running instances also on AWS , and now I get the following node-red-contrib-mp4frag error on t4g.micro Ubuntu and/or Debian servers. Both node-red-con…

It’s hard to say the trouble could be. Those nodes are still experimental and have extra debugging info. Not sure what that image is showing the unhelpful error. Can you post a screenshot of the flow so I can see how things are connected. I have an opposite problem in that I can’t make mine break. …

Totally agree. I was able to fix it in Ubuntu 18.04 Version 43.0, so now it's working perfect

I have an issue with audio from a rtsp camera not working (no sound) Using these args as configuration in the ffmpeg-spawn node: ["-loglevel","quiet","-rtsp_transport","tcp","-i","rtsp://freja.hiof.no:1935/rtplive/_definst_/hessdalen03.stream","-an","-c:v","copy","-c:a","libfdk_aac","-f","mp4","-m…

Oh so stupid, I caused the problem myself...the param "-an" means .....disable audio

Ha! I looked at the args and didn't even notice, either. Just curious, i played it via vlc and it is just hissing and popping. Probably has water in the mic or is simply too far from sources of sound?

Node-RED

Node-RED Forum

Node-red-contrib-ffmpeg-spawn

Developing Nodes

Topic		Replies	Views
@kevingodell/node-red-ffmpeg published to npm Share Your Nodes	6	528	17 February 2023
Display camera ip in dashboard and store video in raspberry General	68	14438	13 September 2020
[beta testing] nodes for live streaming mp4 Share Your Nodes	342	18671	21 September 2021
Technical details about decoding rtsp streams via node-red-contrib-ffmpeg-spawn General	15	1228	29 July 2022
Problem with node-red-contrib-mp4frag General	5	112	19 March 2025

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Node-red-contrib-ffmpeg-spawn

Related topics