similar to: A couple of questions about channel mapping

lvqcl wrote: > Martin Leese wrote: >> Why place restrictions on which speaker a >> user can use? ... >> Finally to answer your question, for a >> single-channel file, FLAC should accept any >> one of the three masks 0x00000001 (FL), >> 0x00000002 (FR), 0x00000004 (FC), plus any >> one of the 15 other single-bit masks, plus zero. Please note that the

Friends, My name is Igor, I am new to this forum. I have a peculiar problem with my OGG/Speex implementation: I encode a short PCM stream in OGG/Speex, but the result can not be read by VLC and MediaInfo <http://mediaarea.net/nn/MediaInfo> reports that the file is too short (240ms). In reality the file contains about 2.7 sec worth of audio. Another interesting thing I noticed is that the

I apologize for the terribly long message, but here goes. ------------------------------------------------------------------------------------------------- First, regarding existing tools that I now about. libavcodec and users (e.g. HandBrake): - if there are 6 channels or less, the layout is set by the decoder as per the FLAC specification - if there are more than 6 channels, the layout is

lvqcl wrote: ... > From FLAC 1.2.1 documentation: > > 0000-0111 : (number of independent channels)-1. Where defined, the channel > order follows SMPTE/ITU-R recommendations. The assignments are as follows: > 1 channel: mono > 2 channels: left, right > 3 channels: left, right, center > 4 channels: left, right, back left, back right > 5 channels: left, right, center,

lvqcl wrote: > Martin Leese wrote: >> Note that the channel order may not be defined. > > IMHO it doesn't matter in this place of documentation (which describes > default channel assignments for FLAC). Your proposed wording was: 0000-0111 : (number of independent channels)-1. The channel order follows SMPTE/ITU-R recommendations. The assignments are as follows: The

Martijn van Beurden wrote: > Op 16-07-15 om 17:58 schreef lvqcl: >> But this text describes only those 4 bits in frame header. >> IMHO this sectoin should not describe WAVEFORMATEXTENSIBLE_CHANNEL_MASK, >> it should be described somewhere in vorbis comments section. > > I would propose: 0000-0111 : (number of independent channels)-1. > The channel order is defined

On 7/16/15, Martin Leese <martin.leese at stanfordalumni.org> wrote: > Martijn van Beurden wrote: >> I would propose: 0000-0111 : (number of independent channels)-1. >> The channel order is defined through the >> WAVEFORMATEXTENSIBLE_CHANNEL_MASK vorbis comment, if defined. If >> no WAVEFORMATEXTENSIBLE_CHANNEL_MASK is present, the channel >> order follows

Maybe I don't understand you correctly, but 0000 is mono, not undefined. It says: 0000-0111 : (number of independent channels)-1 I agree that the use of WAVEFORMATEXTENSIBLE_CHANNEL_MASK should be documented. I can probably take a look at it this week or so, if no one hasn't already? 2015-07-05 13:54 GMT+02:00 lvqcl <lvqcl.mail at gmail.com>: > An issue was raised at < >

An issue was raised at <http://forum.doom9.org/showthread.php?p=1728923#post1728923> - FLAC uses WAVEFORMATEXTENSIBLE_CHANNEL_MASK tag to describe non-standard layout, but it isn't mentioned anywhere in FLAC format. Channel assignment is described at <https://xiph.org/flac/format.html#frame_header>: "Where defined, the channel order follows SMPTE/ITU-R recommendations."

Martin Leese wrote: > Your proposed wording was: > 0000-0111 : (number of independent channels)-1. The channel order > follows SMPTE/ITU-R recommendations. The assignments are as follows: > > The channel order might not follow SMPTE/ITU-R > recommendations, so this proposed wording > seems misleading to me. But this text describes only those 4 bits in frame header. IMHO

Hello, after mediainfo packages have been updated from 22.12-3.el7.x86_64 to 23.03-1.el7.x86_64, I observe reproducible crashes here, mostly by using it with mkv files. I couldn't find a mirror of the EPEL repository where 22.12 is still available (only found an old 20.08-1). Does anybody reproduces issues w/ mediainfo? Any hint how to find the 22.12-3 rpms? Regards, -- wwp --------------

Am 02.05.23 um 08:51 schrieb wwp: > Hello, > > after mediainfo packages have been updated from 22.12-3.el7.x86_64 to > 23.03-1.el7.x86_64, I observe reproducible crashes here, mostly by using > it with mkv files. I couldn't find a mirror of the EPEL repository > where 22.12 is still available (only found an old 20.08-1). > > Does anybody reproduces issues w/

Hello folks I am encoding music to ogg vorbis format for the first time. From what i have researched, ogg vorbis is natively a vbr format. Also encoding using the -q switch is encouraged instead of specifying a bitrate through -b. Now, while encoding using -b i get this: Encoding "file.wav" to "file.ogg" at approximate bitrate 224 kbps (VBR encoding enabled) Notice

Currently FLAC doesn't read the contents of WAVEFORMATEXTENSIBLE_CHANNEL_MASK tag in a decoded FLAC file and doesn't write correct channel mask to a WAV file. (d->channel_mask == 0 inside DecoderSession_process() function in decode.c) The attached patch fixes this problem but I'm not sure that it doesn't have any side effects... Also, maybe it's better to call

This is equivalent and just makes the code shorter. --- src/flac/decode.c | 24 +++++++++--------------- 1 file changed, 9 insertions(+), 15 deletions(-) diff --git a/src/flac/decode.c b/src/flac/decode.c index fa82c04..98fc430 100644 --- a/src/flac/decode.c +++ b/src/flac/decode.c @@ -333,32 +333,26 @@ FLAC__bool DecoderSession_process(DecoderSession *d) return false; /* set channel

Hello, I'm currently testing Icecast 2.4.99.1 in regards to Opus metadata support. I have a Ogg Opus stream located here: http://50.31.159.156/64.opus When I playback the stream in VLC I see the expected metadata displayed in the client. ffprobe and mediainfo also return the expected metadata. # mediainfo http://50.31.159.156/64.opus General Complete name :

Dear all, It's been a while since I have started to look at the code for Souffleur that was dropped a couple of years ago by its former maintainer. I have now a few patches that I would like to be committed to the trunk of this project if approved. I am sorry if the modifications are not aligned with the project's main purpose but I had no one to talk to about its main goal.

Dennis Brunnenmeyer <dennisb at chronometrics.com> wrote: > Somewhere I thought I saw a list of proposed extensions to the small set > of pre-defined vorbis comments. If adopted, would these become part of > the FLAC standard, or would they stand alone as recommended practice. This is something I did. The spreadsheet is called "FieldNames.xls" and can be found here:

Hi, Sorry for being off topic, but I am stuck. What forums or mailing lists are suitable for advice on how to play a particular video file? The file (actually a set of eight files) has the extension ".wmv", but Windows Media Player gave the error that the file format did not match the extension. VLC also will not play the file. If anybody wants to look inside, I have placed the file

Dear members of the flac-dev list, I'm writing to ask for feedback from the FLAC community regarding the possibility of standardizing the FLAC specification through the Internet Engineering Task Force. I'm working with MediaArea on the PREFORMA project which focuses on building conformance checkers for Matroska and FFV1. Since Matroska and FFV1 are not yet formally standardized, this