similar to: [PATCH] Add appropriate WAV channel masks for 7 and 8 channel files.

On 13-03-01 2:17 PM, Erik de Castro Lopo wrote: > Ralph, looks like there's a missing closing brace there. Do you want to fix > it and resubmit or should I fix it? Sorry about that. Is this one better? -r -------------- next part -------------- commit 93d92eb5e98cacd8cab185a0bfdaafb795b14b22 Author: Ralph Giles <giles at mozilla.com> Date: Thu Jan 17 16:21:45 2013 -0800

Now that we've selected a channel mapping for 7 and 8 channel flac, the command-line encoder tools needs updating to accept wav files with compatible channel maps. -r -------------- next part --------------

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

The commit http://git.xiph.org/?p=flac.git;a=commitdiff;h=99257e177eac96fa41a107b423080232f59ebe45 also requires some changes in write_iff_headers() function: currently flac don't write WAVEFORMATEXTENSIBLE header if decoder_session->channel_mask is equal to 0, 1 or 3. After the commit 99257e17 flac should do this for channel_mask equal to 0, 4 or 3. The patch fixes this.

lvqcl wrote: > The commit http://git.xiph.org/?p=flac.git;a=commitdiff;h=99257e177eac96fa41a107b423080232f59ebe45 > also requires some changes in write_iff_headers() function: > > currently flac don't write WAVEFORMATEXTENSIBLE header if > decoder_session->channel_mask is equal to 0, 1 or 3. > After the commit 99257e17 flac should do this for channel_mask > equal to

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

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

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

On 13-01-01 4:36 PM, Tim W. wrote: > - 4 channels: left, right, back left, back right (FL FR BL BR) > - 5 channels: left, right, center, back/surround left, back/surround right > (FL FR FC BL BR or FL FR FC SL SR, same order so doesn't matter) > - 6 channels: left, right, center, LFE, back/surround left, back/surround right > (FL FR FC LFE BL BR or

Curt Sampson wrote: > On Sun, 24 Aug 2003, smoerk wrote: > > >>there are different channel profiles for 5.1: >>L R C LFE Ls Rs (DVD) >>L R Ls Rs C LFE >>L C R Ls Rs LFE (Film) > > > I don't see why you need more than one of the above formats. It's not > like you can't decide to put the LFE channel into "input 3" or "input

I vote for documenting the --channel-map option in the --help I don't like the idea of rejecting a multichannel file merely for mapping, so there should be a documented option plus an error message pointing to the option. This should compare to the WAVE and AIFF errors where the utility suggests to the user how to get the file converted safely. Brian Willoughby Sound Consulting On

Hi , I was trying to guess the channel order or Tremor decoder for 5.1 channel file. Though the standard state it to be FL,C,FR,RL,RR,LFE but in my opinion its FL,C,FR, LFE RL,RR. I am not sure if my guess is correct . I came to this conclusion after downmixing from five to two channels. If i assume the channel order to be as per the standard then my two channel output is not correct but if i

On Sun, 24 Aug 2003, smoerk wrote: > there are different channel profiles for 5.1: > L R C LFE Ls Rs (DVD) > L R Ls Rs C LFE > L C R Ls Rs LFE (Film) I don't see why you need more than one of the above formats. It's not like you can't decide to put the LFE channel into "input 3" or "input 5" or whatever set of inputs your sending it to, depending on

Josh Coalson wrote: > --- smoerk <smoerk@gmx.de> wrote: > >>i didn't find anything about tagging flac files as surround files. i >>think there should some possibility to tell the player how to play a >>multi-channel file (how to map the different channels to the speakers >>or if there some decode is needed, like for ambisonic files). > > > it

I've been doing a fair amount of work with Vorbis support for Ambisonics, which seems to be going along nicely. It seems that there is signifant interest in coding 5.1 material with Vorbis esp as tarkin becomes more complete, so I've decided to take a break from pure ambisonic work to look into this. I've decided that the best (from a pure elegance and patent avoidance) way to handle

I've been doing a fair amount of work with Vorbis support for Ambisonics, which seems to be going along nicely. It seems that there is signifant interest in coding 5.1 material with Vorbis esp as tarkin becomes more complete, so I've decided to take a break from pure ambisonic work to look into this. I've decided that the best (from a pure elegance and patent avoidance) way to handle

On 20030610: Gregory Maxwell wrote: (in reply to Ralph Giles) >> I assume you're aware of the technical documentation on dolby's site? >> (http://www.dolby.com/pro/) In particular the surround mixing guide has >> a lot of detailed guidelines. I don't have any practical experience >> with it though, so I can't vouch for it. >Yes I am. I've done a

Hey everyone, I've added Ogg Opus support to my Adobe Premiere plug-in here: http://github.com/fnordware/AdobeOgg Now I'll add Opus support to me WebM plug-in too. I've got this Opus stuff mostly figured out, but I have a few questions. Here's one: What do the numbers in mapping mean? I see that opus.h refers to the Vorbis channel mapping order, so does mapping in Opus take

On 2014-01-06 10:24 AM, Brendan Bolles wrote: > http://github.com/fnordware/AdobeOgg Cool! > What do the numbers in mapping mean? These numbers tell you how to map the decoded opus channels to particular speakers. > For example, opus_multistream_surround_encoder_create() sends out mapping[] = {0, 4, 1, 2, 3, 5}. > For 6 channels the Vorbis order is front left, center, front right,

I like the idea of standardizing the channel maps. I would suggest the following channel orderings: 6.1: L R C LFE Ls Rs Cs (MPEG 6.1 A layout) 7.1: L R C LFE Ls Rs Rls Rrs (MPEG 7.1 B layout) I think this more closely matches what Apple has done and what the default WAVE channel order is (http://msdn.microsoft.com/en-us/windows/hardware/gg463006.aspx). Stephen On Friday, September 21,