similar to: vcedit/vorbiscomment heterogeneous streams

When I create a chained file with a mono and then a stereo substream, winamp crashes when it gets to the second stream. in_vorbis v1.16c. And when vcedit writes comments from a chained file, it only saves the first substream and throws subsequent streams away. Perhaps this is woth mentioning somewhere... Matthijs --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project

I've been looking at modifying vcedit so it will work on Ogg streams containing primarily Vorbis data (i.e. first page is the Vorbis header, most pages are Vorbis and a few are something else e.g. metadata or lyrics). I've managed to get something that works by: 1. During the header opening in vcedit_open push non-Vorbis pages onto a buffer added to vcedit_state and write them out after

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

Hi Jerry, I'd say the best would be to simply replace the #ifdef USE_SMALLFT by #ifdef USE_TI_FFT #include "ti_fft_wrapper.h" #elif defined(USE_SMALLFT) and have everything in the include file. There's no real point in overriding individual functions since they all go together. Also, make sure you wrap the FFT in the same way as I did with the fixed-point kissfft. For example,

I am in the process of dropping the TI DSP lib fft routines into the AEC. Currently, FFTWrap.c uses the USE_SMALLFT and USE_KISS_FFT to select between two packages of FFT routines. ] #ifdef USE_SMALLFT ... #elif defined(USE_KISS_FFT) ... #else #error No other FFT implemented #endif My guess is that every DSP and many other processors will have their own specific FFT and iFFT. What method

[Cc: changed to vorbis-dev] On 12/04/2008, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > On Fri, Apr 11, 2008 at 10:11 PM, Conrad Parker <conrad at metadecks.org> wrote: > > No, vorbiscomments are meant to be human-readable. > > > But I CAN read base64! :-) > It's a win-win situation, with the added bonus that it wouldn't > require

Hello, In one of my recent assignments, I was asked to develop a ogg player. I am not able to find the right repository of the source code. There are few repositories on vorbis but I am not clear which one is the right one for Windows environment. If somebody has successfully compiled any ogg player ever, his ideas will be helpful to me. In one of the code set, I was able to compile the

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

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

Hi I've a bug in vorbis-tools's libutf8 - some share/*.[ch] files don't include config.h; as a result, utf8.c:convert_set_charset doesn't try charset = nl_langinfo(CODESET) which would correctly return UTF-8, because HAVE_LANGINFO_CODESET isn't defined (it's defined in config.h, but config.h is not included). So, the bugfix is simple - just include config.h everywhere

" 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

Could someone please tell me what I'm doing wrong here? I have some oggs tagged using other applications and ogginfo doesn't give me any warnings when I use UTF-8 in them. I did the following: $ vorbiscomment --raw -a test.ogg -t "test=åäö" $ vorbiscomment --raw -l test.ogg test=åäö $ ogginfo -v test.ogg Processing file "test.ogg"... New logical stream (#1, serial: