similar to: How to get audio data from microphone on pocketPC ?

Displaying 20 results from an estimated 3000 matches similar to: "How to get audio data from microphone on pocketPC ?"

2006 Jun 23
1
How to get audio data from microphone on pocketPC ?
Hi jere, thanks for this link, i'll see if i can do something good with that. speex.dll : ----------- I have a speex.dll which work, and i can encode and decode a wav file. (i used male.wav on speex.org for my test). But my dll is specific to my softphone. In fact i just include speex.h and i call speex functions for [en;de]coding. My code is based on speex website's sample :
2006 Jun 23
0
How to get audio data from microphone on pocketPC ?
Hi You should try using fmod(www.fmod.org) for recording. You need fmodce for pocketpc, and there is recording sample included. Also you should download fmodex, because there is record to disk sample. I have developed application for pocket pc which records sound in a wav file. My problem is that I have not been able to encode sound to speex in pocket pc. So I have also question for you: do have
2006 Jun 09
4
c++ Wav->ogg encoder
Hi I'm new with ogg and also with using third party libraries. I'm making a C++ PocketPC program and I need a simple wav->ogg encoder function. But as I have tried to use ogg vorbis libraries I don't know what or how to use them. I think that best way would be to use libogg 1.1.3 and libvorbis 1.1.2. Do I even need both of them, since I only need to have capability of
2006 Jun 13
1
LIBC.lib and developing for PocketPc
Hi I downloaded speex_win32_1.0.4_setup.exe. I was pretty happy to see that there was libspeex.lib and libspeex.dll. Everything went fine until I tried to build speexenc.c as win32 console program. Visual Studio 2005 gives error: "fatal error LNK1104: cannot open file 'LIBC.lib'". What is this LIBC.lib file? My ultimate goal would be to make wav->speex encoder
2005 Feb 07
1
PocketPC Softphone?
Anybody got any preferences for a good SIP softphone? Ideally, a free download for the moment, as this is just for some initial proof-of-concept. -- Adrian Chapman Director Trivas Ltd Business on the Move Mobility - Messaging - Infrastructure - Security - Remote Access 07796 690210 - 01582 626552
2006 Nov 06
2
PocketPC 2005
Hi, I'm experiencing weird problems while testing speex (I want to test the echo canceller first) on PDA with WM5 version pocket PC 2005. Here is the strange scenario: 1-> App running without being linked with speex -> no problem 2-> App running while being linked with speex -> crash at always the same place. NO ACCESS TO
2007 Nov 04
3
WaveIn/WaveOut and Speex
Hello, I know my question has been asked before because I spent the last week searching the web for how to use Speex in combination with WaveIn/WaveOut and I ran into a few posts, but none of them answer the question. There is still a lot of confusion how to use WaveIn/WaveOut and Speex by junior developers such as myself. Even after examining code for SpeexDec and SpeexEnc, I cannot get clear
2002 Mar 05
1
ogg vorbis on the pocket pc
Hi, i'm not too familiar with how the ogg vorbis community works, so i hope this is within the topic of the list, but i didnt really want to leave this thing i've did out in the dark either. :) i've just ported libvorbis, libogg, and vorbisfile stuff to the pocket pc a while ago, it was pretty straight forward (just add a few more #ifdefs around the ftoi function and some others) and
2004 Aug 06
2
[ANNOUNCE] PocketPC Port for speex-1.1.5 with sample code
Hi Jean-Marc, Based on the wonderful Speex project, I've created SpeexOutLoud, essentially a Speex codec port for Windows Mobile 2003 devices. I've included a sample project intended to show the usage of SpeexOutLoud codec in a Pocket PC application based on .NET Compact Framework. I'd request you to please go through the attached build, and include it as a contribution to the
2006 Nov 06
2
PocketPC 2005
On Mon, 6 Nov 2006, Jean-Marc Valin wrote: > That's quite a strange problem. Considering that Speex doesn't have any > "init code" (stuff that executes when it's loaded), there's no way this > could be a bug in Speex. True. > I see two likely possibilities (plus lots of > unlikely): > 1) A bug in your code. Linking with Speex pushes your code to a
2004 Nov 03
4
libspeex for other platforms
wouldn't it be a good idea to have the libraray available as a binary for non-PC platforms like the PocketPC, Symbian and Mac? i am suggesting this as it will allow the developers to go ahead and program to an interface while the development continues. there are builds for symbian, pocket pc and linux already in the tar ball. putting their binaries on the download section will probably
2006 Nov 06
1
PocketPC 2005/echo canceller
If you want to test the AEC, I recommend using the svn version of Speex. Jean-Marc Aymeric Moizard a ?crit : > > I finally solved my problem: > > My **static** speex library is compiled with: > -D_LIB > > While I should compile it with: > -D_USRDLL > > I'm not able to understand completely why: anyway, it > now can be compiled without breaking anything.
2004 Aug 06
3
RE: Difference in Encoding of files on Pocket PCvis-à-vis desktop
Hello Jean-Marc, I encoded a 143 kb file on both the desktop as well as the Pocket PC using the default settings/ Here are the results. Size : Desktop - 17.6 Kb, Pocket PC -17.1 kb (not much difference in size) Now when I try to decode the file encoded on the Pocket PC, I get a message "This doesn't look like a Speex file". However, when I decode the Pocket PC encoded file on
2004 Aug 06
1
status report on the Windows CE (PocketPC) ACM codec
> > It was essentially my own mistake. After the Embedded C++ IDE crashed unexpectedly, > the .lib file was no longer present in the project settings (the project had not been saved) > so all the errors I got were caused by a missing .lib reference in the link stage! > I had to change my cross compiler target to "arm-wince-pe" because otherwise the > object/.lib files
2007 Nov 04
2
WaveIn/WaveOut and Speex
Thank you for such a quick response. The only reason I started with Char buffers is because WaveIn and WaveOut on Windows XP accept/emit WAVEHDR structures, which store audio data in LPSTR, which is Char*. typedef struct { LPSTR lpData; DWORD dwBufferLength; ... } WAVEHDR; When I was going from Char to float and back looked very wrong to me as well, but I was just not
2004 Aug 06
3
status report on the Windows CE (PocketPC) ACM codec
Christian Buchner wrote: > Now here is where I have problems and not yet found a solution: I know very little about this, so take everything that follows with a large pinch of salt. > * the function names exported in the .lib created by gcc are not compatible > with the function name decorations that the VisualC++ embedded linker expects. Which version of gcc are you using? I know
2004 Aug 06
2
1.0.3 in ACM soon
Hi Rodrigo, I'm Fabio and i'm in your identical situation, i need Speex to run on PocketPC in real time mode for my tesis. I've to develop a sort of VoIP apllication for pocketPC... I recently discover speex (Only yesterday i joined this mailing list....) and I'm doing many test using mostly VC++ 6.0 but only because i'm still undestandig speex... I did many works with EVC++
2004 Apr 22
0
PocketPC 2003 taking samba file share?
Hi All, Anybody ever succeeded in getting a samba share opened by PocketPC 2003 File Explorer? I am using a h4150 iPaq with WLAN capabilities, but haven't been able to succesfully take in any type of samba share, public nor private. I have used Pocket Hosts to make sure the samba server is known by it's hostname, but even by referencing the samba server by it's IP address directly, I
2005 Mar 16
0
IAX softphone on WinCE/PocketPC
Hi, Is anyone aware of an IAX client that's made for the Windows CE/Pocket PC platform? Or even the Palm platform for that matter. Thanks.
2006 Nov 06
0
PocketPC 2005
That's quite a strange problem. Considering that Speex doesn't have any "init code" (stuff that executes when it's loaded), there's no way this could be a bug in Speex. I see two likely possibilities (plus lots of unlikely): 1) A bug in your code. Linking with Speex pushes your code to a different place in memory and triggers the bug 2) A bug in Visual Studio. You can