Method and system for predicting a latency spike category of audio and video streams to adjust a jitter buffer size accordingly

[0001] This application is a continuation application of U.S. patent application Ser. No. 13/087,167, filed Apr. 14, 2011, entitled “METHOD AND SYSTEM FOR PRECISE SYNCHRONIZATION OF AUDIO AND VIDEO STREAMS DURING A DISTRIBUTED COMMUNICATION SESSION WITH MULTIPLE PARTICIPANTS, which is a divisional application of U.S. patent application Ser. No. 12/024,089, filed Jan. 31, 2008, now issued as U.S. Pat. No. 7,949,980 issued on May 24, 2011, entitled METHOD AND SYSTEM FOR PRECISE SYNCHRONIZATION OF AUDIO AND VIDEO STREAMS DURING A DISTRIBUTED COMMUNICATION SESSION WITH MULTIPLE PARTICIPANTS. This application is a non-provisional application and claims priority to U.S. Provisional Patent Applications No. 60/887,555, filed Jan. 31, 2007, and entitled “METHOD AND SYSTEM FOR LOW LATENCY HIGH QUALITY MUSIC CONFERENCING” by Surin et al, all of which are herein incorporated by reference.

[0002] Synchronization is critical to many aspects of distributed communications. In a multiway audio video conferencing session it is important to keep audio and video streams from all the participants in synch with each other as well as pay special attention to audio and video synchronization. In gaming applications it is important to synchronize clocks and multimedia data sent between the players, handicap players with faster connection so that everybody in the system plays in the common time frame.

[0003] It is highly desirable in the above applications to implement synchronization methods to fight with network imperfections such as jitter and other delays affecting the quality of audio and/or video stream due to increasing synch latency. The current invention addresses some of the toughest problems regarding synchronization in a multiway multimedia communication system. The examples of such a system can be in audio/video conferencing, live music concerts by remote musicians playing together over the Internet, as well as multi-player gaming.

[0004] Described are the architecture of such a system, algorithms for time synchronization during a multiway conferencing session, methods to fight with network imperfections such as jitter to improve synchronization, methods of introducing buffering delays to create handicaps for players with faster connections, methods which help players with synchronization (such as a synchronized metronome during a music conferencing session), methods for synchronized recording and live delivery of synchronized data to the audience watching the distributed interaction live over the Internet.

[0013] FIG. 1 depicts an example of synchronized multi-way audio and video conferencing system audio pipeline architecture. Among most important modules for the precise synchronization of audio and video streams are the following (marked with bold borders on the diagram):

[0014] 1. Synchronization Module 102

[0015] 2. Playout Buffer Module 104

[0016] 3. Local Delay Module 106

[0017] 4. Mixer Module 108

[0018] 5. Recording Synch Module 110

These 5 major components are described in detail in separate sections of this document below.

[0019] The purpose of other components in the pipeline architecture is as follows:

[0020] 1. AudioStack 112: captures input sound, passes it to three components: LocalDelay 106, FrameBuffer 114, SoundHistory 116; also it passes a sound rendered by Mixer to output (speakers). The pipeline is implemented to support various audio interfaces such as ASIO or Kernel Streaming to communicate with the kernel mode audio stack. An example of an audio stack 112 is a low latency high quality audio stack described in 2007/0223675 patent application.

[0021] 2. FrameBuffer 114: Stores a sound from inputs of AudioStack 112—to be used by Encoder 118 with possibly different buffer sizes.

[0022] 3. Encoder 118: gets needed quantity of sound from FrameBuffer 114 using blocking Render( ) method, then encodes it with selected options, produces an encoded page and passes it to PacketBuilder 120.

[0023] 4. PacketBuilder 120: builds packets to be passed over Network. When a new encoded page is received, it adds synchronization data (see the corresponding section). It also adds audio re-send requests into the outgoing packets in case of packet loss.

[0024] 5. PacketCoder 122: adds packet header: packet serial number, bytes sent and so on. Also it produces FEC XOR packet based on each “n” packets passed. All the “n” packets with FEC XOR packets are sent to all the participating hosts using UdpSocket 124 (relayed or multi-send “multicast emulation”, see the corresponding section).

