-
-
Notifications
You must be signed in to change notification settings - Fork 236
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
Reolink RLC-520 not working #126
Comments
I see a lot of respawning of the ffmpeg streams which suggests they might be terminating early for some reason. If you copy one of those ffmpeg lines and run it by hand, do you see any error messages? |
I can run the command and output it to a test.flv just fine with no errors, some warnings. it seems the cam proxy is triggering the restart not a ffmpeg error.
|
And another test
|
and the root of the problem might be the broken pipe error trying to send the stream to unifi?
Edit, Apparently i did not have netcat installed, so disregard this noise. |
I tried running the command:
This was the output:
|
ffmpeg 4.3.3 aparently crashes when its sent the modifier for reolink cams
Others are reporting. -vbsf is now depreciated the correct flag is -bsf:v. Others have reported in here that they had to downgrade their ffmpeg. See #31 and im also working to get these cams working here #127 |
That's great and I hope you can figure something out 😄. I tried running your PR code but it still respawns and closes the process all the time. I then tried running the command it does which is and I get this error
I am using ffmpeg |
Yeah give 4.1.x a try... There are static binaries available for most platforms. This might be a ffmpeg bug or we might need a different bitstream filter for the latest versions. |
what does |
|
Hmm either our syntax is wrong for 4.3.3 (something chnaged again) or its a bug. can you try 4.1.X? |
How do I install that version? |
Put this on your |
Thank you so much @GhostlyCrowd and @acortelyou ! Downgrading to 4.1.4 fixed the issue so now live view in both mobile and desktop work, as well as recording. |
@acortelyou @Fanman03 @keshavdv REMOVING |
@Fanman03 Mind posting the args you're passing? I downgraded to 4.1.4 and am still experiencing ffmpeg crashes. |
I have an RLC-520 and trying to get this working via Docker on Unraid. Passing |
So have noticed the code referenced in the docs here is missing the '=', causing that error. |
I'm having the same ffmpeg restarting issue on an RLC-420 here, too. Running the ffmpeg commands by hand gives me the same output as @GhostlyCrowd - no errors, just a few warnings about low_delay_hrd_flag. I've tried a variety of different ffmpeg versions with the same results each time, including on 4.1.4 and on the 4.1.6 the current dev docker image has been changed to. I see in the console output each ffmpeg restart is immediately preceded by a Thanks |
need to choose your cameras strem, |
Thanks for the clarification. The docker runs now but once again, plagued with the repeating error in the logs, trying both -s main and sub:
I've heard a few ppl actually have a working stream. Is the args that are working that you can share? |
I spoke to @Fanman03 and he mentioned that he did not in fact get it working stable and was still encountering issues. I don't believe there is anyone who has a stable RLC-520 setup. |
I don't have a Reolink camera so my debugging abilities are limited. If you can, please privately send me a short 20-30s video file captured from the RTSP output via email or be willing to share access to a device. In the meantime, can you try the latest dev docker image (keshavdv/unifi-can-proxy:dev) with the --verbose flag and include the proxy output in a paste? It should include the output from ffmpeg and have a bit more information about why it keeps crashing. I noticed that the last few command shared in this thread are missing the "copy" part from the recommended args. Can you try it again with the following? --ffmpeg-args='-c:v copy -vbsf "h264_metadata=tick_rate=60000/1001" -ar 32000 -ac 1 -codec:a aac -b:a 32k' |
Today I've discovered that the reolink firmware outputs natively a flv stream. this may be very usefull for these cameras if we can use it. For example i have I''m not good enough with python to do this though. |
@keshavdv There is also beta firmware for many of the Cams that enabled keyframes finally. It seems to have been very beneficial for camera stream recording/quality reliability. I have it flashed to one of my RLC-410-5MP I started a discussion on some things I've found recently, since it's out of the scope of an issue report. The native FLV stream is the most reliable and stable from these cameras. it also opens up a third substream called External which could be leveraged. I'm not sure what video 1-3 do in this great cam proxy, I assume one is high quality (main) one is low (sub) and the third is for mobile viewing (external/ext) just as the reolink flv streams are used. |
Temporary access to a camera would be best since I imagine this will need quite a few attempts to get right, but video clips are at least a start. The FLV stream generally is just a container for the same h264-encoded video that you can access via RTSP so while it does have flash-level metadata, the inner video stream is still probably missing a few key components. The beta firmware sounds interesting -- the biggest reason Reolink cameras struggle is the lack of certain VUI markers within the h264 stream. Easiest way to know if it fixes anything is to try the RTSP implementation without any ffmpeg-args and see if it streams smoothly in the web viewer. |
No such luck running the base RTSP implementation. I can get the camera access set up tonight hopefully for you. |
@keshavdv I have the RLC-522 working well on my proxy. what level of access do you want to have so you can work with it and deploy code improvements? just a rtsp port forwarded? do you want the web ui and admin? flv and rtmp ports forwarded? Also best way to contact you privately with the access info? |
Ideally, RTSP and web/admin access would be great since I'm planning to experiment with the more official reolink API if I can. My email is [email protected]. |
@keshavdv everything you need is sent let me know if you need anything else shoot me an email. |
Forgot to mention I've baffled the mic (didn't want to disable it for your work) , so its pretty deaf. mainly because you're just going to hear me at my work pc clacking away on the keyboard, or my cats fighting. there is enough sound to hear you will get something inaudible when there is something to hear, and if you really want to hear something adjust the optical zoom in the Web UI the mic rattle traps when that happens. |
installed ffmpeg 4.1.4 but same freezes with other nvr software i have used a rtmp stream that is more stable for reolink cams rtmp://ip adress/bcs/channel0_main.bcs?channel=0&stream=0&user=usenam&password=pass thanks in advance |
I can provide remote access to my camera - email me at [email protected] and I'll give you a public address to hit the camera. |
For folks using an RLC-520, does live streaming work on iOS or Android? In my testing, it seems to only be the web player that struggles to handle the Reolink stream. My testing has been with the existing reolink implementation. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sorry for the late reply, Has there been any progress on this by anyone? |
Sorry for the delay, I ended up using Frigate in the meantime since I couldn't get this working properly. I see your commit has been merged into the main repo, and I've tried the latest build via Docker with partial success but there still are some issues. Streaming works fine from the Protect app on mobile, but on Desktop the streaming doesn't work and just endlessly loads. The mobile stream also has lots of artifacting when attempting to view the desktop one. The console outputs lots of lines of the following:
This is my
If I can assist the development in any way, please let me know and I'll be happy to provide any additional info. |
I believe this is unrelated to Reolink and is a general bug. I was able to fix it by downgrading to Protect v1.21.2 by running the following via SSH on the UDM Pro:
|
I've installed a beta reolink firmware that is supposed to have fixed RTSP, but now I'm getting this error. I'm on Protect v1.21.2 so I don't think its related to the new FLV format issue.
This is the command I'm using:
|
@Fanman03 I'm getting the same error as you with the RLC-510A. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I have some Reolink RLC-520s I would like to use in UniFi Protect, however when I use this proxy they only show snapshots and do not play live video on either the desktop site or the mobile app.
I have tried running both with and without the argument
--ffmpeg-args '-c:v copy -vbsf "h264_metadata=tick_rate=60000/1001:fixed_frame_rate_flag=1" -ar 32000 -ac 2 -codec:a aac -b:a 32k'
. Is there a known fix for this issue?Here is my console output
https://i.imgur.com/35pNuE1.png
The text was updated successfully, but these errors were encountered: