similar to: ssh-add -h gives incomplete message

The format you're describing here actually has *more* overhead than Ogg, not less. It's also unseakable, not robust errors, and without support for metadata. I'm not sure why you would want that. It's not like you're forced to include much data in the Ogg metadata (which seems to be the source of all the overhead you're seeing). Jean-Marc On 05/12/2016 11:51 AM, Amit

>>> Ralph Giles <giles at thaumas.net> schrieb am 21.12.2015 um 19:51 in Nachricht <CAEW_RkshUM55uwdvU6DsE17pLZki651Xvvu7d2Y6jObePXZwCQ at mail.gmail.com>: > On 21 December 2015 at 04:31, Ulrich Windl > <Ulrich.Windl at rz.uni-regensburg.de> wrote: > >> opusenc does not display the file name it processes. In Lunux when you use > some batch processing,

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

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

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

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) + 1 segment entry (which is the size of the segment itself) + 64 bytes will amount to (4+1)/(4+1+64) = ~7.2%. This when compared with the original Oggs container itself for the same data payload size (26+1)/(26+1+64) = ~29.6%. Even if

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

http://bugzilla.mindrot.org/show_bug.cgi?id=511 Ulrich.Windl at rz.uni-regensburg.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|INVALID | ------- Additional Comments From Ulrich.Windl at

>>> Linfeng Zhang <linfengz at google.com> schrieb am 25.04.2017 um 01:52 in Nachricht <CAKoqLCDvAk7eeS-gpmqSHVxp4t-Lzzw7TLo5rRo=Ey_Q==cxGg at mail.gmail.com>: > 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

Hello Jean-Marc, I suspected the answer to be No. 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. At the same time the file processing complexity is way too less considering that CRC's do not not need to be considered (programmer pods ensure that)

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, with OpenSSH_2.3.0p1 running in HP-UX 11.00 I noticed that the "SD commands" (like "swcopy") produce the following error when being logged in via SSH: ERROR: RPC exception: "Who are you failed (dce / rpc)" 11/29/00 11:20:18 MET Ideas? Regards, Ulrich P.S. Not subscribed to the list

Hello Ulrich 20ms is the size of each frame. The overall sound clips may be 0.25 - 0.75 secs each. Regards Amit On Fri, May 13, 2016 at 2:15 AM, Ulrich Windl < Ulrich.Windl at rz.uni-regensburg.de> wrote: > >>> Amit Ashara <ashara.amit at gmail.com> schrieb am 12.05.2016 um 17:47 in > Nachricht > <CAEyg9sgjbsxQY-=VnhQrKiGeTcFSRr1wxOPUhNyCQF8Piuahow at

"Unfortunately my search for a good free player for Android was not very successful" - I presume you are using an Android device. If that's the case, portable devices have really bad electronics from the point of view of HiFi - because of low voltage and output amplitude being close to power rails. My point is that you are not really comparing one lossy format to another, but rather

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! 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, this is a bit off-topic, but maybe you can help me: When extracting the autio track of a concert on video DVD, I noticed that the *.VOB files each contained only about 16 minutes of music, resulting in multiple files. I extracted to flac for further processing, but now I wonder how to make one continuous sound stream of those: Can I simple concatenate the flac files to make on big file

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

On 21 December 2015 at 04:31, Ulrich Windl <Ulrich.Windl at rz.uni-regensburg.de> wrote: > 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": In situations like this, i usually insert an 'echo $f;' before he

>>> Drew Allen <bitllama at google.com> schrieb am 10.10.2017 um 20:29 in Nachricht <CABQ9DctQ0+gBgUif7BBJpjjKR7_V_H5OC1JM47w50oaaLXL4Tg at mail.gmail.com>: > Hi Jean-Marc, > > Thanks for the feedback. Attached are my comments and an updated patch. > > 1) I see that it's adding an #include of stdarg.h to opus_multistream.h > Is that left over from the