RTP Payload Format for DV Video

Slides:



Advertisements
Similar presentations
Re-INVITE Handling draft-camarillo-sipping-reinvite-00.txt
Advertisements

RTP Payload Format for Reed Solomon FEC of Multiple Flows
Draft-ietf-pim-port-06. port-06 update Changes made in response to second wglc comments and following discussion Many minor editorial issues fixed Changed.
Low Delay RTCP Feedback Format. Low Delay RTCP Documents RTCP-based Feedback: Concepts and Message Timing Rules (draft-wenger-avt- rtcp-feedback-01.txt)
Codecs and RTP payload formats in SDPng
H. 323 Chapter 4.
RTP Payload Format for Multiple Flows FEC draft-peck-fecframe-rtp-mf-01 Orly Peck, RADVISION IETF 77 – March 2010.
RTP Payload Format for Reed-Solomon FEC draft-galanos-fecframe-rtp-reedsolomon-00 Sarit Galanos, RADVISION IETF 76 – November 2009.
RTP Payload Format for Multiple Flows FEC draft-peck-fecframe-rtp-mf-00 Orly Peck, RADVISION IETF 76 – November 2009.
Multimedia Streaming Protocols. signalling and control protocols protocols conveying session setup information and VCR-like commands (play, pause, mute,
1 MMusic Offer/Answer Considerations for G.723 Annex A and G.729 Annex B (draft-muthu-mmusic-offer-answer-g723-g729-00) Authors: Muthu A M. Perumal, R.
® HM-DH30000 The HD Solution. D-VHS is creating a smooth transition from analog to digital. Benefits carried over from the Current VHS Technology New.
RTP: A Transport Protocol for Real-Time Applications Provides end-to-end delivery services for data with real-time characteristics, such as interactive.
RefTek Systems Training
SDP.  Session Description Protocol (SDP) an application-layer protocol intended to describe multimedia sessions a text-based protocol when describing.
PAYLOAD Ali Begen Roni Even IETF 81 Quebec July 2011.
Lecture 5 and 6 notes: Reji Mathew & Jian Zhang NICTA & CSE UNSW COMP9519 Multimedia Systems S
RTP/RTCP(RFC 1889) Real-time transport protocol (RTP) is the de facto standard media transport protocol in the Internet Media transport: audio, vedio,
IPv4-Embedded IPv6 Multicast Address draft-ietf-mboned-64-multicast-address-format IETF 84 Vancouver 1.
AARNet Copyright 2011 Network Operations SDP Deep Dive Bill Efthimiou APAN33 SIP workshop February 2012.
Via contains the address at which the originator is expecting to receive responses to this request. Mandatory To contains a display name and a SIP URI.
Introduction to SDP Issues. Content Background Goals SDP Primer RTP Primer Use cases “New” Functionalities in SDP Multiple RTP Streams in SDP Decision.
Allyn Romanow Mark Duckworth ) Andy Pepperell Brian Baldino
1 Fax and Modem Training May Modem Types.
MPEG-4 RTP transport Philippe Gentric Philips Digital Networks 49th IETF Conference San Diego, 14 December 2000.
1 RTP Payload Format for DV Format Video draft-kobayashi-dv-video-00.txt Akimichi Ogawa Keio University.
Audio/Video Transport Working Group 44th IETF, Minneapolis March 1999 Stephen Casner -- Cisco Systems Colin Perkins -- UCL Mailing list:
Signal Digitization Analog vs Digital Signals An Analog Signal A Digital Signal What type of signal do we encounter in nature?
Roni Even Jonathan Lennox Mapping RTP streams to CLUE media captures draft-even-clue-rtp-mapping-03 IETF-84.
Gonzalo Camarillo Advanced Signalling Research Lab 48th IETF MMUSIC WG Gonzalo Camarillo draft-camarillo-sip-sdp-00.txt.
HDTV Video and AC-3 Payload Formats Ladan Gharai Allison Mankin USC/ISI.
M337 Standards Based Video Interop Interoperability modelling for Video Skype for Business Video Interoperability Server (VIS)
H.323, IP Multicast Conferencing, And TAPI 3.0 Don Ryan Development Lead Windows Networking And Communications Microsoft Corporation.
13 Dec 2000AVT WG - 49th IETF1 RTCP-based Feedback: Concepts & Message Timing Rules draft-wenger-avt-rtcp-feedback-01.txt Stephan Wenger TU Berlin
RTP Payload Format for Payload Meta-Information draft-serenyi-avt-rtp-meta-00.txt Denis Serenyi QuickTime, Apple.
SIP and SIPPING WGsMay, IETF Interim Meeting Orit levin Conferencing Requirements for SIP Based Applications.
XRBLOCK IETF 84 Vancouver RTCP XR Report Block for QoE metric Reporting draft-ietf-xrblock-rtcp-xr-qoe-02 Geoff Hunt Alan Clark Roland Scott.
RTP Payload Format for DV Format Video draft-ietf-avt-dv-video-00.txt Akimichi ogawa Keio university.
Congestion Status Precondition for SIP draft-alexander-congestion-status-preconditions-00.txt Corey Alexander John Rutledge
BUNDLE Christer Holmberg, Ericsson Harald Alvestrand, Google IETF#84, Vancouver.
March 22th, 2001 MMUSIC WG meeting 50th IETF MMUSIC WG meeting The fid attribute draft-ietf-mmusic-fid-00.txt
CLUE Overview and Architecture IETF 82 CLUE ad hoc meeting Allyn Romanow
SIP-SIP Video Delayed Offer-Delayed Offer
Nov 18 th, th IETF MMUSIC WG draft-levin-mmusic-xml-media-control-00.txt O. Levin / RADVISION S. Olson / Microsoft R. Even / Polycom.
A RTCP-based Retransmission Protocol for Unicast RTP Streaming Multimedia draft-podolsky-avt-rtprx-00.txt Matthew Podolsky, Koichi Yano, and Steven McCanne.
RTP Profile for RTCP-based Retransmission Request for Unicast session Koichi Yano (Canon) Matthew Podolsky, and Steven McCanne (U.C. Berkeley) (FastForward.
The Session Initiation Protocol - SIP
1 Ali C. Begen Grouping of Adjacent Media in SDP Cullen Jennings and Ali C. Begen {fluffy, IETF 80 – March 2011 draft-jennings-mmusic-adjacent-grouping-03.
The 3D SDP signalling drafts Bert Greevenbosch
1 SIPREC Protocol draft-portman-siprec-protocol Virtual interim meeting Dec 16, 2010 Authors: L. Portman, H. Lum.
Pitch-to-MIDI Converter Project Presentation - II By Scott Stroupe and Andrew Rogers.
MPEG-4 SL Payload Format
Codec Control for RTCWEB
SMS module HDL-MGSM.431.
Use of “Latent Configurations" in CLUE
SDP Offer/Answer mechanism to negotiate the usage of bundled media
Pedro Capelastegui 3D Video in the Session Description Protocol (SDP) draft-capelastegui-mmusic-3dv-sdp-00 Pedro Capelastegui.
Cisco Unity Connection
RTP: A Transport Protocol for Real-Time Applications
Discussions on Signaling for UL HE MU PPDU
IETF#67 – 5-10 November 2006 FECFRAME requirements (draft-ietf-fecframe-req-01) Mark Watson.
Audio/Video Transport Working Group
O. Levin / RADVISION S. Olson / Microsoft R. Even / Polycom
RTCP XR Blocks for multimedia quality metric reporting draft-wu-xrblock-rtcp-xr-quality-monitoring-04 Zorn ) Qin Wu
This is an ending page..
Running SIP behind NAT Dr. Christian Stredicke, snom technology AG
draft-rajeshkumar-mmusic-gpmd-01.txt 55th IETF – November 18, 2002
draft-ggalimbe-ccamp-flexigrid-carrier-label-02
SIP Basics Workshop Dennis Baron July 20, 2005.
SDP Simple Capability Negotiation (SDP Simcap)
Presentation transcript:

RTP Payload Format for DV Video draft-ietf-avt-dv-video-02.txt This is about the draft of RTP Payload Format for DV Video

updates 01 -> 02 Some minor changes We had feedback from implementers Some implementers consider DV audio only format is not necessary Audio for DV is shuffled Reshuffling is needed to convert DV audio to common audio formats Today’s CPU has enough performance for reshuffling Compatibility with other audio format is much important We had some minor changes when updating the draft from 01 to 02. We also received some issues from implementers for this DV video draft. Some implementers considered DV audio only format is unnecessary. The Audio in the DV format is shuffled. But, Today’s CPU has enough performance for reshuffling in realtime, AND, Compatibility with other audio format is much more important.

Issues When sending unbundled DV stream,,,, Using legacy format (L16, DAT12, L20, L24) is RECOMMENDED RECOMMENDED -> MUST ???? Do not allow DV DIF block only audio When sending DV audio only, use legacy audio format Which do you think is better? RECOMMENDED MUST So, this is the issue for the DV video draft. In the DV video draft, it says, When sending unbundled DV stream, it is RECOMMENDED to send unbundled audio Using legacy format, like, L16, DAT12, L20 and L24. The issue from some implementers, was, to change RECOMMENDED to a MUST. When RECOMMENDED is changed to a MUST, DV DIF block only audio can not be sent. Which do you think is better? Recommended or MUST? We think MUST is too strict.

RTP Payload Format for 12 bits, 20bits and 24 bits DV Audio draft-ietf-avt-dv-audio-01.txt This is about the RTP Payload Format for 12 bits, 20bits and 24bits DV audio.

Changes (added non AIFF-C audio channel convention) DV audio channel allocation DAT12 audio mode in DV format has maximum of 8 channels For example… Audio with…. Left, Right, Center, Woofer, Left Surround, Right Surround AIFF-C can not specify “woofer” AIFF-C only contains location information Non AIFF-C audio channel convention was added to this draft. This was needed because, DAT12 audio mode in DV format has maximum of 8 channels, AND, for example the audio channel can go like, Audio with left, right, center, woofer, left surround, and right surround. And when trying to show the audio channels in a AIFF-C manner, the allocation of some channels can not be done. For example, AIFF-C can not specify “woofer”.

SDP format for audio channel convention a=fmtp:<payload type> channels:<channel convention> [<symbol1 [/symbol2…]>] ・ channel convention   - AIFF-C (default)  - DV ・ symbols (next page) This is the SDP format for audio channel convention. We defined a new fmtp record to resolve the channel allocation issue. “Channels” field represent the channel convention The symbols stand for each channel.

Symbols used for DV(1) L: Left channel of stereo R: Right channel of stereo M: Monoral signal C: Center channel of 3,4,6 or 8 ch stereo S: Surround channel of 4 ch stereo LS, LS1, LS2: Left surround channel RS, RS1, RS2: Right surround channel These are the name of the channels. L is left channel of stereo R is right channel of stereo M is monoral C center S surround, LS LS1 LS2 are left surround channel RS RS1 RS2 are right surround channel

Symbols used for DV(2) LC: Left center channel of 8 ch stereo RC: Right center channel of 8 ch stereo Q1: 0.7071LS + 0.7071RS Q2: 0.7071LS - 0.7071RS WO: Woofer channel Lmix: L + 0.7071C + 0.7071LS Rmix: R + 0.7071C + 0.7071RS T: 0.7071C These are also channels description for DV audio.

SDP example v=0 o=ikob 2890844526 2890842807 IN IP4 126.16.64.4 s=POI (Audio only) i=A Seminar of how to make Presentation u=http://www.koganei.wide.ad.jp/~ikob/index.html e=ikob@koganei.wide.ad.jp (Katsushi Kobayashi) c=IN IP4 224.2.17.12/127 t=2873397496 2873404696 m=audio 49170 RTP/AVP 112 113 a=rtpmap:112 L16/48000/2 a=rtpmap:113 DAT12/32000/4 a=fmtp:113 contents:DV L/R/C/WO Audio is sent using RTP payload type 112 and 113 Payload type 112 sends L16 audio Payload type 113 sends DAT12 audio This is a SDP example. Audio is sent using RTP payload type 112 and 113. Payload type 112 sends L16 audio. Payload type 113 sends DAT12 audio. DAT12 audio contains 4 channel audio : left, right, center and woofer. DAT12 audio contains 4 channel audio : Left, Right, Center, Woofer

Use of audio channels attribute Audio “channels” attributes AIFF-C (this is default) DV AIFF-C MUST be use if possible DV is used when channel allocation is beyond AIFF-C convention AIFF-C will be used for default for The audio “channels” attribute. And, when AIFF-C can not show the description for the audio channels, channel description DV is used. If you have interest, we can show the sample implementation of the DV over RTP. Please contact us when we are in the terminal room. Thank you.