[Asterisk-video] Videomixing in MeetMe

[Klaus Darilion]

Lorenzo Miniero wrote:
> Hi Klaus,
> 
> I'm glad you got the mixer working!
> My answers to your comments are inline.
> 
> 
>> HI Lorenzo  - this fix works. Thus, I got mixed video. Below some comments:
>>
>> - I have lots of troubles with eyebeam when video is activated. System 
>> and eyebeam need lots of CPU resource and I can't do anything else on my PC.
 >
> Is it always so with eyebeam+video (with any other video call you have with
> anyone), or only when eyebeam receives the frames from the mixer?

Always - IMO a problem inside eyebeam or Windows (i have a "System" 
process which takes up to 70% CPU)

> 
>> -- this one happens very often during mixing
>> [h263 @ 0xb7de8ca0]I cbpc damaged at 0 4
>> [h263 @ 0xb7de8ca0]Error at MB: 164
>> [h263 @ 0xb7de8ca0]I cbpc damaged at 0 8
>> [h263 @ 0xb7de8ca0]Error at MB: 328
>> [h263 @ 0xb7de8ca0]I cbpc damaged at 0 12
>> [h263 @ 0xb7de8ca0]Error at MB: 492
>> [h263 @ 0xb7de8ca0]I cbpc damaged at 0 16
>> [h263 @ 0xb7de8ca0]Error at MB: 656
>> [h263 @ 0xb7de8ca0]I cbpc damaged at 0 20
>> [h263 @ 0xb7de8ca0]Error at MB: 820
>> [h263 @ 0xb7de8ca0]I cbpy damaged at 0 24
>> [h263 @ 0xb7de8ca0]Error at MB: 984
>> [h263 @ 0xb7de8ca0]concealing 609 DC, 609 AC, 609 MV errors
>> [h263 @ 0xb7de8ca0]Bad picture start code
>> [h263 @ 0xb7de8ca0]header damaged
>> ...
>> [h263 @ 0xb7de8ca0]concealing 707 DC, 707 AC, 707 MV errors
>> [h263 @ 0xb7de8ca0]Bad picture start code
>> [h263 @ 0xb7de8ca0]header damaged
>> [h263 @ 0xb7de8ca0]vbv buffer overflow
>> [h263 @ 0xb7de8ca0]I cbpc damaged at 0 4
>> [h263 @ 0xb7de8ca0]Error at MB: 164
>> [h263 @ 0xb7de8ca0]I cbpc damaged at 0 8
>> [h263 @ 0xb7de8ca0]Error at MB: 328
>> [h263 @ 0xb7de8ca0]I cbpc damaged at 0 12
>> [h263 @ 0xb7de8ca0]Error at MB: 492
>> [h263 @ 0xb7de8ca0]I cbpc damaged at 0 16
>> [h263 @ 0xb7de8ca0]Error at MB: 656
>> [h263 @ 0xb7de8ca0]I cbpc damaged at 0 20
>> [h263 @ 0xb7de8ca0]Error at MB: 820
>> [h263 @ 0xb7de8ca0]I cbpc damaged at 0 24
>> [h263 @ 0xb7de8ca0]Error at MB: 984
>> ...
> 
> 
> This could be related to two aspects:
> 
>         * the H.263 codec used by eyebeam could be not-100%-compliant with the
> ffmpeg H.263 codec (and this is something we'd have to live with);
>         * there might be problems with the H.263 payload header and how I handle
> it.
> 
> I'm still investigating the H.263 payload header issue, also considering that
> there are three different modes for it. In fact, different settings give
> different results according to the client (for example, a setting that works
> fine with our client gives strange behaviour with Wengophone, while settings
> that work fine with Wengophone don't work at all with our client, and the same
> applies with some other clients we tested). I'll try eyebeam myself as soon as
> I can to see if I can sort it out. Of course, if you have advices for this, let
> me know!

Sorry - no advices. But interesting to know that wengophone works too. 
Which version of wengophone do you use? I never had success with using 
wengophone at all (lots of crashes).

> Thanks a lot for your precious feedback, it's much appreciated!
> If you have any other question and/or advices/suggestions/criticisms about this
> work, I'll be glad to hear them.

Where should the discussion happen - here or on another mailing list? (I 
prefer here - asterisk-dev).

btw: some feature requests for the next version ;-)
- a MeetMe option which automatically activates this caller as video 
source (an implicit "videoswitch x y")
- A overlay in each video showing the name of the caller. e.g. by 
setting a certain variable before calling MeetMe.
- a option to have only all other peers mixed, but not yourself. E.g. 
currently if all sources are activiated, using eyebeam you see yourself 
two times: 1: in the eyebam video preview, 2: in the received mixed 
video. Of course this requires that each participant gets a dedicated 
mixed stream which probably requires much more load for the mixing.
-more debug outpout, e,g, in "meetme list 123" with details about the 
video (which source is activated, codec, ...)

btw: When activating video I always get logs like:
Incoming call: Got SIP response 415 "Unsupported Media Type" back from 
83.136.33.3

Is this only a warning that my SIP client does not support some 
conference extension (I saw INFO requests with XML payload)

regards
klaus