similar to: [PATCH] Add missing options to flac man page.

--- doc/html/documentation_tools_flac.html | 8 +++++--- doc/html/ru/documentation.html | 2 +- man/flac.1 | 6 ++++-- man/flac.sgml | 5 +++-- src/flac/main.c | 4 +++- 5 files changed, 16 insertions(+), 9 deletions(-) diff --git a/doc/html/documentation_tools_flac.html b/doc/html/documentation_tools_flac.html

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*

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

For some reason all documentation lists the max rice partition order to be 16, while the maximum is 15. This fixes flac -H, the man page and the HTML source code documentation --- doc/html/documentation_tools_flac.html | 2 +- man/flac.1 | 8 ++++---- man/flac.sgml | 8 ++++---- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git

On Sat, Nov 29, 2008 at 2:20 PM, Josh Coalson <xflac at yahoo.com> wrote: > --- Martin Leese <martin.leese at stanfordalumni.org> wrote: >> Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: >> ... >> > Whats more, the sndfile-convert program can also convert >> > from FLAC to the following file formats that support 63 bit >> > file

RF64 support sure would be nice, but it wouldn't really help to do this "instead of" CAF. For one thing, Logic Studio Pro does not seem to support RF64, because the manual states that WAVE and BWF are limited to 4 GB. CAF may be a format which lacks universal support, but RF64 is also very limited in usefulness. Treating either one as a substitute for the other is not

Hi Josh, Here are all the patches that are currently applied to the Debian packages for flac. You may disagree with some of them but as the current maintainer, I'm submitting them all for your consideration. (I should've submitted them earlier, but I've been quite busy. Sorry!) Here is a listing of the patches that I'll be sending: Patch 1 fixes a simple typo in metaflac

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/attachments/20130313/6c5c1f45/attachment.bin

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

The packaging/lsb/rsync.spec file is broken as shipped: It has a "Sept" month (rpmbuild here takes only 3-letter month names), and RH gzips the manpages, so the %files list can't find them. I also added doc/README-SGML and doc/rsync.sgml to the %doc files. Patch follows. Thanks for all the good work! --- rsync-2.5.6/packaging/lsb/rsync.spec.orig 2003-01-28 06:28:35.000000000 +0100

Folks, Samba version 2.0.5a, as shipped with RedHat Linux 6.1. There may be an obvious answer to the problem I am facing, but no matter how many times I leave it and come back to it, I'm still unable to see what I'm doing wrong. Please can anyone help? I'm trying to Here's the problem. I have reason to want a directory tree to be writable by virtue of the GID of users

I have help files in several formats. Up until now I have converted nroff files to S-Plus 6 sgml and html files using Splus doc_to_S ... (creates .sgml file) Splus HINSTALL ... (creates .sgm and .html files) I maintain master help files in R .Rd files, and for some of my functions converting from .Rd to .sgm using R CMD Rdconv --type=Ssgm ... produces better .sgm files than beginning with

Hi I am running the following code: sym <- c(sym1,sym2,sym4) lifedxm <- c("O-BD","O-WELL","O-UNI") life <- c(lifedxm,lifedxm,lifedxm) tp <- c("TP-ANY","TP-ANY", "TP-ANY", "TP-SUB", "TP-SUB", "TP-SUB", "TP-CLIN" , "TP-CLIN", "TP-CLIN") data <-

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- I made the assumption that showing the address is generally useful. Worst case, it won't make sense but still be displayed. Seems simpler than special-casing things. drivers/gpu/drm/nouveau/core/engine/graph/nv50.c | 117 ++++++++++++----------- 1 file changed, 63 insertions(+), 54 deletions(-) diff --git

HI, I am testing several models about three latent constructs that measure risk attitudes. Two models with different structure obtained identical of fit measures from chisqure to BIC. Model1 assumes three factors are correlated with each other and model two assumes a higher order factor exist and three factors related to this higher factor instead of to each other. Model1: model.one

Hello all, Help me please do mirror of freebsd.org. I got *.sgml through CVSup, installed textproc/docproj. But when I typed make: [root@xxx /www/freebsd/]make ===> en ===> en/security ===> en/commercial ===> en/docproj ===> en/news ===> en/news/1993 ===> en/news/1996 ===> en/news/1997 ===> en/news/1998 ===> en/news/1999 ===> en/news/2000 ===> en/news/2001

Further to the discussion between Murray Jorgensen and Brian Ripley, it seems to me better to choose tabulations that will not come and bite you. Suppose your data are sligtly irregular, e.g. (for the sake of the argument): data( warpbreaks ) warpbreaks$variant <- rep( 1:5, len=54 ) attach( warpbreaks ) tb <- table( wool, tension, variant ) tb # in this case you would like to see: tp

Further to the discussion between Murray Jorgensen and Brian Ripley, it seems to me better to choose tabulations that will not come and bite you. Suppose your data are sligtly irregular, e.g. (for the sake of the argument): data( warpbreaks ) warpbreaks$variant <- rep( 1:5, len=54 ) attach( warpbreaks ) tb <- table( wool, tension, variant ) tb # in this case you would like to see: tp

I have a package that will have an sgml file. One of the demos in ./demo will use it. Where should I put it? I tried putting it in ./demo but it did not survive the build so currently I put it in ./inst and it gets copied to the same level as the DESCRIPTION file and the demo gets it from there. Is that right or is there a better choice? I assume I can't use ./data since its not in the

Dear R fellows, Assume I define a <- expression(fn+tp) sen <- expression(tp/a) Now I'd like to know, which variables are necessary for calculating sen all.vars(sen) This results in a vector c(tp,a). But I'd like all.vars to evaluate the sen-object down to the ground level, which would result in a vector c(tp,fn) (because a was defined as fn+tp). In other words, I'd like