There is a thread over on Hydrogen Audio forums:
http://www.hydrogenaudio.org/forums/index.php?showtopic=99757
I will answer what I can here.
> mudlord says :
> As usual, Fidel Castro Loco ignored Windows.
Wrong. As the git logs show, I have commited a bunch of windows
specific fixes myself as well as commiting windows fixes by others.
> zfox
> My own Linux build could not decode 1 file out of 4 that were tested. It
ended with an error:
>
> 03.flac: ERROR while decoding data
> state = FLAC__STREAM_DECODER_END_OF_STREAM
I would like more information about this. Specifically I would need to
see a WAV or AIFF file encoded with flac-1.2.1 that doesn't decode
correctly with 1.3.0*.
> Case says:
> Compiling it with MSVC required some modifications and I'm unhappy to
> see that it still can't encode larger than 2 GB files.
a) Still working on MSVC, thanks especially to Ben Allison.
b) This is not the case. The --ignore-chunk-sizes option was added in
this commit:
commit 5967f4981ec6ed719ca391165b4209bd2be354dd
Author: Josh Coalson <jcoalson at users.sourceforce.net>
Date: Sat Jul 7 05:50:58 2007 +0000
and I added documentation and --help output just today.
> ktf said:
> No unicode support for Windows either.
Somebody that knows about windows unicode needs to work on this and
supply a patch. I'm happy to help out with guidance and testing.
> C.R.Helmrich said:
> OK, so aside from the vendor string, will 1.3.0 produce exactly the
> same FLAC bit-streams as 1.2.1?
Yes, feature, not bug.
> I'm just wondering whether 7- and 8-channel support is the only new
> feature for end users like me.
Yes, pretty much. Oh, and support for 64 bit windows which did not
exist when flac 1.2.1 was released.
Finally, there was also some discussion about compression rate. Neglecting
the minor change in files sizes due to the difference between "1.2.1"
and
"1.0.3pre1" there should be no difference in compression ratio or bit
streams.
Erik
--
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/
I would be willing to add Windows Unicode support (and large file mode) to the flac binary tool, but frankly I'm not sure that it could be done as a single cross-platform source file. There would be a significant amount of either Windows API function calls or MSVC-specific extensions to the C library (like _wfopen). It would quickly devolve into an #ifdef _MSC_VER mess.>> ktf said: >> No unicode support for Windows either. > > Somebody that knows about windows unicode needs to work on this and > supply a patch. I'm happy to help out with guidance and testing.
Take a look at how the Opus Tools package handles it. So far as I remember, it requires minimal changes to the file(s) containing references to the main entry point and to fopen. It imports the command line arguments as wchar_t and converts them to UTF-8, and has replacement functions for fopen and some text output that accept UTF-8 instead of ANSI. I think it automatically kicks in on definition of WIN32, or something like that. Worth a look, at least as a base implementation. On Tue, 5 Mar 2013 11:39:19 -0500 "Ben Allison" <benski at winamp.com> wrote:> I would be willing to add Windows Unicode support (and large file > mode) to the flac binary tool, but frankly I'm not sure that it could > be done as a single cross-platform source file. There would be a > significant amount of either Windows API function calls or > MSVC-specific extensions to the C library (like _wfopen). It would > quickly devolve into an #ifdef _MSC_VER mess. > > >> ktf said: > >> No unicode support for Windows either. > > > > Somebody that knows about windows unicode needs to work on this and > > supply a patch. I'm happy to help out with guidance and testing. > > _______________________________________________ > flac-dev mailing list > flac-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/flac-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05.03.2013 20:39, Ben Allison wrote:> I would be willing to add Windows Unicode support (and large file > mode) to the flac binary tool, but frankly I'm not sure that it > could be done as a single cross-platform source file. There would > be a significant amount of either Windows API function calls or > MSVC-specific extensions to the C library (like _wfopen). It > would quickly devolve into an #ifdef _MSC_VER mess. > >>> ktf said: No unicode support for Windows either. >> >> Somebody that knows about windows unicode needs to work on this >> and supply a patch. I'm happy to help out with guidance and >> testing.I've sent a utf-8 support patch to flac-dev, but it didn't arrive. The patch file is around 64k, so i believe that this is the problem. Maybe i should compress it? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRNpnRAAoJEOs4Jb6SI2CwwtMH/jpumjH6RoUsn+AuTUXo8lVO aky7VPjgt1NqWAhPWhn0REcQ70woIVesPBm3EdivQPIAzuEkLIBBiyLphMAOIbFM iiyo2SL5IhXvCuWtzzMFqdg5sYN/WKo5cX8XSFfkiWWq9LwwlHGrQ72HShMLW3nV pWNtr+Ob8sU/XOCPMn5SyDuw+AfxzRueV1TId6oSULSthE2HdUedudpFpyAyH0sn k5rLOSyYqJbhsGlVwHTeYf+yS9jza/KIc1t6+ExzvlUYqPd8vcHciq73S8PTR1O8 gMoK+IkIh+Ho6cYL82v5hk9xp94As3lKvBnuBtv2Bk2wtHebRoMGAPOLHzXfEeE=6ALy -----END PGP SIGNATURE-----