RE: [Wengophone-devel] Native Alsa support on Linux

2007-01-23 Thread Jerome WAGNER 
Hello,

Yes I think you are right ; forcing the audio device in your case leads to a
bug.

select_audio_device is supposed override the deviceId when it is forced, but
I guess that the "const char *" stops this from working.

Maybe you can try and patch it this way (making sure that when we get out of
select_audio_device, the deviceId has been changed)

Like you get with your patch you should get something like

(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phmedia-alsa.c:316) alsa_stream_open: (name: alsa: in=0 out=0, rate: 16000,
framesize: 640)

(confirming that the alsa driver is given an alsa name)

After that you should look on line (122) of phmedia-alsa:
  rc = snd_pcm_open(&handle, name, type, 0);

It seems to me that using "name" is a bug here
And this would be why it tells you
"unable to open < in=0 out=0> pcm device"

The snd_pcm_open (a native alsa primitive if I understand it right) should
be given a device name that is compatible with it.

The principle in phapi is that

"alsa:in=0 out=0"

Is a shortcut device id string. This string is parsed to get the in= and the
out= values. These values are used as native driver ids.

You can also look at the portaudio impl : phmedia-portaudio.c (192). It has
been coded in yet another way (!)

I hope this will help you in your quest !

Jerome







-Message d'origine-
De : Didier LINK [mailto:[EMAIL PROTECTED] 
Envoyé : mercredi 24 janvier 2007 01:25
À : Jerome WAGNER
Cc : 'Wengophone Devel'
Objet : RE: [Wengophone-devel] Native Alsa support on Linux

Le mardi 23 janvier 2007 à 20:03 +0100, Jerome WAGNER a écrit :
> Hello Didier,
> 
> >(debug) 18:07:01 static std::list >std::allocator > AudioDeviceManager::getOutputDeviceList():
> >output device found=(default) /dev/dsp OSS
> 
> Means that the GUI is binded on OSS.

Ok, I see, it's disturbing to initialize all the devices type at once.

> 
> Do you have DBG_DYNA_AUDIO_DRV logs when you start a call ? They should
> mention the usage of the ALSA backend because of the FORCE_xxx thing.

The tests with portaudio works with a call, not a very good sound at all
but it work. With the Alsa backend I've no sound and the log is:

(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:39) registering audio driver of kind "alsa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:58) ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:39) registering audio driver of kind "pa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:58) ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:39) registering audio driver of kind "null" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:58) ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:39) registering audio driver of kind "file" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:58) ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phmedia-alsa.c:310) alsa_stream_open: (name: pa:IN=0 OUT=0, rate: 16000,
framesize: 640)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phmedia-alsa.c:94) alsa_dev_open: (name: pa:IN=0 OUT=0, rate: 16000,
framesize: 320)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phmedia-alsa.c:132) unable to open  pcm device: Aucun
fichier ou répertoire de ce type
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phmedia-alsa.c:310) alsa_stream_open: (name: pa:IN=0 OUT=0, rate: 16000,
framesize: 640)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phmedia-alsa.c:94) alsa_dev_open: (name: pa:IN=0 OUT=0, rate: 16000,
framesize: 320)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phmedia-alsa.c:132) unable to open  pcm device: Aucun
fichier ou répertoire de ce type

It's a problem in the name of the device, I've used "alsa: in=0 out=0"
in the variable PH_FORCE_AUDIO_DEVICE but the result is a mix between
initialization of Alsa with portaudio parameters.

In a gdb session I see that the deviceId is picked from a phcfg
structure:

ph_msession_start(s, phcfg.audio_dev) in wifo/phapi/phapi-old.c:3395

I think in this context of forcing the device driver it's a bug :)

I've tried the attached patch but it's just a step further, the
phlogger.log contain :

(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phmedia-alsa.c:316) alsa_stream_open: (name: alsa: in=0 out=0, rate: 16000,
framesize: 640)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phmedia-alsa.c:94) alsa_dev_open

RE: [Wengophone-devel] Native Alsa support on Linux

2007-01-23 Thread Didier LINK 
Le mardi 23 janvier 2007 à 20:03 +0100, Jerome WAGNER a écrit :
> Hello Didier,
> 
> >(debug) 18:07:01 static std::list >std::allocator > AudioDeviceManager::getOutputDeviceList():
> >output device found=(default) /dev/dsp OSS
> 
> Means that the GUI is binded on OSS.

Ok, I see, it's disturbing to initialize all the devices type at once.

> 
> Do you have DBG_DYNA_AUDIO_DRV logs when you start a call ? They should
> mention the usage of the ALSA backend because of the FORCE_xxx thing.

The tests with portaudio works with a call, not a very good sound at all
but it work. With the Alsa backend I've no sound and the log is:

(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "alsa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "pa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "null" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "file" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:310)
 alsa_stream_open: (name: pa:IN=0 OUT=0, rate: 16000, framesize: 640)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:94)
 alsa_dev_open: (name: pa:IN=0 OUT=0, rate: 16000, framesize: 320)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:132)
 unable to open  pcm device: Aucun fichier ou répertoire de ce 
type
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:310)
 alsa_stream_open: (name: pa:IN=0 OUT=0, rate: 16000, framesize: 640)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:94)
 alsa_dev_open: (name: pa:IN=0 OUT=0, rate: 16000, framesize: 320)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:132)
 unable to open  pcm device: Aucun fichier ou répertoire de ce 
type

It's a problem in the name of the device, I've used "alsa: in=0 out=0"
in the variable PH_FORCE_AUDIO_DEVICE but the result is a mix between
initialization of Alsa with portaudio parameters.

In a gdb session I see that the deviceId is picked from a phcfg
structure:

ph_msession_start(s, phcfg.audio_dev) in wifo/phapi/phapi-old.c:3395

I think in this context of forcing the device driver it's a bug :)

I've tried the attached patch but it's just a step further, the
phlogger.log contain :

(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:316)
 alsa_stream_open: (name: alsa: in=0 out=0, rate: 16000, framesize: 640)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:94)
 alsa_dev_open: (name: alsa: in=0 out=0, rate: 16000, framesize: 320)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:132)
 unable to open < in=0 out=0> pcm device: Aucun fichier ou répertoire de ce type

I think the change will be made in the function
select_audio_device(const char *deviceId) in phmedia-audio.c:2070

If this function return the deviceId after test the env vars, I think
the use of this vars can be more transparent for all drivers.

What do you think about this enhancement ?

Sorry for the long message and thanks for your attention.

Best regards.

Didier Link

Index: wifo/phapi/phmedia-alsa.c
===
--- wifo/phapi/phmedia-alsa.c(révision 9392)
+++ wifo/phapi/phmedia-alsa.c(copie de travail)
@@ -306,7 +306,13 @@
 int alsa_stream_open(phastream_t *as, char *name, int rate, int framesize, ph_audio_cbk cbk)
 {
   struct alsa_dev *ad = 0;
+  char *forceDeviceId;
 
+  forceDeviceId = getenv("PH_FORCE_AUDIO_DEVICE");
+
+  if(forceDeviceId)
+ name = forceDeviceId;
+
   DBG_DYNA_AUDIO_DRV("alsa_stream_open: (name: %s, rate: %d, framesize: %d)\n", name, rate, framesize);
   ad = calloc(sizeof(*ad), 1);
   if (!ad)


signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Wengophone 2.1 - Boost problem

2007-01-23 Thread Andreas Schneider 
Alessandro Corbelli wrote:
> Hi all,
Hi Alessandro,

> I'm having this problem when compiling wengo 2.1
> 
> C:\wengo\build>build_nmake.bat
> 
> C:\wengo\build>cmake .. -DCMAKE_VERBOSE_MAKEFILE=1 -G "NMake Makefiles"
> Subversion svn command line not found, it is recommended to install it
> -- OS: Windows-5.1
> -- Processor: x86
> -- Compiler: C:/Programmi/Microsoft Visual Studio .NET 2003/Vc7/bin/cl.exe
> -- Build type: Debug
> -- Build tool: nmake
> -- Build directory: C:/wengo/build/debug
> -- svn revision: 0
> CMake Error: Could not find Boost
> -- Configuring done
> 
> Boost is correcty installed in C:\Boost
> 

try

C:\wengo\build>set BOOST_ROOT=C:\Boost
C:\wengo\build>cmake .. -DCMAKE_VERBOSE_MAKEFILE=1 -G "NMake Makefiles"


-- andreas

> ___
> Wengophone-devel mailing list
> Wengophone-devel@lists.openwengo.com
> http://dev.openwengo.com/mailman/listinfo/wengophone-devel

-- 
http://www.cynapses.org/ - cybernetic synapses




signature.asc
Description: OpenPGP digital signature
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] YUV Files

2007-01-23 Thread Jerome WAGNER 
Hello Christopher,

The YUV file that you are mentioning was not done via an editor. I don't
know if such editor exists.

If you really want to modify this image, you will need to use the jpeg2yuv
converter that you can find here :

http://dev.openwengo.com/trac/openwengo/trac.cgi/browser/playground/jpegtora
wyuv

I can't assure you that it will compile and don't remember what are the libs
you will need installed on your computer, but I am sure that you will
understand the basics of how this YUV file was build.

This is the program that was used to generate the image you are talking
about.

Jérôme

-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de
Christopher Jimenez
Envoyé : mardi 23 janvier 2007 18:25
À : wengophone-devel@lists.openwengo.com
Objet : [Wengophone-devel] YUV Files

Hi Wengo comunity.
I was looking into the No webcam image that pops up if the users does not 
have a webcam and found that this is a yuv file, that phapi send.
So i have a couple of questions about this. This YUV files has to be in wat 
YUV Pixel format? Whats its header size? What are all its properties so 
wengo play it correctly. I ask this becuase i try with other one and was not

showing correctly.
Also, some one know a good YUP editor on windows, that i could create my own

YUV files? I was looking but could not found one.
I was thinking, i dont know that if is posible, that maybe this could be use

for some kind of video emoticons, so when you are talking you can push yuv 
files into the video and use them as emoticons.
Thanks in advance for all the help
Regards,
CJC

_
FREE online classifieds from Windows Live Expo – buy and sell with people 
you know 
http://clk.atdmt.com/MSN/go/msnnkwex001001msn/direct/01/?href=http://exp
o.live.com?s_cid=Hotmail_tagline_12/06

___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] g.729 codec

2007-01-23 Thread Vadim Lebedev 



Zahid Ayar wrote:

what is the IPP sample directory... would u plz give me a directory 
structure


i have to build them? arent they already built, if so how should i 
build them?




IPP sample directory is directory wher you download and build IPP speech 
coding samples you download from Intel site


Vadim


zahid

On 1/23/07, *Vadim Lebedev* <[EMAIL PROTECTED] 
> wrote:


Zahid you need to dowloans IPP speech coding samples from Intel site,
and to build them

IPPSAMPLEROOT should point to the IPP sample directory


Vadim

Zahid Ayar wrote:

> hello
>
> i've downloaded and installed an evaluation copy of intel's ipp
> containing the g729 audio codec
>
> in the build instructions for wengo
> <

http://dev.openwengo.org/trac/openwengo/trac.cgi/wiki/HowToBuildFromSourceNg>
> it says:
>
> * Only needed when compiling with G729 support, and you need the IPP
> lib from Intel :
>
> * IPPROOT: specify the Intel Integrated Performance Primitives
>   root directory
> * IPPSAMPLEROOT: specify the Intel IPP sample directory
>
> what should i set for IPPROOT and IPPSAMPLEROOT?
>
> after i set those environment variables, is it enough 4 me to just
> compile wengo and it will support g729? or r there any other steps
> needed to be done for g729 support?
>
> thanks 4 ur time
> zahid
>
> (ps. seems ppl have been working on g729 support on wengo for quite
> some time... check out these posts
> <

http://dev.openwengo.com/trac/openwengo/trac.cgi/search?ticket=on&changeset=on&wiki=on&q=g729&noquickjump=1&page=1

>
> )
>
> --
> Allahumma Salli Ala Muhammad
> --
> By Time! Verily mankind is in loss! Except the ones who have
Iman, and
> do righteous deeds, and advise one another towards truth, and advise
> one another towards patience. Quran 103:1-3.
> --
> Muhammed Zahid Ayar
> [EMAIL PROTECTED]  >
> 1-518-466-5631
> blog.ayar.org  
> --
> Organize your knowledge with nelements.net
  !
