On Wed, Jul 25, 2012 at 11:49 PM, SanskritFritz wrote:

On Tue, Jul 24, 2012 at 12:25 AM, Mauro Santos wrote:

...

There are reports that the uvcvideo module needs to be loaded with nodrop=1 in order to get things to work smoothly, do search in the forums, I believe I saw something about this there.

I can't believe that I did not find this valuable information earlier. Thank you, that solved this problem.

...and just after I wrote this, the system froze again, after several hours of skyping :( This time it happened when I opened a movie during a skype session. nodrop=1 is still on.

On Thu, Jul 26, 2012 at 12:34 AM, Mauro Santos wrote:

I don't know if the graphics card you are using supports video decoding acceleration and if skype can make use of it, but at least here with the ati binary blob, I can only get video decoding acceleration for one video stream at a time, trying to decode 2 videos at the same time with video decoding acceleration results in a hard crash. I have never tried with skype and currently I'm using the free drivers so I have no way to test this. If this is true for your case it should be quite easy to reproduce.

It might have been just a random crash caused by skype too, since it isn't the most stable piece of software you can use.

Thanks for this valuable advice again. I tested it, and indeed, when I turn on another video, the system locks up after a while (not immediately though).

On 01-08-2012 18:48, SanskritFritz wrote:

Has anyone succeeded to use Pidgin video and audio over gtalk? Jitsi works but I would like to use Pidgin. I'm trying to move away from Skype.

Since no one chimed in so far I'll report what I have tested a while ago. Pidgin to gtalk didn't work, pidgin to pidgin worked, _however_ some restrictions seemed to apply. Background: I'm not a fan of upnp and automagic port forwarding, so I don't use that and I disable upnp on devices I manage. The tests I have performed were done using gmail accounts, the accounts' configuration used were the ones needed get chat working plus specifying static ports for incoming traffic. I know this influenced the ease of use, but given that you can't be sure to always connect within networks you manage or get a public IP with no port filtering I'd say it was a relatively fair test. Having said that, what I have found is that both port forwarding _and_ firewalls must be configured correctly for things to work. If I remember correctly, the side which doesn't have things setup properly (or has some restriction) will not be able to receive sound/video. This makes it harder if not impossible to establish a working audio/video call. Given that not all users are tech savvy and some networks may be managed by third parties, I'd say that as it is, calls over jingle are not nearly as easy and hassle free as calls with skype. I know I'm going to sound like the devil's advocate, but skype actually does a really good job at hiding and working around all the complexities of establishing a working connection with someone else, and in a way it is security friendly as it uses the one static port you configure in the options for incoming connections. -- Mauro Santos