similar to: While I'm Thinking About metaflac...

Thanks Graue. That makes sense. Like I said - it's not causing a problem, I was just curious what it was doing. -Brad On 4/15/07, Graue <graue@oceanbase.org> wrote: > > "Brad Leblanc" <brad.leblanc@gmail.com> wrote: > > > While I'm playing around with it, I'd like to ask about something I've > > noticed. > > > > Sometimes

Pleas learn how to snip uneeded text from your posts. Version 1.2.0 is a stable release, which had some earlier beta revisions. I'd say it was quite well tested. Furthermore, there's no upgrade risk, as the API is still compatible. FLAC is backwards and forwards compatible. -Ivo

Josh Coalson <xflac@yahoo.com> wrote: > --- Scott F <graue@oceanbase.org> wrote: > > > If I use flac to encode with the --replay-gain > > option, I get a warning about the --no-padding > > option... > > > > "NOTE: --replay-gain may leave a small PADDING block even with > > --no-padding" > > > > ...even though I'm

If I use flac to encode with the --replay-gain option, I get a warning about the --no-padding option... "NOTE: --replay-gain may leave a small PADDING block even with --no-padding" ...even though I'm not using --no-padding. And the file does end up with a small padding block, so changing tags is slow. I'd fixed this bug in my own copy of flac 1.1.4, but forgot to submit the

Hello FLAC fans, I was wondering if anyone had any suggestions for tagging a large volume of FLAC's (in Windows) without filling them out by hand. I know metaflac can do stuff like this. Can someone help me with the syntax to do this? For example, I tried: ============= E:\Music\Folder>metaflac --import-tags-from=E:\Music\tag.txt *.flac *.flac: ERROR: reading metadata, status =

Quick question - if I use 1.1.4 to encode some files and send them to a friend who is using 1.1.2 - is it possible he won't be able to decode them? Having some trouble with this, wondering if the above could be related. Thanks, - Brad -------------- next part -------------- An HTML attachment was scrubbed... URL:

Howdy, Flac-1.1.4 is refusing to encode some WAV files (amd64, gentoo): % flac Song\ Name-Track01.wav Song Name-Track01.wav: WARNING: legacy WAVE file has format type 1 but bits-per-sample=24 Song Name-Track01.wav: 100% complete, ratio=0.546Song Name-Track01.wav: ERROR during read of data pad byte % sfinfo Song\ Name-Track01.wav File Name Song Name-Track01.wav File Format Microsoft RIFF

hmm... your cut-and-paste looks like ascii, but is the cuesheet in utf-8? --- Ariel Arelovich <aarelovich@gmail.com> wrote: > Hollo I'm new, My name is Ariel Arelovich > > I've encountered the following problem trying to sue metaflac. I used > the > following command: > > c:\Archivos de programa\FLAC>metaflac >

Hollo I'm new, My name is Ariel Arelovich I've encountered the following problem trying to sue metaflac. I used the following command: c:\Archivos de programa\FLAC>metaflac --set-tag-from-file="CUESHEET=sola.cue" so la.flac sola.flac: ERROR: file 'sola.cue' for 'CUESHEET' tag value has embedded NULs And I've got that error. See I have the flac that is

In 1.6.0, when creating a MDT, you could specify multiple --mgsnode options and it would failover between them. 1.6.3 only seems to take the last one and --mgsnode=192.168.1.252 at o2ib:192.168.1.253 at o2ib doesn''t seem to failover to the other node. Any ideas how to get around this? Robert Robert LeBlanc College of Life Sciences Computer Support Brigham Young University leblanc at

Hi all, I added -Wmissing-prototypes -Wstrict-prototypes to the CFLAGS and found that there were a number warnings generated. The patch below fixes those warnings and adds the two -W flags to configure.in. Cheers, Erik ----------------------8<----------------------8<---------------------- --- src/metaflac/operations_shorthand.h 1970-01-01 00:00:00 +0000 +++

Hello, This is really a user question, but I couldn't find the speex-user list (i.e., there wasn't one) so I hope posting it here will be okay. So, one day I was browsing around the Ogg site, already a fan of Vorbis and FLAC, and I came across Speex. Hey, this looks cool, I said. So I played around with it by encoding various voice recordings, and was quite pleased with the results. But

Anybody made OpenSSH work on a SPARC machine yet? I managed to get OpenSSL to compile correctly, via a patch to fix the location of perl (on RPM based systems, it will almost always be in /usr/bin/perl, not in /usr/local/bin/perl), and a small patch to the spec file to allow for SPARC builds. That RPM is built and installed without any errors that I can detect. OpenSSH is failing during a key

I've looked around and can't find the answer. We have a Samba file server joined to our Active Directory and using ACLs. We are enforcing quotas on this machine, but when specifying the home directory, the directory is owned by the person who created it. Using Windows and going into the security permissions, there doesn't seem to be a way to remove the owning user/group. When you hit

wow, that was a mighty keen eye - you must really have been looking at it (thanx!) - that is just a typo, the example just above and below that line still show that the issue i'm having exists. an easy test anyone can do is: metaflac --version metaflac --show-sample-rate c:/any.flac metaflac --show-sample-rate /cygdrive/c/any.flac On Dec 13, 2007 5:43 PM, Christopher Brown

ever since going from flac 1.1.2 to 1.1.4 on cygwin I've encountered an issue where I can't use metaflac on certain path specifications (see examples below). I tried again with 1.2.1 and it still doesn't work (I can't recall but I think it is from the cygwin dist, not the windows installed version) not sure if this is a flac issue, or a cygwin one, but thougt i'ld start here.

Using metaflac (1.0.3) like this: metaflac file.flac --set-vc-field=title=test??????e? The vorbiscomment will not be UTF8-encoded, instead they will be stored directly as ANSI. When trying to add some more comment, it gave the following error: ERROR: writing FLAC file file.flac, error = FLAC__METADATA_CHAIN_STATUS_OK Does that mean that weren't enough room for the comments? But

strlen() returns the length excluding the terminating null byte..then an string of len 4 will be off-by-one in application_id[4]; GCC 4.7 detects this bug. --- src/metaflac/options.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/metaflac/options.c b/src/metaflac/options.c index eb3498d..2cb0959 100644 --- a/src/metaflac/options.c +++ b/src/metaflac/options.c @@

Is terir any known problem with this? Can someone let me know if they are movingp and Solrais with rsync.

Hello Jan, I assume the problem is that metaflac has no way of knowing the encoding that was provided on the command line, since it could literally be anything. The --no-utf8-convert option means that metaflac does nothing to the letters as they pass through, and then the problem becomes that the next program to read the tags has to assume the character set without any information. If the program