Ok, sorry all, never mind. I got it all figured out and although I know many people will think this is ridiculous and unecessary, I wanted to see if I could make this work.
My original intention was to be able to livestream back to a server in my home office from the DJI Fly app. This way I could have a "black box" record of all video my drone has ever taken as it is happening live, complete with audio from the controller app. As I was setting this up, it also helped me realize that this is a great solution for pushing RTMP to multiple sources, Youtube, Facebook etc and all at the same time. (No, I do not have an audience for it, but just wanted to see how it would be done.)
Alternatively, anyone with a RTSP player from their mobile device could also receive the stream as well. Anyways, turns out it is pretty easy to set-up.
I have an extra windows host that I use to run Flight reader and a few other windows only apps so I did this one on Windows, but should work same way on Linux.
Downloaded nginx 1.7.11.3 gryphon - this is the version for Windows that includes the RTSP module.
In the nginx.conf file, updated the rtmp section to include:
rtmp {
server {
listen 1935;
chunk_size 4096;
application live {
live on;
record all;
record_unique on;
#record all;
record_path d:/nginx/recordings;
# To push to multiple locations, uncomment lines below and substitute in your RTMP URI and stream key
# push rtmp://server/path/streamkey;
# push rtmp://server/path/streamkey;
# HLS options below
#hls on;
#hls_path /http/directory/;
#hls_fragment 3;
#hls_playlist_length 60;
#hls_continuous on;
}
}
After that, and verified that nginx starts ok, and could write to the recordings directory I pointed it to, I had to set some port forwarding. RTSP is tcp port 1935 so pointed that to the windows box running nginx.
And finally, configure the transmission section on the DJI Fly app with your URL.
rtmp://youraddress_or_ip/live/streamname
I like the idea that should I want to stream live it's going to a server and storage I control.
