search for: wave64

Here's a patch that fixes WAVE64 format handling. GUID had one word incorrectly in little endian order. -------------- next part -------------- A non-text attachment was scrubbed... Name: fix_wave64.zip Type: application/x-zip-compressed Size: 2261 bytes Desc: not available Url : http://lists.xiph.org/pipermail/flac-dev/attachmen...

Our DAW REAPER (www.reaper.fm) supports W64 as well. We'd be happy to share our W64 reading/writing implementations if someone wishes to integrate them into flac... -Justin Chris Cantwell wrote: > > 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

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

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

...input AIFF is auto-detected. +.TP +\fB--force-rf64-format\fR +Force the decoder to output RF64 format. This option is not needed if the output filename (as set by -o) ends with \fI\&.rf64\fR\&. Also, this option has no effect when encoding since input RF64 is auto-detected. +.TP +\fB--force-wave64-format\fR +Force the decoder to output Wave64 format. This option is not needed if the output filename (as set by -o) ends with \fI\&.w64\fR\&. Also, this option has no effect when encoding since input Wave64 is auto-detected. .SS "NEGATIVE OPTIONS" .TP \fB--no-adaptive-mid-sid...

...ain about an unexpected end-of-file. If the size given is less, samples will be truncated. .TP \fB--force-raw-format\fR Force input (when encoding) or output (when decoding) to be treated as raw samples (even if filename ends in \fI\&.wav\fR). @@ -300,6 +300,8 @@ Force the decoder to output Wave64 format. This option is not needed if the out .TP \fB--no-adaptive-mid-side\fR .TP +\fB--no-cued-seekpoints\fR +.TP \fB--no-decode-through-errors\fR .TP \fB--no-delete-input-file\fR @@ -320,7 +322,7 @@ Force the decoder to output Wave64 format. This option is not needed if the out .TP \fB-...

Hi all, Here are two patches, one for flac.git and one for flac-website.git, which 'merges' them. This is mainly some cleanup work I did earlier on the website that were copied to the html docs, and documentation on new features (like Wave64 and RF64 support, --preserve-modtime etc.) that were copied the other way. *flac.git patch* http://www.audiograaf.nl/misc_stuff/0001-Various-documentation-fixes-merge-with-website.patch *flac-website.git patch* http://www.audiograaf.nl/misc_stuff/0001-Various-documentation-fixes-merge-with-html...

Brian Willoughby <brianw at sounds.wa.com> wrote: > Hello all, > > Is anyone here potentially up to the task of adding support for CAF > (the CoreAudio Format) into the flac command-line? ... > I've already made some recordings > that are so long that they cannot be uncompressed from FLAC to WAV or > AIFF because they would exceed 4 GB - the maximum file size for

...>> > Au, Caf, rf64, w64 >> >> I am glad somebody mentioned RF64. >> Supporting RF64 instead of CAF would solve >> Brian's problem equally well, and would be the >> natural extension to supporting WAVE. > > BTW current flac in CVS supports RF64 and wave64; they will be > in the next release. I'll have to look into CAF. Core Audio Format (CAF) is from Apple, visit: http://developer.apple.com/documentation/MusicAudio/CoreAudio-date.html I have never tried to code CAF, but my guess is that it will be a lot more work than the successors to WAV...

>> used it forever anyways and haven't seen a commit since January nor >> a release since 2007... > what's queued up for the next release, see http://flac.cvs.sourceforge.net/viewvc/*checkout*/flac/flac/doc/html/changelog.html Hmm interesting, so given the above timeframes, should one presume that cvs head is indeed stable/release quality and that it's an ok thing to

...r file functions. That means printed texts and tags that contain non-ascii characters will be broken, but it is fixable if these changes are acceptable. I compiled a test binary with MSVC 2012 and uploaded it to http://www.saunalahti.fi/~cse/temp/flac-1.3pre2-mod.zip. This compile includes the Wave64 fix. -------------- next part -------------- A non-text attachment was scrubbed... Name: win32_unicode.zip Type: application/x-zip-compressed Size: 4216 bytes Desc: not available Url : http://lists.xiph.org/pipermail/flac-dev/attachments/20130317/313398c4/attachment.bin

...n order (0..16). min defaults to 0 if unspecified. Default is -r 5. +Set the [min,]max residual partition order (0..15). min defaults to 0 if unspecified. Default is -r 5. .SS "FORMAT OPTIONS" .TP \fB--endian={\fIbig\fB|\fIlittle\fB}\fR @@ -378,9 +378,9 @@ Force the decoder to output Wave64 format. This option is not needed if the out These flags can be used to invert the sense of the corresponding normal option. .SH "SEE ALSO" .PP -metaflac(1). +metaflac(1) .PP The programs are documented fully by HTML format documentation, available in \fI/usr/share/doc/libflac-doc/h...

On 12.12.2012, at 20:10, Ralph Giles wrote: > On 12-12-12 10:47 AM, Max Horn wrote: > >> If you point me to the sources of the site (is there a repos for it?), I'll be happy to provide a patch for this, too! > > The new site repo is https://git.xiph.org/flac-website.git Hum. Actually, I just noticed that the website is also in the flac repos itself, under doc/html/ The

Hi, I’ve been thinking about what the strategy to use for boolean values in GlobalISel. There are a few semantic and mechanical issues I’ve encountered. For background, on AMDGPU, there are two kinds of bool/s1 values. Contextually, a real boolean value will either be a 1-bit scalar condition (in a non-allocatable physical condition register, which will need to be copied to an allocatable class