similar to: vorbis-tools reorganziation and UTF-8 stuff

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

Some days ago i noticed in the ogg vorbis documentation that the comment-field contents should be encoded in UTF-8. A brilliant idea I think, sadly it seems like no one is using it. oggenc and vorbiscomment included in vorbis-tools writes strings to the comments fields blindly without any encoding conversion in violation of the spec. I intend to try to solve these problems to the best of my

Dear vorbis-dev lurkers, I bring you the first beta release of vorbis-tools 1.3.0. It has quite a few new features and the final version will have even more, so I am sure it is to everyone's benefit that it gets as much tested as possible so we can do a quick release. Here's the changelog so far: * Fixed an error in configure.ac; --with-speex/flac work again (#1319) * Corrected

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

Or rather - the ogg123 seems to run faster than the oggenc. Based on the vorbis toots 1.0_1,3 I've got (on freebsd) a small streaming server which essentially takes the oss/vox audion input; uses the code from oggenc to make a stream and then a bit of apache 2.0 to dole that stream out over TCP to various clients: setup oss /dev/dspW0.0 16 bit stereo 44k1. create ogg/vorbis

Hi every body , ( Please forgive my dumb poor english ) I got many tracks in ogg/vorbis format . I would like to make a "preview" of them . I mean : I have a track : foo.ogg ( wich is 3:00 minutes long ) i want to have : preview_foo.ogg ( wich is foo.ogg but from 1:00 -> 1:15 ) I read man oggdec , man ogg123 , man oggenc but i did not see what suits me . I use zsh shell , on a

--- vorbiscomment/vorbiscomment.1 | 4 +--- 1 files changed, 1 insertions(+), 3 deletions(-) diff --git a/vorbiscomment/vorbiscomment.1 b/vorbiscomment/vorbiscomment.1 index 0108e78..2bceb83 100644 --- a/vorbiscomment/vorbiscomment.1 +++ b/vorbiscomment/vorbiscomment.1 @@ -39,13 +39,11 @@ Reads, modifies, and appends Ogg Vorbis audio file metadata tags. .IP "-a, --append" Append

This works: oggenc -b 192 -a "Astral Projection" -l "In the Mix - CD1 (Sundown)" \ -t "Another World" -o "01-another_world-(floorplay_remix).ogg" \ -c "TRACKNUMBER=01" -c "TRACKCOMMENT=Floorplay_remix" \ 01-another_world-(floorplay_remix).wav But this doesn't: oggenc -b 192 -a "Astral Projection" -l "In

Ok, I managed to compile the Ogg and Vorbis libs. Then, after modifying the file audio_out.c as follows: original: #include <dlfcn.h> modified: #include <win32/include/dlfcn.h> I was able to (finally!) compile libao. Then I tried to compile the module vorbis-tools, but uninvited problems came to my party. [...] > /usr/bin/ld: multiple definitions of symbol _getopt >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 26.02.2012 14:18, Erik de Castro Lopo wrote: > I ... would appreciate reports of successful compiles (and even > more importantly any failures) on ... Windows ... > 1) I have to update automake version from 1.7 to 1.11. This might be fixable with installing automake-1.7 for mingw, but i haven't bothered with that, and i prefer 1.11

Hi All, For my new file (and thus mp3) server I've decided to switch completely to Ogg Vorbis. This means having to reencode ~30GB worth of 128Kb MP3's, but i figured that it would all be worth the effort. So I downloaded the sources for libogg, libvorbis and vorbis-tools and fired up my trusty old compiler. libogg and libvorbis built and installed like a charm. Not so for

Does anyone know if GCC 2.95.2 compiles a broken oggenc? My .ogg files sound like they're being played by a CD player stuck on fast- forward. . . . And I wonder what the solution is. Philippe (YellowDogLinux 1.2.1 (a Red Hat 6.2 derivative) on an iMac) -- --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from

I have got libao up to oggenc and ogg123 working on Mac OS X Public Beta now. I'd like to submit patches, but last time I did, they never got committed by anyone. Who is in charge of committing stuff? Does someone want to nominate themselves to review and commit my patches? The patches are briefly: - On Mac OS X dlopen() is not very well supported, so libao has been cleaned up a bit to

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

I am trying to convert some a few WAV files to ogg format (using vorbis-tools-1.0beta4 oggenc). I tried: $ oggenc -o nash.ogg nash.wav ERROR: Wav file is unsupported subformat (must be 16 bit PCM or floating point PCM ERROR: Input file "nash.wav" is not a supported format And: splay -d - nash.wav | oggenc -r -o nash.ogg - The resulting file when played with ogg123 played so

On Aug 22 09:38:17, u.windl at ukr.de wrote: > I wonder: What happens if you disable cURL's (default) buffering? With curl -N, I see the same behaviour. That's curl 8.1.2. What about you? I still can't see the original problem. Jan > -----Original Message----- > From: Vorbis <vorbis-bounces at xiph.org> On Behalf Of Jan Stary > Sent: Tuesday, August 22, 2023

vorbis-tools/oggenc/utf8.c:164 has a //-style comment; it should be /* ... */ so that non-gcc compilers won't barf (e.g., solaris Forte 6.1 cc). Patch included, if you're really lazy. :-) {+} Jeff Squyres {+} squyres@cse.nd.edu {+} Perpetual Obsessive Notre Dame Student Craving Utter Madness {+} "I came to ND for 4 years and ended up staying for a decade" Index: oggenc/utf8.c

Greetings one and all; I'm not subscribed to this list so I'm first sending this message to verify that mails from me make it through, and then later I'll send the juicy messages with patches. Also, the address I'm using is IPv6-only and doesn't often work, so drop me from any replies and I'll catch the archives, or drop only the hostname part to get an IPv4 address that

This patch (along with all the previous patches) gets oggenc and ogg123 working. This does not get vorbiscomment working, although I assume that would be trivial -- just add the getopt stuff to the project just like I did in ogg123. In addition to this patch, as I just mentioned, getopt1.c getopt.h and getopt.c need to be copied from oggenc to ogg123 and added. The host check in

Hi all, I think we're getting close to the first FLAC release in over 4 years. I have tested whats currently in Git on x86, x86_64 and PowerPC Linux and would appreciate reports of successful compiles (and even more importantly any failures) on OSX, Windows and elsewhere. Cheers, Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo