similar to: question on usage of the libraries

Displaying 20 results from an estimated 20000 matches similar to: "question on usage of the libraries"

2004 Aug 06
3
question on usage of the libraries
> Ok, I forgot to mention that I want to incorporate speex into my own > program (which is for e.g. streaming audio and a couple of other > things). JM> One thing you'll need to decide: do you want to pack in into an Ogg JM> container or will you take care of handling the packets yourself? I take care of that myself. JM> If you JM> want to pack it in Ogg, I suggest you
2004 Aug 06
3
question on usage of the libraries
> Is the following code correct for compressing audio? The output I get is so > extremely small, but what is more important: if I pass it through zlib, it > gets at least 50% smaller! JM> On regular data, gzip might get a 5% reduction, so I doubt you can get JM> 50% unless you're encoding zeros or doing something wrong... I think I'm doing something wrong :o) Don't know
2004 Aug 06
0
question on usage of the libraries
> Could it be, that if I call > speex_init_header(&header, rate, 1, mode); > with rate set to 22050 that the encoder fails > producing garbage? > I could not find anything in the documentation > on what I should set rate to. JM> No, even if you put garbage in the header, the encoder will still work JM> (though you'd need to send the header info to the decoder
2008 Apr 01
0
cross compilation for ARM - ogg headers problem
Hi Conrad, Thanks for your help. I am unlucky. No i have this following error : source='speexdec.c' object='speexdec.o' libtool=no \ depfile='.deps/speexdec.Po' tmpdepfile='.deps/speexdec.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ arm-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../libspeex -I/usr/include -O2 -fno-exceptions -O2
2006 Apr 20
3
Recommended version for production use
Hi -- I'm looking at adding Speex decoder and encoder support to the Miles Sound System, a commercial library used by game developers on various platforms including PCs, the Mac, and game consoles. As part of my initial evaluation, I've gone ahead and downloaded the 1.0.4 and 1.1.1 Win32 binary distributions and played around encoding and decoding various files with the speexenc.exe and
2004 Aug 06
1
patch for compiling on IRIX
The following patch (based off of the current CVS tree) is necessary to compile Speex on IRIX (or any other system that doesn't include getopt_long in the system libraries). I would suggest further that src/getopt_win.h be renamed to getopt_long.h since it's not just Windows that lacks getopt_long. Michael Index: configure.in
2008 Jan 11
1
Patch for OS/2 STDIN/STDOUT
Hi, to make in/output on STDIN/STDOUT work on OS/2 this small patch is needed: ---cut--- diff -ruN o:src/speexdec.c src/speexdec.c --- o:src/speexdec.c 2007-12-08 05:01:08.000000000 +0100 +++ src/speexdec.c 2008-01-12 00:48:00.000000000 +0100 @@ -231,6 +231,8 @@ { #if defined WIN32 || defined _WIN32 _setmode(_fileno(stdout), _O_BINARY); +#elif defined OS2 +
2006 Aug 02
1
[PATCH] skeleton support for speexenc and speexdec
Hi, I have done some code cleanup of my speexenc patch for skeleton support. Also a warning message have been added to let the users know that some decoders may fail with skeleton output enabled. The speexdec patch enables speexdec to play skeleton enabled speex file. Thanks in advance for the feedbacks. --tahseen -------------- next part -------------- A non-text attachment was scrubbed...
2004 Aug 06
0
RE: Difference in Encoding of files on Pocket PCvis-à-vis desktop
Hi, Here's a couple things to look at: 1) Are you using your own encoder and decoder? If so, try with speexenc and speexdec. 2) Is PocketPC big endian? If so, try defining WORDS_BIGENDIAN when compiling Speex. 3) The "This doesn't look like a Speex file" error sounds very suspicious because it only involves looking at the first chars of the first packet and looking for the
2004 Aug 06
1
speexenc and speexdec
When I use speexenc appplication to encode a wav file and then speexdec to decode it the decoded wav is bigger than the original, why this happens? Thanks. Miguel Gomes <p> -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 2786 bytes Desc: winmail.dat Url :
2004 Aug 06
1
Problem with Win32 libraries
Hi I downloaded Speex 1.0.1 and I am not able to compile the source files (examples) speexenc.c and speexdec.c What are the libraries needed to run the above examples ? I am using VC++ 6.0 /Win XP. I addes ogg.lib and libspeex.lib files. do I need to any more lib files ? Please advise. Regards Ravi. <p>--------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95
2017 May 29
0
[PATCH] Add CMake build script
Description =========== This patch adds support of CMake meta build system, so you can generate Unix makefiles, VS 6.0-2017 projects and many more. Features ======== * Win32 and Linux tested * Travis CI test added * Generates working Visual Studio 6.0-2017 solutions * Generates working Unix Makefile * Supported options (<option> - <default value>): * `ENABLE_FLOATING_POINT` - on
2009 Apr 06
2
help needed for freebsd
Hi, I'm trying to run tinc 1.0.9 on freebsd 7.1-RELEASE-p4. I tried: Device=/dev/net/tun0 DeviceType=tun I tried it without the device-line, i tried the other devicetype-options, none of them work. With all of them I get the following error: 30311: open("/dev/net/tun0",O_RDWR|O_NONBLOCK,05024360414) = 3 (0x3) 30311: ioctl(3,TUNSIFHEAD,0xbfbfec58) ERR#45 'Operation not
2007 Jul 14
0
file couldn't play after Speex encode and decode
The encoded speex file should, by convention, be given the '.spx' extension rather than '.wav', but that is not the issue. What appears to be happening is that the '.wav' extension on your named output file from speexdec is not being recognised as '.wav' and, consequently, the file is being written as 'raw' data without the wave file header. I am not sure
2010 Nov 22
7
local address announcements
Hi everyone, you can find the current version of my enhanced tinc using subversion: svn://tardyon.mon-clan.de/tinc I allowed anonymous read access, so feel free to download the sources. Unfortunately, my enhancements are based on a rather old git-checkout from Guus. The version should run under windows and Debian/Ubuntu. Best, Daniel -----Original Message----- From: folkert [mailto:folkert
2011 May 04
0
speexenc/speexdec doubles file size
Juha Heinanen writes: > any idea why size of wav file doubles when it is encoded to speex and > back to wav: > > $ ls -ls testi.wav > 40 -rw-r--r-- 1 foo foo 40674 May 4 14:38 testi.wav > > $ speexenc --denoise --agc --quality 10 testi.wav testi.spx > Encoding 8000 Hz audio using narrowband mode (mono) > > $ ls -ls testi.spx > 20 -rw-r--r-- 1 foo foo 16405
2004 Aug 06
3
protocol description
Hi, Do you have any documentation on the protocol used by the icecast-server? I wrote a tool for multiplexing (proxying) shoutcast-sessions and I would also like to convert it for icecast-sessions. This shoutcastproxy makes it possible to listen with a couple of people to a session while only 1 is retrieved from a shoutcastserver (http://www.vanheusden.com/shoutcastproxy/). <p>Folkert van
2004 Aug 06
3
protocol description
Hi, Do you have any documentation on the protocol used by the icecast-server? I wrote a tool for multiplexing (proxying) shoutcast-sessions and I would also like to convert it for icecast-sessions. This shoutcastproxy makes it possible to listen with a couple of people to a session while only 1 is retrieved from a shoutcastserver (http://www.vanheusden.com/shoutcastproxy/). <p>Folkert van
2004 Aug 06
0
RE: [Speex-devel] Subject: Problems with win32 port of Speex
> > I had no trouble building the ogg, vorbis and speex libraries. Also, > > speexenc.exe built correctly. However, speexdec.exe will build but does not > > create output (either to soundcard or to pcm/wav) and eventually crashes. > > I'm not sure I understand. In the first part, you say you have trouble > building speexdec and here you say speexdec does build but
2005 Oct 25
0
Noisy sound quality with Blackfin in WB-mode
Hi Bernhard, Can you confirm I'm understanding everything correctly? You encode with the same encoder and then decode with either A) blackfin assembly and fixed-point or B) fixed-point only on Blackfin. Then A) sounds bad and B) sounds good. If you do the same in narrowband, it sounds OK. Is that correct? If that's the case, it's *probably* some kind of bug and/or invalid assumption