[0025] 6. FecQueue 126: Network receives packets from UdpSocket 124 and puts it to the FecQueue 126 corresponding to the sender's connection. FecQueue is used to “buffer” network packets and to correct packet drops using FEC XOR packets. When simple packet or XOR packet is received, it determines if “next” packet can be produced (already exists or can be recovered using FEC XOR packet) and if so passes it to the PacketDispatcher 128 of the corresponding receive pipeline.

[0026] 7. PacketDispatcher 128: splits received packets into encoded page, synch data and re-send requests. This very component does the processing of the synchronization section data and then passes the encoded page to the Decoder 130. The re-send requests are directed to the PacketBuilder 120 to re-send the lost packet (packet not delivered to the session peer).

[0027] 8. Decoder 130: performs decoding process and also sound repair in case of packet loss (if the codec supports this). Passes decoded and repaired portion of sound to the Playout Buffer 104. On successful decoding: puts the sound portion to the Recording component, otherwise puts a “sound resend” request to the PacketBuilder.

[0028] The same pipeline architecture is used for handling video streams. The audio and video pipelines share the following modules:

[0029] 1. Synchronization 102

[0030] 2. Mixer 108

[0031] 3. RecordingSynch 110

[0032] 4. QualityFeedback 130

[0033] The following modules share the common functioning principles, yet handle audio and video data using similar yet different algorithms in audio and video pipelines:

[0034] 1. PacketBuilder 118

[0035] 2. PacketCoder 122

[0036] 3. PacketDispatcher 128

[0037] 4. FecQueue 126

[0038] 5. FrameBuffer 114

[0039] A receiving pipeline is used for each incoming connection. The playout buffers 104 share their “I want to keep this delay” values and keep the shared delay. If some of the playout buffers 104 “can keep” the delays more than the comfortable one (option selected by the user), their “I want to keep” delays are thrown away when calculating the shared delay value. This shared delay value is the one to be passed to the LocalDelay module 106 as the network delay. If some of the playout buffers 104 can keep delay less than the shared delay value, it keeps the delay equal to the shared delay.

[0040] FIG. 2 depicts an example of a Multicast 202, Copy-send 204, and Relayed Multicast 206 in case of N=4. Each client 208 sends its outgoing stream to all other peers in the jam session. If UDP multicasting is available, it is used for audio streaming 202. Otherwise, it sends N−1 copies of each packet to all N−1 participating computers 204. If the uplink bandwidth is not sufficient to send N−1 packets directly to all other participating computers, the relay server 210 is used 206. When the relay server 210 is used, the client 208 sends only one outgoing stream to the relay server 210 and the relay server 208 re-sends the packets to all other participating computers. The relay server should be selected from the server pool in the way that has the minimal network latency among the connections in the jam-session (min max latency).

I. Synchronization Module: A Common Time System Algorithm for a Distributed Audio/Video Conferencing Session With Multiple Participants

[0041] There is a problem that clock generators on different computers are not working exactly synchronously. Moreover, even if we synchronize the 2 PC clocks exactly at a given moment the difference in time can be as high as 20 ms after 10 minutes. This happens due to the fact that the embedded clocks on different PC have slightly different accuracies. 20 ms of synch latency during 10 minutes is quite a lot: if a distributed broadcast lasts for an hour without interruption the total latency generated due to differences in clock generators will total as much as 120 ms which would make the performance impossible practically after half an hour. In order to address this problem an algorithm of precise computer clock synchronization was invented. As a universal time measure Ti for a Synchronized Multi-Way Audio and Video Conferencing session the number of sound samples played from the beginning of music session divided by the audio card's sample rate is used.

