similar to: metaflac Help

While I'm playing around with it, I'd like to ask about something I've noticed. Sometimes when I use metaflac to add tags, it performs it's operation instantly in a split second. Other times the same command causes lot of HDD I/O's and I can see it create a "filename.flac.metadata_edit" temp file. For example - I just added tags to a 25MB file and it took 15 seconds

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

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.

When I run it (OS X 10.6.2), find builds a list across multiple directories and then runs metaflac, causing metaflac to report. "The FLAC file could not be opened. Most likely the file does not exist or is not readable." I would think this is the expected result as " {} + " is the same as -execdir, except that ``{}'' is replaced with as many pathnames as possible for

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:

Level 1 uses far less compression than level 8. In terms of compression, the lower the "level" the less compression used (and the larger the resulting FLAC file). Hope that helps. -Brad On 7/12/07, Rick <cms0009@gmail.com> wrote: > > I try to make it easier for you to understand, > I do understand about lossless format, hence I installed flac, > second,

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

>The use of R128 also raises the question about "REPLAYGAIN_REFERENCE_LOUDNESS" >tag. Currently flac/metaflac writes "REPLAYGAIN_REFERENCE_LOUDNESS=89.0 dB" >but doesn't use it when decoding (it seems that nothing uses this tag). >R128 defines reference level differently, so this tag makes little sense for >it. IMHO it's better not to write this tag when

As far as I know, R128 as ReplayGain isn't really considered final yet (see http://wiki.hydrogenaud.io/index.php?title=ReplayGain_2.0_specification for example), so it would probably be a bit early to update this in the FLAC source. op 16-06-14 10:15, Olav Sunde schreef: > I mention metaflac because there are a few shell scripts that > use it to write RG tags in a flac music

On Dec 05 20:16:47, hans at stare.cz wrote: > This is 1.3.1 on OpenBSD/amd64. > The --no-utf8-convert option of metaflac(1) does not work for me: > > $ metaflac --no-utf8-convert --set-tag="Artist=?ou?l??ek" aladin.flac > aladin.flac: ERROR: tag value for 'Artist' is not valid UTF-8 > (You probably can't see the Czech letters properly in my mail, > but

Please help me solve the following problem: FLAC tools have a lots of warnings about non-subset files during encoding, but unfortunately don't have easy way to check/test existing FLAC stream for subset compliance. "flac -a" generates the big text file that has data about each frame and subframe. But looks like I need parser and statistics tools to answer on question about subset

On Mon, Dec 1, 2014 at 11:55 PM, Waitman Gobble <gobble.wa at gmail.com> wrote: > > > On Mon, Dec 1, 2014 at 10:40 PM, ???? ?????? <bart.gopnik at gmail.com> > wrote: > >> Please help me solve the following problem: >> >> FLAC tools have a lots of warnings about non-subset files during >> encoding, but unfortunately don't have easy way to

It would really be better to compare against sizeof(application_id) rather than coupling to all these instances of 4 all over the place. ________________________________ From: Erik de Castro Lopo <mle+la at mega-nerd.com> To: flac-dev at xiph.org Sent: Thursday, April 5, 2012 4:02:10 AM Subject: Re: [flac-dev] [PATCH] Fix buffer overflow in metaflac Cristian Rodr?guez wrote: >

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 hi all, i have several flac files which have their comment tag filled up with... comments, as well as the other tags filled in with relevant information. and then i have some similar flac files, resulting from some audio processing on the original flac files, in a subdirectory, S, for example. i am using metaflac 1.2.1-1.2 on ubuntu 9.04 and i am

What difference does it make? Harry Sack wrote: > Why isn't the compression level added in a metadata block by the flac > encoder itself (just like the encoder version)? In this way all programs > that read the file can see what compression level was used. > > thx > > 2007/7/4, Scot Thompson <scot.thompson@cox.net>: >> >> This has been asked many

The compression level is really only just a convenient shortcut for humans to use when creating a flac file. The real values used during compression include Max LPC order, blocksize, Rice partition order (min,)max, exhaustive model search flag, and mid-side or Adaptive mid- side coding flags. As you can see, there are a lot of parameters and options, to the compression level just

I just diffed metaflac 1.1.2 vs. 1.1.4 and I don't see anything that would cause that. did you build binaries yourself or did you get them from cygwin? --- Dat Head <dathead2@gmail.com> wrote: > 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

Olav Sunde wrote: > has anyone looked at adding R128gain code to metaflac so we can select > to use this calculation for RP tags rather than replay gain? Why metaflac only? flac is also able to calculate RG values. And, as far as I can see R128GAIN (http://r128gain.sourceforge.net/) is a standalone app, not a library. So probably it would be difficult to reuse its code in flac/metaflac.

Brian Willoughby wrote: > Jan Stary wrote: >>> This is 1.3.1 on OpenBSD/amd64. >>> The --no-utf8-convert option of metaflac(1) does not work for me: ... >> The problem seems to be in >> src/metaflac/operations_shorthand_vorbiscomment.c >> in the set_vc_field() function. > By the way, I've never used FLAC inside Ogg Vorbis. > Instead, I use pure