"closed: metadata doesn't contain any track" (DJI FlightHub Sync - Stream Forwarding)
JacekKosciesza opened this issue · comments
Which version are you using?
v1.8.0
Which operating system are you using?
- 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
I've a DJI Mavic 3E drone connected to DJI FlightHub 2 drone management platform. It has a new functionality FlightHub Sync which allows you to transfer livestream data (stream forwarding) to a 3rd party using RTMP. I was able to initiate this stream forwarding to MediaMTX (running in Amazon Lightsail), but I get closed: metadata doesn't contain any track error.
2024/04/23 14:07:39 INF [RTMP] [conn 121.22.238.96:1219] opened
2024/04/23 14:07:40 DEB [path 1581F5FHD238P00DVX4S_66-0-0] created
2024/04/23 14:07:40 DEB [path 1581F5FHD238P00DVX4S_66-0-0] destroyed: not in use
2024/04/23 14:07:40 INF [RTMP] [conn 121.22.238.96:1219] closed: metadata doesn't contain any track
Describe how to replicate the issue
Replication is complicated - involves real DJI drone, configuration of DJI FlightHub 2 account, calling DJI API to start livestream etc. I will include logs and network dump, maybe someone will be able to verify on which side is a problem and maybe there is some workaround.
Did you attach the server logs?
yes
Did you attach a network dump?
yes
@JacekKosciesza we're also using mediamtx with the DJI Docks except in our case we're publishing direct from the dock to mediamtx using RTMP. We haven't seen this issue so I suspect the problem is the republish from FlightHub.
I tried the same thing with Ant Media Server and it worked. I was able to see the livestream from the drone:
