New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RTMP Support #885
Comments
@clik86 can you give me an example of such an URL? |
I too would like to see this feature implemented. It should be trivial to set up a VM for testing.
restart nginx send a stream for it to relay: |
@ccrisan +1 for me. This is helpful for ReoLink cams which suffer from "smearing" when viewed via RTSP. See https://forums.zoneminder.com/viewtopic.php?p=108502#p108502 ReoLink URLs are constructed as follows:
where Manually editing the |
@ccrisan +1 from me as well If rtmp works, then this would be perfect as my Reolink cameras in motion eye suffer from low frame rate and smearing. While VLC with rtsp works flawlessly with high resolution and high frame rate motioneye has really sub par performance despite being run on an Intel NUC. |
Any update on support for the RTMP streams? I have just purchased a Reolink RLC-410-5mp camera and can confirm that in Motioneye smears the RTSP badly, and makes motion capture impossible. The camera operates flawlessly in VLC, so unsure of the issue. |
Is the RTMP supported in motion software? Can you guys please run motion without motionEye? Stop motionEye:
Run motion in the foreground:
Check whether RTMP works. If it doesn't, follow this guide and report it to motion developers. |
Works with this: netcam_url rtmp://cam1.cameras/bcs/channel0_sub.bcs?channel=0&stream=1&user=motion&password= netcam_userpass needed to be empty, I guess the basic auth doesn't work with rtmp. [-1372602752:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file motion.conf With the rtmp URL manually configured this also worked with motion 4.1 and motioneye 0.4.0. With motion 4.2 the web preview in motioneye is broken (but capture still working), motion 4.2.2 contains a fix for that. Also highres stream for capture works by just adding ' |
+1, yes please. As mentioned above, with Reolink cameras this should solve smearing issues. Another example url is: rtmp://x.x.x.x/bcs/channel0_main.bcs?channel=0&stream=0&user=user&password=password. Haven't tried with motion but works for me with ffmpeg (I'm on 4.1.4-1~deb10u1). |
Seems to be working for me as well, need to do more testing though. Should be a simple enough fix to just remove the 'rtmp not supported' code? Will make a PR if so. |
Isn't RTMP supported since several versions? (Or why is this ticket still open?) |
It may be that not very many people have reported testing it and it's working. The only ones I've seen have been Reolink users. Hopefully other users of rtmp can report positive or negative... |
I have Reolink RLC-410 5MP and it doesn't work in Motioneye Addon in Home Assistant but the same link works in Frigate which is weird. |
Please test as below:
Also, can you test in a straight motionEyeOS or motionEye on another OS (like Debian or Raspberry Pi OS, instructions here: https://github.com/ccrisan/motioneye/wiki/Installation) |
Is the URL you use: |
I see previous issues (like #188) on this topic but now motion supports rtmp input stream. I test it with one of my camera. It works on motion alone but the motion eye interface refuse url starting with rtmp scheme.
I look at the code to see how it works but you seam to test the connection before being able to add it and i'm not an RTMP protocol expert so I can't help you.
The text was updated successfully, but these errors were encountered: