similar to: TAG-mess

Hi! First, here's some background information: Some friends and I are making music with our computers for some years now. We release our tracks on the Internet for free for private use, both in the original module format and currently MP3. Within the next weeks or months (depending on the leisure time i get), our web site www.kolabore.de will be vorbisised for reasons I won't have to

A month or two ago I sent an email to this list proposing to expand the list of "standard" tags for Ogg Vorbis. No tag would be required, but if you wanted to encode certain types of information about a file, you could use a standard tag. I went through the whole discussion, and revised my proposal in light of all the comments from everyone. Here is the updated proposal. This

Hi! While vorbisizing our web site, I also wrote an information page about OGG Vorbis in order to help our visitors to both understand what OGG is all about and learn how to (easily) play our and others .ogg files. Since English is not my native language, I could use some help/feedback/proofreading on that page. What I want in the end is understandable, plain English (that can also be understood

-----BEGIN PGP SIGNED MESSAGE----- [ Sorry for sending this twice; I sent it to the vorbis-dev list by mistake. ] The ALBUM, ARTIST, TITLE, and TRACKNUMBER tags aren't sufficient for classical music. MP3 muffed it, but since Vorbis is so flexible, I'd like to propose that ogg123 recognize and display the following optional tags, instead of giving an error message that it doesn't

-----BEGIN PGP SIGNED MESSAGE----- [ Sorry for sending this twice; I sent it to the vorbis-dev list by mistake. ] The ALBUM, ARTIST, TITLE, and TRACKNUMBER tags aren't sufficient for classical music. MP3 muffed it, but since Vorbis is so flexible, I'd like to propose that ogg123 recognize and display the following optional tags, instead of giving an error message that it doesn't

Hi, having inspected one of the files found at music.ibiblio.org, I realized that the comments are quite poor or misformatted in the files. I'm telling you, because: 1) I think it's great to have some free music 2) I think the performers deserve to be recognized Generally, I'd put as much as possible into the Vorbis comments. Then you could skip creating these index.html manually:

Hi ogg-dev list, After discussing the [lack of] metadata standards on the irc://irc.freenode.net/#Vorbis channel yesterday I figured I had to contribute to this process. Attached is a sample XML formatted metadata sheet describing a song; and shows off other media type elements as well. How this is to be embedded in the OGG container is not my field. I have only spent a couple of hours

Hi! Today, I found an encoding bug with a new tune by me. http://www.uni-karlsruhe.de/~us87/ogg/vorbis_bassrumble_demo.rar (2.1MB) contains the original .WAV in 16bit/44.1kHz and an .OGG encoded at 350kbit/s. I found the bug when listening to the 128kbit/s version, but encoding it with that high bitrate didn't change a thing. The deep bassdrum contains a rumbling, knocking sound (the first

Based on peoples posts to this list, and feedback on IRC (irc.openprojects.net #vorbis) I have updated the original proposal. You can read it here. Please read it before writing any futher questions, comments, or criticisms of the proposal. http://reactor-core.org/~djw/ogg-tags.txt Cheers Jonathan -------------- next part -------------- A non-text attachment was scrubbed... Name: part Type:

Hi! FYI, the web site http://www.kolabore.de/ where we offer our own music is now completely vorbisized. :-) Because of the many releases we switched from direct download links to a simple database/cgi, so if you stumble over any problems, please let me know! Thanks and bye, Moritz --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To

On Wed, 28 May 2003, Josh Coalson wrote: > interesting idea, CD-TEXT is in the subcode and if cdrdao can > split it out that's better I think than hacking the CUESHEET > block to store CD-TEXT. I suppose the ideal would be to have a metadata block to store the subcode from a CD, and something that could interpret it as CD-TEXT, if that's what it is. Then it would be possible to

I change a lot of my CD to Ogg to be able to listen them easily from my computer (I use foobar, I was used to WMP but it does not support library for Ogg files and plug-ins I found for this where poor) without the need for frequent CD changing. I like my music to be richly tagged. But with classical music CD it is a real pain to tag those files. Typical problems involve: - single CD

Sorry for the repost... I don't think the first one posted.. posted to freebsd.stable, freebsd-current, Freebsd-hardware I checked the hardware in the online documentation manual/hardware It only lists the bits and peices of the machine say the hard drive controller and so forth. but doesn't give you a particular system to look at as a working machine with FreeBSD 6.2 does anybody

dovecot-1.1.beta16]# gcc imaptest.c -o imaptest -g -Wall -W -I. -Isrc/lib-mail -Isrc/lib -Isrc/lib-imap -Isrc/lib-storage/index/mbox -DHAVE_CONFIG_H src/lib-storage/index/mbox/mbox-from.o src/lib-imap/libimap.a src/lib-mail/libmail.a src/lib/liblib.a imaptest.c: In client_append function: imaptest.c:1492: error: too many arguments for i_stream_create_limit function

Daniel Aleksandersen wrote: > Hi again list, > > Attached is a much improved version of yesterday's draft. Introducing the > audio:collection:artwork element to deal with album cover graphics and > such. > > After giving it much though; I decided to drop the audio:preformers and > audio:recording elements. They have been replaced by audio:entities which > is

I had instaled winrar3.51 and I get this errors: fixme:actctx:CreateActCtxW stub! err:rebar:REBAR_AdjustBands Phase 1 failed, x=692, maxx=-4, start=0, end=0 err:rebar:REBAR_AdjustBands Phase 1 failed, x=692, maxx=-4, start=0, end=0 err:rebar:REBAR_AdjustBands Phase 1 failed, x=40, maxx=-4, start=1, end=1 err:rebar:REBAR_AdjustBands Phase 1 failed, x=692, maxx=-4, start=0, end=0

in nv10_exa.c : check_texture does : if (w > 2046 || h > 2046) NOUVEAU_FALLBACK("picture too large, %dx%d\n", w, h); check_render_target does : if (w > 4096 || h > 4096) return FALSE; So we have different size limits for the source and the destination ? Another thing is that nv20 uses nv10_exa.c code, and the limit in

Hello ! I'm a new user of Ubuntu Edgy , but when I try to lauch WINRAR , via the console , I receive that error message : libGL warning: 3D driver claims to not support visual 0x5b libGL warning: 3D driver claims to not support visual 0x5b fixme:shell:SHAutoComplete SHAutoComplete stub err:rebar:REBAR_AdjustBands Phase 1 failed, x=692, maxx=-4, start=0, end=0 err:rebar:REBAR_AdjustBands Phase

Every time I post to the list I get the following response indicating that there is a mail loop. the recipient maxx@digital-system.it has some problems with looping. Hi. This is the qmail-send program at smtp.register.it. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out.

Functionally identical but much simpler. Should also better integrate with future layer/viewport changes/fixes. Cc: 10.1 <mesa-stable at lists.freedesktop.org> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Not *strictly* necessary in stable, but it will make backporting later fixes easier. No regressions in piglit. src/gallium/drivers/nouveau/nv50/nv50_program.c | 5