>
>
>
>___
>Wengophone-devel mailing list
>Wengophone-devel@lists.openwengo.com

>http://dev.openwengo.com/mailman/listinfo/wengophone-devel

>




--
Allahumma Salli Ala Muhammad
--
By Time! Verily mankind is in loss! Except the ones who have Iman, and 
do righteous deeds, and advise one another towards truth, and advise 
one another towards patience. Quran 103:1-3.

--
Muhammed Zahid Ayar
[EMAIL PROTECTED] 
1-518-466-5631
blog.ayar.org 
--
Organize your knowledge with nelements.net  ! 


___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] Native Alsa support on Linux

2007-01-23 Thread Jerome WAGNER 
Hello Didier,

>(debug) 18:07:01 static std::liststd::allocator > AudioDeviceManager::getOutputDeviceList():
>output device found=(default) /dev/dsp OSS

Means that the GUI is binded on OSS.

Do you have DBG_DYNA_AUDIO_DRV logs when you start a call ? They should
mention the usage of the ALSA backend because of the FORCE_xxx thing.

Jerome



-Message d'origine-
De : Didier LINK [mailto:[EMAIL PROTECTED] 
Envoyé : mardi 23 janvier 2007 19:32
À : Jerome WAGNER
Cc : 'Wengophone Devel'
Objet : RE: [Wengophone-devel] Native Alsa support on Linux

Le mardi 23 janvier 2007 à 14:18 +0100, Jerome WAGNER a écrit :
> Hello Didier,

Hi Jerome and all wengonautes,

> 
> What result did you have for direct ALSA support ?

Thanks for the wiki page I've tried to use the env variable and the
debug define but without success.

The debug log say that Alsa is loaded :

"(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phap
i/phaudiodriver.c:39) registering audio driver of kind "alsa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:58) ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:39) registering audio driver of kind "pa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:58) ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:39) registering audio driver of kind "null" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:58) ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:39) registering audio driver of kind "file" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
/phaudiodriver.c:58) ...registration ok"

But with 
PH_FORCE_AUDIO_DEVICE="alsa: in=0 out=0" wengophone always use the OSS
driver of portaudio :

(debug) 18:07:01 int main(int, char**): WengoPhone started
(debug) 18:07:01 static std::list > AudioDeviceManager::getOutputDeviceList():
output device found=(default) /dev/dsp OSS
(debug) 18:07:01 static std::list > AudioDeviceManager::getInputDeviceList():
input device found=(default) /dev/dsp OSS
(debug) 18:07:01 static std::list > AudioDeviceManager::getOutputDeviceList():
output device found=(default) /dev/dsp OSS

Maybe there is another place to force the use of direct Alsa driver ?

Thanks for your help.

Didier


___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] g.729 codec

2007-01-23 Thread Zahid Ayar 

what is the IPP sample directory... would u plz give me a directory
structure

i have to build them? arent they already built, if so how should i build
them?

zahid

On 1/23/07, Vadim Lebedev <[EMAIL PROTECTED]> wrote:


Zahid you need to dowloans IPP speech coding samples from Intel site,
and to build them

IPPSAMPLEROOT should point to the IPP sample directory


Vadim

Zahid Ayar wrote:

