Intel® Integrated Performance Primitives
Deliberate problems developing high-performance vision, signal, security, and storage applications.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
6814 Discussions

GSM Codec

harald85
Beginner
‎07-13-2009 07:06 AM
468 Views
Hi
I use the GSM and G729 codec for an rtp Stack but know i have an Problem. I initialize the Codec at the beginning of the program and then i use for every rtp session these codecobject. When one rtp session is active it works fine but when i start an second rtp session i have a noise in the audiostream. The both rtp session are simultaniur active and the encoding is done one after one. Must I initilaize the codec every time when i encode an new rtp session?

Harald
0 Kudos

Link Copied

1 Reply
Vyacheslav_Baranniko
New Contributor II
‎11-25-2009 05:14 AM
468 Views
Quoting - harald85
Hi
I use the GSM and G729 codec for an rtp Stack but know i have an Problem. I initialize the Codec at the beginning of the program and then i use for every rtp session these codecobject. When one rtp session is active it works fine but when i start an second rtp session i have a noise in the audiostream. The both rtp session are simultaniur active and the encoding is done one after one. Must I initilaize the codec every time when i encode an new rtp session?

Harald
Hi Harald,

EachRTP session must be processed by separate USC codec instance.

Regards,
Vyacheslav
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.