Open Novex opened 5 years ago
I just saw the following error on Node-Media-Server 2.1.2 after a 6h 47m stream over LAN with a GoPro Hero 7:
7/22/2019 23:44:40 10208 [ERROR] rtmp packet parse error. { header: { fmt: 0, cid: 43, timestamp: 3769403, length: 539464, type: 56, stream_id: 2326294421 }, clock: 0, payload: null, capacity: 0, bytes: 0 } 7/22/2019 23:44:40 10208 [INFO] [rtmp publish] Close stream. id=W2TVZGH4 streamPath=/gopro/ streamId=1 7/22/2019 23:44:40 10208 [INFO] [rtmp disconnect] id=W2TVZGH4 7/22/2019 23:44:40 10208 [ERROR] rtmp packet parse error. { header: { fmt: 0, cid: 10, timestamp: 10452295, length: 8430360, type: 69, stream_id: 1198454657 }, clock: 0, payload: null, capacity: 0, bytes: 0 } 7/22/2019 23:44:40 10208 [ERROR] rtmp packet parse error. { header: { fmt: 2, cid: 10, timestamp: 16202377, length: 8430360, type: 69, stream_id: 1198454657 }, clock: 10452295, payload: <Buffer fc 83 6e c7 93 70 68 e7 52 26 d7 a3 ca 32 08 66 84 86 65 94 07 af 21 0b a1 6b bf 7a a5 f6 36 fe 24 14 44 40 04 30 bb d4 f5 26 4b de ec ca c0 75 33 ba ... >, capacity: 8431384, bytes: 128 } 7/22/2019 23:44:40 10208 [ERROR] Unknown field 22 7/22/2019 23:44:40 10208 [ERROR] uncaughtException TypeError: Cannot read property 'value' of null at Object.decodeAMF0Cmd [as decodeAmf0Cmd] (C:\Users\Seb\Development\gopro-node-media-server\node_modules\node-media-server\node_core_amf.js:1015:18) at NodeRtmpSession.rtmpInvokeHandler (C:\Users\Seb\Development\gopro-node-media-server\node_modules\node-media-server\node_rtmp_session.js:810:29) at NodeRtmpSession.rtmpHandler (C:\Users\Seb\Development\gopro-node-media-server\node_modules\node-media-server\node_rtmp_session.js:550:21) at NodeRtmpSession.rtmpChunkRead (C:\Users\Seb\Development\gopro-node-media-server\node_modules\node-media-server\node_rtmp_session.js:458:18) at NodeRtmpSession.onSocketData (C:\Users\Seb\Development\gopro-node-media-server\node_modules\node-media-server\node_rtmp_session.js:283:23) at Socket.emit (events.js:198:13) at addChunk (_stream_readable.js:288:12) at readableAddChunk (_stream_readable.js:269:11) at Socket.Readable.push (_stream_readable.js:224:10) at TCP.onStreamRead (internal/stream_base_commons.js:94:17)
I'm happy to try to test and debug further, but thought you might have some ideas as to the cause or where to start looking.
Huh, happened again from the GoPro.
I'm testing another device to see if it does the same thing, otherwise I assume it's something buggy in the GoPro (definitely likely).
Hello, you found any solution to this?
I just saw the following error on Node-Media-Server 2.1.2 after a 6h 47m stream over LAN with a GoPro Hero 7:
I'm happy to try to test and debug further, but thought you might have some ideas as to the cause or where to start looking.