On 17-01-13 08:10, Erik de Castro Lopo wrote:
> There were no code changes to the FLAC library or tools.
My mistake, I assumed that because of this documentation change, the
FLAC utility would be updated as well to handle this correctly.
___
flac-dev m
For reference, I copied missing file from 1.2.1 version and standard
installation process ended as expected
___
flac-dev mailing list
flac-dev@xiph.org
http://lists.xiph.org/mailman/listinfo/flac-dev
Martijn van Beurden wrote:
> I can't compile the git as autogen.sh fails here
That should be fixed now. Please re-test.
>
> Maybe this bug still persists? Can anyone take a look there to provide a
> 'second opinion'? See here:
> http://lists.xiph.org/pipermail/flac/2013-January/thread.html
R
On 13-01-16 11:10 PM, Erik de Castro Lopo wrote:
> My understanding is that the recent changes for 7 and 8 channels was
> a documentation change only.
I think we should also change the flac front-end utility to construct
and interpret the WAVE channel mask for 7 and 8 channel files. No one
has wr
Small code cleanup patch.
-r
>From add7f0f30566ddbaebe80eacef1192c473cd1fb8 Mon Sep 17 00:00:00 2001
From: Ralph Giles
Date: Thu, 17 Jan 2013 16:30:22 -0800
Subject: [PATCH] Hoist a repeated conditional in the channel mapping code.
This is equivalent and just makes the code shorter.
---
src/f
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
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 sugg
The flac front-end utility should have its own version number, on a
separate schedule from the flac library. I can see that we'd be able
to add features to the utility quite extensively without ever
changing the file format or the library. I realize that the utility
has historically shared
On 13-01-17 7:26 PM, Brian Willoughby wrote:
> I vote for documenting the --channel-map option in the --help
I suspect it's undocumented because 'none' is the only implemented
argument, which is a way to work around the defined channel map
signalling. I.e. it doesn't make interoperable files.
-r
On 13-01-17 7:26 PM, Brian Willoughby wrote:
> The flac front-end utility should have its own version number, on a
> separate schedule from the flac library. I can see that we'd be able
> to add features to the utility quite extensively without ever
> changing the file format or the library.
On 13-01-17 7:26 PM, Brian Willoughby wrote:
> I vote for documenting the --channel-map option in the --help
Do you ever use --channel-map yourself, or recommend it to clients?
-r
___
flac-dev mailing list
flac-dev@xiph.org
http://lists.xiph.org/mail
Ralph Giles wrote:
> Small code cleanup patch.
Applied, thanks.
Erik
--
--
Erik de Castro Lopo
http://www.mega-nerd.com/
___
flac-dev mailing list
flac-dev@xiph.org
http://lists.xiph.
12 matches
Mail list logo