At 08:58 AM 5/1/03 -0400, Paul Cosway wrote:
>I was just about to post a question that I discussed with gwright and
>robla a week or so ago, but I think I may have found the answer in
>HELIX_CONFIG_SLUGGISHAUTOUPGRADE.
>
>If I understand Milko's description and my brief look at some of the
>code, HELIX_CONFIG_SLUGGISHAUTOUPGRADE is intended to allow a player to
>play a SureStream stream, even if it does not have all the codecs and
>will also prevent ASM from subscribing to a rule that uses any of the
>missing codecs.  I had managed the first (playing even without all the
>codecs) but was wondering if there was a reliable way to then exclude
>ASM rules.  Is my understanding broadly correct?

Yes.
The disabled ASM rules are collapsed and the bandwidth ranges associated 
with them are reassigned to the rules with lower bandwidth range (if there 
are such remaining).


>I haven't had time to test it fully, but on a couple of quick tests on
>my platform (ARM) it did not work - execution ended with a segmentation
>fault.  Unfortunately, I won't be able to investigate why or test on an
>x86 until the end of next week.  Has it been working reliably on an x86
>for others?

This is a new feature that we haven't had much opportunity to exercise yet 
- but we will - ARM included.


>Here's a stream that has both dnet and cook components:
>rtsp://real-live-a1.ginger.com/encoder/VirginRadio

We'll try.

Thanks,
Milko


>Paul Cosway
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe at helix-client.helixcommunity.org
>For additional commands, e-mail: dev-help at helix-client.helixcommunity.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe at helix-client.helixcommunity.org
For additional commands, e-mail: dev-help at helix-client.helixcommunity.org