similar to: rtp payload format

Hi all, Apologies in advance, this email is quite long. I've prepared an updated Vorbis RTP Internet Draft, which is a continuation of draft-moffitt-vorbis-rtp-00.txt which can be found below. If this new draft gets the ok I'd like to submit this to the AVT WG later this week. There are a number of changes over the original I-D, notably the changing of the M bit function in the RTP

Hi. I got bored of writing papers last week so I decided to write an app for sending and receiving multicast vorbis streams over RTP. A first version is available here: http://www.cdt.luth.se/~rolle/vorbis/ (I use the JOrbis decoder, so you need Java 2 with Javasound, e.g. JDK1.3. Since the decoding is done in Java, you probably need at least 300-350 MHz. Works with the IBM JDK1.3 on Linux on a

Hi. I got bored of writing papers last week so I decided to write an app for sending and receiving multicast vorbis streams over RTP. A first version is available here: http://www.cdt.luth.se/~rolle/vorbis/ (I use the JOrbis decoder, so you need Java 2 with Javasound, e.g. JDK1.3. Since the decoding is done in Java, you probably need at least 300-350 MHz. Works with the IBM JDK1.3 on Linux on a

Hi all, Below is the Vorbis RTP Internet Draft as sent to the AVT working group of the IETF. Comments and feedback is still welcomed from the Vorbis community. Cheers Phil ---------------------------8<-----------------8<------------------------ Network Working Group Phil Kerr Internet-Draft The Ogg Vorbis January 07, 2003 Community / OpenDrama

Hi, I am not sure if this is the right mailinglist (since I have an ogg problem not a vorbis)..... I am looking for some pointers on how to packetize an ogg stream. My idea is to use udp packets for transport, so I would need a way that would minimalize the impact of lost packets. Are there any code examples out there for this? Thanks, Jeroen p.s. Please cc me, I am not subscribed to this

Hi, I am not sure if this is the right mailinglist (since I have an ogg problem not a vorbis)..... I am looking for some pointers on how to packetize an ogg stream. My idea is to use udp packets for transport, so I would need a way that would minimalize the impact of lost packets. Are there any code examples out there for this? Thanks, Jeroen p.s. Please cc me, I am not subscribed to this

Hi! What happened to this document? Was it just left dying in the IETF system? Tor --- >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-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the

We want to push for an open and standards compliant system for all multimedia. We've done a good job on the interoperability side with icecast and MP3. We're making a ton of progress with the Vorbis codec as well, which will allow us to do many things we weren't able to do before. It's time to start thinking about RTSP, RTP, Multicast and all of the other standards and features.

alpha. (that about sums it up) Will encode and play back via an sdp file and multicast on one computer (over the net if you transfer the sdp file over by hand). rc/rtenc3 and src/rtdec3 are in the style of encoder/decoder_example ...so this means you MUST edit it them to suit your system. For example, I specify my rtenc3 to multicast just on eth1 (to avoid pissing off my cable supplier on

Hi all, I'm in the final stages of putting a new Vorbis RTP draft together, the new sections are below. There are a number of open questions: 1.) At present there is a 16 bit length field for the codebooks. As they are spec'd as being unbound in length, but typically around 15K, are there situations where they may be greater than 64KB? The size limit can be extended to 2MB as there

Hi Jack, > You're comments are welcome. Here they are... 3.1 RTP Header Payload Type (PT): I don't see an alternative to using a value of the dynamic range (96-127). IIRC, other ranger are reserved for fixed values assigned by IETF. "A dynamic payload type MUST be used - i.e., one in the range [96,127]." 3.2 Payload Header If you refer to RFC2119, please keep the capital

Hi All, Please find below an updated Vorbis-RTP Internet Draft document for review and discussion at the Xiph IRC meeting on Saturday. The changes in this version have been: Codebook caching mechanism Expanded SDP parameters Expanded MIME section Expanded introduction Packet loss section Minor tweaks and clarity changes to text There are probably some minor tweaks to the formatting needed

Hi everybody, this is an update on the developed Ogg IETF standard documents and their status. All of these documents are in the process of discussion and have not yet been accepted as standards. <p>The following Internet-Drafts (I-Ds) have been prepared for standardisation and submitted to the IETF: 1) an I-D requesting to register "application/ogg" as a mime-type written by

Hi everybody, this is an update on the developed Ogg IETF standard documents and their status. All of these documents are in the process of discussion and have not yet been accepted as standards. <p>The following Internet-Drafts (I-Ds) have been prepared for standardisation and submitted to the IETF: 1) an I-D requesting to register "application/ogg" as a mime-type written by

Hi everybody, this is an update on the developed Ogg IETF standard documents and their status. All of these documents are in the process of discussion and have not yet been accepted as standards. <p>The following Internet-Drafts (I-Ds) have been prepared for standardisation and submitted to the IETF: 1) an I-D requesting to register "application/ogg" as a mime-type written by

Go monty! jack. ----- To: cvs@xiph.org Subject: [xiph-cvs] cvs commit: vorbis/vq huffbuild.c latticetune.c make_residue_books.pl Date: Sun, 3 Jun 2001 22:50:13 -0700 (PDT) From: xiphmont@xiph.org (Monty) Precedence: bulk Reply-To: cvs@xiph.org xiphmont 01/06/03 22:50:12 Modified: lib codebook.c codebook.h floor0.c mapping0.c os.h res0.c vq

(hello all, this is my first writing. so please bear with me if I'm wrong anywhere.) orry to break too lately, but how is the RTP payload submission is going? could we see the new payload at March IETF? I agree that it would be fairy straightforward to make an RTP payload for ogg vorbis, assuming raw packets, AFAIK. using physical bitstream is, in this case, not adequate by the reasons in

FYI, the Opus RTP payload format is now RFC7587: https://tools.ietf.org/html/rfc7587 Cheers, Jean-Marc -------- Forwarded Message -------- Subject: [payload] RFC 7587 on RTP Payload Format for the Opus Speech and Audio Codec Date: Tue, 30 Jun 2015 16:33:17 -0700 (PDT) From: rfc-editor at rfc-editor.org To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org CC: drafts-update-ref at

Hi everyone, After years of effort, the Speex RTP payload format is now approved as an RFC: http://www.rfc-editor.org/rfc/rfc5574.txt Many thanks to everyone who participated. Enjoy! Jean-Marc

Hi everyone, After years of effort, the Speex RTP payload format is now approved as an RFC: http://www.rfc-editor.org/rfc/rfc5574.txt Many thanks to everyone who participated. Enjoy! Jean-Marc