similar to: Questions on Opus encoding

Hi! Playing with Opus 1.3 I converted a tone sweep with a sample rate of 96kHz (just for fun). Before I had converted that from WAV to FLAC, and to Vorbis without problems. With Opus I noticed that the file size for 48kHz and 48 kbps compared to 96kHz Vorbis at 31kbps is about double the size and it sounds even worse (than Vorbis) (there is a lot of noise in the lower frequencies when a low

Hi! Excuse the delay, but I had to deal with a corrupted NTFS file system that ate many important files on an USB stick... The FLAC version of the original is almost 6MB and it can be downloaded slowly from this time-limited link: https://sbr5vjid0jgmce4q.myfritz.net:40262/nas/filelink.lua?id=0ba5a10529a6fe7b On the meaning of a logarithmic sweep: If you use foobar2000 and the

Hi! Sorry, I know the rules for comparing objective subjective listening impressions, but I'd like to know whether from the algorithmic or implementer's point of view the following personal impressions can be confirmed: Comparing MP3 with Vorbis at rather high bitrates, I had the impression the Vorbis sounded more crispy, while MP3 sounded somewhat softened. I preferred Vorbis for that

Hi! You probably know already, but recently there's "fobbar2000 mobile" available for Android (I think Windows and iOS, too), and it plays Opus even ol older Android (like 4.0). Ulrich

Hi! I have some MP3 audio material which is basically speech with some background noises, essentially > 120Hz and < 5kHz. I had the idea to reduce the file size by recoding the material to Opus at 56kbps. Unfortunately the result is a file sampled at 48kHz much larger than the original. I hope you agree that it does not make sense to create a file larger than the original (MP3). Of course

Hi! Useful advice, thanks! Actually I had been using foobar2000 to recode, because it just makes it so easy to convert multiple files while keeping the metadata (I confess, I'm a "tagger"). But it's easy to miss some encoder option when being presented some default suggestions in a dialog form... Apart form that I always had the impression that Opus could be quite smart

On Mon, Nov 5, 2018 at 11:01 AM Jan Stary <hans at stare.cz> wrote: Attached I send the spectrogram (vic SoX) of the first 20 seconds > for the wav file and the opus file. Indeed, there is extra noise > for the low frequencies, but somewhere around -100 dB. > > Jan > That might be entirely due to SoX treating it as a 16-bit file, which it is not; -100dB is almost

Hello Jean-Marc, As an example, I am using the output of opus encoder to store the file as the following format and read back the same during decode process, without having much overhead. (Thought it would be useful to put a picture rather than running text) [image: Inline image 2] Regards Amit On Thu, May 12, 2016 at 10:47 AM, Amit Ashara <ashara.amit at gmail.com> wrote: > Hello

On 05/12/2016 10:35 AM, Amit Ashara wrote: > For HMI panels, except for the capture pattern and a single page segment > entry, other fields are not important, and which results in almost 7% > overhead for a 20ms raw frame encoded with Opus. I'm not sure how you get a 7% overhead. In most uses I've seen, the overhead is more around 1%. > At the same time the > file

The overhead of Ogg (in file size) is pretty small and it's efficient enough for most applications (and uses far less CPU than the codec anyway). If anything, you might want to look at optimizing the existing Ogg implementation (e.g. like Tremor did in the context of Vorbis). Of course, you're always free to design a new container, but I doubt it's worth it and it's a lot of work

Hi, I'm wondering: If you have audio files like foo1.ogg and foo1.mp3, and the Vorbis file has nice comments (title, tracknumber, artist, album, date, etc), is there a tool to copy the information to an MP3 file on a "best effort" strategy? I know that MP3 TAGs are quite limited regarding lengths. Regards, Ulrich

>>> Amit Ashara <ashara.amit at gmail.com> schrieb am 11.05.2016 um 19:32 in Nachricht <CAEyg9sjvTWMBMMCJ8HQcYmbv1BtNt54CgpqWaGNm02MWrKcxaQ at mail.gmail.com>: > Hello Jean-Marc, > > So for the moment we can assume that this method is also OK to use? > > On Embedded Systems, both SRAM and Flash can be a restricting factor > besides the compute time. To

switch between speech and music encoding rather quickly. I wanted to try that for a CD track that has a vocal (talk) introduction = followed by music (just two instruments). Using foobar2000 with some custom setup for Opus, I tried VBR encoding = with a 256kbps setting (opus-tools-0.1.9-win32). My expectation was that = the bitrate would be significantly lower than 256kbps while speech is =

Hi Ulrich, As Jean-mark recommended, we created "--enable-check-asm" config option to active OPUS_CHECK_ASM macros in the optimization, where the C function is called inside and the results of C and optimization functions are compared when encoding/decoding the real audio files. Thanks, Linfeng On Wed, Apr 19, 2017 at 11:46 PM, Ulrich Windl < Ulrich.Windl at

(Please wrap your lines.) On Oct 26 01:38:34, Ulrich.Windl at rz.uni-regensburg.de wrote: > Playing with Opus 1.3 I converted a tone sweep with a sample rate of 96kHz (just for fun). Before I had converted that from WAV to FLAC, and to Vorbis without problems. Can you please post the original wav? I am not sure what Audacity means by a logarithmisch sweep. Is that a fixed number of Hertz per

opusdec -V opusdec opus-tools f2a2e88 (using libopus unknown) I've got an opus file encoded from a .wav off a cd, 44100Hz: opusinfo 2-24-Overture_in_C_\(In_Memoriam\).opus Processing file "2-24-Overture_in_C_(In_Memoriam).opus"... New logical stream (#1, serial: 38134f1f): type opus Encoded with libopus unknown User comments section follows... ENCODER=opusenc from opus-tools

Dear authors of Opus, currently, the manpages that come with opus-tools are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on the

Hi! I was just trying libopus0-1.1-3.2.x86_64 and opus-tools-0.1.9-3.2.x86_64 on openSUSE Leap, and I was wondering: opusenc does not display the file name it processes. In Lunux when you use some batch processing, it might be interesting! Example output for "for f in *.wav;do opusenc --bitrate 160 $f ${f%.wav}.opus; done": ---just on file--- Encoding using libopus 1.1 (audio)

Hello, I had talked earlier with 'Timothy B. Terriberry' <tterribe at xiph.org>, about adding support for AVX instructions in Opus, but since he appears to be busy I would like to resend this on the mailing list. I've created a pull request https://github.com/xiph/opus/pull/5 to add the testing infrastructure for the changes before adding the actual code. A draft for the rest

>>> Amit Ashara <ashara.amit at gmail.com> schrieb am 12.05.2016 um 17:47 in Nachricht <CAEyg9sgjbsxQY-=VnhQrKiGeTcFSRr1wxOPUhNyCQF8Piuahow at mail.gmail.com>: > Hello Jean-Marc, > > Assuming that a 48KHz, 20ms 8-bit linear PCM data which is 960 bytes is > compressed to 64 bytes (for assumption). The with the Oggs header (4 byte) Actually what I don't