Getting Media Duration

I'm a bit lost regarding if this is for JSR135 or straight
Helix interface 
use but if you're calling Helix APIs cannot you use the
client registry to 
get the duration once "OnPresentationOpened" is
called?

JEff

At 05:52 PM 6/6/2006, Milko Boic wrote:
>At 05:40 PM 6/6/2006, Angus Huang wrote:
>>Milko,
>>
>>Are you referring specifically to this state
diagram?
>><https://helix-client.hel
ixcommunity.org/nonav/2005/devdocs/JSR-SOD-JSR135Adaptation_
files/image003.gif>https://helix-client.helixcommunity.or
g/nonav/2005/devdocs/JSR-SOD-JSR135Adaptation_files/image003
.gif 
>>
>
>Yes.
>
>>
>>In this diagram, it looks like the player will move
from the READY to the 
>>PREFETCHED state after calling
OpenURL()/OpenRequest(). Somewhere during 
>>this call, OnPosLength() should be called, however,
I don't see this 
>>happening when testing. The first call I see to
OnPosLength() is made 
>>after calling Begin(). Additionally,
OnPresentationOpened() and 
>>OnBuffering() are called after Begin() as well.
>>
>>This behavior doesn't seem to support the state
diagram. Could you 
>>clarify this for me?
>
>It does, you are just calling Begin() early (prior to
player entering 
>PREFETCHED state) which causes begin to be effectively
queued and applied 
>only when player reaches the PREFTECHED state.
>That is a proper approach if you wish to minimize
playback start-up time 
>as calling Begin() early will simply cause player to
automatically 
>transition from PREFETCHED to PLAYING state.
>
>All my comments below apply.
>
>Milko


_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev

Client registry contains ancillary information about media
not crucial for 
precise player control.  It is an optional component of the
engine.
Duration of the media is fundamentally needed for precise
player control 
and would be very inadvisable for an application to rely on
presence of 
registry to achieve it.  If that was indeed needed we would
need to take 
corrective action.

OnPosLength is reported prior to OnPresentationOpened().

Milko


At 05:21 PM 6/7/2006, Jeff Ayars wrote:
>I'm a bit lost regarding if this is for JSR135 or
straight Helix interface 
>use but if you're calling Helix APIs cannot you use the
client registry to 
>get the duration once "OnPresentationOpened"
is called?
>
>JEff
>
>At 05:52 PM 6/6/2006, Milko Boic wrote:
>>At 05:40 PM 6/6/2006, Angus Huang wrote:
>>>Milko,
>>>
>>>Are you referring specifically to this state
diagram?
>>><https://helix-client.hel
ixcommunity.org/nonav/2005/devdocs/JSR-SOD-JSR135Adaptation_
files/image003.gif>https://helix-client.helixcommunity.or
g/nonav/2005/devdocs/JSR-SOD-JSR135Adaptation_files/image003
.gif 
>>>
>>
>>Yes.
>>
>>>
>>>In this diagram, it looks like the player will
move from the READY to 
>>>the PREFETCHED state after calling
OpenURL()/OpenRequest(). Somewhere 
>>>during this call, OnPosLength() should be
called, however, I don't see 
>>>this happening when testing. The first call I
see to OnPosLength() is 
>>>made after calling Begin(). Additionally,
OnPresentationOpened() and 
>>>OnBuffering() are called after Begin() as well.
>>>
>>>This behavior doesn't seem to support the state
diagram. Could you 
>>>clarify this for me?
>>
>>It does, you are just calling Begin() early (prior
to player entering 
>>PREFETCHED state) which causes begin to be
effectively queued and applied 
>>only when player reaches the PREFTECHED state.
>>That is a proper approach if you wish to minimize
playback start-up time 
>>as calling Begin() early will simply cause player to
automatically 
>>transition from PREFETCHED to PLAYING state.
>>
>>All my comments below apply.
>>
>>Milko
>



_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev

At 06:51 PM 6/7/2006, Milko Boic wrote:

>Client registry contains ancillary information about
media not crucial for 
>precise player control.  It is an optional component of
the engine.
>Duration of the media is fundamentally needed for
precise player control 
>and would be very inadvisable for an application to rely
on presence of 
>registry to achieve it.  If that was indeed needed we
would need to take 
>corrective action.

Interesting position.  Given the lack of standardization and
planning 
regarding what is in the registry, I probably agree.

>OnPosLength is reported prior to OnPresentationOpened().

I didn't realize that.  It's a good thing as it solves
this problem, but I 
would not have expected it to be called until after Begin
was called based 
on the name of the method and it's implied semantics.

JEff

