[Live-devel] Queries related to Streaming MP3 clips using LIVE server.

[Sathish Kumar Manohar]

One more update on this:

Moreover from the Initial 1 or 2 bytes of the payload, I am not able to find any valid ADU Descriptor Information.
Is there any problem in sending that information from the server?

________________________________
From: live-devel-bounces at ns.live555.com [mailto:live-devel-bounces at ns.live555.com] On Behalf Of Sathish Kumar Manohar
Sent: Tuesday, November 10, 2009 11:35 AM
To: live-devel at lists.live555.com
Subject: [Live-devel] Queries related to Streaming MP3 clips using LIVE server.

Hi Ross,

I have some doubts regarding the RTP Payload for MP3.

1) When I received the payload it's something like this
    00 00 00 00 ff e3 e8 .....
    The valid data starts only after 4 bytes in all the cases. Why is that so?

2) I tried streamed a clip with the following configuration
       MPEG 2.5 Layer III
       160kbps , strereo,
       Sampling Rate: 8000 hz

     In this case, the size of the Computed frame is 1440. So single frame comes in 2 RTP packets.
     The payload length in the first packet is 1436. The payload looked like this
     00 00 00 00 ff e3 e8 ....

    In the second RTP packet, the payload length was 12. And the 12 bytes looks like this
    00 00 05 98 00 00 00 00 00 00 00 00.

    Now I have to give 1440 bytes to my decoder. From the first packet the valid data starts after 4 bytes,
    So the valid data would be of size 1432 bytes. From the Second packet which 8 bytes should I give the
    decoder?. First 8 bytes or last 8 bytes.


  I have attached the ethreal logs also.  Kindly look into them and give your suggestions.
 Also let me know the general rule in handling the continuation frames,  coming in multiple RTP Packets.



Regards
Sathish Kumar M

________________________________
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."

________________________________
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20091111/7bc1a5c0/attachment.html>