I regularly use an EC2 WMS instance to stream a video to visitors and allow them to use a text chat at certain dates and times (like a TV station that's on air occasionally). I start a new standard instance for each streaming session and use the startup package to configure it for my needs.
I'm using ami-5a649833 (WMS v 2.2.4) and it works well.
I tried upgrading to WMV v3.0.3.07 (ami-93824afa), and with this version I encounter two problems. I tried using the old startup file and I tried a new v3 startup file (adjusted for my configuration), and the problems are the same both times.
The first issue is that the textchat module doesn't seem to be part of the standard EC2 configuration. The error log contains the following entry:
Can you fix that or do I need to change something to have the textchat available again?
loadModFunctions[textchat/_definst_]: Module class not found or could not be loaded. Check [install-dir]/conf/textchat/Application.xml to be sure all Modules/Module/Class paths are correct: name:textchat class:com.wowza.wms.plugin.textchat.ModuleTextChat
The second issue is related to streamschedule.smil.
I use the streamscheduler and the .smil file to start the video at a certain time.
As I start the server before the actual video is going to start, I have two entries in the streamschedule.smil, one for a fillervideo that starts immediately and a second for the actual video that starts at the intended time. Here is an example:
I accidentally discovered that I could specify a non-existent video for the filler video. In that case the player just sat there with a black screen with the little circle rotating in it, and the actual video would start playing at the time scheduled for it.
<playlist name="pl1" playOnStream="video" repeat="true" scheduled="2011-12-03 00:00:00">
<video src="mp4:fillervideo.mp4" start="0" length="-1"/>
<playlist name="pl2" playOnStream="video" repeat="false" scheduled="2011-12-03 13:20:00">
<video src="mp4:actualvideo.mp4" start="0" length="-1"/>
This was an ideal behavior for my purposes.
If I didn't specify a filler video the actual video wouldn't start automatically.
If I used a real filler video, it was very challenging to give it exactly the same encoding attributes, and if there were differences, the actual video would not start automatically any more. And the filler video would use bandwidth for nothing.
With WMS v3 the behavior is different. When I specify a non-existent fillervideo, the server switches to the actualvideo immediately and starts to play it, without waiting for the scheduled time.
Could you reinstate the old behavior? If you don't want to do that for any reason, could you at least make the old behavior available through a configuration option?