[0042] Let t be the absolute time (here we neglect the effects of Einstein's relativity theory), then for each computer in the network its local time Ti is
Ti(t)=(1+r(t))*t+c₀(t),  Equation 1

[0043] where r is a specific, almost constant, value for each computer with a uniform distribution between computers; the order of r is 10⁻⁴ sec; r and c₀ are functions of t.

[0044] The time source we use for audio is the amount of sound itself. Number of samples can be converted into convenient time by dividing it by sample rate (e.g. 48000 samples per second). The sound is divided by the audio driver into buffers of a constant size (e.g. 256 samples≈5.3 ms), so the “audio time” increases with steps equal to buffer size (in ms). In order to have “smoother” time, between the moments of buffer change the “local time” is interpolated using the system clock the following way:

[0045] 1. Set the last LocalTimeResult the value of 0.

[0046] 2. With each audio buffer change, the value of Tstart is set getSystemTime( )

[0047] 3. getLocalTime( ) returns value of max(lastLocalTimeResult, min(getSystemTime( ) −Tstart, BufferSizeInMs)+NumberOfSamples/SampleRate) and stores this value to the lastLocalTimeResult variable, where BufferSizeInMs is audio card buffer size in ms, SampleRate is in kHz.

[0048] This allows for smoother local time calculation than simply using “NumberOfSamples/SampleRate”. FIG. 3 depicts an example of a smoother local time calculation result (line 302 compared to stepwise line 304) using the above method.

[0049] The algorithm synchronizes Synchronized Multi-Way Audio and Video Conferencing session time □ on each participating computer by adding a correction value ΔTi to local time Ti.
□(t)=T_i(t)+ΔT_i  Equation 2

[0050] In order to synchronize capture and render times of the local sound with (non-synchronized) sound streams of the remote participants the algorithm uses slightly changes the reading sample rate of the remote sound stream (by throwing away or adding 1 sample per 10 ms). The resampling of order of 0.02% is indistinguishable: 48000 samples per second are resampled either to 48010 or 47990.

[0051] FIG. 4 depicts a diagram of example clock synchronization, where white circles show the moments the computers are ready to send audio packets. The algorithm to determine ΔT_i for a pair of computers where one of them is treated as an “absolute time” generator is as follows:

[0052] 1. One of the computers is defined to be the computer with the “absolute time” (A) 402, all the others are “non-absolute” (N) 404.

[0053] 2. Let RTT_app, be the current best approximation of the network Round-Trip-Time between computers N 404 and A 402.

[0054] 3. Computer A 402 has the t_A,last and t_N,last registers with initial values set to 0

[0055] 4. Periodically (with the period of several seconds) the computers exchange synchronization packets and measure round-trip time RTT. If RTT is more than a D=1.05*RTT_app then the synchronization cycle is discarded because a jitter spike is likely to have occurred. The algorithm is as follows:

[0056] Before sending each audio packet to the computer A 402, the computer N 404 computes t₁=getLocalTimeN( ); and writes t₁ into the synchronization section (synchronization request). When computer A receives the packet, computes t₂=getLocalTimeA( ). If t₁>t_N,last, sets t_A,last the value of t2 and sets t_N,last the value of t₁ from the packet. Before sending each audio packet to the computer N, the computer A calculates t′₂ and writes (t′₁=t₁+t′₂−t₂, t′₂) into the synchronization section (synchronization reply) if such a reply wasn't sent for this value of t_N,last.

[0057] When computer N receives packet with (t′₁,t′₂), do the following:

[0058] 1. Compute t₃=getLocalTimeN( ).

[0059] 2. Computer N calculates RTT=t₃−t′₁.

[0060] 3. If RTT_app value is undefined, assign RTT_app the value of RTT.

[0061] 4. If RTT<1.05* RTT_app, assign RTT_app the value of min(RTT_app+RTT_drift, RTT), otherwise go to step 1.

[0062] 5. In case of ideal synchronization (r is not a function oft) t′₂≈(t′_1+t3)/2 where the error is much less than (t₃−t′₁)/2 and this is the reason why we discarded the “slow” round-trips (RTT>D=1.05 * RTT_app).

[0063] 6. Let □T_N-A(t) be the mean value of (t′2−(t′1+t3)/2) for the last 1000 cycles (or less, if not enough data is buffered yet).

[0064] 7. Assign □T_N the value of □T_N-A for the computer N.

[0065] 8. Calculate corrected session time for the computer N as the following:
□(t)=T_N(t)+ΔT_N.

[0066] Computer A keeps □T_A equal to 0. RTT_drift is introduced in order to adapt to possible growth of packet round trip time (e.g. due to a change of packet routing). The inventors have experimentally found the value of RTTdrift to be 1 ms divided by the synchronization cycle rate in Hz. As the synchronization replies store both the answer and the request time, there's no need for any sequence identification numbers.

[0067] Synchronization information is added to each data packet so that the Synchronized Multi-Way Audio and Video Conferencing session times on participating computers can be synchronized to a very high degree of precision (equal to computer clock definition).

[0068] The above algorithm is asymmetric, because one computer uses a correction to its local time to calculate the Synchronized Multi-Way Audio and Video Conferencing session time and the other doesn't. Suppose we have computers B and C. In order to synchronize them in a symmetric way two simultaneous synchronization algorithms described above are used with the following modification:

[0069] 1. Computer B treats computer C as absolute, calculates ΔT_B-C using the above procedure and ΔT_B=ΔT_B-c/2.

[0070] 2. Computer C treats computer B as absolute, calculates ΔTC-B using the above procedure and ΔT_C=ΔT_C-B/2.

[0071] 3. For the sake of optimization, both computers make only synchronization replies after they receive first synchronization requests.

[0072] In case of N computers' synchronization, there are the following additions:

[0073] 1. Each computer i synchronizes with all the others using the above symmetric algorithm and calculates ΔT_i=ΣΔT_i-j/N, where □T_i-i=0

[0074] 2. For the N-way case we use multicasting, N-sends or relay multicasting as shown in FIG. 2. Thus, all the packets from any of the computers are sent with the same data. To allow for this the synchronization reply format is slightly changed, now it incorporates also the identification number of the sender of the request replying. Synchronization request format is unchanged in the N-way case.

[0075] 3. Each computer makes synchronization replies to all the others in a round-robin manner.

II. Playout Buffer Module

[0076] Synchronized Multi-Way Audio and Video Conferencing system which uses Internet Protocol for the transport of music data is prone to defects in audio and video quality due to random variations of latency across the transport path. These variations, called jitter, have spiky character depend on the traffic routes and are out of control of Synchronized Multi-Way Audio and Video Conferencing software. FIG. 5 depicts a graph of network latency example with very high jitter (a graph of time propagation for each packet). FIG. 6 depicts a graph of network latency example with very relatively low jitter (a graph of time propagation for each packet). Ways to manage jitter can be performed by the plavout buffer module of FIG. 1 or the participating computer 204 of FIG. 2, including: receiving the audio signal; storing data from the audio signal in a jitter buffer; dynamically adiusting the size of the jitter buffer in order to address litter in the specific network, analyzing latency spikes of the audio signal in the specific network; determining that a given latency spike is beginning; predicting characteristics of the given latency spike; and changing the size of the litter buffer according to the predicted characteristics of the given latency spike.

[0077] The jitter can result in sound glitches and distortions. For example, if the latency suddenly increased to 100 ms the sound we have no sound to play during those 100 ms unless we have a sufficient supply of sound data. If we have no sound to play the short period of silence will appear as an unpleasant pop or a click or a glitch unless a special algorithm described below is applied.

[0078] The common way of addressing jitter problems is to have a sufficient supply of sound data so that we always have some sound to play. This technique is called buffering and the buffer is called “jitter buffer” and is commonly used in many Voice over IP applications.

[0079] Jitter buffer size is measured in milliseconds—the larger it is, the less the probability of glitches, but the more the overall latency of the system. For example, if jitter buffer size is 100 ms, then jitter less than 100 ms can be handled without sound distortions but the latency introduced by jitter buffer is also 100 ms.

[0080] In order to minimize the total latency the buffer size must dynamically change adapting to the changes of packet latency. This technique is commonly referred to as the ‘adaptive jitter buffer’. In the ideal case the graph of the jitter buffer size must be exactly the same as the graph of the packet propagation latency in the given network scenario. The main problem is that both the moment of the “latency splash” and the size of the splash are completely unpredictable.

[0081] The jitter buffer algorithm of Synchronized Multi-Way Audio and Video Conferencing system proposed here has the goal to deliver the maximum quality of music being transmitted while maintaining minimal latency. The jitter buffer algorithm disclosed herein is performed by the playout buffer module. The algorithm has two parts: 1) analyzing the nature of latency spikes in the given network, predicting the main characteristics of the spike including determining spike size categories of the latency spikes as soon as a latency spike begins to appear, and changing the buffer size correspondingly; 2) synthesizing sound to play when the playout buffer 104 is empty due to a large spike.

