similar to: flac/metaflac 32/64 Universal OS X builds

In my experience, with the gcc compiler, cross-compiling is highly reliable. If your code runs on one processor, then it will run on all. Linking and such might be an issue, which you will discover immediately when the first person tries to run what you've built on their system. It still would be great to run these tests on all four. Actually, you should be able to test 32-bit

Brian Willoughby wrote: > In my experience, with the gcc compiler, cross-compiling is highly > reliable. Your experience doesn't match mine. > If your code runs on one processor, then it will run on > all. That can easily break down in all sort of places. For instance, I'm the main author of libsndfile and when Apple first announced Intel based machines I started

I guess I should add this to the long list of things Apple has broken that used to work well on NEXTSTEP (the operating system that has been turned into OS X). Now that you mention it, I remember having a problem getting flac to cross-compile in one build step, so I just did the manual lipo glue that you talked about. I assumed it was only because I was too lazy to figure out how to

Following up to some extent on Friday's discussion regarding the 'validation' of R, could I ask the list group's opinion on possible advantages of R over Splus from a pharma/devices perspective? I wish to exclude the obvious price difference, which doesn’t seem to carry as much weight as I would have thought. Besides, I have noticed many former Splus users gravitating towards R,

Dear list, I am trying to work out how the improveProb() function works and how to interpret the results, and I have a few questions. I would be grateful if anyone could shed some light on these. in the Net Reclassification Improvement section of the output, is the 2P column the two-sided p-value for the differences in classification? So if a limit is set at 0.05, then lower values indicate

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 @@

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

Hi Erik, I've noticed a couple small things missing in the metaflac man pages. Namely, the new sample rates provided by Earl Chew as well as the PICTURE block being a valid block type. Attached is a patch for metaflac.sgml and metaflac.1 that details the new sample rates metaflac's replaygain supports. Also, there is now the PICTURE block added as a valid block type. Thanks!

Erik, I don't know what abcde would be providing as tags, or why on Earth it would be importing that from stdin. Unfortunately, abcde is a bash script, and so not exactly easy for me to read. I haven't gotten any response from posting on their mailing list. I do get the same crash when running metaflac without the --import-tags-from, so I'm not sure this is the problem. Unless

Ooops? I accidently sent a reply privately instead of to the list, sorry for that. Here it is again, this time hopefully to the list: ---------- Forwarded message ---------- From: Johnny Rosenberg <gurus.knugum at gmail.com> Date: 2013/4/23 Subject: Re: [flac-dev] Metaflac UTF-8 fixes To: Janne Hyv?rinen <cse at sci.fi> 2013/4/23 Janne Hyv?rinen <cse at sci.fi>: > Hopefully

Hello all, I used metaflac to add replay-gain to a lot of flac-files. But with few of them metaflac exit and sais "Speicherzugriffsfehler" which I translate to "memory access error" or somethin like this. The problematic files has the same size like the other ones and I dont know why metaflac has a problem with them. I tested them with flac and the files seems to be ok. I use

Hi FLAC list! I have a question (maybe a strange one) about getting the compression level (0-8) using metaflac. So I want to know for a given FLAC file what compression level was used to compress that file. I tried using the --list option but this doesn't give any information about this. Is there a way to get the compression level of a given FLAC file using metaflac or another tool? thx

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

Hi, I realize that this is not strictly flac-related, but... I've got my collection in flac now, and at the end of the endeavor, I realized that (I think...) I've managed to have a few different encodings in the tags, one way or another. For instance: [root@localhost Zen Arcade]# metaflac --list 01-Something\ I\ Learned\ Today.flac > 1 [root@localhost Zen Arcade]# metaflac

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

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: >

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