similar to: metaflac --no-utf8-convert complains about UTF

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

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 that's beside the point.) Indeed, it is not valid UTF8 (it's LATIN2),

Martin Leese wrote: ... > Finally, Jan might have more luck taking his > problem with metatflac over to the flac-dev list. Even better, he could submit a bug report at: http://sourceforge.net/p/flac/bugs/ Regards, Martin -- Martin J Leese E-mail: martin.leese stanfordalumni.org Web: http://members.tripod.com/martin_leese/

Hopefully the last patch from me to UTF-8 issues. Metaflac can now print all console supported characters from tags on the screen. It also fixes metaflac to be able to import its own exports back without non-ascii characters getting mutilated. And --no-utf8-convert now works properly with import and export commands. I updated my Windows binary archive with these changes for any interested

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

Martijn van Beurden wrote: > Op 16-07-15 om 17:58 schreef lvqcl: >> But this text describes only those 4 bits in frame header. >> IMHO this sectoin should not describe WAVEFORMATEXTENSIBLE_CHANNEL_MASK, >> it should be described somewhere in vorbis comments section. > > I would propose: 0000-0111 : (number of independent channels)-1. > The channel order is defined

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

--- Mattias Dahlberg <mdati00@student.vxu.se> wrote: > 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. yes, metaflac is currently not doing utf-8 encoding. the same libutf8 from libvorbis is in the flac source tree but it's not

That's how I understand how flac.exe works with unicode under Windows: There's a flag win_utf8_io_codepage that is equal either to CP_ACP or to CP_UTF8. Initially it's equal to CP_ACP. Then flac.exe/metaflac.exe call get_utf8_argv() that do some things and sets win_utf8_io_codepage to CP_UTF8 on success. This is the only way to set this flag to CP_UTF8. The programs continue to work

Martin Leese wrote: > Just so it is clear in my own mind. > > You are offering to add support for extended > file attributes to flac, the command-line > wrapper around libFLAC to encode and > decode .flac files. Presumably such support > would reside in libFLAC, and so libFLAC++ > and metaflac should also be updated. (Not > sure whether the various music player input

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

lvqcl wrote: > Martin Leese wrote: >> Note that the channel order may not be defined. > > IMHO it doesn't matter in this place of documentation (which describes > default channel assignments for FLAC). Your proposed wording was: 0000-0111 : (number of independent channels)-1. The channel order follows SMPTE/ITU-R recommendations. The assignments are as follows: The

OK Martin. Thank you for the explanations and for your time. I am writing a program that reads and writes all existent Tags types. It lacks only to end the edition (rewriting) of "Native" Flac and Matroska. Both cases for the same problem: the separation of Tags and Picture in different blocks. In Flac I resolved it, but now I have to add METADATA_BLOCK_PICTURE. Reading Vorbis

On Wed, Jul 22, 2009 at 7:24 PM, Martin Leese<martin.leese at stanfordalumni.org> wrote: > Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > >> Martin Leese wrote: >>> Anyway, calling alloc()s with no corresponding >>> free()s is a memory leak. Not good code. >> >> The alloca() function allocates space on the stack and >> that

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

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

You said "With the exception of where to put a picture file, VorbisComments in a Vorbis stream are the same as VorbisComments in a FLAC stream." In METADATA_BLOCK_PICTURE case they would not be the same. Up to now we could exchange the complete block of VorbisComments. But with the addiction of METADATA_BLOCK_PICTURE doesn't happen this way. In Ogg files the METADATA_BLOCK_PICTURE

Small change to metaflac hexdump function. Changed so utf-8 decoding is only used for filename printing and changed hex output printing to not rely only on isprint. That function seems to return true for tabulator control character under Windows when application isn't using C-locale. At least it did so for all locales I tried (Finnish, German, English US). -------------- next part

On 24.4.2013 15:42, Erik de Castro Lopo wrote: > Janne Hyv?rinen wrote: > >> +#define PPR if(filename) if(raw) printf("%s:",filename); else flac_printf("%s:",filename); > Are you sure about that line? > > GCC complains about an ambiguous 'else'. It definitely needs some > curly braces somewhere there to make the intend explicit. > So it

Here's a patch that stops the flac binary from writing empty tag fields. At least in Windows world these come to files by accident. CD extraction programs pass all possible metadata entries they allow setting in the UI to flac binary and most of the time most fields are empty when basic info like artist, album, title, track number and release date are the only fields that are set.