> hello
>
> i've downloaded and installed an evaluation copy of intel's ipp
> containing the g729 audio codec
>
> in the build instructions for wengo
> <
http://dev.openwengo.org/trac/openwengo/trac.cgi/wiki/HowToBuildFromSourceNg
>
> it says:
>
> * Only needed when compiling with G729 support, and you need the IPP
> lib from Intel :
>
> * IPPROOT: specify the Intel Integrated Performance Primitives
>   root directory
> * IPPSAMPLEROOT: specify the Intel IPP sample directory
>
> what should i set for IPPROOT and IPPSAMPLEROOT?
>
> after i set those environment variables, is it enough 4 me to just
> compile wengo and it will support g729? or r there any other steps
> needed to be done for g729 support?
>
> thanks 4 ur time
> zahid
>
> (ps. seems ppl have been working on g729 support on wengo for quite
> some time... check out these posts
> <
http://dev.openwengo.com/trac/openwengo/trac.cgi/search?ticket=on&changeset=on&wiki=on&q=g729&noquickjump=1&page=1
>
> )
>
> --
> Allahumma Salli Ala Muhammad
> --
> By Time! Verily mankind is in loss! Except the ones who have Iman, and
> do righteous deeds, and advise one another towards truth, and advise
> one another towards patience. Quran 103:1-3.
> --
> Muhammed Zahid Ayar
> [EMAIL PROTECTED] 
> 1-518-466-5631
> blog.ayar.org 
> --
> Organize your knowledge with nelements.net  !
>
>
>
>___
>Wengophone-devel mailing list
>Wengophone-devel@lists.openwengo.com
>http://dev.openwengo.com/mailman/listinfo/wengophone-devel
>





--
Allahumma Salli Ala Muhammad
--
By Time! Verily mankind is in loss! Except the ones who have Iman, and do
righteous deeds, and advise one another towards truth, and advise one
another towards patience. Quran 103:1-3.
--
Muhammed Zahid Ayar
[EMAIL PROTECTED]
1-518-466-5631
blog.ayar.org
--
Organize your knowledge with nelements.net !
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] Native Alsa support on Linux

2007-01-23 Thread Didier LINK 
Le mardi 23 janvier 2007 à 14:18 +0100, Jerome WAGNER a écrit :
> Hello Didier,

Hi Jerome and all wengonautes,

> 
> What result did you have for direct ALSA support ?

Thanks for the wiki page I've tried to use the env variable and the
debug define but without success.

The debug log say that Alsa is loaded :

"(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "alsa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "pa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "null" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "file" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok"

But with 
PH_FORCE_AUDIO_DEVICE="alsa: in=0 out=0" wengophone always use the OSS
driver of portaudio :

(debug) 18:07:01 int main(int, char**): WengoPhone started
(debug) 18:07:01 static std::list > AudioDeviceManager::getOutputDeviceList():
output device found=(default) /dev/dsp OSS
(debug) 18:07:01 static std::list > AudioDeviceManager::getInputDeviceList():
input device found=(default) /dev/dsp OSS
(debug) 18:07:01 static std::list > AudioDeviceManager::getOutputDeviceList():
output device found=(default) /dev/dsp OSS

Maybe there is another place to force the use of direct Alsa driver ?

Thanks for your help.

Didier



signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] g.729 codec

2007-01-23 Thread Vadim Lebedev 
Zahid you need to dowloans IPP speech coding samples from Intel site, 
and to build them


IPPSAMPLEROOT should point to the IPP sample directory


Vadim

Zahid Ayar wrote:


hello

i've downloaded and installed an evaluation copy of intel's ipp 
containing the g729 audio codec


in the build instructions for wengo 
 
it says:


* Only needed when compiling with G729 support, and you need the IPP 
lib from Intel :


* IPPROOT: specify the Intel Integrated Performance Primitives
  root directory
* IPPSAMPLEROOT: specify the Intel IPP sample directory

what should i set for IPPROOT and IPPSAMPLEROOT?

after i set those environment variables, is it enough 4 me to just 
compile wengo and it will support g729? or r there any other steps 
needed to be done for g729 support?


thanks 4 ur time
zahid

(ps. seems ppl have been working on g729 support on wengo for quite 
some time... check out these posts 
 
)


--
Allahumma Salli Ala Muhammad
--
By Time! Verily mankind is in loss! Except the ones who have Iman, and 
do righteous deeds, and advise one another towards truth, and advise 
one another towards patience. Quran 103:1-3.

--
Muhammed Zahid Ayar
[EMAIL PROTECTED] 
1-518-466-5631
blog.ayar.org 
--
Organize your knowledge with nelements.net  !



___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel


___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] Wengophone 2.1 - Boost problem

2007-01-23 Thread Alessandro Corbelli 
Hi all,
I'm having this problem when compiling wengo 2.1

C:\wengo\build>build_nmake.bat

