mediamtx
mediamtx copied to clipboard
DJI Osmo Action 4: Audio track not set up (RTMP)
Which version are you using?
v1.9.0
Which operating system are you using?
- [ ] Linux amd64 standard
- [x] 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
When starting an RTMP stream with the DJI Osmo Action 4, a lot of times MediaMTX will immediately terminate the stream as the audio track is not set up but an audio packet is received.
When configuring a live stream, the DJI app offers the following options:
- Resolution
- 480p (smooth)
- 720p (HD)
- 1080p (UHD)
- Streaming Quality
- Auto
- Smooth
- HD
- EIS (Stabilization)
- Off
- Various modes of "Rocksteady"
Pretty much any configuration will result in this error, but from experience setting 1080p/HD will, most of the time, result in MediaMTX actually setting up an audio track and the stream actually working.
Curiously, once one successful attempt has been made, relaunching the livestream with a different configuration will work as well.
The camera is running with the following firmware versions:
Firmware: 01.04.07.10
Camera Firmare: 10.04.00.10
(Not sure why there's two)
Describe how to replicate the issue
- Start server
- Initiate RTMP live stream on camera
- MediaMTX recognizes a connection but won't set up an audio track
- The stream terminates
Did you attach the server logs?
yes (Excerpts)
Instance of a failed stream:
INF [RTMP] [conn 172.18.0.1:34254] opened
INF [RTMP] [conn 172.18.0.1:34242] is publishing to path 'glide', 1 track (H264)
INF [RTMP] [conn 172.18.0.1:34242] closed: received an audio packet, but track is not set up
Instance of a successful stream:
INF [RTMP] [conn 172.18.0.1:47558] opened
INF [RTMP] [conn 172.18.0.1:47558] is publishing to path 'glide', 2 tracks (H264, MPEG-4 Audio)
Did you attach a network dump?
Attached are multiple dumps, mostly failed ones and with different quality configurations.
A dump of a successful stream has also been attached.
I'm not sure if there's actually any meaningful difference between the failed dumps, but I attached them nonetheless. dumps.zip