Amvya,
Could you send me the h263 file or link, and the log file?
It's not obvious
that it is a
Helix/JSR135 problem, since you can play other datatypes.
You might also want
to update your jsr135 sources and rebuild, just to make sure
that we aren't
debugging
something that has already been fixed.
--christina
At 05:04 AM 6/14/2006, Amvya Patel wrote:
>We are using java application to play h263,amr and aac
files through
>Helix DNA Client v3.0 - Atlas. we are able to play aac
and amr files.
>But while we are trying to play h263 file it is getting
blocked in
>Realize state. _Player::realizeFunc()
>is getting called and m_pRequest->SetURL(m_url)
by this function
>url is getting set, then
>
>pRequestContext->SetRequester((IHXDataFile*)m_pDataSo
urceAdapter)
>requester is called but at the end of realizeFunc() it
gets stuck.
>but when we are able to realize smaller h263 file it
gets stuck in
>Starting state.
>
>can u suggest how to get it realized.
>
>
>On 5/9/06, Christina Dunn <cdunn real.com> wrote:
>>At 02:26 AM 5/6/2006, Amvya Patel wrote:
>> >Hi,
>> >
>> >As per
>> >https://helix-client.helixcommunity.org/
nonav/2005/devdocs/JSR-SOD-JSR13
>> 5Adaptation.html
>> >section 2.4.1. createPlayer:
>> >
>> >"Middleware layer will have to cache
different input designations
>> >until the player is transitioned through
realized state as Helix DNA
>> >Client takes input designation at the time of
realization."
>> >
>> >Now in the emulator I have, in java, once, I
say
>> >manager.createplayer(), the win32 callback
function createplayer() is
>> >getting called without any input designations.
[The data comes only
>> >when I say player.realize() in my java
application] The body of this
>> >win32 createplayer() is to be filled by me. I m
planning to call the
>> >helix's C++ function _manager.createplayer()
here. But helix's
>> >_manager.createplayer() needs input
designations where as I m going to
>> >get it only when I say player.realize in my
java application. The
>> >input designation caching is taken care by the
emulator VM.
>> >
>> >Can I pass dummy input designation while
calling
>> >_manager.createplayer() and correct the value
before calling
>> >_palyer.realize()?? I understand from your
design that till
>> >_palyer.realize() is called this data is just
cached and not used in
>> >helix also.
>>
>>You could implement the following to achieve the
above :
>>
>>Add the 'setUrl' method to the _Player object :
>> HX_RESULT _Player::setUrl(char* url)
>> {
>> if (m_state == UNREALIZED) {
>> m_url = url;
>> return HXR_OK;
>> }
>> return HXR_FAIL;
>> }
>>
>>So, call createPlayer, then 'setUrl', then
'realize'.
>>This is out of scope for JSR135, but you can add the
above for your player.
>>
>>--christina
>>
>>
>> >Amvya
>>
>>
_______________________________________________
Helix-client-dev mailing list
Helix-client-dev helixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev
|