C:\wengo\build>cmake .. -DCMAKE_VERBOSE_MAKEFILE=1 -G "NMake Makefiles"
Subversion svn command line not found, it is recommended to install it
-- OS: Windows-5.1
-- Processor: x86
-- Compiler: C:/Programmi/Microsoft Visual Studio .NET 2003/Vc7/bin/cl.exe
-- Build type: Debug
-- Build tool: nmake
-- Build directory: C:/wengo/build/debug
-- svn revision: 0
CMake Error: Could not find Boost
-- Configuring done

Boost is correcty installed in C:\Boost

___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] YUV Files

2007-01-23 Thread Christopher Jimenez 

Hi Wengo comunity.
I was looking into the No webcam image that pops up if the users does not 
have a webcam and found that this is a yuv file, that phapi send.
So i have a couple of questions about this. This YUV files has to be in wat 
YUV Pixel format? Whats its header size? What are all its properties so 
wengo play it correctly. I ask this becuase i try with other one and was not 
showing correctly.
Also, some one know a good YUP editor on windows, that i could create my own 
YUV files? I was looking but could not found one.
I was thinking, i dont know that if is posible, that maybe this could be use 
for some kind of video emoticons, so when you are talking you can push yuv 
files into the video and use them as emoticons.

Thanks in advance for all the help
Regards,
CJC

_
FREE online classifieds from Windows Live Expo – buy and sell with people 
you know 
http://clk.atdmt.com/MSN/go/msnnkwex001001msn/direct/01/?href=http://expo.live.com?s_cid=Hotmail_tagline_12/06


___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] problem installing wengophone 2.1

2007-01-23 Thread Nicolas Lécureuil 
Le mardi 23 janvier 2007 16:31, Aurélien Gâteau a écrit :
> Nicolas Lécureuil wrote:
> > Le mardi 16 janvier 2007 13:33, Nicolas Lécureuil a écrit :
> >
> >
> > this pb is still valid with a snapshot of today.
> >
> > Can someone please help me ? this blocks me to do my rpm :/
>
> The pb with APPLICATION_BIN_INSTALL_DIR and DATA_INSTALL_DIR should be
> fixed in r9375. Can you confirm?
>
> Aurélien

no, this is exactly which revision i tryed today and i still have the pb.
you want more logs ?

-- 
JID: [EMAIL PROTECTED]


pgpDKUIJAaNMd.pgp
Description: PGP signature
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] problem installing wengophone 2.1

2007-01-23 Thread Aurélien Gâteau 

Nicolas Lécureuil wrote:

Le mardi 16 janvier 2007 13:33, Nicolas Lécureuil a écrit :


this pb is still valid with a snapshot of today.

Can someone please help me ? this blocks me to do my rpm :/


The pb with APPLICATION_BIN_INSTALL_DIR and DATA_INSTALL_DIR should be 
fixed in r9375. Can you confirm?


Aurélien

___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] Native Alsa support on Linux

2007-01-23 Thread Jerome WAGNER 
Hello Didier,

What result did you have for direct ALSA support ?

I added a small wiki page [1] regarding the activation and debug of the ALSA
support. Maybe this will help. Maybe I made a mistake about the in=0 and
out=0 thing. I hope not.

Jerome

[1]
http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki/PhApiAudioDriverAlsa



-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Didier
LINK
Envoyé : mardi 23 janvier 2007 09:44
À : Wengophone Devel
Objet : [Wengophone-devel] Native Alsa support on Linux

Hi all,

We have discussed during the openwengo summit about the native support
of Alsa by the wengophone. For testing this feature I need some
informations : how to enable direct Alsa using by phapi ? I've found the
PH_FORCE_AUDIO_DEVICE environment variable but no luck in my tests.

For reference, I found this on dmix support [1] related on our
discussion on this subject:

"NOTE: For ALSA 1.0.9rc2 and higher you don't need to setup dmix. Dmix
is enabled as default for soundcards which don't support hw mixing."

Thanks for your help and for the nice summit last week !!

Didier Link

[1] http://alsa.opensrc.org/DmixPlugin



___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] problem installing wengophone 2.1

2007-01-23 Thread Nicolas Lécureuil 
Le mardi 16 janvier 2007 13:33, Nicolas Lécureuil a écrit :


