Re: Playing captured speex frames

Adding ogg header won't do. The ogg is an envelope, not a header.
Lemme see the speex code and mail you the results. I remember that
speexdec processes raw packets and not ogg. There must be an issue
with wireshark itself. Can you send me the output from wireshark?
- farhan

On 7/8/11, Shridhar, Vasant <[email protected]> wrote:
> Speexdec is expecting the frames to be wrapped in an Ogg frame I believe.
> Since you have the raw data can't you just add the Ogg header information to
> this before passing it to Speexdec?
>
> Vas
>
> ________________________________________
> From: [email protected] [[email protected]] On Behalf Of
> Vinod Panicker [[email protected]]
> Sent: Friday, July 08, 2011 12:13 AM
> To: [email protected]
> Subject: Re: [Speex-dev] Playing captured speex frames
>
> On Fri, Jul 8, 2011 at 6:39 AM, Ashhar Farhan <[email protected]> wrote:
>> what you need to do is this: take the wireshark raw dump, read each
>> udp packet and write it back to another file. While writing back to
>> the new file skip the sizeof udp header + rtp header. I can't recall
>> how many bytes you need to skip, however, I suppose it would be in the
>> range of 36 and 32 bytes. A five line perl script will do it.
>
> Thanks for the suggestion, but Wireshark already does what you've
> suggested. There's an option to save the raw payload to a file. This
> file only has the speex frames (no udp+rtp headers). speexdec still
> complains about it not being a valid speex file presumably because the
> file is missing the header.
>
> Apart from manually constructing a header and prefixing it to the
> file, any other ideas?
>
> Regards,
> Vinod.
> _______________________________________________
> Speex-dev mailing list
> [email protected]
> http://lists.xiph.org/mailman/listinfo/speex-dev
> _______________________________________________
> Speex-dev mailing list
> [email protected]
> http://lists.xiph.org/mailman/listinfo/speex-dev
>

-- 
Sent from my mobile device