similar to: No subject

table of magic+offset to determine MIME-type. If no mime type is determined, then I think it passes to the algorithms. Or maybe its vice versa - algorithms are checked then the table. Anyway, the basically means - if something is not in the table, it needs an algorithm Regards, Ali > In another message, Monty wrote: > > > No. The metaheader is meant to be something *much*

In http://advogato.net/person/rakholh/diary.html?start=165 Ali wrote: > For same reason I am arguing with people on vorbis-dev - but I don't > understand what the argument is about (considering that the vorbis > developers proposed a solution which mjs and I thought was reasonable, > and then some developers decided to criticize us again for no reason). Goodness, get dropped

I've come full circle on the Ogg text stream format, back to arbitrary associated xml streams. What's changed? Mostly rolling the requirements around in my head, and weighting them differently. I think we've dealt with the complexity issue; this functionality can be optional for "dumb" audio players, and possibly also for dumb video players, though there it's a smaller

Don't have too much to report, but I talked to Michael Smith about things on IRC this evening and we made some progress in compromising our visions. On the static and stream identification metadata there was a tenative decision to go with RDF, but in such as way that a limited player could choose not to support it and still be able to play the a/v data. Robert mentioned trying to work his

I recently went looking for the beta2 sources and was surprised to not find them anywhere on the website. Worse, the release tags 'public-beta-1' and 'release_1_0_beta_2' longer retrieve the complete code, since part of the repository has been manually rearranged! (Thanks to cvs's non-support of changes in directory structure.) Fortunately, Monty made backups, and was kind

On 30/09/06, Ralph Giles <giles@xiph.org> wrote: > On Sat, Sep 30, 2006 at 12:21:53PM +0200, Danny Ayers wrote: > > > Basically I'd like to embed arbitrary (meta)data in flac files. > > I agree it would be best to define a new block type for RDF > metadata, or probably better for random attached XML data, That sounds reasonable, but... and > let the xml parser

On Mon, Nov 17, 2008 at 11:41 AM, Ralph Giles <ralph.giles at artifex.com> wrote: > On Sun, Nov 16, 2008 at 3:22 PM, Silvia Pfeiffer > <silviapfeiffer1 at gmail.com> wrote: > >> Plus, the W3C is currently >> investigating a new ontology for video/audio metadata. This may be a >> good extension for vorbiscomment once finished. > > Ooh, can you say

On Tue 13 Jun 2000 K<bob> wrote: > I never heard of MNG until just now. (So color me ignorant.) Sorry, I should have included some urls. To briefly summarize, mng is an animated image file format from the people who designed png, and is essentially a multiframe extension of the same. png (pronounced 'ping') is a format developed by a group of volunteers as a replacement for

I've put together the first attempt to defining an RDF metadata vocabulary for use with the CD Index/MusicBrainz/OggVorbis. If you care about metadata issues, please take a look at: http://www.cdindex.org/MM I've included a section for video specific stuff, but everything that I originally had in there is being covered by the MM:Contributors section. The Contributors stuff will allow

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dan Phillips wrote: > With regards the toc problem not compensating for starting from track > 0, is it possible to use the cdrtoa -t or -T options to compensate for > the shift. I am not sure I fully understand the option, but I came > across it and thought I would mention it. I believe the -T and -t flags (to cdparanoia? AFAIK, cdrdao

Charles Steinkuehler wrote: > Dan Phillips wrote: > >> With regards the toc problem not compensating for starting from track > >> 0, is it possible to use the cdrtoa -t or -T options to compensate for > >> the shift. I am not sure I fully understand the option, but I came > >> across it and thought I would mention it. > > I believe the -T and -t flags

(quoting from the web archive, I only just subscribed) Monty wrote: > > > (a bit testy that this flamewar has started again, and no one has learned a > > thing from the previous rounds) > > OK, that wasn't fair... the old timers know what's up, but I do wish some of > the folks who bring things up would browse the archive threads or at least not > jump in

It looked like ogg123 was expecting an out-of-date set of headers. I've updated the printout section to expect the canonical set from docs/v-comment.html. I also found vorbize's use of "track" for the title tag confusing. The second patch is just a rename in the code and ui. Cheers, -ralph -- giles@ashlu.bc.ca <HR NOSHADE> <UL> <LI>TEXT/PLAIN attachment:

On Wed, 8 Nov 2000 15:33:48 -0800 Michel LESPINASSE <walken@zoy.org> wrote: > One reason is i18n of subtitles. You probably dont want to drag full > unicode fonts in each decoder... My point was that we don't want to drag full unicode fonts into the *spec*. On a desktop-class system, you do want to put that complexitiy in the decoder. Streams will benifit from universally from

Hi Daniel, On 9/10/07, Daniel Aleksandersen <aleksandersen@runbox.com> wrote: > It is indeed necessary. I hope this format will be a huge leap in metadata > descriptions for media content. Not only for music, but any media found in > Oggs. You are thinking too small. Such standards should not be made to just work with Ogg, but rather possible to work with any media format out

ly or Hybrid frames for 40 or 60ms packet, respectively. That is based on = concatenating 20ms frames, right? Is 60ms the largest packet opus_encode() can generate? In order to get pac= kets of up to 120 ms by combining multiple frames as described in RFC6716 c= lause 2.1.4 one would need to use the "repacketizer". That is if I want to= have a 120 ms packet, I would need to take

I'm very pleased to come across flac, good work folks! I would like advice and/or have a spec feature request. Please bear in mind that I am totally new to the format, apologies if what I describe has been discussed before. Basically I'd like to embed arbitrary (meta)data in flac files. For example, it may be about the audio, but then again it may be about the creator of the audio, or

Well, partly: I've been "converting" a RHL 7.3 system to approximately Centos 2.1, so found it necessary to "rpm -Va" I was more than a little surprised at this: [root at magpie root]# rpm -V seamonkey missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/browser missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/browser/content missing

Hello, i''m writing an application that needs geocoding information for locations outside of the US. I''m using the brainoff.com geocoding service mappoint = Net::HTTP.new(''brainoff.com'', 80) response = mappoint.get(''/geocoder/rest/?city=Gent,BE'') logger.debug response.body and the body of the response is in the following form : <rdf:RDF

*Vivek Pandya* On Wed, Mar 23, 2016 at 10:28 PM, Krzysztof Parzyszek < kparzysz at codeaurora.org> wrote: > On 3/1/2016 11:26 AM, vivek pandya via llvm-dev wrote: > >> >> Still I am looking for feedback on RDF part and also if some one is >> willing to mentor me. > > Hello Krzysztof Parrzyszek, I switched to other topic as I felt I don't have enough