Nao Iizuka

Hmm, unfortunately it seems impossible. Linux implementation of fs.watchFile() uses libev, and libev uses inotify. In this case, inotify's IN_CLOSE_WRITE is the best possible event for saving a file in...

@adamwuli03 Thanks for using node-rtsp-rtmp-server! To change the server port, open config.coffee with a text editor and replace `serverPort: 80` at [line 9](https://github.com/iizukanao/node-rtsp-rtmp-server/blob/d9fbcec0b849c9626ca0fc03290803cddcdb6ba9/config.coffee#L9) with a port you want to use,...

@Anish009 127.0.0.1 is the IP address of localhost. If you want to publish stream from ffmpeg to node-rtsp-rtmp-server running on the same machine by IP address, please replace rtsp://localhost:80/live/stream with...

@Classsic Thanks for your message! Is this what you want to do? 1. Client requests node-rtsp-rtmp-server to play an RTSP stream. 2. node-rtsp-rtmp-server immediately launches ffmpeg, then ffmpeg receives a...

@Classsic When client requests rtsp://server-ip:80/live/test-stream-id, the client first sends DESCRIBE to server and respondDescribe method in rtsp.coffee is called. You can launch ffmpeg in respondDescribe method and set ffmpeg's output...

That's impossible with node-rtsp-rtmp-server alone. Use ffmpeg to relay your stream from node-rtsp-rtmp-server to YouTube Live.

I don't know much about the effectiveness, but I think ffmpeg is easier to setup than nginx.

@frankville Hi, thanks for your interest! I'm not sure if I understand the former question correctly. node-rtsp-rtmp-server does not support relaying. As for the latter question, in rtsp.coffee, `respondPlay` method...

Really sorry for the delay! Currently, there is no fixed plans to add support for other codecs. If you don't mind, could you please tell me which codec would you...

@Classsic You can effectively set the limit of a packet size by changing the maximum size of single NAL unit at `SINGLE_NAL_UNIT_MAX_SIZE = 1358` in rtsp.coffee. However, why do you...