Displaying 20 results from an estimated 3000 matches similar to: "libFLAC optimizations request"
2018 Feb 04
2
libFLAC optimizations request
Correction, the flac command-line does create a 40-byte Vorbis comment by default. I just never noticed it before. I’ve been using —no-padding all these years for minimal file sizes without realizing that I could save another 40 bytes.
Anyway, since metaflac can remove the Vorbis comment using the standard library, then you should be able to create a solution without modifying libFLAC.
Brian
2018 Feb 04
1
libFLAC optimizations request
I wasn’t suggesting that you run metaflac, but that you examine its source to see how it creates new FLAC files without the Vorbis comment. As far as I know, metaflac uses the standard libFLAC and creates files without the Vorbis overhead.
My quick review of the source seemed to indicate that calling FLAC__metadata_object_new(FLAC__METADATA_TYPE_VORBIS_COMMENT) will create the comment, but I
2018 Feb 04
0
libFLAC optimizations request
Gabriel,
metadata_has_vorbis_comment is a FLAC__bool which defaults to false. There should be no reason to modify stream_encoder.c, but just modify the caller.
The following command:
metaflac —remove —block-type=VORBIS_COMMENT —don’t-use-padding
… will remove Vorbis comments from existing files, so is must be legal without modifying the library. metaflac can clearly create a new FLAC file
2018 Feb 04
0
libFLAC optimizations request
The problem is really as I wrote:
1. Metaflac is no option for me, I use libFLAC.dll
2. There is no way (at least how I read the code) to avoid saving
comment with libFLAC; I would appreciate an extra option to avoid it,
which can default to old behavior if compatibility is important.
3. I have a high speed application, where re-initializing an encoder
is really significant. On corner cases it
2013 May 15
2
FLAC currently won't compile for Android [bisected]
2013/5/15 Ulrich Klauer <ulrich at chirlu.de>
> Felix Homann wrote:
>
> > Yes, HAVE_SYS_PARAM_H is set in config.h:
>
> OK ... Yet still I don't see how a change in
> src/libFLAC/include/private/macros.h could affect src/flac/utils.c in
> any way.
>
> Anyone got an idea?
I haven't spend too much attention to the errors when bisecting, sorry!
The
2018 Mar 22
2
Crash when writing 32bit flac files, am I doing something wrong ?
Hello,
I manage to successfully write 8, 16 and 24 bit, all stereo, FLAC files.
But when I try to write 32 bit FLACs my program crashes.
*FLAC__stream_encoder_set_bits_per_sample *is called to match the desired
bit depth (8, 16, 24, 32)
It's the same code for all bit depths, i provide a fixed-size signed int
buffer to the lib (size=16384), with values with appropriate ranges for
each bit
2018 Feb 02
2
libFLAC optimizations request
Hello again,
After some time, I succeeded in splitting "flush" and "restart"
functions. A quick measurement gives me ~25% speed improvement, which
is quite a lot. Of course this optimization is specific for this use
case (many short signals).
Is this interesting for the project? I would gladly contribute it...
If yes, how should I share it? As a patch against current git?
2014 Oct 03
2
[PATCH 5/5]
This patch adds two AVX2 files and adds AVX2 support code into
init_stream_internal_() in stream_encoder.c.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 05_avx2.zip
Type: application/zip
Size: 7279 bytes
Desc: not available
Url : http://lists.xiph.org/pipermail/flac-dev/attachments/20141003/1471b3d6/attachment-0001.zip
2018 Feb 08
1
libFLAC optimizations request
Hi,
On Sat, Feb 3, 2018 at 10:10 AM, Erik de Castro Lopo
<mle+la at mega-nerd.com> wrote:
> Gabriel Corneanu wrote:
>
>> Is this interesting for the project?
>
> I would theoretically accept a patch that allows direct access to the
> functionality you seek, as long as it doesn't change the existing API.
>
>> If yes, how should I share it? As a patch against
2004 Sep 10
2
libFLAC docs
For those of you using CVS, I have added a libFLAC section to the
documentation page. I'm not sure how detailed to make it but I
think it's a good start. Let me know if there's anything else
you'd like to have in there.
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/~checkout~/flac/flac/doc/documentation.html?rev=HEAD
Also, I'm thinking about splitting the encoder into
2014 Oct 05
1
[PATCH 5/5]
On 5.10.2014 10:22, Erik de Castro Lopo wrote:
> lvqcl wrote:
>
>> This patch adds two AVX2 files and adds AVX2 support code into
>> init_stream_internal_() in stream_encoder.c.
> Ste of 5 patches all applied. Thanks
>
> I did run this on my machine with 4 i5-4440 cores wich accoring to /proc/cpu
> has svx2 support. However I'm not sure if flac was actually using
2004 Sep 10
6
libFLAC docs
> > For those of you using CVS, I have added a libFLAC section to the
> > documentation page. I'm not sure how detailed to make it but I
> > think it's a good start. Let me know if there's anything else
> > you'd like to have in there.
> >
> >
>
2017 Jan 13
9
Upstreaming Gentoo patches
Dear FLAC devs,
I would like to get some of our patches merged into master. Most
of them deal with adhering to GNU conventions, respectively not
overriding flags/variables that are up to the user to set. For instance,
honoring $(htmldir) is important, as we have installation paths for the
documentation that differ from what is currently coded in the various
Makefile.am's.
Regards
David
2004 Sep 10
3
getting framesize in client
On Fri, Nov 08, 2002 at 12:39:52PM -0800, Josh Coalson wrote:
> --- Miroslav Lichvar <lichvarm@phoenix.inf.upol.cz> wrote:
> > I have few notes:
> >
> > It seems there is changed API in CVS again. So, what about adding
> > function like
> > unsigned FLAC__format_frame_size(const FLAC__Frame *frame)
> > which returns size of the frame in bytes. This
2014 Dec 06
2
GCC/clang compilation issues
> Oliver St?neberg wrote:
>
> > I finally got around to trying to update FLAC for the MAME/MESS
> > project again. There were several issues I was able to fix and will
> > submit patches later, but I hit one roadblock with GCC and clang:
> >
> > src/lib/libflac/libFLAC/stream_encoder.c:1696:43: error: cast from function call
> > of type
2004 Sep 10
2
getting framesize in client
I have few notes:
It seems there is changed API in CVS again. So, what about adding
function like
unsigned FLAC__format_frame_size(const FLAC__Frame *frame)
which returns size of the frame in bytes. This can be useful, for
example, in xmms plugin to display current bitrate like vorbis plugin
does.
If 'PERFORMER' field is missing in vorbis comment, it would be nice to
display
2014 Dec 06
2
GCC/clang compilation issues
Hi,
I finally got around to trying to update FLAC for the MAME/MESS
project again. There were several issues I was able to fix and will
submit patches later, but I hit one roadblock with GCC and clang:
src/lib/libflac/libFLAC/stream_encoder.c:1696:43: error: cast from function call
of type 'double' to non-matching type 'FLAC__int32' (aka 'int')
2018 Jul 10
9
[PATCH 0/7] PowerPC64 performance improvements
The following series adds initial vector support for PowerPC64.
On POWER9, flac --best is about 3.3x faster.
Amitay Isaacs (2):
Add m4 macro to check for C __attribute__ features
Check if compiler supports target attribute on ppc64
Anton Blanchard (5):
configure.ac: Remove SPE detection code
configure.ac: Add VSX enable/disable
configure.ac: Fix FLAC__CPU_PPC on little endian, and add
2014 Sep 23
4
Disk fragmentation
I have been running a lot of large compression tests to see how well
Martijn van Beurden's new presets do and was once again reminded how
real the fragmentation problem still is.
To have decent speed it's necessary to run multiple encoders in
parallel. In my setup FLAC was compressing four files at the same time
and each instance writes tiny bits of data to disk at once. A
2006 Jul 11
3
Building a Rice Encoder/Decoder from FLAC
Hi all,
I am interested in building a stand alone Rice Encoder/Decoder, using FLAC
source code as a starting point. I've read the theory behind it, and I am
very interested in info theory. However, I am struggling with how exactly
I would implement the theory in code. I'm a newbie to computer science
(only 1 year experience). I have read the format and documentation links on
the FLAC