In my case, using a RPi3, it works but I could wish for better quality. On the other hand, my source is just 640x480 so I should not complain. The video is delayed a second or so relative to real time and I can briefly see a fragment of the reload arrow approx every 3rd second. But it is not replaying the same. I thought my issues where maybe related to using a slower RPi
Anyway let's check your setup a bit. Your version of ffmpeg and how you built it. Did you build it to also support the OpenMAX H.264 GPU acceleration?
In a command/terminal window, run ffmpeg -encoders | grep 264 What does it show?
In the ui_mp4frag node config, what player do you have/using in the order 1 position? In my case I use hls.js, Also mp4 works but then the reload arrow stays longer in the video
Regarding all parameters for ffmpeg, I honestly don't know. The -re I think means "read from real time", maybe try without this parameter? Found the post where @kevinGodell explained this: " One thing I noticed is that the ffmpeg command needs a little tweak to smooth out the video. Add -re in front of the -i so that it reads at realtime instead of going too fast."
ffmpeg version 4.1.6-1~deb10u1+rpt1 Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 8 (Raspbian 8.3.0-6+rpi1)
V..... libx264 libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (codec h264)
V..... libx264rgb libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 RGB (codec h264)
V..... h264_omx OpenMAX IL H.264 video encoder (codec h264)
V..... h264_v4l2m2m V4L2 mem2mem H.264 encoder wrapper (codec h264)
V..... h264_vaapi H.264/AVC (VAAPI) (codec h264)
Honestly cannot remember how I installed it, followed some instruction I found somewhere.
My source is also 640X480 at 10fps, I'm using the h264_omx option without audio settings you had.
It seems like the putting hls.js to the top of the list works, without the jumping effect.
However I can see the start of spinning circle constantly being redrawn in Chrome, although its not visible in firefox. I'm not sure if this is a problem or not, maybe it causes more traffic, connections etc ?
CPU load for ffmeg is only around 0.7 to 1% as shown by top so I guess thats no problem.
I happy to live with the circle, unless anyone has any other sugestions.
I just reinstalled it on my pi4 using that command and it successfully installed and runs ok after reboot. My guess is that there is a configuration issue. Please post additional details, such as any errors listed in the command line when installing, etc.
because this package is being pulled from github and not published via npm, yet, you will need to setup git on your windows pc and then make sure the git command is in PATH.
After installing git, it may not work by opening a command line and running it as git because your system may not know where it is. The git installer may do that for you, I am not sure. If you try to install git, let me know if the npm command works afterward.
I installed npm using your command in Git CMD. It said a peer of socket. Need to install peer dependecies yourself. But when I open my node red flow still those nodes are not available
ui_mp4frag already in my node red. only the mp4frag node is not available. according to command windows, it stated there is an error: cannot find module 'socket.io'
It was probably a warning and not an error, I hope. The reason for the peer dependency is because socket io v2 is not compatible with v3 and i did not want to force a version with my node that might break other nodes, such as the node-red-dashboard that is still using v2. Most likely you already have v2 installed if you have the dashboard installed and there should not be any run time errors. Maybe soon the node-red-dashboard will update to v3 and then I will also list socket.io as a regular dependency and no longer support v2.
i already got those nodes required. Just when being deployed, the dashboard ui only showing video playback ready sign. Not showing any stream from my camera
Hi. Im using exec node for my rtsp url which is ffmpeg -loglevel quiet -rtsp_transport tcp -i rtsp://xxxx@192.168.1.xxx:554//h264Preview_01_main -an -c:v copy -f mp4 -movflags +frag_keyframe+empty_moov+default_base_moof pipe:1. and connect the node to mp4frag and ui_mp4frag nodes by Kevin Godell. After deploy i only see video playback ready sign at dashboard. How to solve this?
Your rtsp url. Does it work in VLC?. I do not have rtsp cameras myself but the link below normally works (when the camera is available). Try your rtsp url first in VLC, if it doesn't work there, no idea to try further until fixed. Also check how you have configured the ui_mp4frag node
mp4 is mp4
Quality is best when there is less movement in view. Principle for mp4 is to transfer not complete images but the difference from frame to frame. Check now what durations you get. Eventually reduce duration and resolution in camera setting. Try socket.io and see if it is better