Displaying 20 results from an estimated 5000 matches similar to: "mac os x"
2004 Sep 10
2
KAudioCreator
In case you cut and paste this, I think Matt meant argv[3] to be
--tag=artist=%artist
--
Brady Patterson (brady@spaceship.com)
Do you know Old Kentucky Shark?
On Sun, 25 May 2003, Matt Zimmerman wrote:
> flac -o %o --tag=title=%artist --tag=album=%album --tag=title=%song
> --tag=tracknumber=%track %f
2004 Sep 10
6
libFLAC internals
Howdy.
I'm working on Altivec versions of some of the libFLAC functions. I figured
the best candidates would be those that had MMX/SSE/3dnow versions, and I
picked FLAC__lpc_restore_signal() to do first, since it's relatively simple.
In stepping through some runs, it appears that 'order' mod 4 is always 0. Is
that guaranteed, either by the format or by higher functions in the
2004 Sep 10
4
Altivec Optimizations
Hi,
I have been playing with Altivec, and I rewrote a couple of the routines
in assembly. Looking at the archives, I noticed that there may already
be some effort on this. Anyways...
Right now, I have two routines working. They need to be cleaned up,
made
relocatable, and documented; otherwise, they seem to work fairly well.
I
see an overall ~27% speed improvement when encoding with the
2004 Sep 10
2
KAudioCreator
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am the the author of KAudioCreator. A simple cd ripper/encoder application
for KDE. I would like to add flac (or is it FLAC?) to the default encoders.
KAudioCreator uses a simply command line listing for its encoders. For
example:
To leave as a wav file: "mv %f %o"
To encode with oggenc: "oggenc -o %o -a %artist -l %album -t
2004 Sep 10
2
Altivec, automake
finished hooking up the altivec stuff so it works in ProjectBuilder.
I ran a test, doing a 'flac -t' on 400MB of files compresses at
level 5. the runtime dropped from from 180 sec to 105 sec!
once I get the latest autotools on my ibook I'll try and get
asm compilation to work that way.
Josh
--- Josh Coalson <xflac@yahoo.com> wrote:
> OK, checked it all in (only minor
2004 Sep 10
2
command-line: AIFF writer advice
--- Matt Zimmerman <mdz@debian.org> wrote:
> On Tue, Jul 30, 2002 at 09:04:38PM -0500, Brady Patterson wrote:
>
> > The patch I submitted only reads AIFF files. I'm about to start
> the patch to
> > write AIFF files.
> >
> > To do so, we need a command-line option to specify AIFF. My
> inclination is to
> > add an option:
> >
> >
2004 Sep 10
2
Altivec, automake
Here's what I listed in that email. Merging doesn't appear to be necessary. If
you have any build problems, let me know.
Note that my detection code is Darwin-specific. It's a BSD call (sysctl()), so
a change to the platform-detection macros should enable it to work on other
BSDs. However, I don't know what that would be, and I couldn't determine any
safe way to do the check
2005 Jan 29
4
A couple of points about flac 1.1.1 on ppc/linux/altivec
On Thu, 27 Jan 2005, John Steele Scott wrote:
> That looks fine to me as well. However, the best solution is something which
> Luca suggested a few months ago, which is to use the functions defined in
> altivec.h. These are C functions which map directly to Altivec machine
> instructions. I am willing to help out, but I don't find the current lpc_asm.s
> very easy to follow, and
2004 Sep 10
2
build problems (autoconf/libtool)
Hi.
I want to add some code to flac and am having trouble building it out of cvs.
I've had several problems, most of which were pretty easy to work around or
had already been discussed here. But this one has me stumped (though I am
admittedly new to autoconf, automake, and libtool). Here's the problem.
autoconf does not see any definition for AC_PROG_LIBTOOL. There is such a
2004 Sep 10
2
command-line: AIFF writer advice
--- Brady Patterson <brady@spaceship.com> wrote:
> > Brady, I would say for now, your proposal is fine. I am going
> > to move flac to getopt soon...
> >
> > Matt, that would be cool if you wanted to take on the audiofile
> > support. I have actually been waiting to ask you for that,
> > waiting until I got the getopt support done, and the new
> >
2004 Sep 10
1
FLAC/assert.h overwrites /usr/include/assert.h?
I always use --prefix, and it gets put in the right place
(<prefix>/include/FLAC/assert.h), which I'm sure sheds no new light on this.
I'd still like to know why FLAC__ASSERT() is necessary. K&R is very clear that
the preprocessor is to remove calls to assert() if NDEBUG is defined. (Some
compilers, including gcc, implicitly define NDEBUG when optimizing, but of
course it can
2004 Sep 10
1
Altivec, automake
Thanks. I was worried about the assembler invocation but it looks like you
solved that problem.
Smooth build on my pbook (G4, 10.2.8, gcc-3.3, ac-2.59, am-1.6.3). Only problem
was lack of check for docbook-to-man; my patch is attachments 1-2.
Not so smooth on my imac (G3, 10.2.8, gcc-3.3, ac-2.52, am-1.6.1; that's what
came with the last 10.2-compatible dev tools). First problem: typo in
2004 Sep 10
1
Re: libFLAC internals
On Fri, 21 Feb 2003, Jason Lunz wrote:
> Try oprofile. It's more accurate than gprof, and it doesn't require you
> to recompile the source you're profiling.
That looks like a nice piece of software, but it appears to be specific to
Linux-x86, so I don't think it will be much help in profiling Altivec code.
:)
--
Brady Patterson (brady@spaceship.com)
Do you know Old
2004 Sep 10
3
Altivec, automake
I think I've gotten FLAC__lpc_restore_signal() about as good as I'm going to
get it.
Here's what I have:
-a new file, lpc_asm.s, which has the assembly routines
-changes to cpu.h, cpu.c, and stream_decoder.c to enable them
-changes to configure.in to support the new cpu stuff
-a preliminary Makefile.am
-maybe something else I'm forgetting
Now automake complains that configure.in
2004 Sep 10
4
Re: nice idea
Okay, I deleted most of this thread, so I was waiting for another message to
respond to, so unfortunately this will be out of place in the thread.
This is in response to Miroslav's idea about variable block sizes. I may be a
bit out of my league here as I'm just starting to look at how the actual
encoding gets done. But it seems to me that you could make a decent guess
about when
2004 Sep 10
1
libFLAC internals
On Fri, 21 Feb 2003, Miroslav Lichvar wrote:
> No, 1 <= order <= 32. There is -l option :).
Indeed. For some reason I decided to debug an optimized build, which for some
reason was showing order being off by a factor of 4. Thus it appeared that
order%4 == 0 in that case, when actually it wasn't. Needless to say I've
turned off optimization for the time being, which I should
2004 Sep 10
1
altivec lpc_restore_signal
I've had this a long time but haven't submitted it yet.
I've tried to mirror the ia32 setup, so there should be a new subdirectory
src/libFLAC/ppc . The first two attachments go there. The third is a context
diff for src/libFLAC/Makefile.am .
I have some more modified files, which I figured I'd submit after the above
are checked in and working for somebody other than me. If you
2004 Sep 10
2
FLAC/assert.h overwrites /usr/include/assert.h?
Let me pass this on to the dev group. I haven't seen this
but I never install to /usr. I would think that it should
still end up in /usr/include/FLAC/assert.h... maybe automake
is handling the file specially because of the name?
Josh
--- Kyle Sallee <cromwell@kublai.com> wrote:
> It's installation overwrites /usr/include/assert.h
> which is isntalled by glibc, thus causing
2004 Sep 10
2
[Flac-users] Quicktime plug-in?
Is there any quicktime plug-in being developed for flac, especially on a Mac? I've searched, but haven't been able to locate one. Also, are the mailing list archives searchable? If they are, how??
Thanks,
TJ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xiph.org/pipermail/flac/attachments/20030920/8b6be911/attachment.htm
2004 Sep 10
3
Re: nice idea
--- Miroslav Lichvar <lichvarm@phoenix.inf.upol.cz> wrote:
> On Thu, Oct 17, 2002 at 09:51:02AM -0500, Brady Patterson wrote:
> > ... But it seems to me that you could make a decent guess
> > about when something "new" happens based on the second derivative
> of the signal
> > (where the first derivative is the difference between a given
> sample and the