My guess is it's in the player itself, you can trace it all the way back tothe netstream class. I could be wrong though, maybe one of the Adobe guyscan think of a way to flush that buffer without having to restart thecamera.-Eric

Sure glad it's helpful. No technical reason for XMPP, in fact an LCCSmessage is probably better. I just already knew how to send XMPP messagesso it was the easy route for me.-Eric

flash.media.camerahttp://livedocs.adobe.com/flex/3/langref/flash/media/Camera.html

I did a little work this past week to improve our performance, and automatically scale back our bandwidth usage when we were in low bandwidth situations.  Primarily we were trying to combat choppy audio, video delay, and low video framerate.   It turned into more work than I expected.Anyway I though...

We do something similar with our product. We use XMPP for presence, callsetup, teardown etc. Then we just use AFCS (LCCS) to do the peer-peer videocalls over RTMFP. We use AFCS's server side api's to look up account infofrom our MySQL server. So without knowing more it sounds possible -Eric

Is there a way to flush or reset the transmit buffer of the webcamPublisher, without stopping and restarting publishing?I ask because when I lower the bandwidth between to clients, I now automatically lower my settings to send less video data / second.  The only problem is there is now a huge delay ...

isCameraPublishing fires when I do this webPub.stop(); is that not supposedto happen?

When using a webcamPublisher and listening to the change event I only get an event fired when the camera starts publishing, but not when it stops.changeevent Event object type: flash.events.Event Dispatched when the camera is accessed for publishing or is stopped.If I use the isCameraPublishing eve...

Ok so in my documentation for the Class AudioPublisher there is an eventlisted in it's event table like this:streamPublishing eventEvent object type:com.adobe.rtc.events.StreamEvent<file:////Users/eric/Documents/com.adobe.afcs/docs/asdocs/com/adobe/rtc/events/StreamEvent.html>Dispatched when the c...

bah never mind I'll do another way.