[0082] 1. The algorithm analyses latency statistics for the period of 1-5 minutes to determine the nature of spikes and calculates average jitter characteristics. There are 3 categories of spikes: large (A category), medium (B category) and small spikes (C category). For each spike category A, B and C the algorithm determines average, minimum and maximum for the following values: spike peak (ms), duration between spikes, total duration of spike, spike “ascend time” (period of time from the moment when spike begins until the moment when it reaches its peak), spike “descend time” (period of time from the moment when spike reaches its peak until the moment it ends). A linear approximation is used to model spikes.

[0083] This data is used to predict the kind of spike as soon as it begins to appear and adjust jitter buffer size accordingly. The user of the Synchronized Multi-Way Audio and Video Conferencing system can select whether he/she prefers the minimal latency or the best quality. In this way the user indirectly affect the “insurance level” of the jitter buffer. The insurance level is a number of milliseconds in jitter buffer size beyond the current average latency, i.e. if the network latency is currently 10 ms and jitter buffer size is 30 ms, then the “insurance level” is 20 ms. In general the insurance level is being kept as low as possible (depending on the behavior of the network).

[0084] 2. Sometimes spikes may exceed its peak levels and the playout buffer 104 may become empty. The Synchronized Multi-Way Audio and Video Conferencing system which takes sound quality as a high priority can't afford just to play the silence which would result in a pop or a click. An algorithm to synthesize short portions or pieces of music based on the previously played material is used to fill the gaps. Note that such algorithms are useful only for music transmission. For voice transmission you can use much simpler and more effective techniques which take advantages of the frequent pauses during the conversation. These pauses however don't take place during the musical performance and while people having a conversation over a VoIP solution can afford to make such pauses musicians can't because the performance will be ruined. So this is a novel approach which is only well-taken for real-time transmission of music data.

