[Ekiga-list] Audio-Problems
Hello Why do I get this message? Audiokanal zum Audioempfang konnte nicht geöffnet werden Beim Versuch, Audio für den Audio-Empfang über die Soundkarte auszugeben, ist ein Fehler aufgetreten. Bitte überprüfen Sie, dass die Soundkarte nicht anderweitig benutzt wird und dass der Treiber Voll-Duplex unterstützt. Der Audioempfang wurde deaktiviert. Br jm ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Audio-Problems
Hello, Le mardi 30 décembre 2008 à 08:29 +0100, Judith Meili a écrit : Hello Why do I get this message? Audiokanal zum Audioempfang konnte nicht geöffnet werden Beim Versuch, Audio für den Audio-Empfang über die Soundkarte auszugeben, ist ein Fehler aufgetreten. Bitte überprüfen Sie, dass die Soundkarte nicht anderweitig benutzt wird und dass der Treiber Voll-Duplex unterstützt. Der Audioempfang wurde deaktiviert. La carte son est déjà occupée par un autre programme ? -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]]
Le lundi 29 décembre 2008 à 20:49 +0100, Judith Meili a écrit : Damien Sandras? Do you want to answer? Original-Nachricht Betreff: Re: [Ekiga-list] [Fwd: echo canceller] Datum: Mon, 29 Dec 2008 12:38:10 +0100 Von: Judith Meili jme...@gmx.ch Antwort an: Ekiga mailing list ekiga-list@gnome.org An: Ekiga mailing list ekiga-list@gnome.org Referenzen: 4958a804.3020...@gmx.ch 1230553201.32518.0.ca...@achille Thanks. You do not even have a hook atenable echo cancelation. I have a hook there and a hook where ever you show a hook and the people are still complaining. Can't Ekiga improve that? Improve echo cancellation ? We use the best algorithm currently available. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Audio-Problems
Mais par quel program? J'ai aucun program ouvert sauf skype. Damien Sandras schrieb: Hello, Le mardi 30 décembre 2008 à 08:29 +0100, Judith Meili a écrit : Hello Why do I get this message? Audiokanal zum Audioempfang konnte nicht geöffnet werden Beim Versuch, Audio für den Audio-Empfang über die Soundkarte auszugeben, ist ein Fehler aufgetreten. Bitte überprüfen Sie, dass die Soundkarte nicht anderweitig benutzt wird und dass der Treiber Voll-Duplex unterstützt. Der Audioempfang wurde deaktiviert. La carte son est déjà occupée par un autre programme ? ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]]
Le mardi 30 décembre 2008 à 08:34 +0100, Judith Meili a écrit : Thanks. So maybe the microphone is too close to the speaker? Everybody complains because of echo. Are the speakers and microphones attached to the same soundcard or do you use speakers + USB mic or similar ? -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Audio-Problems
It's perhaps skype in that case. Le mardi 30 décembre 2008 à 08:34 +0100, Judith Meili a écrit : Mais par quel program? J'ai aucun program ouvert sauf skype. Damien Sandras schrieb: Hello, Le mardi 30 décembre 2008 à 08:29 +0100, Judith Meili a écrit : Hello Why do I get this message? Audiokanal zum Audioempfang konnte nicht geöffnet werden Beim Versuch, Audio für den Audio-Empfang über die Soundkarte auszugeben, ist ein Fehler aufgetreten. Bitte überprüfen Sie, dass die Soundkarte nicht anderweitig benutzt wird und dass der Treiber Voll-Duplex unterstützt. Der Audioempfang wurde deaktiviert. La carte son est déjà occupée par un autre programme ? ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Compile Problem
Eugen, Thanks this put me on the right track. I can confirm that suse 11.1 is the problem. In ekiga-3.0.1/lib/engine/ it still uses *.la files all these have been removed in 11.1, in addition there is practically nothing in /opt/gnome/lib. Most of those files have been moved to /usr/lib. There were about 6 other files that were deleted altogether. What a mess! Anyway I got over all of them, and engine compiled ok. Now I get to /usr/lib/gcc/i586-suse-linux/4.3/../../../../i586-suse-linux/bin/ld: cannot find -lresmgr collect2: ld returned 1 exit status make[3]: *** [ekiga] Error 1 make[3]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1' make: *** [all] Error 2 Only to discover that suse dropped support for resmgr after 10.3. It nolonger exists in 11.1. Suse now appears to use hal-resmgr. Once I figured out what libs were required where, I coped, but I do not understand how to proceed with this one. Is it possible to remove the requirement to load resmgr? Thanks, Brian Eugen Dedu wrote: Brian wrote: Damien, Can you provide a full log ? Do you mean from a ekiga -d 4? I fear the V4L2 plugin is not installed, but only the 'deprecated' V4L2 plugin... I agree, that is what it looks like and last time I got out of the same situation by installing the latest pwlib. I believe I have the latest installed, see below. Brian pwlib-plugins-v4l2 - V4L2 support for pwlib This plugin enables 'video for linux' (version 2) support (e.g. for USB cameras) for pwlib. The level of support is unspecified pwlib-plugins-v4l2-1.10.10-56.2 - V4L2 support for pwlib This is the old plugin. ekiga 3.0 compiles only with the latest versions of ptlib (previously caled pwlib) and opal: ptlib 2.4.2 (you have here 1.10.10) and opal 3.4.2. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Compile Problem
Damien, FYI I have just got on to the suse forum to see if I could get some help. Keyed in ekiga and the very first hit I get was somebody saying they have just upgraded to 11.1 and it does not work. Later, Brian PS. I will try to find out who the old packager was and see if they can help. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]]
iMac has inbuilt microphone and speaker. Damien Sandras schrieb: Le mardi 30 décembre 2008 à 08:34 +0100, Judith Meili a écrit : Thanks. So maybe the microphone is too close to the speaker? Everybody complains because of echo. Are the speakers and microphones attached to the same soundcard or do you use speakers + USB mic or similar ? ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] 473 Filtered destination
Le mardi 30 décembre 2008 à 12:00 +0100, Palo S. a écrit : I have reproduced the same problem on yet another computer running Ubuntu with Ekiga 3.0 packaged by Yannick. So my suspicion on distribution specificity is wrong. I am even more wondering why nobody else complains about this... weird. Can you try to remove from your contact list all things related to ekiga.net : 5...@ekiga.net, 5...@ekiga.net and so on ? You can keep your normal contacts. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] 473 Filtered destination
Le mardi 30 décembre 2008 à 12:00 +0100, Palo S. a écrit : I have reproduced the same problem on yet another computer running Ubuntu with Ekiga 3.0 packaged by Yannick. So my suspicion on distribution specificity is wrong. I am even more wondering why nobody else complains about this... weird. This is quite an interesting question. I must admit I've seen myself the same issue you reported: my ekiga 3 not being able to accurately display presence for my contacts in the long run. Why I did not reported this? My packs are not latest stable version, I did not have something more accurate than just I can see it did not work all time. In short, I did not believe I had enough to track the bug down efficiently. And I also admit my commitment to this project is sometime weaker... Let's no fall in the mistake of being guilty, but when comparing to other similar projects backed by profit, it is quite depressing. This also raise question about the quality process for Ekiga. I do not count much on our users to perform such testing by themselves, except for obvious bugs like craches, totally broken feature, etc. Fortunately there is people like you taking time to report, but this is not the right way for most people who need a lot of guidance for it and who probably do not have the culture background to clearly see how much feedback is important for us. I congrats you for being so insistant on this issue. Most people would have given up a long time ago. I think we should improve this part of our practise: http://wiki.ekiga.org/index.php/Pre-release_test And I also need to set back up the daily snapshots/last stable for Ubuntu. So many work to do... I think we should: 1- ease the process of reporting issues; waiting for people to show up in the right place, then asking for a -d 4 probably make it harder to report. 2- build up automatic testing/regression test for ekiga Best regards, Yannick ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Audio-Problems
It shouldnt be skype. I need both programs. After restarting it was working again. Damien Sandras schrieb: It's perhaps skype in that case. Le mardi 30 décembre 2008 à 08:34 +0100, Judith Meili a écrit : Mais par quel program? J'ai aucun program ouvert sauf skype. Damien Sandras schrieb: Hello, Le mardi 30 décembre 2008 à 08:29 +0100, Judith Meili a écrit : Hello Why do I get this message? Audiokanal zum Audioempfang konnte nicht geöffnet werden Beim Versuch, Audio für den Audio-Empfang über die Soundkarte auszugeben, ist ein Fehler aufgetreten. Bitte überprüfen Sie, dass die Soundkarte nicht anderweitig benutzt wird und dass der Treiber Voll-Duplex unterstützt. Der Audioempfang wurde deaktiviert. La carte son est déjà occupée par un autre programme ? ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Audio-Problems
It shouldnt be skype. I need both programs. After restarting it was working again. Then you should maybe complain to Skype developers? It looks like Skype is blocking Ekiga, not the other way around. It works in the same way for me too, I have to quit Skype otherwise audio in Ekiga does not work. (For me it is no problem, I use Skype rarely.) __ http://www.inzeraty.sk/ - Bezplatná inzercia v najobľúbenejších kategóriách ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] 473 Filtered destination
- Originálna Správa - Od: yannick Komu: Ekiga mailing list Poslaná: 30.12.2008 12:40 Predmet: Re: [Ekiga-list] 473 Filtered destination Le mardi 30 dĂŠcembre 2008 Ă 12:00 +0100, Palo S. a ĂŠcrit : I have reproduced the same problem on yet another computer running Ubuntu with Ekiga 3.0 packaged by Yannick. So my suspicion on distribution specificity is wrong. I am even more wondering why nobody else complains about this... weird. This is quite an interesting question. I must admit I\'ve seen myself the same issue you reported: my ekiga 3 not being able to accurately display presence for my contacts in the long run. Well, the issue that I reported causes more important problem - it is not possible to reach the client after some time (ie no incoming calls because server rejects them although outcoming work just fine). And this is something I thought people would notice and report... However, wrong presence indication accompanies this issue so maybe you actually do suffer by the same problem? It is easy to see in the logfile: after some time there are no messages at all. Also, the client cannot be closed properly then. Why I did not reported this? My packs are not latest stable version, I did not have something more accurate than just I can see it did not work all time. In short, I did not believe I had enough to track the bug down efficiently. And I also admit my commitment to this project is sometime I also noticed more issues but did not report from the same reasons. Presence indication not working correctly after some time was the first I noticed. Then there is video not transmitted when using theora codec in certain cases, h264 not initialized correctly in certain cases, occasional hang of Ekiga when releasing the call... However these issues are clearly not that important and not so reproducible as the one that I reported. weaker... Let\'s no fall in the mistake of being guilty, but when comparing to other similar projects backed by profit, it is quite depressing. Yes, this is clearly a problem. However, I have been using Ekiga 2 for some 2 years for calls with relatives without any major problems and I can say that in my experience and for my purposes it worked significantly better than Skype. And Ekiga 3 is close to fix the remaining smaller problems or missing features I had with 2 (such as cpu getting to 100% with video or missing presence indication). So the state of Ekiga is clearly not that depressing. Given the very limited manpower and free time based development it is actually unbelievable how reliably Ekiga worked for me in the last years. Now with 3.0 and new server more issues emerged and your questions about how these could be prevented are of course very important to ask. This also raise question about the quality process for Ekiga. I do not count much on our users to perform such testing by themselves, except for obvious bugs like craches, totally broken feature, etc. Fortunately there is people like you taking time to report, but this is not the right way for most people who need a lot of guidance for it and who probably do not have the culture background to clearly see how much feedback is important for us. I congrats you for being so insistant on this issue. Most people would have given up a long time ago. Well, suddenly my relatives started to complain that they cannot call me and I also noticed I could not call them sometimes. That was enough to convince even a lazy man like me to have a closer look and report my findings :) I think we should improve this part of our practise: http://wiki.ekiga.org/index.php/Pre-release_test And I also need to set back up the daily snapshots/last stable for Ubuntu. So many work to do... I think we should: 1- ease the process of reporting issues; waiting for people to show up in the right place, then asking for a -d 4 probably make it harder to report. 2- build up automatic testing/regression test for ekiga I am sure both these points would help a lot. Regarding 1, I can think of several improvements (note that I am not Ekiga developer so some of these may be wrong/ not possible/not feasible etc): a) It should be possible to send the data from crash directly to Ekiga developers with one click. Similar thing as eg Firefox handles this. Maybe it is already intended but when I get a crash, I only get the possiblity to save the log and send it to an email address - hard to imagine that a usual user would do that. b) There could be an option in the GUI to deal with problems and their reports. This would enable the user to turn on/off log catching and in case it is turned on, to send it as well as the report directly from the client. Regarding 2, certainly something that would be very useful. It could certainly not catch all the possible problems but could still help a lot. At the beginning, something simple like automatic periodic trunk/stable
Re: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]]
This is basically a simple acoustic issue with the iMac since the microphone and speaker are pretty close together in the same case = echo between them. I got around it by using a separate microphone OR earphones - you only need one of the two. This is enough to stop the echo. You could even do it wirelessly if your model supports Bluetooth headsets. Oliver --Original Message-- From: Judith Meili Sender: ekiga-list-boun...@gnome.org To: Ekiga mailing list ReplyTo: Ekiga mailing list Subject: Re: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]] Sent: 30 Dec 2008 10:22 iMac has inbuilt microphone and speaker. Damien Sandras schrieb: Le mardi 30 décembre 2008 à 08:34 +0100, Judith Meili a écrit : Thanks. So maybe the microphone is too close to the speaker? Everybody complains because of echo. Are the speakers and microphones attached to the same soundcard or do you use speakers + USB mic or similar ? ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -- Oliver de Peyer PhD Lab 209 Division of Molecular Structure National Institute for Medical Research The Ridgeway Mill Hill London NW71AA United Kingdom Tel 0208 816 2688 Fax 0208 816 2580 Mobile phone +44 7908 783367 ope...@nimr.mrc.ac.uk ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] 473 Filtered destination
Can you try to remove from your contact list all things related to ekiga.net : 5...@ekiga.net, 5...@ekiga.net and so on ? You can keep your normal contacts. Looks like a good shot! Running for two hours now and still ok. Also the amount of traffic is much smaller. The log is 400k now while it used to be maybe 40M at this time with 500 and 501 in contact list. I still cannot confirm with 100% though, I will try on another computer and for longer time and let you know. Palo __ Mobilné telefóny v slovenskej premiére a najaktuálnejšie informácie - http://mobil.sme.sk/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] 473 Filtered destination
- Originálna Správa - Od: Damien Sandras Komu: Ekiga mailing list Poslaná: 30.12.2008 15:20 Predmet: Re: [Ekiga-list] 473 Filtered destination Le mardi 30 dĂŠcembre 2008 Ă 15:20 +0100, Palo S. a ĂŠcrit : Can you try to remove from your contact list all things related to ekiga.net : 5...@ekiga.net, 5...@ekiga.net and so on ? You can keep your normal contacts. Looks like a good shot! Running for two hours now and still ok. Also the amount of traffic is much smaller. The log is 400k now while it used to be maybe 40M at this time with 500 and 501 in contact list. I still cannot confirm with 100% though, I will try on another computer and for longer time and let you know. There is a bug in Asterisk on ekiga.net, I need to find a workaround tonight. I don\'t think Ekiga is faulty there. I was suspecting it could be ekiga.net issue again a.o. because I started to use Ekiga 3.0 longer time ago and this problem only appeared relatively recently. Very good that finally we are getting close to the problem localization! Palo -- _ Damien Sandras (o- //\\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list __ Mozaika storočia denníka SME - http://mozaika.sme.sk ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]]
In other words Apple sells rubbish. Correct? ope...@nimr.mrc.ac.uk schrieb: This is basically a simple acoustic issue with the iMac since the microphone and speaker are pretty close together in the same case = echo between them. I got around it by using a separate microphone OR earphones - you only need one of the two. This is enough to stop the echo. You could even do it wirelessly if your model supports Bluetooth headsets. Oliver --Original Message-- From: Judith Meili Sender: ekiga-list-boun...@gnome.org To: Ekiga mailing list ReplyTo: Ekiga mailing list Subject: Re: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]] Sent: 30 Dec 2008 10:22 iMac has inbuilt microphone and speaker. Damien Sandras schrieb: Le mardi 30 décembre 2008 à 08:34 +0100, Judith Meili a écrit : Thanks. So maybe the microphone is too close to the speaker? Everybody complains because of echo. Are the speakers and microphones attached to the same soundcard or do you use speakers + USB mic or similar ? ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -- Oliver de Peyer PhD Lab 209 Division of Molecular Structure National Institute for Medical Research The Ridgeway Mill Hill London NW71AA United Kingdom Tel 0208 816 2688 Fax 0208 816 2580 Mobile phone +44 7908 783367 ope...@nimr.mrc.ac.uk ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Compile Problem
Brian wrote: Eugen, Thanks this put me on the right track. I can confirm that suse 11.1 is the problem. In ekiga-3.0.1/lib/engine/ it still uses *.la files all these have been removed in 11.1, in addition there is practically nothing in /opt/gnome/lib. Most of those files have been moved to /usr/lib. There were about 6 other files that were deleted altogether. What a mess! Anyway I got over all of them, and engine compiled ok. Now I get to /usr/lib/gcc/i586-suse-linux/4.3/../../../../i586-suse-linux/bin/ld: cannot find -lresmgr collect2: ld returned 1 exit status make[3]: *** [ekiga] Error 1 make[3]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1' make: *** [all] Error 2 Only to discover that suse dropped support for resmgr after 10.3. It nolonger exists in 11.1. Suse now appears to use hal-resmgr. Once I figured out what libs were required where, I coped, but I do not understand how to proceed with this one. Is it possible to remove the requirement to load resmgr? Hi, I didn't know what resmgr is, so I took a look at http://www.lst.de/~okir/resmgr. In debian, my machine, resmgr does not exist. I searched resmgr in ekiga, ptlib and opal, and I haven't found it either. So I imagine it's suse which adds it to the command line?? Look at the parameters of gcc (gcc -v or other flags, I don't know). Also, try to install the package providing resmgr library. -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Colour format not supported with ekiga-svn
Hi,
I'm trying current svn version of ekiga co (was a checkout from yesterday).
My camera 'logitech quickcam connect' (046d:08d9) works quite well
with ekiga 2.0.11, 2.0.12, 3.0.1 but unfortunately not with current svn.
Message from error-box is:
Your driver doesn't seem to support any of the color formats supported by
Ekiga.
Please check your kernel driver documentation in order to determine which
Palette is supported. ...
From kernel v4l-dvb driver: v4l-dvb/linux/drivers/media/video/gspca/zc3xx.c:
static struct v4l2_pix_format vga_mode[] = {
{320, 240, V4L2_PIX_FMT_JPEG, V4L2_FIELD_NONE,
.bytesperline = 320,
.sizeimage = 320 * 240 * 3 / 8 + 590,
.colorspace = V4L2_COLORSPACE_JPEG,
.priv = 1},
{640, 480, V4L2_PIX_FMT_JPEG, V4L2_FIELD_NONE,
.bytesperline = 640,
.sizeimage = 640 * 480 * 3 / 8 + 590,
.colorspace = V4L2_COLORSPACE_JPEG,
.priv = 0},
};
static struct v4l2_pix_format sif_mode[] = {
{176, 144, V4L2_PIX_FMT_JPEG, V4L2_FIELD_NONE,
.bytesperline = 176,
.sizeimage = 176 * 144 * 3 / 8 + 590,
.colorspace = V4L2_COLORSPACE_JPEG,
.priv = 1},
{352, 288, V4L2_PIX_FMT_JPEG, V4L2_FIELD_NONE,
.bytesperline = 352,
.sizeimage = 352 * 288 * 3 / 8 + 590,
.colorspace = V4L2_COLORSPACE_JPEG,
.priv = 0},
};
Should I get a new cam?
For successfully compiling opal with my ffmpeg version,
I had to apply the attached patch.
--
Stefan Lucke
Index: plugins/video/H.263-1998/h263-1998.cxx
===
--- plugins/video/H.263-1998/h263-1998.cxx (revision 21872)
+++ plugins/video/H.263-1998/h263-1998.cxx (working copy)
@@ -450,14 +450,20 @@
if (!H263_Base_EncoderContext::Open(CODEC_ID_H263))
return false;
+#if LIBAVCODEC_VERSION_INT ((5216)+(08)+0)
_context-rtp_mode = 1;
+#endif
_context-rtp_payload_size = 200;
_context-rtp_callback = rtp_callback;
_context-opaque = (H263_RFC2190_EncoderContext *)this; // used to separate
out packets from different encode threads
_context-flags = ~CODEC_FLAG_H263P_UMV;
_context-flags = ~CODEC_FLAG_4MV;
+#if LIBAVCODEC_VERSION_INT ((5216)+(08)+0)
_context-flags = ~CODEC_FLAG_H263P_AIC;
+#else
+ _context-flags = ~CODEC_FLAG_AC_PRED;
+#endif
_context-flags = ~CODEC_FLAG_H263P_AIV;
_context-flags = ~CODEC_FLAG_H263P_SLICE_STRUCT;
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Colour format not supported with ekiga-svn
Hi, Le mardi 30 décembre 2008 à 18:39 +0100, Stefan Lucke a écrit : Hi, I'm trying current svn version of ekiga co (was a checkout from yesterday). My camera 'logitech quickcam connect' (046d:08d9) works quite well with ekiga 2.0.11, 2.0.12, 3.0.1 but unfortunately not with current svn. Did you compile PTLIB with libv4l support ? Most probably ekiga 2.0.11 were compiled with libv4l support but not TRUNK, which would explain this problem. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Colour format not supported with ekiga-svn
On Tuesday 30 December 2008, Damien Sandras wrote: Hi, Le mardi 30 décembre 2008 à 18:39 +0100, Stefan Lucke a écrit : Hi, I'm trying current svn version of ekiga co (was a checkout from yesterday). My camera 'logitech quickcam connect' (046d:08d9) works quite well with ekiga 2.0.11, 2.0.12, 3.0.1 but unfortunately not with current svn. Did you compile PTLIB with libv4l support ? I think I did so: ste...@jarada /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib $ grep v4l config.log $ ./configure --prefix=/usr --enable-v4l --enable-v4l2 configure:16342: running /bin/sh ./configure '--prefix=/usr' '--enable-v4l' '--enable-v4l2' --cache-file=/dev/null --srcdir=. Most probably ekiga 2.0.11 were compiled with libv4l support but not TRUNK, which would explain this problem. From ekiga -d 5 and a slightly modified ptlib I get the following output: 1195724874 = 0x4745504A = GEPJ (JPEG) 842093913 = 0x32315559 = 21UY (YU12) 2008/12/30 19:58:23.700 0:00.757 Detecting V4L2 devices 2008/12/30 19:58:23.700 0:00.757 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2008/12/30 19:58:23.700 0:00.757 PV4L2Plugin detected capture device USB Camera (046d:08d9) 2008/12/30 19:58:23.700 0:00.757 PVidInDev Open() devName:/dev/video0 videoFd:-1 2008/12/30 19:58:23.700 0:00.757 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.700 0:00.757 PVidInDev colour format mismatch. (1195724874,842093913). 2008/12/30 19:58:23.700 0:00.757 PVidDev SetColourFormatConverter, want YUV420P trying YUV420P 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,842093913). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying I420 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying IYUV 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying YUV420 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,825382478). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying RGB32 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,876758866). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying BGR32 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,877807426). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying RGB24 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,859981650). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying BGR24 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,861030210). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying YUY2 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,1448695129). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying YUV422 2008/12/30 19:58:23.701 0:00.758
[Ekiga-list] direct phonecall by clicking on a phone number in the white pages
hello When I click on a phone number in http://tel.local.ch/ it wrights automatically the number in Ekiga like this: callto://+41317355755 Then I always have to delete callto://+ and write sip:0041317355755. Why does it change to callto://+. It would be very convenient if it stays like sip:00 Thanks. Br jm ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Debian packages
Eugen Dedu wrote: There are two solutions: - either stay as we are now. Note that only gnome-desktop-environment is removed (+old pwlwib/opal), not 47 packages!! - or do not use ekiga-snapshot anymore, but ekiga (while ptlib and opal are still named -snapshot, to avoid soname problems). Note that this will not be intrusive or conflict with debian package, because the version will be carefully chosen. What about a third solution, namely adding a provides statement to the package definition of ekiga-snapshot? I.e. Provides: ekiga. See http://www.debian.org/doc/FAQ/ch-pkg_basics#s-depends. AFAIK this approach is widely used, one example is the thunderbird package which has a Provides: mail-reader. HTH, Hannes ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Debian packages
On Tue, Dec 30, 2008 at 08:39:54PM +0100, Eugen Dedu wrote:
Rick Pasotto wrote:
gnome-desktop-environment depends on ekiga (= 2.0.12)
Since 'aptitude install ekiga-snapshot' removes ekiga,
gnome-desktop-environment becomes BROKEN and the installation would
REMOVE 47 other packages.
As far as I'm concerned, this means that ekiga-snapshot is NOT
installable.
I think that the problem is that the version number for
ekiga-snapshot is 0-20081220-1 which is less than 2.0.12. Perhaps if
the version number were changed to something greater that 2.0.12 (eg,
3-20081220-1) then the problem would go away.
Hi,
Increasing the version of ekiga-snapshot does not work.
There are two solutions: - either stay as we are now. Note that only
gnome-desktop-environment is removed (+old pwlwib/opal), not 47
packages!! - or do not use ekiga-snapshot anymore, but ekiga (while
ptlib and opal are still named -snapshot, to avoid soname problems).
Note that this will not be intrusive or conflict with debian package,
because the version will be carefully chosen.
What do people prefer??
Sorry to hear that changing the version number doesn't work. I'm not
really clear on exactly how the debian version number punctuation works.
Did you try using 3.0.0 or even 2.9? Perhaps the fact that the first
non-digit character is a '-' makes a difference.
The number of packages that depend on gnome-desktop-environment will
vary from system to system. On my machine the following 45 packages
would be removed:
arj{u} at-spi{u} cheese{u} dasher{u} dasher-data{u} dmz-cursor-theme{u}
eog{u} festival{u} festlex-cmu{u} festlex-poslex{u} festvox-kallpc16k{u}
file-roller{u} gcalctool{u} gconf-editor{u} gedit{u} gedit-common{u}
gnome-accessibility{u} gnome-accessibility-themes{u} gnome-core{u}
gnome-desktop-environment gnome-network-admin{u} gnome-orca{u}
gnome-power-manager{u} gnome-screensaver{u} gnome-themes{u} gok{u}
gstreamer0.10-tools{u} gucharmap{u} iceweasel-gnome-support{u}
libalut0{u} libavahi-ui0{u} libbrlapi0.5{u} libglew1.5{u}
libgnome-speech7{u} libgtk-vnc-1.0-0{u} libswfdec-0.6-90{u} libxevie1{u}
mousetweaks{u} python-brlapi{u} python-gtksourceview2{u}
python-pyatspi{u} rss-glx{u} swfdec-gnome{u} unace{u} vinagre{u}
I guess I'll have to stay with 2.0.12.
--
He who has never hoped can never despair. -- George Bernard Shaw
Rick Pasottor...@niof.nethttp://www.niof.net
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Debian packages
On Tue, Dec 30, 2008 at 09:12:47PM +0100, Hannes Ebner wrote: Eugen Dedu wrote: There are two solutions: - either stay as we are now. Note that only gnome-desktop-environment is removed (+old pwlwib/opal), not 47 packages!! - or do not use ekiga-snapshot anymore, but ekiga (while ptlib and opal are still named -snapshot, to avoid soname problems). Note that this will not be intrusive or conflict with debian package, because the version will be carefully chosen. What about a third solution, namely adding a provides statement to the package definition of ekiga-snapshot? I.e. Provides: ekiga. See http://www.debian.org/doc/FAQ/ch-pkg_basics#s-depends. AFAIK this approach is widely used, one example is the thunderbird package which has a Provides: mail-reader. The 'provides' is already there. Can the provides include a version number? -- An avidity to punish is always dangerous to liberty. It leads men to stretch, to misinterpret, and to misapply even the best of laws. He that would make his own liberty secure must guard even his enemy from oppression: for if he violates his duty he establishes a precedent that will reach to himself. -- Thomas Paine, 1795 Rick Pasottor...@niof.nethttp://www.niof.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] direct phonecall by clicking on a phone number in the white pages
Le mardi 30 décembre 2008 à 19:16 +0100, Judith Meili a écrit : hello When I click on a phone number in http://tel.local.ch/ it wrights automatically the number in Ekiga like this: callto://+41317355755 Then I always have to delete callto://+ and write sip:0041317355755. Why does it change to callto://+. It would be very convenient if it stays like sip:00 It is a setting of your browser or desktop environment, but I do not know which one. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Colour format not supported with ekiga-svn
Le mardi 30 décembre 2008 à 20:02 +0100, Stefan Lucke a écrit : On Tuesday 30 December 2008, Damien Sandras wrote: Hi, Le mardi 30 décembre 2008 à 18:39 +0100, Stefan Lucke a écrit : Hi, I'm trying current svn version of ekiga co (was a checkout from yesterday). My camera 'logitech quickcam connect' (046d:08d9) works quite well with ekiga 2.0.11, 2.0.12, 3.0.1 but unfortunately not with current svn. Did you compile PTLIB with libv4l support ? I think I did so: ste...@jarada /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib $ grep v4l config.log $ ./configure --prefix=/usr --enable-v4l --enable-v4l2 configure:16342: running /bin/sh ./configure '--prefix=/usr' '--enable-v4l' '--enable-v4l2' --cache-file=/dev/null --srcdir=. You are confusing 'building the V4L2' plugin and 'building the V4L2 plugin with libv4l'. Libv4l is an external library that our V4L2 plugin can use. It adds support for some color palettes, and it is especially required by the spcaxxx driver you seem to be using. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Debian packages
Le mardi 30 décembre 2008 à 20:39 +0100, Eugen Dedu a écrit : Rick Pasotto wrote: gnome-desktop-environment depends on ekiga (= 2.0.12) Since 'aptitude install ekiga-snapshot' removes ekiga, gnome-desktop-environment becomes BROKEN and the installation would REMOVE 47 other packages. As far as I'm concerned, this means that ekiga-snapshot is NOT installable. I think that the problem is that the version number for ekiga-snapshot is 0-20081220-1 which is less than 2.0.12. Perhaps if the version number were changed to something greater that 2.0.12 (eg, 3-20081220-1) then the problem would go away. Hi, Increasing the version of ekiga-snapshot does not work. There are two solutions: - either stay as we are now. Note that only gnome-desktop-environment is removed (+old pwlwib/opal), not 47 packages!! - or do not use ekiga-snapshot anymore, but ekiga (while ptlib and opal are still named -snapshot, to avoid soname problems). Note that this will not be intrusive or conflict with debian package, because the version will be carefully chosen. What do people prefer?? Perhaps 1:2008blah... would work ? -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Debian packages
Rick Pasotto wrote: On Tue, Dec 30, 2008 at 08:39:54PM +0100, Eugen Dedu wrote: Rick Pasotto wrote: gnome-desktop-environment depends on ekiga (= 2.0.12) Since 'aptitude install ekiga-snapshot' removes ekiga, gnome-desktop-environment becomes BROKEN and the installation would REMOVE 47 other packages. As far as I'm concerned, this means that ekiga-snapshot is NOT installable. I think that the problem is that the version number for ekiga-snapshot is 0-20081220-1 which is less than 2.0.12. Perhaps if the version number were changed to something greater that 2.0.12 (eg, 3-20081220-1) then the problem would go away. Hi, Increasing the version of ekiga-snapshot does not work. There are two solutions: - either stay as we are now. Note that only gnome-desktop-environment is removed (+old pwlwib/opal), not 47 packages!! - or do not use ekiga-snapshot anymore, but ekiga (while ptlib and opal are still named -snapshot, to avoid soname problems). Note that this will not be intrusive or conflict with debian package, because the version will be carefully chosen. What do people prefer?? Sorry to hear that changing the version number doesn't work. I'm not really clear on exactly how the debian version number punctuation works. Did you try using 3.0.0 or even 2.9? Perhaps the fact that the first non-digit character is a '-' makes a difference. Provides does not yet work with version number. Here is a discussion on chat from this evening: eugen-busy hi! Pkg A in debian depends on pkg B (= 2.0.12). I want to create pkg B-svn, which conflicts with B. Pkg B-svn has version 1.0. The question is: what can I do so that when users install B-svn, A still remains on the system? I have changed the version of B-svn to 3.0 and make it Provides and Conflicts and Replaces B, however it still does not work (I hope I am not wrong in my check). mgoetze eugen-busy: why don't you give B version 2.0.12+svn-r1234 or something? HE eugen-busy: If you want to change the package name, you need to change A. The problem you are seeing is a misssing (?) feature in dpkg, usually called versioned provides eugen-busy I made it version 3.0, still does not work. Why 2.0.12+... should work? eugen-busy I cannot change A, A=gnome-desktop-environment Rhonda eugen-busy: versioned-depends can't be resolved by provides. HE eugen-busy: Why not? gnome-desktop-environment is easy to change, even I can do so :) eugen-busy HE, is it a joke or serious? Rhonda I don't see a joke statement here. * Piet has quit (Remote host closed the connection) eugen-busy so the correct solution is that I provide also gnome-desktop-environment with a modified Depends field? eugen-busy (only for pkg A)? HE eugen-busy: I'm more or less serious. It's not a problem to change g-d-e, it's just a package like every other (actually, it's even less complex, being a meta-package). And I can change it because I'm a Gnome maintainer :) eugen-busy it is not sufficient :o) eugen-busy I work on ekiga-snapshot packages. HE eugen-busy: Yeah, just change g-d-e to Depend on B (= 2.0.12) | B-svn Rhonda eugen-busy: versioned depends can't be resolved by provides. So if your B-svn must conflict with B and packages have versioned depends on B, these depending packages need to get changed. eugen-busy HE, could you change g-d-e to depend on ekiga (...) | ekiga-snapshot, provided that ekiga-snapshot is not in debian repository, but on ekiga own servers? ron do we really need two ekiga packages in the same suite? ron why not just upload the -svn version to experimental? eugen-busy it's because I change it very often, say once per week ron so? that's what we have version numbers for ron and what we have experimental for if it's really that volatile * glandium (~...@2a01:e35:8a5f:8130:21d:e0ff:fe26:f4b) has joined #debian-devel eugen-busy snapshots are not so stable, I think it's better to have them outside debian. HE eugen-busy: Errr ... Please file a bug ron ok, but you can still version them so they just naturally replace the earlier 'stable' snaphots eugen-busy HE, about what? e-snapshots for g-d-e or versioned provides? ron then you don't have to jump through name | name | name hoops, it all Just Works as it's supposed to eugen-busy ron, there is another impossible problem: eugen-busy ekiga depends on 2 libs, and these libs change the soname each month, so I cannot call them -snapshot too; and this pollutes package space (a binary package each month * 2) * jackyf has quit (Quit: KVIrc 3.4.0 Virgo http://www.kvirc.net/) * cortana (~...@62-31-63-21.cable.ubr12.aztw.blueyonder.co.uk) has joined #debian-devel HE eugen-busy: There's already a row of bugs about versioned provides, so just file one against g-d-e ron do they _release_ with a new soname each month, or are people just abusing it for intermediate snapshots at _every_ change? eugen-busy they _do_ release each month. I know it's not good, but... eugen-busy they _do_ release a new
Re: [Ekiga-list] Debian packages
Damien Sandras wrote: Le mardi 30 décembre 2008 à 20:39 +0100, Eugen Dedu a écrit : Rick Pasotto wrote: gnome-desktop-environment depends on ekiga (= 2.0.12) Since 'aptitude install ekiga-snapshot' removes ekiga, gnome-desktop-environment becomes BROKEN and the installation would REMOVE 47 other packages. As far as I'm concerned, this means that ekiga-snapshot is NOT installable. I think that the problem is that the version number for ekiga-snapshot is 0-20081220-1 which is less than 2.0.12. Perhaps if the version number were changed to something greater that 2.0.12 (eg, 3-20081220-1) then the problem would go away. Hi, Increasing the version of ekiga-snapshot does not work. There are two solutions: - either stay as we are now. Note that only gnome-desktop-environment is removed (+old pwlwib/opal), not 47 packages!! - or do not use ekiga-snapshot anymore, but ekiga (while ptlib and opal are still named -snapshot, to avoid soname problems). Note that this will not be intrusive or conflict with debian package, because the version will be carefully chosen. What do people prefer?? Perhaps 1:2008blah... would work ? I tried 3-... and installed it. When I try to install g-d-e, it still wants to remove ekiga-snapshot and install ekiga etc. So here I was almost sure it does not work. I checked on debian guidelines or something like that, it says more or less that versioning does not work for provide, but it was not so clear to me. Finally, I was on chat and their answer is in my previous e-mail. -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Debian packages
Rick Pasotto wrote: Can the provides include a version number? I just read about it at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-virtual, which says: So, a Provides field may not contain version numbers, and the version number of the concrete package which provides a particular virtual package will not be looked at when considering a dependency on or conflict with the virtual package name. That's also where the root of the problem lies, gnome-desktop-environment depends on a particular version number (or higher), which is not (and cannot be) provided by the virtual package. So it doesn't work via provides. Sorry for the noise. Best regards, Hannes ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] G.722 or CELT in Ekiga?
Damien Sandras wrote: Hi, Le mardi 30 décembre 2008 à 18:21 +0100, Mikael A. Bjerkeland a écrit : Hi Damien, do you have any plans to add the G.722 and CELT (http://www.celt-codec.org/) codecs to Ekiga? I just added G.722 support this week-end. However, it is not interoperable (yet) with other implementations. Ekiga advertises it as G722/16000 in the SDP (which is correct), but should advertise it as G722/8000 (which is not correct, but everybody is doing it that way because there is a mistake in the RFC!) I need to find the time to work on it. And what happened to the Debian builds? I can't find any of Ekiga 3. Not sure, they should be there. Eugen ? I have just uploaded them! They will be installable in 3 hours or so. Note that G722 is there too (but I didn't test it). -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Debian packages
Hannes Ebner wrote: Rick Pasotto wrote: Can the provides include a version number? I just read about it at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-virtual, which says: So, a Provides field may not contain version numbers, and the version number of the concrete package which provides a particular virtual package will not be looked at when considering a dependency on or conflict with the virtual package name. That's also where the root of the problem lies, gnome-desktop-environment depends on a particular version number (or higher), which is not (and cannot be) provided by the virtual package. Yes, but ekiga-snapshot is not a virtual package. That's why I was not sure 100%. So it doesn't work via provides. Sorry for the noise. -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Colour format not supported with ekiga-svn
On Tuesday 30 December 2008, Damien Sandras wrote: Le mardi 30 décembre 2008 à 20:02 +0100, Stefan Lucke a écrit : On Tuesday 30 December 2008, Damien Sandras wrote: Hi, Le mardi 30 décembre 2008 à 18:39 +0100, Stefan Lucke a écrit : Hi, I'm trying current svn version of ekiga co (was a checkout from yesterday). My camera 'logitech quickcam connect' (046d:08d9) works quite well with ekiga 2.0.11, 2.0.12, 3.0.1 but unfortunately not with current svn. Did you compile PTLIB with libv4l support ? I think I did so: ste...@jarada /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib $ grep v4l config.log $ ./configure --prefix=/usr --enable-v4l --enable-v4l2 configure:16342: running /bin/sh ./configure '--prefix=/usr' '--enable-v4l' '--enable-v4l2' --cache-file=/dev/null --srcdir=. You are confusing 'building the V4L2' plugin and 'building the V4L2 plugin with libv4l'. Libv4l is an external library that our V4L2 plugin can use. It adds support for some color palettes, and it is especially required by the spcaxxx driver you seem to be using. Thanks, I've been indeed a bit confused by those v4l options. But they where not necessary. A simple './configure --prefix=/usr' was enough for detecting everything after an 'emerge libv4l'. Ekiga svn version now works. -- Stefan Lucke ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Colour format not supported with ekiga-svn
Le mardi 30 décembre 2008 à 22:21 +0100, Stefan Lucke a écrit : On Tuesday 30 December 2008, Damien Sandras wrote: Le mardi 30 décembre 2008 à 20:02 +0100, Stefan Lucke a écrit : On Tuesday 30 December 2008, Damien Sandras wrote: Hi, Le mardi 30 décembre 2008 à 18:39 +0100, Stefan Lucke a écrit : Hi, I'm trying current svn version of ekiga co (was a checkout from yesterday). My camera 'logitech quickcam connect' (046d:08d9) works quite well with ekiga 2.0.11, 2.0.12, 3.0.1 but unfortunately not with current svn. Did you compile PTLIB with libv4l support ? I think I did so: ste...@jarada /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib $ grep v4l config.log $ ./configure --prefix=/usr --enable-v4l --enable-v4l2 configure:16342: running /bin/sh ./configure '--prefix=/usr' '--enable-v4l' '--enable-v4l2' --cache-file=/dev/null --srcdir=. You are confusing 'building the V4L2' plugin and 'building the V4L2 plugin with libv4l'. Libv4l is an external library that our V4L2 plugin can use. It adds support for some color palettes, and it is especially required by the spcaxxx driver you seem to be using. Thanks, I've been indeed a bit confused by those v4l options. But they where not necessary. A simple './configure --prefix=/usr' was enough for detecting everything after an 'emerge libv4l'. Ekiga svn version now works. Excellent news! -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Compile Problem
Hi guys, a quick mail to say I successfully compiled ekiga 3.0.1 on my OpenSUSE 11.1 (x86_64 version) at work past afternoon. just using the sources tarballs provided at www.ekiga.org I used standard ./configure command the only noticable thing is that I had to provide --libdir=/usr/lib64 explicitelly. I'll resend a mail tomorrow with the exact ./configure command I used when I'll be back at work. Hth, Fabrice Le mardi 30 décembre 2008 à 18:17 +0100, Eugen Dedu a écrit : Brian wrote: Eugen, Thanks this put me on the right track. I can confirm that suse 11.1 is the problem. In ekiga-3.0.1/lib/engine/ it still uses *.la files all these have been removed in 11.1, in addition there is practically nothing in /opt/gnome/lib. Most of those files have been moved to /usr/lib. There were about 6 other files that were deleted altogether. What a mess! Anyway I got over all of them, and engine compiled ok. Now I get to /usr/lib/gcc/i586-suse-linux/4.3/../../../../i586-suse-linux/bin/ld: cannot find -lresmgr collect2: ld returned 1 exit status make[3]: *** [ekiga] Error 1 make[3]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1' make: *** [all] Error 2 Only to discover that suse dropped support for resmgr after 10.3. It nolonger exists in 11.1. Suse now appears to use hal-resmgr. Once I figured out what libs were required where, I coped, but I do not understand how to proceed with this one. Is it possible to remove the requirement to load resmgr? Hi, I didn't know what resmgr is, so I took a look at http://www.lst.de/~okir/resmgr. In debian, my machine, resmgr does not exist. I searched resmgr in ekiga, ptlib and opal, and I haven't found it either. So I imagine it's suse which adds it to the command line?? Look at the parameters of gcc (gcc -v or other flags, I don't know). Also, try to install the package providing resmgr library. -- ALPHONSO Fabrice http://alphonso.dyndns.org/blog/ http://alphonso.dyndns.org/gallery2/ sip:fabr...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Compile Problem
Eugen, Only to discover that suse dropped support for resmgr after 10.3. It nolonger exists in 11.1. Suse now appears to use hal-resmgr. Once I figured out what libs were required where, I coped, but I do not understand how to proceed with this one. Is it possible to remove the requirement to load resmgr? I didn't know what resmgr is, so I took a look at http://www.lst.de/~okir/resmgr. In debian, my machine, resmgr does not exist. I searched resmgr in ekiga, ptlib and opal, and I haven't found it either. So I imagine it's suse which adds it to the command line?? Look at the parameters of gcc (gcc -v or other flags, I don't know). Also, try to install the package providing resmgr library. On my system the following files reference resmgr. file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/libekiga_engine.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/.libs/libekiga_engine.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/libekiga.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/.libs/libekiga.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/gui/gtk-core/libgmgtk-core.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/gui/gtk-core/.libs/libgmgtk-core.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/gui/gtk-frontend/libgmgtk-frontend.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/gui/gtk-frontend/.libs/libgmgtk-frontend.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/gui/libgmwidgets.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/gui/.libs/libgmwidgets.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/toolbox/libtoolbox.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/toolbox/.libs/libtoolbox.la On your debian system do you use *.la files at all? If not then I need to look at why I do. Thanks, Brian ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Compile Problem
Fabrice, a quick mail to say I successfully compiled ekiga 3.0.1 on my OpenSUSE 11.1 (x86_64 version) at work past afternoon. just using the sources tarballs provided at www.ekiga.org I used standard ./configure command the only noticable thing is that I had to provide --libdir=/usr/lib64 explicitelly. Great, at least we know it is possible. Can I ask if you did a new install of 11.1 or an upgrade? I am using the same tarballs as you but somehow I end up looking for resmgr. I'll resend a mail tomorrow with the exact ./configure command I used when I'll be back at work. Will give it another go as soon as I get it. Brian ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
