-
Notifications
You must be signed in to change notification settings - Fork 150
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
interop with CP3PRO #331
Comments
Before, it'd look like the following, as mentioned in #331: ``` 2024-12-09T20:53:24.853572 WARN s-CP3PRO-main streamer{stream="CP3PRO-main"}: moonfire_nvr::streamer: sleeping for 1 s after error err=UNKNOWN caused by: deadline has elapsed ``` ...which isn't as clear as it could be, particularly if you don't notice the `caused by` bit. After, it should look more like the following: ``` 2024-12-09T20:53:24.853572 WARN s-CP3PRO-main streamer{stream="CP3PRO-main"}: moonfire_nvr::streamer: sleeping for 1 s after error err=DEADLINE_EXCEEDED unable to play stream and get first frame within PT30S caused by: deadline has elapsed ```
Hello: and yes: the h.265 stream is from a Tenda CP3PRO but forget all about 192.168.40.124 as its a TENDA CP3 configured for a test and streaming in h.264. Tenda CP3 h.264 192.168.40.124 is working fine for months streaming in h.264 to Moonfire NVR standard without h.265 support I will plug a new tenda CP3PRO and config moonfire-nvr h.265 version with it as the only stream in h.265 for a more clean log. I will keep you informed when i finish doint it. best regards and thank you again !!! |
Here you have: configured with only one cp3pro streaming at h.265 Tenda CP3PRO v22.5.4.79 192.138.40.30 2024-12-12T21:09:09.653169 INFO main moonfire_nvr::cmds: Opening /var/lib/moonfire-nvr/db/db in ReadWrite mode with SQLite version 3.40.1 conn: 192.168.40.124:32802(me)->192.168.40.30:554@2024-12-12T21:09:09 conn: 192.168.40.124:32814(me)->192.168.40.30:554@2024-12-12T21:09:11 conn: 192.168.40.124:32824(me)->192.168.40.30:554@2024-12-12T21:09:14 |
Moving from #33: @nalonsor1 wrote that a camera called CP3PRO (a Tenda CP3 Pro, I presume?) does not work, and pasted the following log:
Moonfire logs
The error is here:
I'll improve that message, but it means Moonfire didn't receive a full frame within 30 seconds. There might be clues as to why in a couple earlier messages:
That
sprop-parameter-sets
starts with (converted from base64 to hex)00000001674d00168d8d405017fcb37010101400002ee000057e4010
. The00000001
is the problem; it's an Annex B NAL separator, which shouldn't be there. But it's probably harmless to add some code to look for that separator and skip over it, and it might help....but I'm more concerned about the following message:
If it's sending the data on a different channel than expected, that could certainly cause the problem. Not as sure how we'd work around this one.
@nalonsor1 Would you feel comfortable getting a packet capture of the traffic to
192.168.40.26:8554
via say Wireshark? You could share it with me over email if you don't want to paste it in the public channel. This might have data that would help understand more closely what's going on.The text was updated successfully, but these errors were encountered: