similar to: 2GB limit?

Brian Willoughby wrote: > I do not see the need to jump to 64-bit merely to get beyond the 2 GB > limit. There are modern API that handle 32-bit unsigned file lengths > - i.e., up to 4 GB - without going to 64-bit. When we are talking about offset_t we are talking about the flac C and C++ API. Currently if we have a flac file with more than 2Gig samples it is not possible to seek

(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 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.

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. And most don't work over 2 GB. The solution we (Xiph) have used in other projects (opusenc,

> 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 That's not enough. At least, the followings are also needed. 1. Change off_t to something else. off_t can lead to ABI

Hi all, I was reading the discussion about this 1.3.0pre1 release on HydrogenAudio and someone linked an old thread in which one patched FLAC 1.2.1 to support WAV-files larger then 2GB. It might be worth investigating: http://www.hydrogenaudio.org/forums/?showtopic=84014#entry725304

(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,

I realize that it isn't much of an improvement, but AIFF supports 4GB recordings, and flac is compatible with this. Being an avid "taper" myself, I have, on many occasions recorded up to this limit, and I always back up my original recordings using flac. W64 support is more than welcome, but AIFF support gets you twice the length right away. Brian Willoughby Sound

Hello, I'm trying to set up a samba server for a friend who has a mac. He's running OSX, version 10.2. He's got some really big video editing files that are well in excess of 2gb. We're trying to back these up to the samba server, but it quits right around 2gb. That seems to be a magical number. This is with version 2.2.3 of Samba, and Linux-Mandrake 8.2, ext3 file system. I

On May 13, 2007, at 05:45, Harry Sack wrote: > If I encode 192 kHz sound @ 24 bit for some days (WAV file) and I > encode it to FLAC, I think you can have a very big file and 1.5 TB > is reached very quickly. > And in the future audio will even get bigger, when used for HD-DVD > en Blu-ray media and 5.1 channels is considered the 'minimum' > setting for surround

Hi, A bug I've had reported is that scp doesn't work with large files (Debian bug number 106809). The problem seems to be scp.c:504: if ((fd = open(name, O_RDONLY, 0)) < 0) Is there some reason why making that if ((fd = open(name, O_RDONLY|O_LARGEFILE, 0)) < 0) would break things? It seems a simple fix to me... Thanks, Matthew -- "At least you know where you are

Hi, I'm still waiting for my list subscription but if I don't send in this bug report now I won't for who-knows-how-long and I want to get it in.... I'm using 2.5.6 compiled from cvs on SCO Open Server 5.0.6 bothe machines are the same version of OS and the same copy of rsync. on my live machine one of the database files eventually got to be 2 gigs the file has since then been

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: -ff { raw | wav | aif } In some sense, "-ff" is silly since it probably stands for "format format". Still, I think it's better than just "-f", since the first

What possible factors can cause a 2 gig file size limit ? I've verified that the underlying filesystem can handle much larger files. I'm using the standard samba package from Debian testing, version is 2.2.3a-12. Please cc me on responses. Thanks in advance ! -- Josh Litherland (fauxpas@temp123.org) -------------- next part -------------- A non-text attachment was scrubbed... Name:

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 > > That's not enough. At least, the followings are also

Hi, I am attempting to use flac to encode 96k/24-bit broadcast wav (BWF) files. BWFs are wav files with some extra meta-data chunks, and is the favoured archival format for many institutions around the world. These files are encoded successfully by flac, however the resulting flac file is not playable on all flac players - it plays successfully in foobar2000 but is silent in winamp, and when

On 5/13/07, Brian Willoughby <brianw@sounds.wa.com> wrote: > If we ever reach this 64 GigaSample limit, the fact that FLAC is a > stream should allow multiple FLAC headers to be concatenated in a > single file - although that might be tricky. I believe you can do this with Ogg FLAC. The Ogg container manages the multiple FLAC streams. Theoretically, we'll never see limit

Hi all, Currently I'm looking for users of the --keep-foreign-metadata feature of FLAC. There has been some improvement of this feature in FLAC 1.4.0. Since 2007 there has been a warning in FLAC that --keep-foreign-metadata is a new feature. I think removal of this warning is long overdue, but there are still some issues surrounding it. So, if there are users of this feature on the mailing

I use Sony (previously Sonic Foundry) Sound Forge, which allows me to save audio files in .w64 (Wave 64) format to get around the 2GB .wav file limitation. W64 was invented by Sonic Foundry, and is an open format as far as I know. The only programs I know about using the .w64 format at the moment are Sound Forge and Steinberg Nuendo, although there may be others out there. With increasing

Hello, I'm on a Mac and I'm noticing that encoding via the flac command line is significantly slower with version 1.3.0 than 1.2.1. I'm encoding a 24/96 file to flac, both from wav and aiff and both formats are showing the same speed decrease when using 1.3.0. Also, 1.2.1 will not encode an aiff-c file, but 1.3.0 will. Is this change documented anywhere? Thanks, Scott --------------