Open on4ami opened 2 months ago
You can set trace log level for rtsp module and check logs. You can do this on any go2rtc in your LAN. You can run it on your PC for debugging.
RTSP trace log:
The probe sometimes works, but mostly it gives an error. Probe now says:
{
"producers": [
{
"id": 17,
"format_name": "rtsp",
"protocol": "rtsp+tcp",
"remote_addr": "192.168.10.100:554",
"url": "rtsp://REDACTED:REDACTED@192.168.10.100:554/stream1",
"sdp": "v=0\r\no=- 417891503 1 IN IP4 192.168.10.100\r\ns=HTMS\r\ni=stream1\r\ne=NONE\r\nt=0 0\r\na=tool:HTMS\r\na=control:*\r\na=range:npt=0-\r\na=x-qt-text-nam:HTMS\r\na=x-qt-text-inf:stream1\r\nm=video 0 RTP/AVP 96\r\nc=IN IP4 192.168.10.100\r\nb=AS:4\r\na=rtpmap:96 H264/90000\r\na=fmtp:96 packetization-mode=1;profile-level-id=4d0032;sprop-parameter-sets=Z00AMo2NQBQAWtNwEBAUAAAcIAAFfkAQ,aO48gA==\r\na=control:track=1\r\na=recvonly\r\na=Media_header:MEDIAINFO=494D4B48010100000400010000000000000000000000000000000000000000000000000000000000;\r\nm=audio 0 RTP/AVP 0\r\nc=IN IP4 0.0.0.0\r\nb=AS:64\r\na=rtpmap:0 PCMU/8000\r\na=control:track=2\r\na=recvonly\r\nm=audio 0 RTP/AVP 0\r\nc=IN IP4 0.0.0.0\r\nb=AS:64\r\na=rtpmap:0 PCMU/8000\r\na=control:audioback\r\na=sendonly\r\n",
"user_agent": "go2rtc/1.9.4",
"medias": [
"video, recvonly, H264",
"audio, recvonly, PCMU/8000",
"audio, sendonly, PCMU/8000"
],
"receivers": [
{
"id": 18,
"codec": {
"codec_name": "h264",
"codec_type": "video",
"level": 50,
"profile": "Main"
},
"childs": [
19
]
},
{
"id": 20,
"codec": {
"codec_name": "pcm_mulaw",
"codec_type": "audio",
"sample_rate": 8000
},
"childs": [
21
]
}
],
"senders": [
{
"id": 23,
"codec": {
"codec_name": "pcm_mulaw",
"codec_type": "audio",
"sample_rate": 8000
},
"parent": 22
}
]
}
],
"consumers": [
{
"id": 16,
"format_name": "probe",
"protocol": "http",
"remote_addr": "192.168.10.21:6976",
"user_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36",
"medias": [
"video, sendonly, ALL",
"audio, sendonly, ALL",
"audio, recvonly, ANY"
],
"receivers": [
{
"id": 22,
"codec": {
"codec_name": "ANY",
"codec_type": ""
},
"childs": [
23
]
}
],
"senders": [
{
"id": 19,
"codec": {
"codec_name": "h264",
"codec_type": "video",
"level": 50,
"profile": "Main"
},
"parent": 18
},
{
"id": 21,
"codec": {
"codec_name": "pcm_mulaw",
"codec_type": "audio",
"sample_rate": 8000
},
"parent": 20
}
]
}
]
}
Well. As usual. Awful RTSP realisation from noname camera.
#media=video
)Contacts in github profile
Hi, I have the same outdoor PA4 camera and go2rtc works fine without any special settings.
But another model of the indoor camera H42 of the same manufacturer also doesn't work. So, I think there might be something wrong with the firmware. I have already contacted AliExpress seller and will forward the information to their technician. No more details at this time. What firmware version do you have?
This works: Device Type: PA4 Uboot Version: uboot-2016-20 Kernel Version: linux-4.9-12 Software Version: V1.12.37-20240124
This doesn't work: Device Type: H42 Uboot Version: uboot-2016-14 Kernel Version: linux-4.9-15 Software Version: V1.14.10-20240725
Hi, just a fresh update. I've just downgraded the firmware of my H42 to the version below and go2rtc started work like a charm.
This older firmware also works: Device Type: H42 Uboot Version: uboot-2016-12 Kernel Version: linux-4.9-14 Software Version: V1.11.91-20231116
So, I recommend you contact Ali seller or checking official website for a fixed firmware. IPC Software Download: https://www.vatilon.com/ipcrjxz
I had the same issue and just upgraded my H42 to the latest H42-H43-v1.14.48-20240903 and it resolved the issue.
I have the same issue with a PB4 camera running software version V1.14.10-20240725. Trying to get an earlier firmware but no luck so far.
Hi
I have an AliExpress IPcam model Vatilon PA4. I can view the stream succesfully with VLC, but go2rtc/Frigate won't work.
Any ideas where to start looking please?
VLC stream info:
I can change the main stream to h265 or lower the resolution, but I keep getting the error error="streams: wrong transport: " stream=Tuinhuis2
go2rtc stream info:
But sometimes when I click info or probe again, I get the "streams: wrong transport: "