similar to: metadata on the wiki

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:

On 12/09/2007, Ian Malone <ibmalone@gmail.com> wrote: > So wiki discussion on the new metadata format > is ongoing. I'd like to move some things about > a bit. Hi Ian, I find the existing Metadata page a bit waffly, and I think we could improve it to be more constructive. Perhaps it should simply give a very brief introduction to how we approach metadata, and links to the

On 14 April 2012 23:40, Ian Malone <ibmalone at gmail.com> wrote: > On 14 April 2012 23:34, Ian Malone <ibmalone at gmail.com> wrote: > >> http://pastebin.com/xXhPyZuQ > >> ./jpegtoblock.pl ?-i DSCN7376.JPG -o flacblock > >> You'll need to add the "METADATA_BLOCK_PICTURE=" which makes it into a >> comment file yourself. >> >

Another spin-off discussion. The scheme used on <http://wiki.xiph.org/index.php/Metadata> was to packetize XML (split it up into packets at the root level, each of which was self contained (the terminology has temporarily abandoned me), and have the bos packet as the opening <?xml &c. stanza, the eos a </xml>. It is probably more sensible to include a magic number identifying

Hello, I am new to using opus but so far I really am loving it. At 16kbps spoken content sounds fabulous. I am using opusenc on 64-bit linux - mostly with flac input. The one thing I can't figure out how to do is add album art. I tried passing the vorbis way of adding a metadata_block_picture comment field to opusenc but it complained about the length. I can't seem to find any

Ralph Giles wrote: > > A URI/URL scheme for referencing streams would be a generally useful > thing. Should we override the query mechanism like the time fragment > draft? "?oggserial=0x15323421" ? > This is roughly what was suggested the last time around. A possible refinement is to provide a mapping from identifiers to IDs so you could say "?oggid=myvideo".

Hi list, On 2007-09-10 Silvia Pfeiffer wrote: > 2) we need a XML annotation format for audio - in particular for music - > that is more structured than vorbiscomment (and this probably > applies to video, too) Above, Silvia sums up nicely what I used three days and a tone of emails to say. (Though she did not say that this format should replace Vorbis comments all together, which is

Wednesday next week would be the Xiph monthly meeting. It is there enough going on at the moment (IETF document being submitted soon, the various aspects of metadata) to warrant one? -- imalone

Wednesday next week would be the Xiph monthly meeting. It is there enough going on at the moment (IETF document being submitted soon, the various aspects of metadata) to warrant one? -- imalone

Wednesday next week would be the Xiph monthly meeting. It is there enough going on at the moment (IETF document being submitted soon, the various aspects of metadata) to warrant one? -- imalone

It seems there still isn't a tool (at least not a Xiph one) for modifying Opus comments from the command line. I've had a go at adding support in liboggz (which is fairly trivial, since it just means adding recognition for the Opus stream). That certainly works for comment editing, but I'm not sure if it's is good enough to commit back, because timing gets reported back slightly

It seems there still isn't a tool (at least not a Xiph one) for modifying Opus comments from the command line. I've had a go at adding support in liboggz (which is fairly trivial, since it just means adding recognition for the Opus stream). That certainly works for comment editing, but I'm not sure if it's is good enough to commit back, because timing gets reported back slightly

Hi, The following changes allow vorbiscomment to read and edit the tags for the first occuring vorbis stream in a muxed (and chained) Ogg bitstream, while retaining the renormalisation. I've tested it on a number of combinations of muxed and chained streams, using the write comments from file option for vorbiscomment to rewrite the comment header and then cmp for binary differences. Seems

> Ogg/Spots has no implementation since we agreed that Ogg/MNG would > fully cover all the functionality of Ogg/Spots. However, Ogg/MNG has > not progressed as much as we would all have liked. > > So, if you would like to get images into Ogg, I'd recommend > improving/implementing Ogg/MNG support. :-) I'd looked at MNG (which I didn't know about at the time) and to

Hi ogg-dev list, I have improved the format formally known as Media Description and Metadata (MDMF) for the Ogg Container Format. Please have a look at the M3F page in the wiki http://wiki.xiph.org/M3F The format have been simplified and designed primarily with audio and movie recordings in mind. The old version focused on providing separate tools for each media type, were the new version

On 31 December 2016 at 14:03, Timothy B. Terriberry <tterribe at xiph.org> wrote: > Ian Malone wrote: >> >> out, due to the Opus pre-seek, I think. Fixing that probably requires >> adding an Opus-specific metric to liboggz, since the current default >> linear one doesn't deal with first granule position being set. Thought >> I'd check before getting

Silvia Pfeiffer wrote: > Hi Ian, > > hmm, there was a whole bunch up on media.aidabrowser.com, but it seems > that CSIRO have taken that site offline. > > I thought there was a version of the media in cmmlwiki that produces > annodex files, but there may be a bug on the server that prevents > that. Conrad - is this a known issue? > Thanks for getting back to me.

On 10/09/2007, Daniel Aleksandersen <aleksandersen+xiphlists@runbox.com> wrote: > On Monday 10. September 2007 23:39:50 Silvia Pfeiffer wrote: > > 2) we need a XML annotation format for audio - in particular for music > > - that is more structured than vorbiscomment (and this probably > > applies to video, too) > > It would have to apply to any kind of media. >

----- Original Message ----- From: "Ian Malone" <ibmalone@gmail.com> To: <ogg-dev@xiph.org> Sent: Friday, March 10, 2006 8:42 AM Subject: Re: [ogg-dev] oggfile, skeleton and vorbis tools > Re-reading Monty's email: when you talk about vorbis-only vorbisfile and > the concurrent vorbis stream case do you mean vorbisfile will need to be > able to choose?

On 16/01/07, Ivo Emanuel Gon?alves <justivo@gmail.com> wrote: > On 1/15/07, Ian Malone <ibmalone@gmail.com> wrote: > > > First, there is apparently a new version of MS DOS coming out shortly, > > does anyone know if it is any more sensible than it's predecessors? > > I've not heard of anything in that regard. Actually, I'm not sure it > would