pombreda / libjingle

Automatically exported from code.google.com/p/libjingle
0 stars 0 forks source link

Call example with GTalk - one way bad videooutput dump file #268

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Run the "call" example with gmail's GTalk; make a video call from the console
using initially the testdata files provided. The audio and video go through 
correctly to GTalk, everything seems fine. End the call.
2. Use the --videooutput dump file as input in another call towards GTalk. This 
time the video does not get displayed in gmail/GTalk.
3. The scenario above works fine if I call from GTalk and autoanswer in "call" 
( option -a). 

What is the expected output? What do you see instead?
Obviously I should see the video in GTalk, but I see just the generic "no face".

What version of the product are you using? On what operating system?
libjingle-0.6.6, call example in Linux(Ubuntu), gmail/GTalk browser client in 
Windows or Linux. 

Please provide any additional information below.
It is interesting it works only one-way, when placing the calls from GTalk 
towards "call". It is not specific only to 0.6.6. I wonder how many iterations 
are still needed to fix this.

Original issue reported on code.google.com by ddrago...@gmail.com on 31 Dec 2011 at 1:52

GoogleCodeExporter commented 9 years ago
I forgot to mention, this happens when I comment out

// video_codecs.push_back( 
//      cricket::VideoCodec(99, "H264-SVC", 640, 360, 30, 0));

in mediaenginefactory.cc, in other words, I want to use only H264, not H264-SVC.
It may have to with H264 keyframes, but this is pure speculation.

Original comment by ddrago...@gmail.com on 31 Dec 2011 at 4:05

GoogleCodeExporter commented 9 years ago
The "input" rtpdump file is in "H264/AVC" format due to compatibility concerns, 
however, when calling from console to Gmail/Talk without any code change, by 
default, the "SVC" codec will be used, so the "output" file you saved is an 
"SVC" dump file.
Then you removed the "SVC" support from the console app and try to feed it with 
an "SVC" dump file that you saved previously. This is why it won't work.  

Original comment by jun...@google.com on 4 Jan 2012 at 12:08