similar to: vorbiscomment, ogg123 charset bug - ticket #685

Here's a propsed heavy-duty solution for your UTF-8 problems. I'm including a patch in this message, but I'll put the new files on my web site at http://rano.org/tmp/xiph_files.tar.gz I've tested this by running vorbiscomment with and without -DHAVE_ICONV=1 in vorbis-tools/share/Makefile. It seems to work. Changed files: acinclude.m4: Add a test for nl_langinfo(CODESET). This

I got the following compile error in R-1.9.0 on NetBSD 1.5: <-- snip --> ... gcc -I../../src/extra/zlib -I../../src/extra/bzip2 -I../../src/extra/pcre -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -O2 -mcpu=v8 -c main.c -o main.o main.c: In function `setup_Rmainloop': main.c:463: `CODESET' undeclared (first use in this function)

Hello Some time ago I posted a lil' patch to this list which adds milliseconds display of playlength to ogginfo. Some folks replied that it's plausible and this patch will be merged to the next version. Vorbistools-1.0.1 got out and the patch is not in it. Why? Anyway, here's this patch for vorbistools-1.0.1. I hope this time you will include it, because milliseconds support is

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

On Thu, 2015-05-14 at 22:45 +0200, Stephan Seitz wrote: > On Wed, May 13, 2015 at 11:57:55AM -0400, Konrad Rzeszutek Wilk wrote: > >> > according to the documentation the option ucode=scan should tell XEN to > >> > look for a microcode update in an uncompressed initrd. > >> > > >> > While I don?t use the Debian kernel the tools to generate the

Hi, I have downloaded the latest stable version *1.0.2 opus audio codec* from the following link: http://www.opus-codec.org/downloads/ *Details of OS & CPU:* OS : Microsoft Windows XP CPU : intel core 2 Duo cpu I am using Microsoft visual C++ 2010 Express to build the codec (opus.vcxproj available in the package downloaded). I am able to build it & could generate the application

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

Hi, And thanks for flac. There's a minor problem when compiling flac: libtool warns about mixing up shared and static libraries. Typical messages are: *** Warning: Linking the shared library libxmms-flac.la against the *** static library ../../src/plugin_common/libplugin_common.a is not portable! *** Warning: Linking the shared library libxmms-flac.la against the *** static library

I think that vorbiscomment should really use -c "this=that" to specify tags on the commandline, consistent with oggenc. That displaces the tag source file, so I'd suggest -f, consistent with at least some other programs (although I can only think of tar, right now). I'd also suggest that it use -o for an output filename rather than splattering the second file on the

Hi all, I just committed some big changes to vcedit (the core of vorbiscomment, and also the core comment rewriting functionality used by a number of other programs (xmms, for instance). It's now able to handle several nasty cases that it couldn't before, but it may have new problems - so, everyone, go and throw nasty or broken input files at it, and see if it breaks. Please. And those

> While you are at it, can you check/fix the following warning > ? > > metadata.cpp:812:98: warning: narrowing conversion of > 'strlen(((const > char*)string))' from 'size_t {aka long unsigned int}' to > 'FLAC__uint32 > {aka unsigned int}' inside { } is ill-formed in C++11 > [-Wnarrowing] > > > Thanks ! Yeah sure! I don't get

Bastiaan Timmer wrote: > Attached is a patch that adds 5 missing Patch applied. Thanks. > Looking at the FLAC__metadata_object_cuesheet_* FLAC__metadata_ > object_picture_* functions, it looks like the corresponding FLAC++ > classes are already complete. Maybe some functions are missing from > CueSheet::Track. If nobody objects, I will take a look later this > week. Thanks.

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.

I have written up a z shell completion function for the Ogg Vorbis metadata editing program, vorbiscomment. It is attached, and available at http://netwood.net/usr/jessw/_vorbiscomment The Z shell is an alternative shell, with a very powerful completion system. I look forward to any suggestions, bug reports, etc. Feel free to include the file in the distribution, or link to it, as you

David K. Gasaway wrote: > Daniel Aleksandersen wrote: >> On Monday 17. September 2007 07:47:19 David K. Gasaway wrote: >>> Even today, I use my own "metadata format" -- essentially a superset of >>> vorbis comments. There is one file per release, even with a multi-disc >>> release. As a final part of the ripping process, I apply this metadata

Hi, I guess you already know this, but src/plugin_common/vorbiscomment.h is missing from the 1.0.4beta tarball. The best thing would be to release a new beta ASAP, thanks. -- G?tz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--

Hi, I guess you already know this, but src/plugin_common/vorbiscomment.h is missing from the 1.0.4beta tarball. The best thing would be to release a new beta ASAP, thanks. -- G?tz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--

" Ivo Emanuel Gon?alves " <justivo at gmail.com> wrote: ... > To be fair, only the Vorbis users requested albumart. FLAC users > should in theory be able to use the tag too if they want, but this > wouldn't be something we'd see in other codecs like Speex and Theora. This is a minor point, but FLAC users can already do this using METADATA_BLOCK_PICTURE (which

Some of these things may allready be addressed: Comments in oggfiles: (meaning the accutall keyword "comment(s)" With xmms you can edit oggtags, among artist and title you have "comment" * xmms creates comment attributes starting with "=" * freeamp does not seem to understand ogg-"comment" at all. * oggenc seems to like to put the comment as is without

First, the in the links section of www.vorbis.com is a link to http://www.vorbislinks.com/ which no longer a vorbis dedicated site (it's one of those general dns parking/general index). I don't know who's the webmaster, it is implied that's Simon Yorkston, but I'm not sure. Anyway, the real rason of this mail is that I'm ripping my CDs collection, and I'm taking a