You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TypeError: Cannot read property 'videoData' of undefined
at RTSPServer.onInterleavedRTPPacketFromClient (/root/node-rtsp-rtmp-server/rtsp.coffee:803:59)
at RTSPServer.handleOnData (/root/node-rtsp-rtmp-server/rtsp.coffee:842:8)
at Socket. (/root/node-rtsp-rtmp-server/rtsp.coffee:452:12)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at TCP.onread (net.js:607:20)
This seems to happen when a new stream is published. It doesn't happen all the time but does happen frequently enough to be an issue.
Thanks in advance,
~Jazzy
The text was updated successfully, but these errors were encountered:
Hi,
I'm having trouble with RTPS in particular, seems over a high latency connection (say, 100~ms between FFMPEG in the EU and the server in the US)
I was originally having an AAC error were the packet would be larger then the limit, but setting AAC to strict 2 in FFMPEG seems to have fixed that.
The current error is:
2020-09-23 02:38:19.337 [rtsp/http:client=c7] connected
/root/node-rtsp-rtmp-server/server.coffee:46
throw err;
^
TypeError: Cannot read property 'videoData' of undefined
at RTSPServer.onInterleavedRTPPacketFromClient (/root/node-rtsp-rtmp-server/rtsp.coffee:803:59)
at RTSPServer.handleOnData (/root/node-rtsp-rtmp-server/rtsp.coffee:842:8)
at Socket. (/root/node-rtsp-rtmp-server/rtsp.coffee:452:12)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at TCP.onread (net.js:607:20)
This seems to happen when a new stream is published. It doesn't happen all the time but does happen frequently enough to be an issue.
Thanks in advance,
~Jazzy
The text was updated successfully, but these errors were encountered: