hi how cani find this source code of g.729..this codec using CS-ACELP algorithm and ineed codes of this compressing algorithm..
g.729 codec matlab source code
Started by arda, Dec 21 2006 02:26 PM
7 replies to this topic
#1
Posted 21 December 2006 - 02:26 PM
#2
Posted 21 December 2006 - 07:42 PM
Google.
reedbeta.com - developer blog, OpenGL demos, and other projects
#3
Posted 22 December 2006 - 08:15 PM
google? i search google for hours but i found nothing man!!
#4
Posted 22 December 2006 - 09:35 PM
There is nothing that guarantees you will find something, but there are good ways to search for something. Google is very effective.
If you don't find something, the simplest explanation is that it's just not there. MATLAB source code of advanced codecs are not exactly widespread. If you're lucky you might find C implementations though.
Is this for a school project? In that case you probably should be able to implement it yourself with what you've learned in the course and the specifications that are available. If not, contact your instructor...
If you don't find something, the simplest explanation is that it's just not there. MATLAB source code of advanced codecs are not exactly widespread. If you're lucky you might find C implementations though.
Is this for a school project? In that case you probably should be able to implement it yourself with what you've learned in the course and the specifications that are available. If not, contact your instructor...
#5
Posted 24 December 2006 - 07:19 PM
yes its a school project but i cant do it myself because itis very hard to write the source codes...if i can find some codes iwill study on these codes and iwill make some changes
#6
Posted 24 December 2006 - 10:29 PM
If the assignment is too difficult then your fellow students will have the same problem and you can ask your profs for a solution. Otherwise you have to study a bit more, but hey, you don't get your (degree/title/whatever you get) for free ;)
#7
Posted 25 December 2006 - 06:32 AM
i know this and i dont want to reach to the codes for free.. but i need any idea or nay codes for the start
#8
Posted 26 December 2006 - 09:02 AM
It is part of your education to learn how to deal with large and complex tasks. One of the basic approaches is to split it into small and simple tasks and work incrementally.
This is an audio codec, so first set up a framework where uncompressed audio goes into a coder, it's sent through a channel, gets decompressed in the decoder, and then is made audible. In your first version the coder, channel and decoder don't have to do anything. Just make sure you get the structure right and can pass the data through. A small and simple task.
CS-ACELP is based on ACELP, and ACELP, is based on CELP, and CELP is based on LPC. So start with the latter, a small and simple task, and verify that it works correctly by testing it with the framework. Only then implement the changes for CELP, ACELP, and CS-ACELP. All small and simple tasks. In the end you have completed a large and complex task.
During the process you could look for other implementations, but in general this will just slow you down. If something doesn't work, split it into even smaller pieces and test each of them individually.
Just start coding. Good luck!
This is an audio codec, so first set up a framework where uncompressed audio goes into a coder, it's sent through a channel, gets decompressed in the decoder, and then is made audible. In your first version the coder, channel and decoder don't have to do anything. Just make sure you get the structure right and can pass the data through. A small and simple task.
CS-ACELP is based on ACELP, and ACELP, is based on CELP, and CELP is based on LPC. So start with the latter, a small and simple task, and verify that it works correctly by testing it with the framework. Only then implement the changes for CELP, ACELP, and CS-ACELP. All small and simple tasks. In the end you have completed a large and complex task.
During the process you could look for other implementations, but in general this will just slow you down. If something doesn't work, split it into even smaller pieces and test each of them individually.
Just start coding. Good luck!
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users











