search for: opustool

Hello everybody, I just want to inform you, that the first alpha-version of a GUI for the opustools for Windows is online available [1]. Critics and comments are welcome - maybe someone know how to transfer that project to an open source site. with greetings, Daniel Thomae [1] http://foveon.de/sonstiges/opusdrop/index.htm

I was transcoding a 128K MP3 speech podcast into 28K Opus and noticed that part of musical opening sounded a little worse with the recently released 1.2 OpusTools compared to the earlier 1.1 build. I thought maybe you would like to be made aware of a problem sample. I also thought there is a good chance over-compressing a musical section of 128K MP3 to 28K Opus isn't really an important use case, so no worries. I uploaded a zip containing 7s clips of...

...m the answering machine). I have no idea why they decided to do so, but it's a matter of fact. The format is still the same in the current firmware. There are hacks out that allow the tools to process files without the Ogg header, and I wonder how hard it would be to provide some options in the opustools to be able to use the standard instead of some hacks. Try Googling for "speex-1.2beta3-fritzboxtam-beta1-src.tar.bz2. Regards, Ulrich "

There was a post in the Opus subthread on HA where there was a link to the file called Opus-tools-0.2-34-g98f3ddc_(using_libopus_1.5.2-21-gff6dea5)_Win_GCC142.7z. That's the one I'm currently using. First, I used GoldWave to convert your input file from ?-law to PCM and saved it as a ".wav" file. Next, I encoded it with Opusenc, I decoded its result with Opusdec with the

...9;ve removed the Microsoft-specific code and it runs/reproduces on Linux now as well. Also, to simplify things further, I replaced the mu-law input file with a linear16 sample file and removed the extra code to do the conversion from mu-law to linear in the sample app. I don't believe that the opustools utilities support controlling DTX option, so I don't think this can be reproduced using those tools. But if you have a built opus and a recent C++ compiler, it should be dead simple to compile and run this sample application. I put an example command line for compiling under Linux in the READM...

Take a look at how the Opus Tools package handles it. So far as I remember, it requires minimal changes to the file(s) containing references to the main entry point and to fopen. It imports the command line arguments as wchar_t and converts them to UTF-8, and has replacement functions for fopen and some text output that accept UTF-8 instead of ANSI. I think it automatically kicks in on definition

...: opusfile-Support-for-Ambisonics-and-Projection-API.patch Type: text/x-patch Size: 12344 bytes Desc: not available URL: <http://lists.xiph.org/pipermail/opus/attachments/20180306/ea47482b/attachment-0004.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: opustools-Support-for-Ambisonics-and-Projection-API.patch Type: text/x-patch Size: 4419 bytes Desc: not available URL: <http://lists.xiph.org/pipermail/opus/attachments/20180306/ea47482b/attachment-0005.bin>

This patch to opus-tools adds optional support to WavPack lossless format as input to opusenc. Like support to FLAC, it depends on an external library, libwavpack, and may be disabled on configure. Lucas Clemente Vella (1): Reading input from WavPack files. Makefile.am | 7 +- configure.ac | 37 ++++++++ src/audio-in.c | 71 ++++++++------- src/opusenc.c | 19 +++- src/opusenc.h