I have a server-side module that is triggered when the write is complete that moves the resulting MP4 file into a specific directory depending on the stream name. This all seems to work fine IF I use something like ffmpeg to send the stream, e.g.:
However, when our client (using their application) tries it, the live stream occurs, you can watch it live, but when it's over the system writes an FLV file and never writes the MP4 file. I'm not sure if my module is ever triggered. Their application is iPhone based, I don't know what libraries they're using.
Any ideas? Could this be the application versus application instance (stream name) problem? I thought that only affected VOD playback.
Can you please confirm that your custom module is writing the FLV file to a specified directory, or if the file is being saved to the [install-dir]/content directory.
If you are running a Wowza version previous to Wowza 4.x, and the custom module is working as expected but not creating an .mp4, it could be because previous versions of Wowza recorded to .flv. You can specify the recordings be saved to .mp4 by editing
[install-dir]/conf/Server.xml and change:
There is no "DefaultStreamPrefix" property in any of the XML config files on our server, and no "<Streams></Streams>" stanza in Server.xml, so I'm not sure where to put this. Should it go in the application's Application.xml file?
to the library and it would split things at the last "/". Everything before that was the application name, and everything after it was the stream name. Hence the stream name wasn't prefixed by "mp4:", so it wrote FLV files. They got a beta version of the library and now they can specify the application and stream name and things are good as far as that's concerned.
We've hit another problem. I use the above publishing URL to have ffmpeg stream my web camera. I then try to watch the live streams.
Using an OSMF player to play "http://ourserver/rtmplive/_definst_/NewLayout/ricktest06/manifest.f4m" seems to work (although there is a huge delay...possibly something from ffmpeg). However, if I try to play "http://ourserver/rtmplive/_definst_/NewLayout/ricktest06/playlist.m3u8" using Safari on a Macbook Air, I get the m3u8 file, but we get 404s on the chunklists associated with it and the m3u8 file itself has a MIME type of "application/vnd.apple.mpegurl" (which Safari can't handle).
Am I doing something wrong here? What would be correct live URLs for people to watch the streams?