similar to: embeding xml to ogg

On 6/4/12, Benjamin M. Schwartz wrote: > On 06/04/2012 04:08 PM, Martin Leese wrote: ... >> The optimal solution is described at: >> https://wiki.xiph.org/XMLEmbedding > > As that page says, "This page is for development of a specification for > embedding XML streams in Ogg.". "XML streams" are not simply XML > documents. They are _temporally

On 05.06.2012 20:41, Martin Leese wrote: > On 6/4/12, Benjamin M. Schwartz wrote: > >> On 06/04/2012 04:08 PM, Martin Leese wrote: > ... >>> The optimal solution is described at: >>> https://wiki.xiph.org/XMLEmbedding >> >> As that page says, "This page is for development of a specification for >> embedding XML streams in Ogg.".

Oleksij Rempel <bug-track at fisher-privat.net> > On 05.06.2012 20:41, Martin Leese wrote: ... >> On 6/5/12, Oleksij Rempel wrote: >> || We need fallowing tags: >> || creation datetime: seconds and time zone should be included. >> || source host: it can be name or guid. to organise created files by >> sources. >> || keywords,events. >> || date

Hi all, i googled about it first but didn't got needed results. I work on project which basically record speech and manage it. The format of choice is ogg/speex or ogg/vorbis, depending on quality. To manage files we can't use VorbisComment. We also can't use external database to store needed information. XMP fits to our needs, but it looks like there is still no ready documentation

On 7/23/13, Silvia Pfeiffer <silvia at silvia-pfeiffer.de> wrote: > On Wed, Jul 24, 2013 at 3:59 AM, Martin Leese >> ... >>>> Information about Metadata >>>> has been collected together in the Xiph Wiki >>>> at: >>>> https://wiki.xiph.org/Metadata >> Page updated. See what you think. > > M3F is also not used anywhere

On 06/04/2012 04:08 PM, Martin Leese wrote: > "Benjamin M. Schwartz" wrote: > >> Just store the XMP in a >> VorbisComment field named "XMP" (or whatever name you like). > > This suggestion falls well short of an optimal > solution. You haven't specified any requirements, so I have no idea what would be more helpful. > The optimal solution

On 7/23/13, Silvia Pfeiffer <silviapfeiffer1 at gmail.com> wrote: > On 23 Jul 2013 15:17, "Martin Leese" <martin.leese at stanfordalumni.org> > wrote: ... >> Information about Metadata >> has been collected together in the Xiph Wiki >> at: >> https://wiki.xiph.org/Metadata > > That page is a bit outdated. It has CMML in it which we

I have been tidying up the VorbisComment page in the XiphWiki. The problem with it was that it was a mixture of proposals and discussion of those proposals. This made it difficult for implementers to see what to implement. The problem section is: http://wiki.xiph.org/index.php/VorbisComment#New_ENCODER_field_name_proposal This is a mess, and all I could do was add attributions to the

On 11/14/08, David Flynn <davidf+nntp at woaf.net> wrote: > Correct; there is no metadata handling capability in the current > mapping spec. I'd suggest at some point to look into separate stream solution for metadata, perhaps M3F [1]. -Ivo [1] http://wiki.xiph.org/index.php/M3F

" Ivo Emanuel Gon?alves " <justivo@gmail.com> wrote: > On 9/24/07, Ian Malone <ibmalone@gmail.com> wrote: > > The point I > > wanted to bring up was the MAY ignore unrecognised stream > > types, which I understood to be a future proofing mechanism. > > Oh. > > There is a similar notice in the wiki, which I did not integrate in > the

" Ivo Emanuel Gon?alves " <justivo@gmail.com> wrote: > On 9/24/07, Ian Malone <ibmalone@gmail.com> wrote: > > The point I > > wanted to bring up was the MAY ignore unrecognised stream > > types, which I understood to be a future proofing mechanism. > > Oh. > > There is a similar notice in the wiki, which I did not integrate in > the

Oleksij Rempel <bug-track at fisher-privat.net> wrote: > Ok, > you are right, using existing technology will save time :) What has not yet been discussed is what you are streaming *to*. That is to say, what software is going to receive the metadata, and what will it do with it. This is important because VorbisComments can contain pretty much anything you want. Suggestions for field

With changeset 6869, I can _not_ start xend. Did anybody else meet the same issue? [root@xin ~]# xend start Traceback (most recent call last): File "/usr/sbin/xend", line 32, in ? from xen.xend.server import SrvDaemon File "/home/xin/work/xmp/xen32-smp/dist/install/usr/lib/python/xen/xend/serve r/SrvDaemon.py", line 30, in ? File

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

I have found Sweave() to be great for producing PDF documents. I have been experimenting with RweaveHTML (from the R2HTML) package and have had moderate success. My main issue has been that I simply want the R output to be shown verbatim in the HTML document but RweaveHTML tends to convert most output to a table, for example. So, is there a way to force the RweaveHTML driver to simply provide

Am 03.12.2013 23:49, schrieb Monty Montgomery: > Any time code is stuck in a loop calling ogg_sync_pageseek() or > ogg_sync_pageout(), you'll see most of the time sunk into checksum > calculation. It's the only thing in libogg that _can_ take much time. > This is not likely a libogg bug, but a bug in the code calling libogg > in a tight loop. > > Looking at the file

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

Daniel, nobody has accused you of reinventing the wheel. You give up too easily. If you want to develop a standard, it takes a lot of discussion and input - and it takes diplomacy. Attacking people and attacking the community will not be helpful. You have asked for feedback - feedback has been given. Now it's time to think and digest. I for one have been motivated by the topic of discussion,

I set icecast.xmp: <listen-socket> <port>8000</port> </listen-socket> <listen-socket> <port>8443</port> <ssl>1</ssl> </listen-socket> 8000 work, 8443 not work. If set ssl to port 8000 not work nothing V V sob., 27. jun. 2020 ob 18:13 je oseba Paul Martin <pm at nowster.me.uk> napisala:

"Gabriel I." wrote: > Greetings, > > I apologize if I posted this in the wrong list, I wasn't sure where to post > it, but seeing as the tags are called "vorbis comments" I thought vorbis, > rather than ogg-dev, would be the right choice. (actually, I'm not even a > developer anyway) Hi Gabriel, I doubt whether the Xiph community would promote a