recently that Apple ships source code for a FLAC encoder and decoder
codec component in /Developer/Examples/CoreAudio/AudioCodecs/
FLAC.xcodeproj.
You can find a slightly more detailed review of the Apple's FLAC codec
implementation in my blog post at:
I've just finished an Xcode 3.1 project file for flac and metaflac
that builds both tools as 32/64 bit universal binaries. If anyone is
interested in either the binaries or the project, I'll be happy to
share them.
Stephen
___
Flac-dev mailing
From your steps, it seems that it is possible to cross-compile, but
only if you build one architecture at a time and then manually lipo
them together. If I someday find an easy fix for this, I'll let you
know. Then again, Stephen may have figured out the magic incantation
for Xcode to make
I've recently run it through valgrind, and I'm seeing memory leaks like the
following:
12 bytes in 1 blocks are definitely lost in loss record 1 of 5
at 0x402377E: operator new(unsigned) (vg_replace_malloc.c:224)
by 0x41448A8: FLAC::Metadata::local::construct_block(FLAC__StreamMetadata*)
On my system (10.7.2, Xcode 4.2) invoking ./configure builds for 64 bit by
default. The only additional step to take is turning off assembly code:
% ./configure --disable-asm-optimizations
% make
% file src/libFLAC/.libs/libFLAC.dylib
src/libFLAC/.libs/libFLAC.dylib: Mach-O 64-bit dynamically
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
On Sunday, September 23, 2012 at 2:04 PM, Ralph Giles wrote:
On Fri Sep 21 16:31:21 2012, Stephen F. Booth wrote:
6.1: L R C LFE Ls Rs Cs (MPEG 6.1 A layout)
I should have been clearer with the labels I was using:
L = Left
R = Right
C = Center
LFE = Low frequency effects
Ls = Left surround
I'll be happy to post an OS X build of FLAC 1.3.0, but I was operating under
the assumption that Xiph would prefer to compile the official version
themselves. I didn't want to add another unofficial binary to the mix.
Stephen
On Friday, July 12, 2013 at 11:42 AM, Michael wrote:
Stephen F
On Sat, Mar 8, 2014 at 7:49 AM, Каримов Родион rodionkari...@yandex.ruwrote:
I create FLAC file decoding, processing and playing program and have the
following question : how to convert FLAC 16 bit file data to 32 bit float
buffer for CPU processing? I've already inplemented sound playing and
Is this a case where something allowed by the specification isn't
implemented by the reference encoder/decoder (such as 25-32 bits per
sample) but could be in a different implementation? If so, I am not sure
whether it makes sense to change the specification based on the reference
implementation.
be used in very rare cases,
> there is no benefit from allowing this.
>
> Op vr 19 jun. 2020 om 18:03 schreef Stephen F. Booth :
>
>> Is this a case where something allowed by the specification isn't
>> implemented by the reference encoder/decoder (such as 25-32 bits per
11 matches
Mail list logo
