>Hi!
>
[quoted text clipped - 5 lines]
>
>It is a valid feature according to the documentation, but
Please provide a link to that documentation, I can't see that syntax
listed anywhere.
>it appears that wallclock tags the already played element and does
>not considers it again. This taging is shown in case of wallclock
>without the date information, which does not trigger on the next
>day (or the following days) automatically.
That should run if you had only a single wallclock element, following
the defined syntax, which contained only a time but not a date.
>> There's no listing of multiple attribute values for begin with a
>> semicolon separator. Nor can you expect to combine begin and end
[quoted text clipped - 8 lines]
>I think that:
>- multiple wallclocks statements inside begin should be working fine.
No.
>- wallclock statements without the date information should be
>repeating each day.
Yes.
>Now I have to write a short program to generate the playlist
>for the next month with hundreds of entries instead of only 8,
>which could be written manually, if the wallclock would be
>working correctly.
OK so that's pretty simple using any old XML parser ;-)
Cheers - Neil
------------------------------------------------
Digital Media MVP : 2004-2008
http://mvp.support.microsoft.com/mvpfaqs
Atmapuri - 23 Jan 2008 08:17 GMT
Hi!
>>I think that:
>>- multiple wallclocks statements inside begin should be working fine.
>
> No.
There is no link on the web, but this you can read in the Help file
of Windows Media services for the begin attribute:
"
An element can be activated relative to the timing of other elements in the
playlist or by a server event. You can use the begin attribute with a list
of semicolon-delimited event values to identify multiple times when the
element should be played; for example begin="event1;event2;event3". Negative
time values and time values that are shorter in duration than the length of
the element are ignored. For complete information about the supported begin
attribute values, see Timing values
"
>>- wallclock statements without the date information should be
>>repeating each day.
>
> Yes.
It is explicitely stated in the docs that this does not work,
so that is a feature feature request :)
From the wallclock help in the Windows Media Service help file:
"
The wallclock value is set when the playlist is loaded into memory. For
broadcast publishing points, this occurs when the publishing point is
started; for on-demand publishing points, this occurs when a client begins
streaming the playlist. Dynamic changes to the playlist, either
programmatically or through the Windows Media Playlist Editor, are ignored
until the playlist is loaded into memory again.
If a playlist has remained in memory for more than a day, and the wallclock
value does not have a date value assigned to it, the playlist must be loaded
into memory again before that wallclock value is acknowledged. For example,
if a broadcast publishing point references a playlist with a media element
set to begin streaming at 12:30 PM, the publishing point must be restarted
before 12:30 PM the following day to honor that wallclock value again.
"
Please file both !!!
Thanks!
Atmapuri
Neil Smith [MVP Digital Media] - 24 Jan 2008 21:12 GMT
>Hi!
>
[quoted text clipped - 40 lines]
>set to begin streaming at 12:30 PM, the publishing point must be restarted
>before 12:30 PM the following day to honor that wallclock value again.
OK fair point - I rememeber the second one, I wasn't aware of the
first one, I guess it's time I dug out those dusty old help docs ;-)
It's something I can try here over the weekend, if I can't work out
what's up I'll see if there's alternative syntax.
At a push I could try to ask somebody to review the help docs, but
since they're shipped with systems about the only clarification that
could happen would be with the online docs I guess
HTH
Cheers - Neil
------------------------------------------------
Digital Media MVP : 2004-2008
http://mvp.support.microsoft.com/mvpfaqs