similar to: Re: speexenc always crashes on amd64

Hello everyone, I just wanted to see if anyone else is using PLC on the C55x and having success? I am seeing some issues and was curious if I was doing anything wrong/stupid or maybe I have found a bug? I am using: - the CELT library from OPUS 0.9.5 ( I checked the git repo and no check ins have comments about PLC, I assume it hasn't been updated) - FRAME_SIZE: 240 - PACKET_SIZE:

This patch will export new speex functions in the generated library, such as speex_encode_int as well as the preprocessor, echo-cancellation and jitterbuffers. The ordinals used matches the 1.1.6 release from the speex.org website, so any new library created with this def file should be binary compatible with that one. -------------- next part -------------- Index: speex.def

The attached patch to the qemu emulation of the pcnet hardware fixes several problems. It will now only read and write a transmit or receive descriptor once. It will correctly handle transmitting frames with more than two fragments. It will discard oversize frames instead of corrupting memory. I have tested all the changes I have made and even seen an improvement in receive performance from

Charles, here is the command(s) output using uhidd.... # uhidd -v -u /dev/ugen1.3ugen1.3[0]-> HID interface ugen1.3[0]-> Report descriptor size = 27 ugen1.3[0]-> Kernel driver is active ugen1.3[0]-> kernel driver detached! ugen1.3[0]-> Find IN interrupt ep: 0x81 packet_size=0x8 # /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -DDDD 0.000000 debug level is

On Feb 6, 2014, at 9:33 AM, Chris Duffy wrote: > So since this is a new type of UPSonic UPS, do you think > the vendor screwed up or is it just some quirk on Freebsd? It's a pretty fundamental design flaw, although it isn't uncommon among USB devices aimed at the Windows market, and to their credit, it does make implementation and deployment simpler on Windows. Neither the FreeBSD

Thx Charles, So since this is a new type of UPSonic UPS, do you think the vendor screwed up or is it just some quirk on Freebsd? Yes, if you can look into this I would appreciate it. I do not see anyone else on the Web attempting to use this new device yet.....but....... Regards chris On 2/6/14, 8:24 AM, Charles Lepple wrote: > On Feb 6, 2014, at 8:41 AM, Chris Duffy wrote: > >>

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

Hi all, I've another trivial request: Is there any particular reason why speexenc and speexdec return 1 on successful completion? It would be preferable if they returned 0 unless there were errors, to be consistent with other *nix utilities and to allow for easier scripting (eg speexdec sample.spx && cp sample.spx somewhere) Would anyone be against this? TIA, Bernard. --

the stack variable bytes_written is never initialized. Not that it matters - it is only incremented and never used later.... ;) <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'speex-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No

Attached is a small Visual Basic(yeah, I know, VB sucks but its the only thing I'm good with) program that lets you quickly and easily launch speexenc under Windows. If you can't figure out how to use it read the ToolTip text(hover your mouse over each text box/button/whatever). It will crash if you don't give a location for SpeexEnc.exe and click Run. If you're using

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 :

Hello, I have problems to compile speexenc 1.1.4, ihave the following errors <p>speexenc.obj : error LNK2001: unresolved external symbol _speex_preprocess speexenc.obj : error LNK2001: unresolved external symbol _speex_preprocess_ctl speexenc.obj : error LNK2001: unresolved external symbol _speex_preprocess_state_init Debug/speexenc.exe : fatal error LNK1120: 3 unresolved externals Error

Hi Tyler! I found your e-mail in a forum and would like to ask you some questions if you don't mind. I just learn about Speex last night and would like to know if works ok with VB. Since you have working with this in VB your could say something. I intend to make a simple application to allow me to comunicate between to computers using VOIP and in each computer having a two-way

Hi Mon, I added 'misc.h' to the #includes in speexenc.c and commented out the declaration of 'le_int' in 'wav_io.h'. Then, it compiles and works fine. John Mo Win wrote: > Hi all, > > Been trying to compile speex 1.1.10's speexenc for win32 using Visual > C++ 6.0 but came up with some errors (abt 33 of them, syntax errors). I > just traced them to

Dear developers, I am not able to compile speexenc and speexdec projects of speex1.0.5 on windows because of ogg.h file (and related file) are not included with the source code. So can you please include ogg.h and other file which should included in ogg folder in source code so that i can compile it and use this source. Thank you

On Sat, Jul 15, 2006 at 02:17:22PM -0500, Joe Wreschnig wrote: > I'm working on support for tagging Speex files for Mutagen[0] and part > of the specification at [1] is confusing me. It says the first page > should have granulepos 0 and packetno 0. Does this really mean page > sequence number 0, since the Ogg format doesn't number packets? Sounds like a spec bug. The libogg

Hi, I just added skeleton meta data output support in speexenc. The option is disabled by default and can be enabled using -k or --skeleton. I'm using a very simple skeleton API for handling skeleton packet generation which is contained in skeleton.h & skeleton.c. Please check the patch and whether xine/mplayer/quicktime and other players support the skeleton enabled speex file. At the

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...

Hi, Jean it was indeed an error on my part. Its fixed in this update. Also skeleton API has been updated. Thanks for catching the bug. --tahseen -------------- next part -------------- A non-text attachment was scrubbed... Name: speexenc-skeleton.patch Type: text/x-patch Size: 17115 bytes Desc: not available Url :