[vorbis] VORBISCOMMENT

[Zeljko Blace]

How about using mozilla technology (which is platformneutral 
for all frontends)?
www.mozdev.org is full of apps using it ...
???

On Mon, 15
Jan 2001 rik at kde.org wrote:

> #if Michael Smith
> > >A Qt UI will work on Windows and UNIX, but to compile a Windows version,
> > >a 'professional' license is needed, which is about $1500, and I don't
> > >have one. I know someone at Trolltech who might be interested in making
> > >the Windows port himself though, so it's not all bad.
> > 
> > That'd be good (though I don't think anything that requires an
> > expensive license will become a standard (i.e. part of what xiph
> > distributes) tool. So we probably still need a different win32
> > editor.
> 
> Ah yes. Not much point having code if you can't compile it :)
> Someone could probably knock up something identical using one of the
> free Windows compilers. I think Borland does one, but I'm no expert
> on the platform...
> 
> > Good start. However, vorbis explicitly permits multiple instances of
> > each tag (e.g. multiple artists should be represented by multiple
> > instances of the ARTIST tag. The player plugins don't do this
> > properly yet, because I put in the current tag-handling (in xmms and
> > winamp plugins) as a quick hack. Suppose I should find time to
> > update those... It'd definately be neccesary to support that in a
> > GUI.
> 
> I forgot about that. I'd have to think about that to find a nice way
> to present the option of multiple 'standard' tags in the UI.
> 
> BTW, it's quite easy to do things like autocompletion, which would
> be handy IMO. The app would just remember that artist and album names
> you have used previously and as you type 'Sou' it offers 'Soundgarden'.
> 
> There are probably other nice ways to make editing easier.
> 
> > >If there were functions in libvorbisfile that allowed easy tag
> > >editing, I could write this app in my coffee break.
> > 
> > libvorbisfile won't ever do this - it's too completely different from
> > what the rest of the library is aimed at. I suppose a seperate
> > libvorbiscommenteditingstuffwithareallylongname would be possible. I
> > think that it'd probably be better just to clean up the code
> > (libvorbis needs a couple of extra functions to do this cleanly) and
> > provide simple, easy to use example code.
> 
> Ok.
> 
> > >What's up with vorbiscomment ? Is there a lot to do to fix it ?
> > 
> > It's disgusting evil code (I wrote it, I can say that ;) Apart from
> > that, it relies on unix semantics in nasty ways, is slow (making it
> > fast requires a libvorbis addition), and is probably broken right
> > now (it may compile, it's unlikely to run successfully). As a rough
> > example of how to do things, it might serve. As code to use as-is,
> > it's useless. 
> 
> Well, I read it and it looked nasty to me, which is why I haven't
> written a GUI tag editor :)
> 
> > >The nice API that exists for decoding makes it trivial for me to
> > >implement playing from HTTP, FTP, or any other IO.
> > >
> > >So, big wish: IO-type-independent functions to allow tag editing.
> > 
> > Possible, but overkill. Really, this will be a single 40-50 line
> > function. Pain to write really well, but nobody will ever really need
> > to change it.
> 
> Ok. I'll look forward to seeing it sometime. I have a few vorbis files
> which I tagged wrong and I can't edit them - doing CRC in my head is
> too hard :)
> 
> Rik
> 
> 
> --- >8 ----
> List archives:  http://www.xiph.org/archives/
> Ogg project homepage: http://www.xiph.org/ogg/
> To unsubscribe from this list, send a message to 'vorbis-request at xiph.org'
> containing only the word 'unsubscribe' in the body.  No subject is needed.
> Unsubscribe messages sent to the list will be ignored/filtered.
> 

.. :::...::  ::.:::...:..:.:: .. .. ::..::: .. ::.:: ..
                    .plan as a mission
           

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.