The first playlist item that is played on Stream1 is set to play at 14:00 (2pm) today, but you started the server at 22:43, which is 10:43pm, so that starts right away because the scheduled start time is in the past. That item plays for 5 seconds, which is the length setting, and repeat is set to “false”, so you will have to be very quick to catch that. The next one starts at 15:00 (3pm) which is also in the past. That should start as soon as the first item is done (in 5 seconds) because it is also in the past.
12/5/2012 22:43:04 IST comment server INFO 200 - scheduled playlist: Stream1 on stream: Stream1 for:Wed Dec 05 14:00:00 IST 2012
It seems that Maula.mp4 is not in the content folder:
Stream.switch[live/_definst_/Stream2]: index: 0 name:mp4:Maula.mp4 start:0 length:-1
ServerListenerStreamPublisher Scheduled stream is now live: Stream2
ServerListenerStreamPublisher Get Item error: null
ServerListenerStreamPublisher Get Item error: null
ServerListenerStreamPublisher Get Item error: null
I would start very simply. Get it to work with sample.mp4 or another file you know is there. Set the schedule in the past and repeat=true with a single stream (Stream1) so you don’t have to race to play it back. Then try setting in the future, but not too far in the future. The scheduling is extremely precise, it will start the very second you set it to start per your server’s system clock.
The length attribute is seconds. “-1” means play the file to the end
Try this schedule:
<smil>
<head>
</head>
<body>
<stream name="Stream1"></stream>
<playlist name="p1" playOnStream="Stream1" repeat="true" scheduled="2012-12-05 14:00:00">
<video src="mp4:sample.mp4" start="0" length="-1"/>
</playlist>
</body>
</smil>
Now playback in Flash example:
Server: rtmp://[wowza-address]:1935/live
Stream: Stream1
Also, it is extremely helpful to run Wowza in stand-alone (/bin/startup.bat) mode so that you can see log output in the console.
Richard