this pb is still valid with a snapshot of today.

Can someone please help me ? this blocks me to do my rpm :/

> hi,
>
> now i compile it fine but still have some problems :/
>
> During install i obtain:
>
>
> -- Install configuration: "Debug"
> -- Copy file
> from /home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/qtwengophone to /.
> running /usr/bin/cmake -E
> copy_if_different
> "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/qtwengophone" "/."
> 2>&1
> Error copying file (if different)
> from "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/qtwengophone"
> to "/.".
> -- Copy file
> from /home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libowcurl.so to /.
> running /usr/bin/cmake -E
> copy_if_different
> "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libowcurl.so" "/."
> 2>&1
> Error copying file (if different)
> from "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libowcurl.so"
> to "/.".
> -- Copy file
> from /home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libportaudio.so
> to /.
> running /usr/bin/cmake -E
> copy_if_different
> "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libportaudio.so" "/."
> 2>&1
> Error copying file (if different)
> from "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libportaudio.so"
> to "/.".
> -- Copy file
> from /home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libphamrplugin.so
> to /.
> running /usr/bin/cmake -E
> copy_if_different
> "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libphamrplugin.so"
> "/." 2>&1
> Error copying file (if different)
> from
> "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libphamrplugin.so" to
> "/.".
> -- Copy file
> from
> /home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libphspeexplugin.so to
> /.
> running /usr/bin/cmake -E
> copy_if_different
> "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libphspeexplugin.so"
> "/." 2>&1
> Error copying file (if different)
> from
> "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libphspeexplugin.so"
> to "/.".
> -- Copy file
> from /home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libowwebcam.so to
> /. running /usr/bin/cmake -E
> copy_if_different
> "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libowwebcam.so" "/."
> 2>&1
> Error copying file (if different)
> from "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libowwebcam.so"
> to "/.".
> -- Copy file
> from /home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libphapi.so to /.
> running /usr/bin/cmake -E
> copy_if_different
> "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libphapi.so" "/." 2>&1
> Error copying file (if different)
> from "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libphapi.so"
> to "/.".
> -- Copy file
> from /home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libsfp-plugin.so
> to /.
> running /usr/bin/cmake -E
> copy_if_different
> "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libsfp-plugin.so" "/."
> 2>&1
> Error copying file (if different)
> from "/home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/libsfp-plugin.so"
> to "/.".
> -- Copy file
> from
> /home/neoclust/rpm/BUILD/wengophone-2.1/build/debug/sounds/tones/jungle_svg
>/layer_pound.svg to /sounds/tones/jungle_svg/.
> CMake Error: Error in cmake code at
>
>  :24:
>
> FILE problem creating directory: /sounds/tones/jungle_svg
> Current CMake
> stack:
> /home/neoclust/rpm/BUILD/wengophone-2.1/build/cmake_install.cmake;/home/neo
>clust/rpm/BUILD/wengophone-2.1/build/wengophone/cmake_install.cmake;/home/ne
>oclust/rpm/BUILD/wengophone-2.1/build/wengophone/src/cmake_install.cmake;/ho
>me/neoclust/rpm/BUILD/wengophone-2.1/build/wengophone/src/presentation/qt/cm
>ake_install.cmake;/home/neoclust/rpm/BUILD/wengophone-2.1/wengophone/src/pre
>sentation/qt/CMakeLists-install-linux.txt CMake Error: Error in cmake code
> at
> /home/neoclust/rpm/BUILD/wengophone-2.1/wengophone/src/presentation/qt/CMak
>eLists-install-linux.txt:13: A command failed during the invocation of macro
> "ow_copy_file".
> CMake Error: Error in cmake code at
> �`�`�`в`�`�Y:26:
> ow_copy_file unknown error.
> Current CMake
> stack:
> /home/neoclust/rpm/BUILD/wengophone-2.1/build/cmake_install.cmake;/home/neo
>clust/rpm/BUILD/wengophone-2.1/build/wengophone/cmake_install.cmake;/home/ne
>oclust/rpm/BUILD/wengophone-2.1/build/wengophone/src/cmake_install.cmake;/ho
>me/neoclust/rpm/BUILD/wengophone-2.1/build/wengophone/src/presentation/qt/cm
>ake_install.cmake;/home/neoclust/rpm/BUILD/wengophone-2.1/wengophone/src/pre
>sentation/qt/CMakeLists-install-linux.txt make: *** [install] Error 255
> error: Bad exit status from /home/neoclust/rpm/temp/rpm-tmp.94428
> (%install)
>
>
> RPM build errors:
> Bad exit status from /home/neoclust/rpm/temp/rpm-tmp.94428 (%install)
>
> why does it ignore ${APPLICATION_BIN_INSTALL_DIR}  
> ${LIBRARIES_INSTALL_DIR} and ${DATA_INSTALL_DIR} macros ?
>
> have i miss something ?  have to tell him on make install step ?

-- 
JID

RE: [Wengophone-devel] g.729 codec

2007-01-23 Thread Jerome WAGNER 
Hello,

 

Please update the wiki on
http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki/SpikeCodecs

As you get feedback on the detailed instructions on how to setup G729.

 

It will be beneficial for all those who are looking for this rarely used –
as of now – information.

 

Thank you

Jerome

 

  _  

De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Zahid
Ayar
Envoyé : mardi 23 janvier 2007 08:43
À : wengophone-devel@lists.openwengo.com
Objet : [Wengophone-devel] g.729 codec

 

hello

i've downloaded and installed an evaluation copy of intel's ipp containing
the g729 audio codec

in the build
  instructions for wengo it says: 

* Only needed when compiling with G729 support, and you need the IPP lib
from Intel : 

*   IPPROOT: specify the Intel Integrated Performance Primitives root
directory 
*   IPPSAMPLEROOT: specify the Intel IPP sample directory 

what should i set for IPPROOT and IPPSAMPLEROOT?

after i set those environment variables, is it enough 4 me to just compile
wengo and it will support g729? or r there any other steps needed to be done
for g729 support? 

thanks 4 ur time
zahid

(ps. seems ppl have been working on g729 support on wengo for quite some
time... check out these
  posts )

-- 
Allahumma Salli Ala Muhammad
--
By Time! Verily mankind is in loss! Except the ones who have Iman, and do
righteous deeds, and advise one another towards truth, and advise one
another towards patience. Quran 103:1-3. 
--
Muhammed Zahid Ayar
[EMAIL PROTECTED]
1-518-466-5631
blog.ayar.org
-- 
Organize your knowledge with nelements.net ! 

___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] wengo ui cuztomization

2007-01-23 Thread Philippe BERNERY 

Le 23 janv. 07 à 00:34, Zahid Ayar a écrit :


hello developers

how may i change the menu text and links on the wengophone ui?

zahid


Look at ".ui" files. You can edit them with Qt Designer.

--
Philippe BERNERY <[EMAIL PROTECTED]>
http://dev.openwengo.org



___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] MSVC project build fix

2007-01-23 Thread Philippe BERNERY 

Le 22 janv. 07 à 10:48, Ludovico Cavedon a écrit :


Hi all!

This is a patch that should make building with MSVC80 succeed when  
using

create_vc80_procject.bat (at least in my case).

Anyway, I am afraid it breaks build_nmake.bat :(


As it breaks nmake compilation process it cannot be integrated on the  
repository. But it will be useful for those who want to compile with  
Visual Studio.


Thanks :)

--
Philippe BERNERY <[EMAIL PROTECTED]>
http://dev.openwengo.org



___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] Native Alsa support on Linux

2007-01-23 Thread Didier LINK 
Hi all,

We have discussed during the openwengo summit about the native support
of Alsa by the wengophone. For testing this feature I need some
informations : how to enable direct Alsa using by phapi ? I've found the
PH_FORCE_AUDIO_DEVICE environment variable but no luck in my tests.

For reference, I found this on dmix support [1] related on our
discussion on this subject:

"NOTE: For ALSA 1.0.9rc2 and higher you don't need to setup dmix. Dmix
is enabled as default for soundcards which don't support hw mixing."

Thanks for your help and for the nice summit last week !!

Didier Link

[1] http://alsa.opensrc.org/DmixPlugin




signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel