suppose that in a live media stream, the f4m descriptor just contains the following:
<?xml version="1.0" encoding="utf-8"?>
The official Strobe Player can’t handle this situation (see answers to comments in http://www.osmf.org/dev/1.5gm/setup.html, I tried Strobe 1.5 and I get an error when connecting) so I wonder if this is a general issue with OSMF, as I haven’t been able to make it work with my own OSMF-based player (I tried both 1.6.1 and 2.0).
On the other hand in my attempts, after Flash Media Live Encoder has started streaming and the Wowza server fills the f4m descriptor with media-related data, I can load Strobe or my own OSMF-based player and the playback starts without problems.
<bootstrapInfo id="bootstrap478000" profile="named" url="playlist_b478000_w478000.abst" />
<media bootstrapInfoId="bootstrap478000" width="480" height="360" bitrate="466" url="media_b478000_w478000.abst/">
So my conclusion is: currently I must not open the player before the event starts (which I cannot know in advance of course), or it will find an empty f4m and will get stuck unless the web page embedding it gets reloaded.
Is there a way to solve it? I tried with OSMF 1.6.1 and OSMF 2 in my custom player and strobe 1.5 .
the bugbase has moved to https://bugbase.adobe.com/
AMS usually populates the needed fields with correct information - therefore the tests did not cover the wowza "empty" non-standard f4ms.
As a workaround, I would suggest a web page that would allow access to the stream only after the stream starts, otherwise showing a "plate". This could be done either server-side or in JS.
Hi Silviu, thanks for your opinion.
so if i use adobe media server istead of wowza server osfm should be able to "wait for encoding starts" ? in other words i can open the player and AFTER starts to encode with adobe media live encoder to an adobe media server and the player will works?
and there are hopes that wowza "empty" descriptor will be hadle by osmf framework?