> >I suggest using "openRTSP" as your client (give it the "-d <duration>" flag, > >to record a specific length of time). > >You should end up with a file named something like "VIDEO-H264-1". > >Rename this file to "test.h264". See whether or not you can play it using > >VLC. > >If you can't, then email it to us (if it's short) or else put it on a web > >server and send us the URL - so we can inspect it ourselves. > > Ok, OpenRTSP works, provided I use the –b option to bump up the input buffer > to handle our frame size (I used –b 1000000). > VLC can then play the file produced, however it plays them about 5 times too > fast. A 10sec clip plays in 2secs, a 30sec clip plays in 5secs.
OK, because "openRTSP" - when run on your stream - generated a file that could be played by "VLC", this shows that there is nothing inherently wrong with the LIVE555-related code in your server. Whatever problem(s) that you might have are likely caused by your encoder - and thus are off-topic for this mailing list. (If you were to generate a raw H.264 video file directly from your encoder - without going through any LIVE555 server code at all - you would likely end up with the same result, when the file is played by VLC.) The problem with VLC playing your file too fast needs to be raised on a VLC mailing list, not this one. (However, I suggest that you look at how your encoder is generating frame-rate-related parameters in your stream's SPS NAL unit. Perhaps it's not setting "num_units_in_tick" and "time_scale" properly? But again, off-topic for this mailing list.) Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
