Apologies i dont undertstand what this code is doing, the other code block explains setting up the bandwidth control within a connection and stream. Ive also ticketed that this class is causing exceptions on live streams.
http://jira.red5.org/browse/SN-32 Steven Gong wrote: > Could you please tell me what you don't get? So that I can make some > improvements. Thanks. > > On 3/15/07, Dan Rossi <[EMAIL PROTECTED]> wrote: >> >> I dont get this bit >> >> IBWControllable aControllable; // assume the object is instantiated, >> parent is set and the bandwidth is configured >> IBWControlService bwController; // assume we've got the service from >> spring >> IBWControlContext context; >> >> context = bwController.registerBWControllable(aControllable); >> ITokenBucket audioBucket = bwController.getAudioBucket(context); >> ITokenBucket videoBucket = bwController.getVideoBucket(context); >> ITokenBucket dataBucket = bwController.getDataBucket(context); >> ITokenBucketCallback callback; // assume the callback object is >> available >> >> // acquire tokens via audio, video and data buckets >> boolean result = audioBucket.acquireToken(10 * 1024, 1000); >> result = videoBucket.acquireTokenNonblocking(10 * 1024, callback); >> long tokens = dataBucket.acquireTokenBestEffort(10 * 1024); >> >> bwController.unregisterBWControllable(context); >> >> Dan Rossi wrote: >> > Hi Steve >> > >> >> A simple usage model might be: >> >> In a live meeting session, when the bandwidth limit is low, you might >> >> want >> >> to bias the audio against video. So you could set the bandwidth of >> >> video to >> >> a low value (so that video will look jerky). And the audio sounds >> just >> >> fine. >> >> >> > I read the FMS speeds up the audio to keep up with video or something >> > like that when its being slowed down. I dont think jerky video is the >> > expected output at all, its what currently happens, ive tried >> everything >> > to get a nice smooth rate without frames being dropped. I did notice >> > that a quality setting minus 80 works better than 90-100 but its too >> > blocky to be useful. We're trying to live stream at 240x180 video size >> > though which was ok for windows media streaming via the encoder. I >> dont >> > think jerky video is of much use for vod streaming also. >> > >> >> There're many other usage models. You can also contribute your own >> >> here. I >> >> just provide a framework to make them feasible. >> >> >> >> >> > Ill have to spend time to test things out, i wonder if the server >> can do >> > dynamic buffering if not enough video data is being pushed out ? >> > >> > >> > _______________________________________________ >> > Red5 mailing list >> > [email protected] >> > http://osflash.org/mailman/listinfo/red5_osflash.org >> > >> > >> >> >> _______________________________________________ >> Red5 mailing list >> [email protected] >> http://osflash.org/mailman/listinfo/red5_osflash.org >> > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