[0085] One embodiment teaches a method of filling such a gap. The method assumes generating a short fragment of sound based on fragments of the waveform played previously. This software-generated fragment of sound is ‘smoothly glued’ with the previously played sound and the sound which arrives later thus filling the gap. This approach allows not to resend packets and not to increase latency and to better synchronize sound streams from multiple participants.

[0086] The choice of the most suitable in terms of smooth splicing wave fragment is based on the minimization of the following discreet functional:

[0087] $\begin{array}{cc}F\left(x\right)=\sum _{i=0}^LW_{c+i}-W_{c+i-x}·\left[1+\frac{P\left(L-i\right)}{2}\left(1+\mathrm{sign}\left(i-\left(L-X_0\right)\right)\right)\right],\mathrm{where}x\in \left[L,2L\right]& \mathrm{Equation}3\end{array}$

[0088] In Equation 3, c is the number of the samples on which the procedure of information recovery due to the playout buffer devastation is invoked, W_k is the value of the discreet approximation of the wave function on sample k, L is the length of the “sound window” used to find the optimal (in terms of min F(x)) pre-granular sound fragment, x is discreet wave shift (in samples).

[0089] $\begin{array}{cc}{P}_n\left(i\right)=\sum _{k=1}^n\frac{{A_k\left(X_0-i\right)}^k}{X_0^k}-1& \mathrm{Equation}4\end{array}$
Equation 4 is an example of the weight function of the last X₀ samples.

[0090] By means of experimentation with various audio stream and music instruments the inventors have found out that as a result of the granular synthesis of sound a change in the spectrum of the resulting wave occurs. This effect occurs due to a finite size of a “sound window”. The length of the sound windows L must be 50 ms or more to prevent the feeling of discomfort during the single and double granular sound synthesis (with that approach the base Fourier frequency of the resulting wave is less than 20 Hz, which is the lower limit of audibility for humans).

[0091] After the selection of the optimal time shift interval, the algorithm performs linear cross-mixing W_kand W′_k=W_k-x during 1-2 ms (backward time shift). When the amount of sound data in the playout buffer 104 exceeds a threshold value (about 30 ms), the algorithm performs a forward time shift in the same way as above (W_kand W′_k=W_k+x) and performs linear cross-mixing during the time span of 20 ms.

[0092] A similar technique is used to repair the sound lost due to packet loss for those codecs that do not handle these losses. Suppose we have a contiguous sound stream, than a lost gap. While no further packets are received the playout buffer algorithm behaves as if a jitter spike had occurred. When the packet after the gap is received (we can determine the gap by the packet sequence number and by the start and length information stored inside packets) we should synthesize a sound to fill the gap. Using the above algorithm an appropriate sound before the gap is found, then it is cross-mixed with the entire last packet and with some sound before the gap (actually, with all the sound between the read cursor and the start of the gap, or 1 ms, which value is bigger)

III. Local Delay Module

