search for: nu774

...y fseeko64() and ftello64() available). 3. stat()/fstat() must be also taken care of, when it is used to get file size. 4. In some place, size of off_t is checked to see if FLAC binary is compiled with large file support. These also need modification. I have made a fork on https://github.com/nu774/FLAC including these patches, but it's not tested enough. Erik already knows at least off_t issue, and he said he'd like to fix it in the future. It needs many lines of change (although it basically is a trivial replacement).

(2013/03/05 12:27), Cristian Rodr?guez wrote: > Nothing against you code, that's ugly ..but as it is a first step it can > be forgiven :-) > > I will just force flac to be built with 64 bit file offsets and just > reject any caller trying to include/link libflac into a non-lfs program > like > > http://ac-archive.sourceforge.net/largefile/off_t_headers.html > >

On 03/04/2013 10:57 PM, nu774 wrote: >> This is an older issue reported in 2007: >> http://lists.xiph.org/pipermail/flac-dev/2007-September/002423.html >> >> The fix would be to use _ftelli64 instead of ftell with Visual Studio. >> http://msdn.microsoft.com/en-us/library/0ys3hc0b%28v=vs.110%29.aspx...

Hi, This patch addresses the following issue: [Problem] MinGW build of flac command fails to parse piped WAV input with WAVEFORMATEXTENSIBLE format. [Description] This is because MinGW fseeko() doesn't return error for the attempt to seek on non seekable file (same behavior as MSVC). The simplest solution would be to change #ifdef _MSC_VER to #ifdef _WIN32 here. Instead, this patch tests

(2013/03/05 7:19), Erik de Castro Lopo wrote: > Err, thats a link to a post talking about flac's WAV reader being limited > to 4Gig files. Problem is, *all* WAV files greater than 4Gig are mal-formed. > Due to limitations in the way WAV files are specified, no valid WAV file > can ever be over 4Gig. That's not an issue. FLAC frontend already has a --ignore-chunk-sizes switch,

On Mar 4, 2013, at 20:03, nu774 wrote: > (2013/03/05 12:27), Cristian Rodr?guez wrote: >> Nothing against you code, that's ugly ..but as it is a first step >> it can >> be forgiven :-) >> >> I will just force flac to be built with 64 bit file offsets and just >> reject any caller tryin...

On 04-03-13 23:19, Erik de Castro Lopo wrote: > Link please? http://www.hydrogenaudio.org/forums/index.php?showtopic=99757 > Err, thats a link to a post talking about flac's WAV reader being limited > to 4Gig files. Problem is, *all* WAV files greater than 4Gig are mal-formed. > Due to limitations in the way WAV files are specified, no valid WAV file > can ever be over 4Gig.

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