similar to: The Oft Maligned comment field, initial thoughts.

I mentioned sub-tagging in an earlier post. Here's a more in-depth mail on what i thought of. One of the debates going on here are whether ARTIST is worthy of life. Another is whether the average user will bother filling in the detailed info Jonathan wants. Of course, all tags are optional, but nevertheless we should have a tagging-system that pleases _the_users_, that is, everybody: 1.

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

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

I have just committed this code to CVS, and here is more information about it for those interested : - the spec that I went off of for the protocol can be found here -> http://www.oddsock.org/icecast2yp/spec.html - since icecast2 now needs to potentially connect out to yp servers for communication, libcurl has been added as a dependency...I used curl 7.9.8... - I also have currently

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

http://chrome.blogspot.com/2011/09/problems-with-microsoft-security.html It was just an accident, or not, mr. micro$oft? ...f*ck you..

Hi everybody At work we''ve finally convinced the chief to develop some small project using open source technology. Unfortunately we are deeply involved with Micro$oft technology. That means, windows 2003 server, IIS, MS SQL 2005 and asp. I was thinking about recommending ruby on rails instead of asp, but I''d like to know how well it goes with IIS and MS SQL, because for the

Hi, I have just started using Dovecot (1.0.10) SASL behind my Postfix (2.3.3). Everything works fine, as long as I send the SMTP AUTH command manually. When using M$ Outlook (2000 and 2003) and Outlook Express 6, authentification always fails. Turning on the Dovecot auth debug on reveals the reason: Dovecot SASL expects, in accordance with the standards, the following format of the SMTP AUTH

It will be interesting to see how many standards get broken, and how many proprietary hooks get thrown into the pot. The bean counters smell some money, and their OS franchise is waning: http://www.nytimes.com/2006/06/26/technology/26soft.html -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

On Mon, Sep 10, 2007 at 01:19:05PM +0100, Ian Malone wrote: > as artist=(composer) Beethoven), I think cast lists for films present > a similar problem. There is consistency and indexability to be > addressed (Ludvig van Beethoven; Beethoven, Ludvig van; > Beethoven). ID3 has a concept of "sort" tags, which provide a string for sorting purposes which is different from the

Hi, <p>here's my €0.02 on that topic. First of all, all those new tags are total overkill to be standardized. They're only useful for people who both tag OGG files for a living and listen to classical music only. Imagine what will happen when the Jazz fans, and the Techno fans, and the Rock fans and who knows else demands his very own, customized + standardized set of tags. And

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:

Daniel, these are all good ideas and worth progressing. However, it may be better not to merge too many goals in one format (MPEG-7 did that and ended up as a big mess). So, I suggest to start by structuring the types of things you want - then finding out which parts belong where into existing formats such as vorbis comment, Skeleton and CMML, and only then start to develop a new format. For

The spec seems to be unclear on this: should two comment haeders who only differ in the order of comments be considered equevalent? VCE shows comments in the order read and allows to store them in any order (it has move up/down buttons). Comment editors with a fixed layout (like the commmon TITLE/ARTIST/etc. fields in PP's winamp plugin) don't show the order and give no control of it.

The biggest problem with Vorbis comments are too loose specifications and too little standardisation. Another problem is attribution of involved parties. Currently only the ARTIST field name is supported in software. More standardised field names need to be worked out for organisations and persons involved in the production of the recording. See:

Daniel, before you step over everything that has been done before, we need to determine what exactly is the use case for your new specification. What concerns metadata, we currently have: * vorbiscomment - this is a header at the beginning of a logical bitstream which has metadata that refers to the complete file; there is a specification, which has been public for a long time and is the

Quazgaa and I were talking about the comment tags we'd like in oggenc. Here, as requested by Michael, is the summary. Date (year in id3 land) should be supported. We suggest '-y | --date'. I suggested '%y' for passing it to the filename template, but this may be of limited utility. Track number. -n was the first choice, but is taken by the name template. We settled on

I'm trying to write comment writer thing for zinf, because I love the program, but it doesn't fully support ogg. I've found how to read comments, but can't figure how to write them. There has been some discussion about this previously in the archives, but I couldn't find any specifics, only references to code not posted to the list. The api documentation page is (painfully)

Well, this is a bit stronger than a proposal; this is "what I plan to do unless people see obvious flaws I missed"... The text comment header is the second (of three) header packets that begin a Vorbis bitstream. It is meant for short, text comments, not arbitrary metadata; arbitrary metadata will be put in a metadata stream, likely an XML stream type. We've discussed this in