Mercurial > mplayer.hg
comparison DOCS/tech/codec-devel.txt @ 29263:0f1b5b68af32
whitespace cosmetics: Remove all trailing whitespace.
author | diego |
---|---|
date | Wed, 13 May 2009 02:58:57 +0000 |
parents | 4c9698666a4c |
children | 0ad2da052b2e |
comparison
equal
deleted
inserted
replaced
29262:7d545a6b8aff | 29263:0f1b5b68af32 |
---|---|
72 FOURCCs/format numbers, output formats, and a unique driver name. Remember | 72 FOURCCs/format numbers, output formats, and a unique driver name. Remember |
73 the driver name. | 73 the driver name. |
74 | 74 |
75 Next, create a new source file which contains the main decoding function | 75 Next, create a new source file which contains the main decoding function |
76 that MPlayer will call to decode data. Eventually, you may have multiple | 76 that MPlayer will call to decode data. Eventually, you may have multiple |
77 files which comprise your decoder, but let's start simple here. | 77 files which comprise your decoder, but let's start simple here. |
78 For audio codecs, see ad_sample.c skeleton. For video, choose one of the | 78 For audio codecs, see ad_sample.c skeleton. For video, choose one of the |
79 existing vd_*.c files which you think is close to your codec in behaviour. | 79 existing vd_*.c files which you think is close to your codec in behaviour. |
80 | 80 |
81 Next, modify the Makefile so that it will compile your new source file. | 81 Next, modify the Makefile so that it will compile your new source file. |
82 Also, add your codec to the array in ad.c (for audio) or vd.c (for video). | 82 Also, add your codec to the array in ad.c (for audio) or vd.c (for video). |
186 development team for approval. You will likely need to diff the following | 186 development team for approval. You will likely need to diff the following |
187 files: | 187 files: |
188 - Makefile | 188 - Makefile |
189 - etc/codecs.conf | 189 - etc/codecs.conf |
190 - ad.c or vd.c | 190 - ad.c or vd.c |
191 Of course, you will need to include your newly-created file(s): | 191 Of course, you will need to include your newly-created file(s): |
192 vd_<name>.c -OR- ad_<name>.c. If you contribute enough decoders, the | 192 vd_<name>.c -OR- ad_<name>.c. If you contribute enough decoders, the |
193 development team may even grant you write privileges to the Subversion | 193 development team may even grant you write privileges to the Subversion |
194 repository. | 194 repository. |
195 | 195 |
196 5) Wait for bug reports to start rolling in | 196 5) Wait for bug reports to start rolling in |
197 You may think you're finished when you release the codec and if you're | 197 You may think you're finished when you release the codec and if you're |
198 extremely lucky, you will be right. However, it's more likely that people | 198 extremely lucky, you will be right. However, it's more likely that people |
199 will start throwing all kinds of oddball media at your decoder that it | 199 will start throwing all kinds of oddball media at your decoder that it |
200 never counted on. Cheer up; take comfort in knowing that people are | 200 never counted on. Cheer up; take comfort in knowing that people are |
201 testing your code and attempting to use it as a real world | 201 testing your code and attempting to use it as a real world |
202 application. Download the problem media that people upload to the MPlayer | 202 application. Download the problem media that people upload to the MPlayer |
203 FTP site and get back to work, implementing fixed code that addresses the | 203 FTP site and get back to work, implementing fixed code that addresses the |
204 issues. Contribute more patches and encourage people to hammer on your | 204 issues. Contribute more patches and encourage people to hammer on your |
205 decoder even more. This is how you make your decoder rock-solid. | 205 decoder even more. This is how you make your decoder rock-solid. |
206 | 206 |