Re: Different ways of seeking

Please always CC a Helix list, I am not always around and
others can help.....more below...

Brian Meyerpeter wrote:
> Hi Greg,
> 
> Thanks for the explanation.  I don't have a line number as  I haven't
> built the player libs.  But the trace is as follows:
> 
> 
>> 	sonr3210.dll!07443ffc()
>  	sonr3210.dll!074483d2()
>  	pnen3260.dll!6023d235()
>  	pnen3260.dll!6023f822()
>  	pnen3260.dll!6023b0e1()
>  	pnen3260.dll!6020aa82()
>  	pnen3260.dll!6020bab3()
>  	pnen3260.dll!6022ea8d()
>  	pnen3260.dll!6022eed6()
>  	rpcl3260.dll!627e8671()
>  	rpcl3260.dll!627deb6a()
>  	rpmn3260.dll!6318318b()
> 
> 
> 
> Just a note about our datatype.  Our keyframes are very large (up to 900k)
> and are broken down into 500 byte packets.  If it was trying to stream
> them, it would be a really big job.
> 
> It works pretty well in local playback mode, but when you have the server
> on the other end is when the problems seem to occur.

Yes, if you are quick-seeking network playback, then it will cause a
great deal of network traffic.

We currently have no way to control turning quickseek on or off via
datatype. That could be added pretty easily however. Also, you could
turn it on or off depending on if the content was local or remote. Both
solutions would require some code changes.

Not sure if RP for Windows has an option to turn off quick seeking
via preferences.

--greg.


> 
> I'm wondering if we can disable quickseek for particular datatypes.
> 
> I need to stop the crash somehow as customers can't use RP11 because it is
> causing them grief with the helix server.  I'd rather find someway to
> support it as it is a very nice feature and compliments our datatype quite
> a bit....
> 
> Thanks,
> Brian
> 
>> Brian Meyerpeter wrote:
>>> Hi All,
>>>
>>> This may need to go to a different group (perhaps datatype dev), but I
>>> have a problem with a G2 based rendering/file format plugin during a
>>> seek
>>> operation.
>>>
>>> I believe it has something to do with keyframes but I'm not sure.
>>>
>>> When I click on the slider bar and go directly to a position, the
>>> datatype/server combination seeks appropriately.
>>>
>>> When I take the bar and drag it, it will crash the realplayer.
>>>
>>> My question is:
>>>
>>> Since you have added the functionality to show keyframes while dragging
>>> the slide bar, is there some other interface I need to support either in
>>> the file format, or the renderer?
>>>
>>> What is exactly happening when a person drags the slider back and forth
>>> and then letting it go at a particular location?
>> In that case (when it shows frames while seeking) the player uses
>> the QuickSeek() interface on the engine. While in that mode, the
>> engine does not send any audio packets to audio renderers but just
>> sends video packets.
>>
>> I don't think any changes are required on the video renderer to
>> support this, it is probably exposing a bug that has been there
>> from some time. QuickSeek'ing does make the renderer decode very
>> quickly, so it is not exactly like a normal seek operation. What
>> is the stack trace of the crash?
>>
>> --greg.
>>
>>
> 
> 
> 
> 


_______________________________________________
Helix-client-dev mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev