Building was quite smooth, but I didn't use the makefile (don't know if I even could, I'm quite new to this). I just started CodeBlocks, added all needed files for the library to a project, set the compiler paths so it could find bswap.h and added an empty config.h. Setting up the project for flake was almost the same.

There was only one warning when building:flake\wav.c:473: warning: enumeration value 'WAV_SAMPLE_FMT_UNKNOWN' not handled in switch

That was already present with the gcc 3 I used before (can't remember the exact version)

Building was quite smooth, but I didn't use the makefile (don't know if I even could, I'm quite new to this). I just started CodeBlocks, added all needed files for the library to a project, set the compiler paths so it could find bswap.h and added an empty config.h. Setting up the project for flake was almost the same.

There was only one warning when building:flake\wav.c:473: warning: enumeration value 'WAV_SAMPLE_FMT_UNKNOWN' not handled in switch

That was already present with the gcc 3 I used before (can't remember the exact version)

Hmm. Are you not using ./configure + make because it doesn't work? If you have msys installed that's all that you should need to do.

QUOTE (Synthetic Soul @ Oct 3 2006, 05:33)

I haven't been able to compile using MinGW since rev 48. If I run ./configure I get:

/bin/cat: /tmp/flake-conf-10500-6548-17128.c: No such file or directorygcc is unable to create an executable file.

It still works with cygwin.

I don't need to compile, but I thought it worth pointing out, as it seems relevant at the moment.

That is odd. Can you compile/run a simple hello world program with your MinGW version?edit: looks like I was too slow. I'm glad it works for you now.

QUOTE (kjoonlee @ Oct 3 2006, 09:11)

Does flake use autotools? If yes, would a ./autogen.sh generate new ./configure* files?

No, I did not use autotools for Flake, nor do it ever intend to. I may decide to use some other build system, but it won't be autotools. make distclean + ./configure + make is all that should be necessary under MinGW.

Well, rev.19 of configure does, but none since, and that's not really much use is it?

I dunno. I don't really care! I just thought it may be of interest. It seems to me that something changed in version 50 that breaks configure with my versions (work and home) of MinGW (installed using MinGW 5.0.3 and MSYS 1.0.11). I would assume that this would be the same for others, but if not then, please, forget it. I've been expecting someone else to point this out, but as MedO was releasing versions I thought it was worth piping up.

Could you post or PM me the config.err you get using rev50? This would help me narrow-down which change caused the issue. That was quite a big change from r19 to r50. In retrospect, I probably should have broken it up into smaller commits.

The fact that it doesn't work does concern me, and it may be a simple fix. If I can't figure it out from your config.err output then I'll maybe give up on it.

Hmm. Are you not using ./configure + make because it doesn't work? If you have msys installed that's all that you should need to do.

I didn't install msys, no. I have never used it yet. I know ./configure -scripts from building Linux apps, but I never wrote one or used one under Windows. Hmm, if I have no problems compiling Flake without running ./configure first, does CodeBlocks do the necessary stuff that ./configure normally does?

Hmm. Are you not using ./configure + make because it doesn't work? If you have msys installed that's all that you should need to do.

I didn't install msys, no. I have never used it yet. I know ./configure -scripts from building Linux apps, but I never wrote one or used one under Windows. Hmm, if I have no problems compiling Flake without running ./configure first, does CodeBlocks do the necessary stuff that ./configure normally does?

As I said, I'm quite new to this.

For building binaries only, in Windows, with gcc/mingw...yes CodeBlocks probably does all that is necessary. For building a static library or building on other platforms, the configure script is useful because it tries to automatically detect information that is needed to compile and install. It can also detect system features so it can use compiler flags which will generate faster binaries. But, if you already know gcc well enough, you can just set the compiler flags yourself.

Current SVN version now supports multiple input files. So you can encode a whole directory of wav files with 1 command. It's as simple as running something such as:flake -8 *.wavorflake -12 file1.wav file2.wav file7.wav

This has not been tested in Windows, so I hope it works okay.

Now...no new features until the next release...for real this time. I'll work on documentation and testing (and my ac3 encoder) while I give Flake a little resting time for bugs to show themselves. The docs will take a bit of work, but at least it will be a nice change of pace.

you have #include <inttypes.h> at wav.h . just though i should point that out. just tried building it again with VC++ 2005 and it blew up on syntax errors. i'll try to rebuild it in the future with VC++ 2005 when i get interested in doing that again.

you have #include <inttypes.h> at wav.h . just though i should point that out. just tried building it again with VC++ 2005 and it blew up on syntax errors. i'll try to rebuild it in the future with VC++ 2005 when i get interested in doing that again.

Ah, oh. I see a problem. Does -12 take that much processing power or isnīt it 100% compatible to flac 1.1.2 decoding anymore?My Squeezebox canīt play flake -12 on all titles. It stutters around. Flake -5 for example is fine.

Edit:The compile Garf offered a while back works flawlessly on the Squeezebox and has higher compression already as standard 1.1.2.

Ah, oh. I see a problem. Does -12 take that much processing power or isnīt it 100% compatible to flac 1.1.2 decoding anymore?My Squeezebox canīt play flake -12 on all titles. It stutters around. Flake -5 for example is fine.

After Bukem's positive report, your one is the first negative one and is precisely what I feared.My own decoding tests done with foobar2000 and my old Duron revealed that -11 and -12 are considerably slower than all other modes and than official/Garf's encoder. From memory, it's ~x48 for flake high profile and a bit more than x60 for all other settings/encoders.As a consequence I expected from some devices with few 'power' headroom to have troubles decoding -q11/12 encodings.Could you also try with -q10 and -q11? I guess that the first one should be problem free and the latter to sutter as well as -q12.

After Bukem's positive report, your one is the first negative one and is precisely what I feared.My own decoding tests done with foobar2000 and my old Duron revealed that -11 and -12 are considerably slower than all other modes and than official/Garf's encoder. From memory, it's ~x48 for flake high profile and a bit more than x60 for all other settings/encoders.As a consequence I expected from some devices with few 'power' headroom to have troubles decoding -q11/12 encodings.Could you also try with -q10 and -q11? I guess that the first one should be problem free and the latter to sutter as well as -q12.

Exactly how you predicted. -10 still is playable. From -11 on it stutters.