[0093] LocalDelay introduces a delay to the local sound according to the synchronization algorithm (see N-way section below). This algorithm dynamically estimates the “common delay” according to the delays of incoming audio streams (from all remote peers). This “common delay” could be a mean value of the delays of the peers, maximum value of those delays or some composition of these values.

[0094] Local delay module can gradually change the value of delay introduced re-sampling 1000 samples to 1001 or 1000 samples to 999. This leads to increasing or decreasing the local delay by 1 ms per second. Also using the algorithm similar to the Playout Buffer's granular synthesis, local delay can instantly change its delay value by 10-20 ms. The local delay value should decrease while local musician is not playing to allow easier adaptation. The value to decrease the local delay should be adjustable between 0 ms and 70 ms. After the local musician started playing the local delay value should increase to the “common delay” estimated by the synchronization algorithm. This method allows reduce perception of overall system latency by synchronization musicians with the help of shared drum machine.

[0095] FIG. 7 depicts a diagram of an example of a shared drum machine. Shared drum machine in this context is a set of recorded drum samples which are played simultaneously on all hosts. Drum samples are wave samples for different drums or metronome “tick” sound for synchronized metronome use. These samples encoded using our lossless audio codec and stored in a single file present a “samples bank” that can be easily shared among the performance participants. The musician combines different drum samples into single track then sequence of samples is transmitted to all hosts. For the playback of these samples a drum machine component is used. This component is capable of mixing large numbers of wave samples into an audio stream to be passed to the main mixer (see the diagram). Using the synchronized clock (see the corresponding section above), all the hosts' drum machines start to play the samples in a synchronized manner. As the drum samples are short wave samples (about a second or less), no resampling is needed

[0096] Synchronized wave player is another enhancement of the synchronized drum machine and is used for orchestration or rhythm support during live music session. Wave track can be previously recorded by the system or can be any other file encoded in any format supported by the system. When a musician choose track the system transmits it to all the hosts involved in Synchronized Multi-Way Audio and Video Conferencing session. The file is decoded to PCM format and synchronization time-stamps are inserted into it. After session started stream mixer reports about time stamps played and re-samples wave stream as needed the same way as described in synchronized drum machine discussed above in this section.

IV. Mixer and Recording Synch Modules

[0097] Recording of live performances can be done in the client server manner, but this way it introduces dedicated server and accordingly reduces system scalability. Moreover client-server solution requires one more data channel that consumes additional bandwidth.

[0098] But from the other side recording performance locally on the client can add additional performance overhead which may produce audio glitches. It occurs due to many decode video/encode video procedures which are very CPU consuming tasks. In the current system another approach was invented. Deferred recording method is used. Recording process is split in 3 parts:

[0099] 1. Storing both audio and video data from the network and from local video capture device and sound card on the local hard drive without any processing (encoded audio and video from remote participant and raw captured audio and video from local participant).

[0100] 2. Playing stored audio and video without any processing. Synchronization between audio and video is achieved by time-stamping currently recording video frame by the number of the audio sample which is playing at the same moment.

[0101] 3. Editing, mixing, encoding. This allows creating a multi-channel high-quality audio video recording which can be edited and remixed ever after by video mixing tool which is the part of the system.

[0102] 4. Transmitting data to the web site backend.

[0103] All the peers store all the outgoing sound streams locally using our lossless audio format after the a/v conferencing session has stopped. All the audio channels and streams are stored separately from each other in the recording container file. The recording container file also stores all the output generated by the synchronization module. This data is used to synchronize mix the participants' audio and video streams. These files can be sent to one PC (a mixing server or of one of the players) where, using the synchronization data, audio streams could be easily synchronized and exported as tracks and a project file to any multi-channel audio software for further processing.

[0104] FIG. 8 depicts an example diagram of a detailed description of formats of the recording container file. Header with version information 802 contains 4 bytes protocol identifier and a 4 bytes version number. All other blocks on the diagram are so called chunks. Each chunk has type (4 bytes), size (4 bytes) and payload with size specified in chunk's “size” field. Payload is varying depending on the chunks type. If chunk type is unknown to the reader, it can skip the chunk by moving the file pointer. Stream Format Chunk 804 contains description of the audio and video streams i.e. codec, bitrates, image dimensions etc. Audio Chunk 806 and Video Chunk 808 each contain audio and video content. Metadata Chunk 810 contains metadata of the recording container file.

[0105] Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.