linux encoder Options

[rudefyet]

I downloaded the source code from muspeack.net and compiled mppenc myself...

I've noticed that my compile encodes around 17x, whereas the precompiled versions on musepack.net only run about 15.5x

I was wondering what was different here, I didn't change anything in the Makefile, so why would they be different?

Is there any certain reason i should use the precompiled binary?

and also, I can't get mppdec to compile from source, it fails on wave_out.c every time

[NumLOCK]

I was wondering what was different here, I didn't change anything in the Makefile, so why would they be different?

You probably have a different gcc version...

Is there any certain reason i should use the precompiled binary?

Probably not.. since gcc is a quite reliable tool, so your mppenc should encode safely

[rudefyet]

thanks...i figured i was just being too paranoid

[Seed]

We kept the -ffast-math flag in the makefile and this is the reason your compile is faster. It is very likely to fail on teh_sample, though, and will cause other problems with other samples. Disable it. It will be removed from the makefile too.

[rjamorim]

Probably not..  since gcc is a quite reliable tool, so your mppenc should encode safely 

GCC is reliable indeed, but the MPPenc code doesn't seem to be.
http://www.hydrogenaudio.org/forums/index....howtopic=30758&

[ak]

-ffast-math is there, as it makes things run faster.
But parts of it, that appear to cause teh_sample artifacts, explicitely disabled in Makefile.

Besides musepack.net mppenc was built with -O1, as -O2 and up caused another problems.
But parts of -O2, that seem to be responsible, are also disabled in Makefile.

So in sum if you build it yourself, it's (hopefully) still safe enough.
Anyways you can always check by doing some encodes with musepack.net build and your compile and comparing the results.

[rudefyet]

I see...i will admit, i've heard a few artifacts in the songs i've encoded using --fast-math (although it could just be the fact i upgraded my audio hardware, it's much easier to abx between different bitrates now)

that was the exact flag that worried me in the Makefile

I think i'll stick with the official builds

I'll have to figure out the difference between the dynamicly and staticlly linked builds (i know its common *nix knowledge, but i've forgotten over the years)

This post has been edited by rudefyet: Feb 9 2005, 00:03

[xmixahlx]

a "static" compile includes - within the executable - the linked libraries that a "dynamic" compile depends on.


later