Invalid fourCC with DJI RTMP stream

[Alphalynxjet]

Which version are you using?

v1.1.0

Which operating system are you using?

• [X ] Linux amd64 standard
• Linux amd64 Docker
• Linux arm64 standard
• Linux arm64 Docker
• Linux arm7 standard
• Linux arm7 Docker
• Linux arm6 standard
• Linux arm6 Docker
• Windows amd64 standard
• Windows amd64 Docker (WSL backend)
• macOS amd64 standard
• macOS amd64 Docker
• Other (please describe)

Describe the issue

Trying to stream a RTMP video feed from a DJI drone using DJI Fly app. The Mediamtx server is hosted on Ubuntu 22, here is the status log.

Describe how to replicate the issue

Stream from a DJI Mini using DJI fly app to the Mediamtx server.

Did you attach the server logs?

yes

Sep 22 17:28:21 mediamtx[112677]: 2023/09/22 17:28:21 INF [RTMP] [conn 100.100.17.2:39826] opened
Sep 22 17:28:22 mediamtx[112677]: 2023/09/22 17:28:22 INF [RTMP] [conn 100.100.17.2:39826] closed: invalid fourCC: 4294899479
Sep 22 17:28:22 mediamtx[112677]: 2023/09/22 17:28:22 INF [RTMP] [conn 100.100.17.2:39828] opened
Sep 22 17:28:23 mediamtx[112677]: 2023/09/22 17:28:23 INF [RTMP] [conn 100.100.17.2:39828] closed: invalid fourCC: 4294928407
Sep 22 17:28:23 mediamtx[112677]: 2023/09/22 17:28:23 INF [RTMP] [conn 100.100.17.2:39830] opened
Sep 22 17:28:24 mediamtx[112677]: 2023/09/22 17:28:24 INF [RTMP] [conn 100.100.17.2:39830] is publishing to path 'dji', 1 track (MPEG-4 Audio)
Sep 22 17:28:24 mediamtx[112677]: 2023/09/22 17:28:24 INF [RTMP] [conn 100.100.17.2:39830] closed: invalid fourCC: 4294896919
Sep 22 17:28:24 mediamtx[112677]: 2023/09/22 17:28:24 INF [RTMP] [conn 100.100.17.2:39832] opened
Sep 22 17:28:25 mediamtx[112677]: 2023/09/22 17:28:25 INF [RTMP] [conn 100.100.17.2:39832] closed: invalid fourCC: 4294918167
Sep 22 17:28:25 mediamtx[112677]: 2023/09/22 17:28:25 INF [RTMP] [conn 100.100.17.2:39834] opened
root@:~# systemctl status mediamtx.service

Did you attach a network dump?

no

[aler9]

Hello, were you publishing audio only or both video and audio?

Furthermore, please provide If a dump of the data exchanged between the server and the target (network dump), that can be generated in this way:

1. Download wireshark (https://www.wireshark.org/)
2. Start capturing on the interface used for exchanging RTSP (if the server and the target software are both installed on your pc, the interface is probably "loopback", otherwise it's the one of your network card)
3. Start the server and replicate the issue
4. Stop capturing, save the result in .pcap format
5. Attach

[abhemanyus]

I'm publishing a video-only stream, and getting the same error.
Here's the wireshark log, recorded from before the server was started, then the livestream was started and stopped, the server was stopped, and then the recording was stopped. The error message was the following:
2023/11/14 10:20:44 INF [RTMP] [conn 14.97.37.70:41600] opened 2023/11/14 10:20:45 INF [RTMP] [conn 14.97.37.70:41600] closed: invalid fourCC: 1493468439 2023/11/14 10:20:45 INF [RTMP] [conn 14.97.37.70:41602] opened 2023/11/14 10:20:45 INF [RTMP] [conn 14.97.37.70:41602] closed: invalid fourCC: 1493628439 2023/11/14 10:20:45 INF [RTMP] [conn 14.97.37.70:41604] opened 2023/11/14 10:20:46 INF [RTMP] [conn 14.97.37.70:41604] closed: invalid fourCC: 1493788183 2023/11/14 10:20:46 INF [RTMP] [conn 14.97.37.70:41606] opened
log.txt

[aler9]

Hello, this should be fixed by #2808. Please test this nightly release and let me know if it works (click on artifacts, binaries):
https://github.com/bluenviron/mediamtx/actions/runs/7207849258

[github-actions]

This issue is mentioned in release v1.4.1 🚀
Check out the entire changelog by clicking here

[github-actions]

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.