similar to: No subject

Hi, I think I might have kind of, sort of found a bug in opusenc. But do correct me if I am worng. :) When converting an FLAC file that contains RG tags written by bs1770gain the resulting opus file has a way, way too high RG value. I am talking >90dB(!). Here is the metaflac output of the flac file: % metaflac --block-number=2 --list bs.1770/test.flac METADATA block #2 type: 4

Hi! So here is what I got with different encoder settings; still not sure what the "best" setting is. 6kbps seems to add distortions, so I tried 12kbps. MP3-Original: LAME 3.99r, 120kbps, 44100Hz, Stereo, VBR V5 (22:23, 19.8MB) Opus (--raw-rate 44100 --bitrate 56 --vbr --comp 5): (44:45?, 23.4MB): Broken Opus (--bitrate 56 --vbr --comp 5 --ignorelength - %d): (22:23, 12.1 MB, 74kbps)

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

Hi! I'm using the opus-tools package from the current Debian (it says it is 0.1.2). The output of opusinfo is strange: $ opusinfo demo01.opus Processing file "demo01.opus"... New logical stream (#1, serial: 0000456a): type opus Encoded with libopus 1.0.1-rc3 User comments section follows... ENCODER=opusenc from opus-tools 0.1.5 Opus stream 1: Pre-skip: 356 Playback

heyas- I believe there is a need for a standard vorbis comment field to encode "Total Number of Tracks (on a CD)". Why we need this -------------------- - Existing Vorbis programs already implement this, inconsistently, and hence don't interoperate. These seems the key reason to me. - MP3s include this - Some software (e.g., iTunes) uses this information, e.g., to display

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

>On 11/20/2013 03:37 PM, O'Connor, Kevin wrote: >> I have an application I intend to use Opus for that involves creating >> recordings of two-party conversations where each party is saved as a >> separate channel. Audio may be later processed or analyzed on a >> per-party basis so if audio in one channel affects the other channel, it >> could create problems.

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

(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

('binary' encoding is not supported, stored as-is) Hello, there was a discussion about defining a TRACKTOTAL tag which ended in the conclusion that this is actually metadata about an album and we need a metadata program (like iTunes) to manage it. Well iTunes is about to be released for Windows. For everyone who likes free software or is using Linux: there's a program called prokyon3

Erik de Castro Lopo wrote: > Err, thats a link to a post talking about flac's WAV reader being limited > to 4Gig files. Problem is, *all* WAV files greater than 4Gig are mal-formed. > Due to limitations in the way WAV files are specified, no valid WAV file > can ever be over 4Gig. And most don't work over 2 GB. The solution we (Xiph) have used in other projects (opusenc,

On Aug 07 08:30:31, hans at stare.cz wrote: > On Aug 07 00:41:52, petrparizek2000 at yahoo.com wrote: > > ????#1. To test encoding at low bitrates, I encoded a sine sweep at 12 kbps > > with Opusenc and then decoded the resulting file with Opusdec. > 1) Opusenc --bitrate 12 --downmix-mono Sweep50.wav Sweep50.opus Why are you using a stereo file containing the same sweep in both

>>> Jan Stary <hans at stare.cz> schrieb am 05.11.2018 um 11:05 in Nachricht <20181105100534.GB44329 at www.stare.cz>: > (Are we off‑list now by intention?) No, just fooled by the list defaults (some need just reply, others need reply to all) > >> Did you also try to listen at the beginning, shortly before the real tone > appears in the audible spectrum?

Hello, I'm currently doing a little music player using libflac and libao. What I've currently done works as it should, but I have a problem where only one metadata block is detected, even if there are more (it doesn't have the last attribute set to true). This is using flac 1.3.2 on Gentoo amd64. The main code file is attached, it mainly follows the examples given with the libflac

Hi all! I've read http://reactor-core.org/ogg-tagging.html and http://www.vorbis.com/ot/20030303.html#id2726753 about the goals and non-goals of vorbis comments, but I'm still unsure: 1) Is it by purpose to forget about CDA's index feature because it's so rarely used or did nobody here ever thought about it? -> Add an INDEXNUMER field? 2) If "Vorbis comments are the

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

On Mar 4, 2013, at 14:39, Timothy B. Terriberry wrote: > Erik de Castro Lopo wrote: >> Err, thats a link to a post talking about flac's WAV reader being >> limited >> to 4Gig files. Problem is, *all* WAV files greater than 4Gig are >> mal-formed. >> Due to limitations in the way WAV files are specified, no valid >> WAV file >> can ever be over

Hello, I'm currently doing a little music player using libflac and libao. What I've currently done works as it should, but I have a problem where only one metadata block is detected, even if there are more. This is using flac 1.3.2 on Gentoo amd64. The main code file is attached, it mainly follows the examples given with the libflac and libao doc. And here's what metaflac --list

> First, note that the Vorbis Rage developers were very responsive > and decided to move to TRACKTOTAL; thus my original concern has > been addressed. <p>I brought this same subject up a few years ago, as I missed having a standard way of storing this information. I've decided to support this tag in WinVorbis. I've also added an option to allow or disallow alpha