Re: [Ekiga-devel-list] Status of ekiga tunk?
Quoting Peter Robinson [EMAIL PROTECTED]: BTW updated to Fedora 9 rawhide and with gcc 4.3 and any other changes they've made the OPAL build breaks again g++ -I../../../include -DWITH_RFC_COMPLIANT_DEFAULTS -I../common -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c h261vic.cxx -o obj/h261vic.o h261vic.cxx: In member function 'int H261EncoderContext::EncodeFrames(const unsigned char*, unsigned int, unsigned char*, unsigned int, unsigned int)': h261vic.cxx:275: warning: comparison between signed and unsigned integer expressions ..deleted I did a complete compile of OPAL SVN trunk with gcc 4.3 just after it was released and fixed the few problems that came up. I did it again again a few minutes ago and there were no issues. Well its probably the combination of Fedora enabling some extra stuff in their build system in what will become Fedora9 then. I compiled it OK a couple of days ago on Fedora 8 and just retried again using the latest SVN (rev 19779) and the last of the build before is fails is included below. Peter gcc -I../../../include -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c ima_adpcm.c -o obj/ima_adpcm.o ima_adpcm.c:435: warning: missing braces around initializer ima_adpcm.c:435: warning: (near initialization for 'imaADPCMCodecDefn[0].parm') gcc -shared -Wl,-soname,ima_adpcm -o ima_adpcm_audio_pwplugin.so obj/ima_adpcm.o make[3]: Leaving directory `/usr/src/redhat/BUILD/opal-3.3.0/plugins/audio/IMA_ADPCM' make[3]: Entering directory `/usr/src/redhat/BUILD/opal-3.3.0/plugins/audio/gsm-amr' gcc -g -c -I../../../include -fPIC -I../../../include -I./src -DIF2 -o obj/amrcodec.o amrcodec.c amrcodec.c: In function 'amr_codec_encoder': amrcodec.c:161: warning: incompatible implicit declaration of built-in function 'memcpy' gcc -g -c -I../../../include -fPIC -I../../../include -I./src -DIF2 -o obj/interf_enc.o ./src/interf_enc.c gcc -g -c -I../../../include -fPIC -I../../../include -I./src -DIF2 -o obj/interf_dec.o ./src/interf_dec.c gcc -g -c -I../../../include -fPIC -I../../../include -I./src -DIF2 -o obj/sp_dec.o ./src/sp_dec.c gcc -g -c -I../../../include -fPIC -I../../../include -I./src -DIF2 -o obj/sp_enc.o ./src/sp_enc.c gcc -shared -Wl,-soname,gsmamrcodec -o gsmamrcodec_pwplugin.so obj/amrcodec.o obj/interf_enc.o obj/interf_dec.o obj/sp_dec.o obj/sp_enc.o make[3]: Leaving directory `/usr/src/redhat/BUILD/opal-3.3.0/plugins/audio/gsm-amr' make[3]: Entering directory `/usr/src/redhat/BUILD/opal-3.3.0/plugins/video/H.261-vic' g++ -I../../../include -DWITH_RFC_COMPLIANT_DEFAULTS -I../common -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c h261vic.cxx -o obj/h261vic.o h261vic.cxx: In member function 'int H261EncoderContext::EncodeFrames(const unsigned char*, unsigned int, unsigned char*, unsigned int, unsigned int)': h261vic.cxx:275: warning: comparison between signed and unsigned integer expressions h261vic.cxx: At global scope: h261vic.cxx:1189: warning: missing braces around initializer for 'PluginCodec_Definition::_parm' h261vic.cxx:1189: warning: missing braces around initializer for 'PluginCodec_Definition::_parm::_audio' h261vic.cxx:1189: warning: missing braces around initializer for 'PluginCodec_Definition::_parm' h261vic.cxx:1189: warning: missing braces around initializer for 'PluginCodec_Definition::_parm::_audio' h261vic.cxx:1189: warning: missing braces around initializer for 'PluginCodec_Definition::_parm' h261vic.cxx:1189: warning: missing braces around initializer for 'PluginCodec_Definition::_parm::_audio' h261vic.cxx:1189: warning: missing braces around initializer for 'PluginCodec_Definition::_parm' h261vic.cxx:1189: warning: missing braces around initializer for 'PluginCodec_Definition::_parm::_audio' h261vic.cxx:1189: warning: missing braces around initializer for 'PluginCodec_Definition::_parm' h261vic.cxx:1189: warning: missing braces around initializer for 'PluginCodec_Definition::_parm::_audio' h261vic.cxx:1189: warning: missing braces around initializer for 'PluginCodec_Definition::_parm' h261vic.cxx:1189: warning: missing braces around initializer for 'PluginCodec_Definition::_parm::_audio' g++ -I../../../include -DWITH_RFC_COMPLIANT_DEFAULTS -I../common -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
Re: [Ekiga-list] Fwd: Re: ekiga fails to use sound card, other apps do, config help?
El día Tuesday, March 18, 2008 a las 10:15:59AM -0400, Steve Ames escribió: How could I have access to the pwlib in CVS? I followed what the page http://www.openh323.org/cvs.html says but get connection refused: openh323.org has been a dead-ish site for years. pwlib and openh323 were hosted at voxgratia for a while until the developers had a disagreement and split the projects into h323plus and opal. pwlib has been renamed ptlib in the new order. See: http://www.h323plus.org/ for the latest h323 code http://www.opalvoip.org/ for the latest opal and pwlib/ptlib Both run their CVS off sourceforge now I believe. And I'm confused; the FreeBSD ports speek about pwlib and fetches some tar file pwlib-v1_10_1-src-tar.gz , but the above www.openh323.org speeks about 'ptlib_unix', what is the relation of this? FreeBSD port is currently using pwlib version 1.12.0. I believe that will be the last one actually called pwlib. It was the transition version its pwlib in someplaces and ptlib in others. However the official cut is ptlib 2.0. ptlib_unix is actually the unix based telephony library that comes in pwlib. With the transition to just being ptlib a lot of the windowing libraries got chopped out (they were never used anyway) which streamlined/focused the codebase considerably. Hope this helps the confusion a bit :) Hi Steve, Thanks for the explanation, now I have some light in that jungle :-) maybe it's woth to correct in that case the file pkg-descr of /usr/ports/devel/pwlib which still points (and made me going there) to http://www.openh323.org/ Thx again matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Ekiga V4L FreeBSD
Hello, I've got finally my cam and it attaches fine on USB to the driver: Mar 19 10:31:28 rebelion kernel: pwc0: vendor 0x0471 product 0x0329, rev 1.10/0.03, addr 2 Mar 19 10:31:29 rebelion kernel: pwc0: Philips SPC900NC USB webcam Mar 19 10:31:29 rebelion kernel: pwc0: This camera is equipped with a Sony CCD sensor + TDA8787 (32 the user land application 'pwcview' works fine as well; Ekiga says on start: ... 2008/03/19 10:37:09.739 0:00.414 ekiga Detected the following video input devices: No device found with plugin V4L when I use gconf-editor to set the video device for the application to /dev/video0, Ekiga detects this as: 2008/03/19 10:37:38.369 0:29.044 ekiga PVideoInputDevice_V4L: GetFrameSizeLimits. 160x120 -- 640x480 2008/03/19 10:37:38.528 0:29.203 ekiga PVideoInputDevice_V4L: GetFrameSizeLimits. 160x120 -- 640x480 2008/03/19 10:37:38.543 0:29.218 GMVideoGrabber:0858 VideoGrabber cannot do memory mapping - GMBUF failed. and all is working fine in a video conference; but when I restart ekiga it looses the device and I have to re-insert it with gconf-editor; any hints about this? Thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga Panasonic PV-GS320
Le mardi 18 mars 2008 à 23:28 -0300, J. Paul Bissonnette a écrit : Damien Sandras wrote: Le lundi 17 mars 2008 à 19:17 -0300, J. Paul Bissonnette a écrit : Damien Sandras wrote: Le dimanche 16 mars 2008 à 20:47 -0300, J. Paul Bissonnette a écrit : Part is not working, the audio input DVC, the camera, Video plugins are V4L, V4L2 neither can find the camera. Do you have any other installed? Is the linux driver loaded for your camera? Using the configuration assistant I can use the camera Microphone as the audio input. The next step is the video input, choices are pictures, V4l, V4l2 or 1394avc, but none find the camera. I have the V4L2 loaded. I tried the camera on an Edubuntu 7.10 amd64 it worked with the V4L2 module. Interesting. Compare the lsmod output on both machines. The Module that is missing on the box that does not display the video is call what else video. Which package in Debian testing supplies the video mod? Perhaps the kernel package ? Modprobe video got the video mod loaded camera still not found It is probably a permission problem in that case. Probably you should ask your question on a mailing list dedicated to that distribution ? -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga V4L FreeBSD
Le mercredi 19 mars 2008 à 10:52 +0100, Matthias Apitz a écrit : Hello, I've got finally my cam and it attaches fine on USB to the driver: Mar 19 10:31:28 rebelion kernel: pwc0: vendor 0x0471 product 0x0329, rev 1.10/0.03, addr 2 Mar 19 10:31:29 rebelion kernel: pwc0: Philips SPC900NC USB webcam Mar 19 10:31:29 rebelion kernel: pwc0: This camera is equipped with a Sony CCD sensor + TDA8787 (32 the user land application 'pwcview' works fine as well; Ekiga says on start: ... 2008/03/19 10:37:09.739 0:00.414 ekiga Detected the following video input devices: No device found with plugin V4L when I use gconf-editor to set the video device for the application to /dev/video0, Ekiga detects this as: 2008/03/19 10:37:38.369 0:29.044 ekiga PVideoInputDevice_V4L: GetFrameSizeLimits. 160x120 -- 640x480 2008/03/19 10:37:38.528 0:29.203 ekiga PVideoInputDevice_V4L: GetFrameSizeLimits. 160x120 -- 640x480 2008/03/19 10:37:38.543 0:29.218 GMVideoGrabber:0858 VideoGrabber cannot do memory mapping - GMBUF failed. and all is working fine in a video conference; but when I restart ekiga it looses the device and I have to re-insert it with gconf-editor; any hints about this? Probably a bug in the driver. Why doesn't it detect the device ? It works fine on linux... -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] [SHORT TEST] (again)
Hello, If you believe your Ekiga is working well, please give a try at sip:[EMAIL PROTECTED] for a short ( one minute) audio test only. Thanks in advance, Jacques -- To my old friends : ALL my @pollux.frmug.org adresses are intensively spammed. Please update your address book with : [EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [SHORT TEST] (again)
On Wed, Mar 19, 2008 at 11:34 AM, jacques [EMAIL PROTECTED] wrote: Hello, If you believe your Ekiga is working well, please give a try at sip:[EMAIL PROTECTED] for a short ( one minute) audio test only. Sorry jacques , Ekiga SVN was not really working for me on Gutsy so i could not call you the other night. Is it possible to test vidéo as well ? mIt the major feature I'd like to test. Do you have a Jabber adress ? Because SIMPLE is not really working most of the time .. -- %---% Michel memeteau Blog 0.2 : http://memeteau.free.fr Fixe : 0874763294 Mobile : 0624808051 VOIP | Visio: sip:[EMAIL PROTECTED] jabber/GoogleTalk : xmpp:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga V4L FreeBSD
El día Wednesday, March 19, 2008 a las 11:29:25AM +0100, Damien Sandras escribió: /dev/video0, Ekiga detects this as: 2008/03/19 10:37:38.369 0:29.044 ekiga PVideoInputDevice_V4L: GetFrameSizeLimits. 160x120 -- 640x480 2008/03/19 10:37:38.528 0:29.203 ekiga PVideoInputDevice_V4L: GetFrameSizeLimits. 160x120 -- 640x480 2008/03/19 10:37:38.543 0:29.218 GMVideoGrabber:0858 VideoGrabber cannot do memory mapping - GMBUF failed. and all is working fine in a video conference; but when I restart ekiga it looses the device and I have to re-insert it with gconf-editor; any hints about this? Probably a bug in the driver. Why doesn't it detect the device ? It works fine on linux... What is on Linux the major and minor number of the device file for the cam? on FreeBSD it is: $ ls -l /dev/video0 crw-rw-rw- 1 root operator0, 146 19 mar 09:02 /dev/video0 it seems that the algorithm in vidinput_v4l.cxx depends on minor numbers below 63 in void V4LNames::ReadDeviceDirectory() see also the CVS comment: * Revision 1.3 2003/11/25 22:55:13 dsandras * Added fallback using major and minor numbers for detection of devices * when /proc/video doesn't exist (some 2.4 kernels and all 2.6 kernels). matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga V4L FreeBSD
El día Wednesday, March 19, 2008 a las 11:48:00AM +0100, Matthias Apitz
escribió:
What is on Linux the major and minor number of the device file for the
cam? on FreeBSD it is:
$ ls -l /dev/video0
crw-rw-rw- 1 root operator0, 146 19 mar 09:02 /dev/video0
it seems that the algorithm in vidinput_v4l.cxx depends on minor
numbers below 63 in void V4LNames::ReadDeviceDirectory()
see also the CVS comment:
* Revision 1.3 2003/11/25 22:55:13 dsandras
* Added fallback using major and minor numbers for detection of devices
* when /proc/video doesn't exist
(some 2.4 kernels and all 2.6 kernels).
Yes, it is an issue of major/minor numbers which are diffrent in Linux
and FreeBSD vor the cam; with this small change:
# pwd
/usr/ports/devel/pwlib/work/pwlib_Phobos_release2/plugins/vidinput_v4l
# diff vidinput_v4l.cxx*
462,464c462
// static const int deviceNumbers[] = { 81 };
// for FreeBSD's pwc driver the major number is 0 and minor is 146
static const int deviceNumbers[] = { 0 };
---
static const int deviceNumbers[] = { 81 };
468,469c466
// if (num = 63 num = 0) {
if (num = 146 num = 146) {
---
if (num = 63 num = 0) {
the driver attaches without any problem; to whom to talk about get this
integrated into pwlib?
matthias
--
Matthias Apitz
Manager Technical Support - OCLC GmbH
Gruenwalder Weg 28g - 82041 Oberhaching - Germany
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/
b http://gurucubano.blogspot.com/
Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga V4L FreeBSD
Le mercredi 19 mars 2008 à 13:09 +0100, Matthias Apitz a écrit :
El día Wednesday, March 19, 2008 a las 11:48:00AM +0100, Matthias Apitz
escribió:
What is on Linux the major and minor number of the device file for the
cam? on FreeBSD it is:
$ ls -l /dev/video0
crw-rw-rw- 1 root operator0, 146 19 mar 09:02 /dev/video0
it seems that the algorithm in vidinput_v4l.cxx depends on minor
numbers below 63 in void V4LNames::ReadDeviceDirectory()
see also the CVS comment:
* Revision 1.3 2003/11/25 22:55:13 dsandras
* Added fallback using major and minor numbers for detection of devices
* when /proc/video doesn't exist
(some 2.4 kernels and all 2.6 kernels).
Yes, it is an issue of major/minor numbers which are diffrent in Linux
and FreeBSD vor the cam; with this small change:
# pwd
/usr/ports/devel/pwlib/work/pwlib_Phobos_release2/plugins/vidinput_v4l
# diff vidinput_v4l.cxx*
462,464c462
// static const int deviceNumbers[] = { 81 };
// for FreeBSD's pwc driver the major number is 0 and minor is 146
static const int deviceNumbers[] = { 0 };
---
static const int deviceNumbers[] = { 81 };
468,469c466
// if (num = 63 num = 0) {
if (num = 146 num = 146) {
---
if (num = 63 num = 0) {
the driver attaches without any problem; to whom to talk about get this
integrated into pwlib?
Mail me the patch, I will commit it to trunk.
Isn't the patch also needed for vidinput_v4l2 ?
--
_ Damien Sandras
(o-
//\Ekiga Softphone : http://www.ekiga.org/
v_/_ NOVACOM : http://www.novacom.be/
FOSDEM : http://www.fosdem.org/
SIP Phone : sip:[EMAIL PROTECTED]
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga V4L FreeBSD
El día Wednesday, March 19, 2008 a las 01:51:45PM +0100, Damien Sandras
escribió:
Le mercredi 19 mars 2008 à 13:09 +0100, Matthias Apitz a écrit :
El día Wednesday, March 19, 2008 a las 11:48:00AM +0100, Matthias Apitz
escribió:
What is on Linux the major and minor number of the device file for the
cam? on FreeBSD it is:
$ ls -l /dev/video0
crw-rw-rw- 1 root operator0, 146 19 mar 09:02 /dev/video0
it seems that the algorithm in vidinput_v4l.cxx depends on minor
numbers below 63 in void V4LNames::ReadDeviceDirectory()
see also the CVS comment:
* Revision 1.3 2003/11/25 22:55:13 dsandras
* Added fallback using major and minor numbers for detection of devices
* when /proc/video doesn't exist
(some 2.4 kernels and all 2.6 kernels).
Yes, it is an issue of major/minor numbers which are diffrent in Linux
and FreeBSD vor the cam; with this small change:
# pwd
/usr/ports/devel/pwlib/work/pwlib_Phobos_release2/plugins/vidinput_v4l
# diff vidinput_v4l.cxx*
462,464c462
// static const int deviceNumbers[] = { 81 };
// for FreeBSD's pwc driver the major number is 0 and minor is
146
static const int deviceNumbers[] = { 0 };
---
static const int deviceNumbers[] = { 81 };
468,469c466
// if (num = 63 num = 0) {
if (num = 146 num = 146) {
---
if (num = 63 num = 0) {
the driver attaches without any problem; to whom to talk about get this
integrated into pwlib?
Mail me the patch, I will commit it to trunk.
Isn't the patch also needed for vidinput_v4l2 ?
Yes, the same hardcode major/minor number is in vidinput_names.cxx for
vidinput_v4l2;
concerning a patch, I can't provide a common solution which works on
Linux and FreeBSD because I'm not a C++ programmer; I only could hack
the code as shown above so that it will work in FreeBSD; maybe Steve
should just put this into a patch file for the /usr/ports/devel/pwlib in
the FreeBSD ports tree; Steve?
matthias
--
Matthias Apitz
Manager Technical Support - OCLC GmbH
Gruenwalder Weg 28g - 82041 Oberhaching - Germany
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/
b http://gurucubano.blogspot.com/
Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Fwd: Re: ekiga fails to use sound card, other apps do, config help?
On Wed, Mar 19, 2008 at 09:18:12AM +0100, Matthias Apitz wrote: maybe it's woth to correct in that case the file pkg-descr of /usr/ports/devel/pwlib which still points (and made me going there) to http://www.openh323.org/ Probably. I've never even looked at that file since I picked up maintainership. Heh. -Steve ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
Is it possible there is a mixup in version numbers? I installed Gnome Slackbuild on a Slackware 12.0 box, and this is clearly identified as 2.0.11. I also tried the Windows version that was 2.0.11. The Windows version was from Ekiga site today, 10 Mar 2008. The bugs listed as fixed in 2.0.11 appear to be still present. For instance, - 1. Linux Slackware 12.0 Ekiga from Gnome Slackbuild. I get assertion errors: sndrv_pcm_hw_params: Assertion `err = 0' failed I am using well known Ensoniq ES1371 chipset/driver. The ALSA mixer controls sound fine, and sound system in general works great otherwise with all other software. It was proposed this assert error might be an ALSA-lib problem, but it looks like Ekiga programmers have been working on assertion errors in Ekiga, fixing (some of?) them in 2.0.11. --- 2. Windows XP version 5.1.2600, different computer. I get the Error installing GTK+ runtime that was supposedly fixed in 2.0.11. --- Looks like a great program, but have had little to no success getting this to actually work yet on Windows, Linux or FreeBSD. The light at the end of the tunnel looks bright though. Dee _ Helping your favorite cause is as easy as instant messaging. You IM, we give. http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
Le mercredi 19 mars 2008 à 13:54 +, D Webb a écrit : Is it possible there is a mixup in version numbers? I installed Gnome Slackbuild on a Slackware 12.0 box, and this is clearly identified as 2.0.11. I also tried the Windows version that was 2.0.11. The Windows version was from Ekiga site today, 10 Mar 2008. The bugs listed as fixed in 2.0.11 appear to be still present. For instance, - 1. Linux Slackware 12.0 Ekiga from Gnome Slackbuild. I get assertion errors: sndrv_pcm_hw_params: Assertion `err = 0' failed I am using well known Ensoniq ES1371 chipset/driver. The ALSA mixer controls sound fine, and sound system in general works great otherwise with all other software. It was proposed this assert error might be an ALSA-lib problem, but it looks like Ekiga programmers have been working on assertion errors in Ekiga, fixing (some of?) them in 2.0.11. This bug is an ALSA bug, not an Ekiga bug, we can not do anything about it. --- 2. Windows XP version 5.1.2600, different computer. I get the Error installing GTK+ runtime that was supposedly fixed in 2.0.11. I do not know about that one. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
1. Linux Slackware 12.0 Ekiga from Gnome Slackbuild. I get assertion errors: sndrv_pcm_hw_params: Assertion `err = 0' failed I am using well known Ensoniq ES1371 chipset/driver. The ALSA mixer controls sound fine, and sound system in general works great otherwise with all other software. It was proposed this assert error might be an ALSA-lib problem, but it looks like Ekiga programmers have been working on assertion errors in Ekiga, fixing (some of?) them in 2.0.11. This bug is an ALSA bug, not an Ekiga bug, we can not do anything about it. Thanks for response! Any thoughts on how to end up using Ekiga under Linux, given this ALSA bug has apparently been around for a while? Dee _ Need to know the score, the latest news, or you need your Hotmail®-get your fix. http://www.msnmobilefix.com/Default.aspx___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga V4L FreeBSD
On Wed, Mar 19, 2008 at 01:09:46PM +0100, Matthias Apitz wrote:
Yes, it is an issue of major/minor numbers which are diffrent in Linux
and FreeBSD vor the cam; with this small change:
# pwd
/usr/ports/devel/pwlib/work/pwlib_Phobos_release2/plugins/vidinput_v4l
# diff vidinput_v4l.cxx*
462,464c462
// static const int deviceNumbers[] = { 81 };
// for FreeBSD's pwc driver the major number is 0 and minor is 146
static const int deviceNumbers[] = { 0 };
---
static const int deviceNumbers[] = { 81 };
468,469c466
// if (num = 63 num = 0) {
if (num = 146 num = 146) {
---
if (num = 63 num = 0) {
the driver attaches without any problem; to whom to talk about get this
integrated into pwlib?
The following patch exists in the freebsd port, does it already
address this issue?
--- plugins/vidinput_v4l/vidinput_v4l.cxx.orig Wed Jan 3 23:37:37 2007
+++ plugins/vidinput_v4l/vidinput_v4l.cxx Wed Feb 7 01:30:50 2007
@@ -484,6 +484,15 @@
struct stat s;
if (lstat(devname, s) == 0) {
+#if defined(P_FREEBSD)
+ // device numbers are irrelevant here, so we match on names instead.
+ if (filename.GetLength() = 5 || filename.Left(5) != video)
+ continue;
+ int num = atoi(filename.Mid(6));
+ if (num 0 || num 63)
+ continue;
+ vid.SetAt(num, devname);
+#else
static const int deviceNumbers[] = { 81 };
for (PINDEX i = 0; i PARRAYSIZE(deviceNumbers); i++) {
if (MAJOR(s.st_rdev) == deviceNumbers[i]) {
@@ -493,6 +502,7 @@
}
}
}
+#endif
}
}
}
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
Le mercredi 19 mars 2008 à 14:06 +, D Webb a écrit : 1. Linux Slackware 12.0 Ekiga from Gnome Slackbuild. I get assertion errors: sndrv_pcm_hw_params: Assertion `err = 0' failed I am using well known Ensoniq ES1371 chipset/driver. The ALSA mixer controls sound fine, and sound system in general works great otherwise with all other software. It was proposed this assert error might be an ALSA-lib problem, but it looks like Ekiga programmers have been working on assertion errors in Ekiga, fixing (some of?) them in 2.0.11. This bug is an ALSA bug, not an Ekiga bug, we can not do anything about it. Thanks for response! Any thoughts on how to end up using Ekiga under Linux, given this ALSA bug has apparently been around for a while? See this : https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2601 There are alsa patches. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
This bug is an ALSA bug, not an Ekiga bug, we can not do anything about it. Thanks for response! Any thoughts on how to end up using Ekiga under Linux, given this ALSA bug has apparently been around for a while? See this : https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2601 There are alsa patches. -- _ Damien Sandras I maybe should have mentioned that I already have those patches. Did not fix this unfortunately. Dee _ Helping your favorite cause is as easy as instant messaging. You IM, we give. http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
Le mercredi 19 mars 2008 à 14:21 +, D Webb a écrit : This bug is an ALSA bug, not an Ekiga bug, we can not do anything about it. Thanks for response! Any thoughts on how to end up using Ekiga under Linux, given this ALSA bug has apparently been around for a while? See this : https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2601 There are alsa patches. -- _ Damien Sandras I maybe should have mentioned that I already have those patches. Did not fix this unfortunately. You should probably add a comment on their bugtracker in that case. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
Hello Dee, On Wed, Mar 19, 2008 at 8:21 AM, D Webb [EMAIL PROTECTED] wrote: This bug is an ALSA bug, not an Ekiga bug, we can not do anything about it. Thanks for response! Any thoughts on how to end up using Ekiga under Linux, given this ALSA bug has apparently been around for a while? See this : https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2601 There are alsa patches. -- _ Damien Sandras I maybe should have mentioned that I already have those patches. Did not fix this unfortunately. I am running UbuntuStudio 7.10 and Ekiga 2.0.11 which is Linux and all works fine. I do have some problems with sound breaking up but it works. Peaceed Edward Dunagin-Dunigan-Dunnigan Bozeman, MT 59718 mobile 406-570-0992 Landline 406-556-7282 VOIP:sip:[EMAIL PROTECTED]:5063;transport=udp http://doas.montanalinux.org ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
See this : https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2601 There are alsa patches. -- _ Damien Sandras I maybe should have mentioned that I already have those patches. Did not fix this unfortunately. You should probably add a comment on their bugtracker in that case. -- _ Damien Sandras Great idea. Please note I submitted this bug report to ALSA: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3825 Dee _ Helping your favorite cause is as easy as instant messaging. You IM, we give. http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
I am running UbuntuStudio 7.10 and Ekiga 2.0.11 which is Linux and all works fine. I do have some problems with sound breaking up but it works. Peaceed Edward Dunagin-Dunigan-Dunnigan Excellent! I can see Ekiga is almost working on my Slackware box. It looks to work fine until it crashes due to this assert bug. Could you please offer a few details? For instance, which kernel and are you using ALSA (version?) or some other? What audio hardware? Along these lines I am about to buy a notebook, and would be inclined to go for hardware that others have used Ekiga with success. Dee _ Connect and share in new ways with Windows Live. http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
Le mercredi 19 mars 2008 à 14:26 +, D Webb a écrit : See this : https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2601 There are alsa patches. -- _ Damien Sandras I maybe should have mentioned that I already have those patches. Did not fix this unfortunately. You should probably add a comment on their bugtracker in that case. -- _ Damien Sandras Great idea. Please note I submitted this bug report to ALSA: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3825 Excellent, please add a link to : http://bugzilla.gnome.org/show_bug.cgi?id=413552 And tell them that we have many many duplicates. Btw, are you using pulseaudio ? -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
Dee, On Wed, Mar 19, 2008 at 8:31 AM, D Webb [EMAIL PROTECTED] wrote: I am running UbuntuStudio 7.10 and Ekiga 2.0.11 which is Linux and all works fine. I do have some problems with sound breaking up but it works. Peaceed Edward Dunagin-Dunigan-Dunnigan Excellent! I can see Ekiga is almost working on my Slackware box. It looks to work fine until it crashes due to this assert bug. Could you please offer a few details? For instance, which kernel and are you using ALSA (version?) or some other? What audio hardware? Along these lines I am about to buy a notebook, and would be inclined to go for hardware that others have used Ekiga with success. I running a desktop p-4 with 1gb of ram, kernel 2.6.22-14-generic. gstreamer 0.10 Edward Dunagin-Dunigan-Dunnigan Bozeman, MT 59718 mobile 406-570-0992 Landline 406-556-7282 VOIP:sip:[EMAIL PROTECTED]:5063;transport=udp http://doas.montanalinux.org ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
On Wed, Mar 19, 2008 at 8:38 AM, Damien Sandras [EMAIL PROTECTED] wrote: Le mercredi 19 mars 2008 à 14:26 +, D Webb a écrit : See this : https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2601 There are alsa patches. -- _ Damien Sandras I maybe should have mentioned that I already have those patches. Did not fix this unfortunately. You should probably add a comment on their bugtracker in that case. -- _ Damien Sandras Great idea. Please note I submitted this bug report to ALSA: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3825 Excellent, please add a link to : http://bugzilla.gnome.org/show_bug.cgi?id=413552 And tell them that we have many many duplicates. Btw, are you using pulseaudio ? Sorry to but in, when I use Pulseaudio ekiga sound will not work. I kill pulseaudio and ekiga works ok. I do get these errors: [EMAIL PROTECTED]:~$ ekiga [1] 7602 [EMAIL PROTECTED]:~$ (ekiga:7602): Gnome-WARNING **: invalid gnome config path '=/section/key' (ekiga:7602): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.14.1/gobject/gsignal.c:1019: unable to lookup signal show of unloaded type `GtkMessageDialog' (ekiga:7602): GLib-GObject-CRITICAL **: g_signal_add_emission_hook: assertion `signal_id 0' failed but Ekiga comes up and works. Hope this helps...ed -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -- Edward Dunagin-Dunigan-Dunnigan Bozeman, MT 59718 mobile 406-570-0992 Landline 406-556-7282 VOIP:sip:[EMAIL PROTECTED]:5063;transport=udp http://doas.montanalinux.org ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
I submitted this bug report to ALSA: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3825 Excellent, please add a link to : http://bugzilla.gnome.org/show_bug.cgi?id=413552 And tell them that we have many many duplicates. Done: 0018447 Btw, are you using pulseaudio ? -- _ Damien Sandras I am pretty sure, yes. I took no specific action to add or remove it. I just installed Linux Slackware 12.0 straight off the DVD without any custom settings. I saw a message about pulseaudio during bootup. Could you imagine removing it might help? If so, I would welcome tips on how. Dominic _ Climb to the top of the charts! Play the word scramble challenge with star power. http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_jan___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
Btw, are you using pulseaudio ? Sorry to but in, when I use Pulseaudio ekiga sound will not work. I kill pulseaudio and ekiga works ok. I do get these errors: Thanks for butting in. More ideas means quicker fixes. I have wondered about this for some time. In connection with Ekiga crashes, Pulseaudio keeps popping up. I don't know what it is, but pretty sure it comes installed by default on Slackware 12.0, which is what I have. I should at least try removing it. So, how do I kill pulseaudio? Dee _ Shed those extra pounds with MSN and The Biggest Loser! http://biggestloser.msn.com/___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga V4L FreeBSD
El día Wednesday, March 19, 2008 a las 09:58:10AM -0400, Steve Ames escribió:
The following patch exists in the freebsd port, does it already
address this issue?
--- plugins/vidinput_v4l/vidinput_v4l.cxx.origWed Jan 3 23:37:37 2007
+++ plugins/vidinput_v4l/vidinput_v4l.cxx Wed Feb 7 01:30:50 2007
@@ -484,6 +484,15 @@
struct stat s;
if (lstat(devname, s) == 0) {
+#if defined(P_FREEBSD)
+ // device numbers are irrelevant here, so we match on names instead.
+ if (filename.GetLength() = 5 || filename.Left(5) != video)
+ continue;
+ int num = atoi(filename.Mid(6));
+ if (num 0 || num 63)
+ continue;
+ vid.SetAt(num, devname);
+#else
static const int deviceNumbers[] = { 81 };
for (PINDEX i = 0; i PARRAYSIZE(deviceNumbers); i++) {
if (MAJOR(s.st_rdev) == deviceNumbers[i]) {
@@ -493,6 +502,7 @@
}
}
}
+#endif
}
}
}
Yes, I've tried this patch in the source and it picks up the /dev/video0
file as well;
now I've the next problem:
when I make a call h323:10.0.1.40 to the VX700 where I'm sitting with my
laptop in front of, I can see in Ekiga the local picture from my cam and
the picture grabed by the cam of the VX700 in side-by-side view
mode, but the TV the VX700 is connected to only shows the name of the
session and the rest is dark; I have a -d3 output if this would be
helpfull for you, Damien; thx for any hint;
matthias
--
Matthias Apitz
Manager Technical Support - OCLC GmbH
Gruenwalder Weg 28g - 82041 Oberhaching - Germany
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/
b http://gurucubano.blogspot.com/
Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga V4L FreeBSD
Le mercredi 19 mars 2008 à 14:11 +0100, Matthias Apitz a écrit :
El día Wednesday, March 19, 2008 a las 01:51:45PM +0100, Damien Sandras
escribió:
Le mercredi 19 mars 2008 à 13:09 +0100, Matthias Apitz a écrit :
El día Wednesday, March 19, 2008 a las 11:48:00AM +0100, Matthias Apitz
escribió:
What is on Linux the major and minor number of the device file for the
cam? on FreeBSD it is:
$ ls -l /dev/video0
crw-rw-rw- 1 root operator0, 146 19 mar 09:02 /dev/video0
it seems that the algorithm in vidinput_v4l.cxx depends on minor
numbers below 63 in void V4LNames::ReadDeviceDirectory()
see also the CVS comment:
* Revision 1.3 2003/11/25 22:55:13 dsandras
* Added fallback using major and minor numbers for detection of devices
* when /proc/video doesn't exist
(some 2.4 kernels and all 2.6 kernels).
Yes, it is an issue of major/minor numbers which are diffrent in Linux
and FreeBSD vor the cam; with this small change:
# pwd
/usr/ports/devel/pwlib/work/pwlib_Phobos_release2/plugins/vidinput_v4l
# diff vidinput_v4l.cxx*
462,464c462
// static const int deviceNumbers[] = { 81 };
// for FreeBSD's pwc driver the major number is 0 and minor
is 146
static const int deviceNumbers[] = { 0 };
---
static const int deviceNumbers[] = { 81 };
468,469c466
// if (num = 63 num = 0) {
if (num = 146 num = 146) {
---
if (num = 63 num = 0) {
the driver attaches without any problem; to whom to talk about get this
integrated into pwlib?
Mail me the patch, I will commit it to trunk.
Isn't the patch also needed for vidinput_v4l2 ?
Yes, the same hardcode major/minor number is in vidinput_names.cxx for
vidinput_v4l2;
concerning a patch, I can't provide a common solution which works on
Linux and FreeBSD because I'm not a C++ programmer; I only could hack
the code as shown above so that it will work in FreeBSD; maybe Steve
should just put this into a patch file for the /usr/ports/devel/pwlib in
the FreeBSD ports tree; Steve?
And contribute it back to us, otherwise we can not commit it...
--
_ Damien Sandras
(o-
//\Ekiga Softphone : http://www.ekiga.org/
v_/_ NOVACOM : http://www.novacom.be/
FOSDEM : http://www.fosdem.org/
SIP Phone : sip:[EMAIL PROTECTED]
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga V4L FreeBSD
Le mercredi 19 mars 2008 à 17:11 +0100, Matthias Apitz a écrit :
El día Wednesday, March 19, 2008 a las 09:58:10AM -0400, Steve Ames escribió:
The following patch exists in the freebsd port, does it already
address this issue?
--- plugins/vidinput_v4l/vidinput_v4l.cxx.orig Wed Jan 3 23:37:37 2007
+++ plugins/vidinput_v4l/vidinput_v4l.cxx Wed Feb 7 01:30:50 2007
@@ -484,6 +484,15 @@
struct stat s;
if (lstat(devname, s) == 0) {
+#if defined(P_FREEBSD)
+ // device numbers are irrelevant here, so we match on names instead.
+ if (filename.GetLength() = 5 || filename.Left(5) != video)
+ continue;
+ int num = atoi(filename.Mid(6));
+ if (num 0 || num 63)
+ continue;
+ vid.SetAt(num, devname);
+#else
static const int deviceNumbers[] = { 81 };
for (PINDEX i = 0; i PARRAYSIZE(deviceNumbers); i++) {
if (MAJOR(s.st_rdev) == deviceNumbers[i]) {
@@ -493,6 +502,7 @@
}
}
}
+#endif
}
}
}
Yes, I've tried this patch in the source and it picks up the /dev/video0
file as well;
now I've the next problem:
when I make a call h323:10.0.1.40 to the VX700 where I'm sitting with my
laptop in front of, I can see in Ekiga the local picture from my cam and
the picture grabed by the cam of the VX700 in side-by-side view
mode, but the TV the VX700 is connected to only shows the name of the
session and the rest is dark; I have a -d3 output if this would be
helpfull for you, Damien; thx for any hint;
Most probably it can not decode the stream sent by Ekiga,
but as the VSX is not Open Source, I can't really tell why.
Unfortunately, I can not really help with that. Perhaps you should try
the SVN Trunk version of Ekiga, it supports other codecs like H.264. It
will probably work better.
--
_ Damien Sandras
(o-
//\Ekiga Softphone : http://www.ekiga.org/
v_/_ NOVACOM : http://www.novacom.be/
FOSDEM : http://www.fosdem.org/
SIP Phone : sip:[EMAIL PROTECTED]
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga V4L FreeBSD
On Wed, Mar 19, 2008 at 05:23:12PM +0100, Damien Sandras wrote:
And contribute it back to us, otherwise we can not commit it...
The following is already in the freebsd port and has been verified
to work. Are you interested in other patches that we have in the
port? If so please see:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/pwlib/files/
--- plugins/vidinput_v4l/vidinput_v4l.cxx.orig Wed Jan 3 23:37:37 2007
+++ plugins/vidinput_v4l/vidinput_v4l.cxx Wed Feb 7 01:30:50 2007
@@ -484,6 +484,15 @@
struct stat s;
if (lstat(devname, s) == 0) {
+#if defined(P_FREEBSD)
+ // device numbers are irrelevant here, so we match on names instead.
+ if (filename.GetLength() = 5 || filename.Left(5) != video)
+ continue;
+ int num = atoi(filename.Mid(6));
+ if (num 0 || num 63)
+ continue;
+ vid.SetAt(num, devname);
+#else
static const int deviceNumbers[] = { 81 };
for (PINDEX i = 0; i PARRAYSIZE(deviceNumbers); i++) {
if (MAJOR(s.st_rdev) == deviceNumbers[i]) {
@@ -493,6 +502,7 @@
}
}
}
+#endif
}
}
}
This is against pwlib 1.12.0
-Steve
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [SHORT TEST] (again)
jacques a écrit : Hello, If you believe your Ekiga is working well, please give a try at sip:[EMAIL PROTECTED] for a short ( one minute) audio test only. We had a long test with «gegetel» The sound is good on both ends, we had the oportunity to test headsets and microphone and also some audio plugins. But we encounterem a problem : Gege can call me but I can't call him. We both use 2.0.11 We both use NAT. Can anyone allow me to give him a call in order to try to know on which end is the trouble with calls. I wil be around till 19:30 (TU +1) Thanks, Jacques sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [SHORT TEST] (again)
Le mercredi 19 mars 2008 à 17:50 +0100, jacques a écrit : jacques a écrit : Hello, If you believe your Ekiga is working well, please give a try at sip:[EMAIL PROTECTED] for a short ( one minute) audio test only. We had a long test with «gegetel» The sound is good on both ends, we had the oportunity to test headsets and microphone and also some audio plugins. But we encounterem a problem : Gege can call me but I can't call him. We both use 2.0.11 We both use NAT. Can anyone allow me to give him a call in order to try to know on which end is the trouble with calls. If you can't call him, the problem is on his side. He needs to diminish the NAT binding time using gconf-editor. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Privacy policy of Ekiga
I hope you will be able to point me to the privacy statements of Ekiga or otherwise You will take this subject very seriously. Are you talking about ekiga or ekiga.net? I think both are really important, is it not? Not really: the Ekiga application is just that: an application. It happens to use the network, just like Firefox, but it doesn't (modulo bugs or nasty people adding backdoors) connect to any machine to which you haven't explicitly asked it to connect. I don't think a privacy statement is important here. You seem to assume that Ekiga is an organization, in the way that Skype is an organization. It is not at all the same thing: Skype is a commercial organization with a proprietary product and service; Ekiga is an open source application, and there is a community that supports and uses it. To use myself as an example, the only information that ekiga.net has access to are my name and email address. There need be no privacy statement, since there is no collection of personal data, such as Skype might require and use. The fact that Ekiga.net is not commercial doesn't make much difference: it does keep a database of users with their email address and names, and (more importantly) it does keep track of which ones are connected and from where, so it know about IP addresses and may potentially keep a log of when which user connected with which IP. And the police may order Damien to give out some of that info, or some dire financial need (or juicy offer) may push Damien to sell that info. So a privacy statement explaining what info is kept (e.g. is a log of IP addresses kept?), that to which it is intended (e.g. it's not intended to be distributed to any third party, except the name database which is freely searchable, IIUC), and the worst case guarantee (all the data may be stolen, subpoena'd, sold, ...). Stefan ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
On Wed, Mar 19, 2008 at 9:34 AM, D Webb [EMAIL PROTECTED] wrote: Btw, are you using pulseaudio ? Sorry to but in, when I use Pulseaudio ekiga sound will not work. I kill pulseaudio and ekiga works ok. I do get these errors: Thanks for butting in. More ideas means quicker fixes. I have wondered about this for some time. In connection with Ekiga crashes, Pulseaudio keeps popping up. I don't know what it is, but pretty sure it comes installed by default on Slackware 12.0, which is what I have. I should at least try removing it. So, how do I kill pulseaudio? at a terminal do a ps -aux|grep pulseaudio and this will give you the process numberthen do a kill -9 xxx . (explain xxx = process number.) Peace..ed -- Edward Dunagin-Dunigan-Dunnigan Bozeman, MT 59718 mobile 406-570-0992 Landline 406-556-7282 VOIP:sip:[EMAIL PROTECTED]:5063;transport=udp http://doas.montanalinux.org ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Privacy policy of Ekiga
I assume that everything I read, write, upload or download on the Internet and dates, times and IP addresses are being recorded by several governmental agencies at any given moment. Thus far, I have rarely been proven wrong. I assume everything I do on the Internet could just as well have been shouted at the top of my lungs in a football stadium. It is in this sense that I think privacy statements, while being a profitable marketing gesture for a business, offers no more privacy than no statement at all. Let us say you are going to tell someone over Ekiga about some terrible crime you will commit. Do you really think you will escape police intervention or a prison sentence because of a privacy statement? I guess you could try and file a lawsuit from a prison cell, but would it not be easier to accept my interpretation of VoIP as shouting in a football stadium? Finally, a lawyer could butt in and tell us all these complicated issues and scenarios and pitfalls, and the infinite variances in different countries. Again, would it not be easier to just assume you are shouting in a football stadium and just accept the Internet does not have much mercy for privacy? Dominic _ Climb to the top of the charts! Play the word scramble challenge with star power. http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_jan___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
I should at least try removing it. So, how do I kill pulseaudio? at a terminal do a ps -aux|grep pulseaudio and this will give you the process numberthen do a kill -9 xxx . (explain xxx = process number.) OK, well, the standard kill -9 is easy enough. So how do I prevent it from loading into memory in the first place? Is pulseaudio in the kernel or somewhere else? Dee _ Helping your favorite cause is as easy as instant messaging. You IM, we give. http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
On Wed, Mar 19, 2008 at 11:30 AM, D Webb [EMAIL PROTECTED] wrote: I should at least try removing it. So, how do I kill pulseaudio? at a terminal do a ps -aux|grep pulseaudio and this will give you the process numberthen do a kill -9 xxx . (explain xxx = process number.) OK, well, the standard kill -9 is easy enough. So how do I prevent it from loading into memory in the first place? Is pulseaudio in the kernel or somewhere else? It is in a startup file. something like /etc/init.d but I havent located it yet, so I know to kill it before starting Ekiga. -- Edward Dunagin-Dunigan-Dunnigan Bozeman, MT 59718 mobile 406-570-0992 Landline 406-556-7282 VOIP:sip:[EMAIL PROTECTED]:5063;transport=udp http://doas.montanalinux.org ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] sndrv_pcm_hw_params: Assertion `err = 0' failed
David Mohr a écrit : You should only use kill -9 as a last resort, as it does not allow the kernel to clean up after the process. You dont like zombies :) Jacques, dont -HUP me :) ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