>Milko
>
>
>At 05:21 PM 6/7/2006, Jeff Ayars wrote:
>>I'm a bit lost regarding if this is for JSR135 or
straight Helix 
>>interface use but if you're calling Helix APIs
cannot you use the client 
>>registry to get the duration once
"OnPresentationOpened" is called?
>>
>>JEff
>>
>>At 05:52 PM 6/6/2006, Milko Boic wrote:
>>>At 05:40 PM 6/6/2006, Angus Huang wrote:
>>>>Milko,
>>>>
>>>>Are you referring specifically to this state
diagram?
>>>><https://helix-client.hel
ixcommunity.org/nonav/2005/devdocs/JSR-SOD-JSR135Adaptation_
files/image003.gif>https://helix-client.helixcommunity.or
g/nonav/2005/devdocs/JSR-SOD-JSR135Adaptation_files/image003
.gif 
>>>>
>>>
>>>Yes.
>>>
>>>>
>>>>In this diagram, it looks like the player
will move from the READY to 
>>>>the PREFETCHED state after calling
OpenURL()/OpenRequest(). Somewhere 
>>>>during this call, OnPosLength() should be
called, however, I don't see 
>>>>this happening when testing. The first call
I see to OnPosLength() is 
>>>>made after calling Begin(). Additionally,
OnPresentationOpened() and 
>>>>OnBuffering() are called after Begin() as
well.
>>>>
>>>>This behavior doesn't seem to support the
state diagram. Could you 
>>>>clarify this for me?
>>>
>>>It does, you are just calling Begin() early
(prior to player entering 
>>>PREFETCHED state) which causes begin to be
effectively queued and 
>>>applied only when player reaches the PREFTECHED
state.
>>>That is a proper approach if you wish to
minimize playback start-up time 
>>>as calling Begin() early will simply cause
player to automatically 
>>>transition from PREFETCHED to PLAYING state.
>>>
>>>All my comments below apply.
>>>
>>>Milko
>
>


_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev

At 09:12 PM 6/7/2006, Jeff Ayars wrote:
>At 06:51 PM 6/7/2006, Milko Boic wrote:
>
>>Client registry contains ancillary information about
media not crucial 
>>for precise player control.  It is an optional
component of the engine.
>>Duration of the media is fundamentally needed for
precise player control 
>>and would be very inadvisable for an application to
rely on presence of 
>>registry to achieve it.  If that was indeed needed
we would need to take 
>>corrective action.
>
>Interesting position.  Given the lack of standardization
and planning 
>regarding what is in the registry, I probably agree.

We invest in our standardization and planning where it
matters most given 
high ratio of work to capacity.  We have a consistent
message about what 
the registry is for and what type information it contains. 
I would not 
call that lack of planning and standardization.


>>OnPosLength is reported prior to
OnPresentationOpened().
>
>I didn't realize that.  It's a good thing as it solves
this problem, but I 
>would not have expected it to be called until after
Begin was called based 
>on the name of the method and it's implied semantics.

OnPosLength() reports position and length of the content. 
The name does 
not imply when this information is provided. This is
document in Helix DNA 
Client State machine. OnPosLength is initially reported when
client lands 
into connected state.  In connected state the properties of
the content 
have been acquired (possibly from the server) and client is
capable of 
providing information about the content.  In opened state 
(OnPresentationOpened()), the scarce system resource are
allocated such as 
audio device and client is in full readiness for playback in
terms of 
allocated resources.  Next phase is prefetch...

Milko


>JEff
>
>>Milko
>>
>>
>>At 05:21 PM 6/7/2006, Jeff Ayars wrote:
>>>I'm a bit lost regarding if this is for JSR135
or straight Helix 
>>>interface use but if you're calling Helix APIs
cannot you use the client 
>>>registry to get the duration once
"OnPresentationOpened" is called?
>>>
>>>JEff
>>>
>>>At 05:52 PM 6/6/2006, Milko Boic wrote:
>>>>At 05:40 PM 6/6/2006, Angus Huang wrote:
>>>>>Milko,
>>>>>
>>>>>Are you referring specifically to this
state diagram?
>>>>><https://helix-client.hel
ixcommunity.org/nonav/2005/devdocs/JSR-SOD-JSR135Adaptation_
files/image003.gif>https://helix-client.helixcommunity.or
g/nonav/2005/devdocs/JSR-SOD-JSR135Adaptation_files/image003
.gif 
>>>>>
>>>>
>>>>Yes.
>>>>
>>>>>
>>>>>In this diagram, it looks like the
player will move from the READY to 
>>>>>the PREFETCHED state after calling
OpenURL()/OpenRequest(). Somewhere 
>>>>>during this call, OnPosLength() should
be called, however, I don't see 
>>>>>this happening when testing. The first
call I see to OnPosLength() is 
>>>>>made after calling Begin().
Additionally, OnPresentationOpened() and 
>>>>>OnBuffering() are called after Begin()
as well.
>>>>>
>>>>>This behavior doesn't seem to support
the state diagram. Could you 
>>>>>clarify this for me?
>>>>
>>>>It does, you are just calling Begin() early
(prior to player entering 
>>>>PREFETCHED state) which causes begin to be
effectively queued and 
>>>>applied only when player reaches the
PREFTECHED state.
>>>>That is a proper approach if you wish to
minimize playback start-up 
>>>>time as calling Begin() early will simply
cause player to automatically 
>>>>transition from PREFETCHED to PLAYING state.
>>>>
>>>>All my comments below apply.
>>>>
>>>>Milko
>>
>



_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev