Hi Id like to remind SOC students that everyone should select a seperate qualification task. Having 2 students work on the same task is not good. We had 2 last year who did and it caused problems, i would like to avoid that this year. Currently we have (if i interpreted everyones mails correctly) Sascha VIVO demuxer (or vivo audio?) Marcondes VIVO demuxer (said so after sascha) andi metadata or MLP patch cleanup ? thilani MLP patch cleanup? (said so after andi) Also maybe students should add a note to the wiki below the qualification task they selected. -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The misfortune of the wise is better than the prosperity of the fool. -- Epicurus
Hello, Michael Niedermayer wrote:
Hi
Id like to remind SOC students that everyone should select a seperate qualification task. Having 2 students work on the same task is not good. We had 2 last year who did and it caused problems, i would like to avoid that this year.
Currently we have (if i interpreted everyones mails correctly) Sascha VIVO demuxer (or vivo audio?) Marcondes VIVO demuxer (said so after sascha) andi metadata or MLP patch cleanup ? thilani MLP patch cleanup? (said so after andi)
Also maybe students should add a note to the wiki below the qualification task they selected.
I'm also interested in participating in GSoC this year. May I consider the Mimic decoder a qualification task? Ramiro Polla
Ramiro Polla wrote:
Hello,
Michael Niedermayer wrote:
Hi
Id like to remind SOC students that everyone should select a seperate qualification task. Having 2 students work on the same task is not good. We had 2 last year who did and it caused problems, i would like to avoid that this year.
Currently we have (if i interpreted everyones mails correctly) Sascha VIVO demuxer (or vivo audio?) Marcondes VIVO demuxer (said so after sascha) andi metadata or MLP patch cleanup ? thilani MLP patch cleanup? (said so after andi)
Also maybe students should add a note to the wiki below the qualification task they selected.
I'm also interested in participating in GSoC this year. May I consider the Mimic decoder a qualification task?
Ramiro Polla
Sure, but it needs to hit svn :) MvH Benjamin Larsson
Michael Niedermayer <michaelni@...> writes:
Also maybe students should add a note to the wiki below the qualification task they selected.
until the wiki has open registration, this is not feasible. its strange that some students dont announce which tasks they are working on. only until someone else does, do they reply! ah well, another learning experience. -compn
Hi, On Donnerstag, 13. März 2008, Michael Niedermayer wrote:
Hi
Id like to remind SOC students that everyone should select a seperate qualification task. Having 2 students work on the same task is not good. We had 2 last year who did and it caused problems, i would like to avoid that this year.
Currently we have (if i interpreted everyones mails correctly) Sascha VIVO demuxer (or vivo audio?) Marcondes VIVO demuxer (said so after sascha) andi metadata or MLP patch cleanup ? thilani MLP patch cleanup? (said so after andi)
Also maybe students should add a note to the wiki below the qualification task they selected.
I just realized that vivoaudio is not G723 but G723.1. I take a look at the RL2 task then. Regards Sascha
On czwartek, 13 marca 2008, Michael Niedermayer wrote:
Hi
Id like to remind SOC students that everyone should select a seperate qualification task. Having 2 students work on the same task is not good. We had 2 last year who did and it caused problems, i would like to avoid that this year.
Currently we have (if i interpreted everyones mails correctly) Sascha VIVO demuxer (or vivo audio?) Marcondes VIVO demuxer (said so after sascha) andi metadata or MLP patch cleanup ? thilani MLP patch cleanup? (said so after andi)
Also maybe students should add a note to the wiki below the qualification task they selected.
Hello, in GSOC 2007 I wrote part of the code of E-AC3 decoder. Unfortunately, because of incomplete documentation and lack of samples for a long time I wasn't able to write all of it in the time of holidays, then, when the academic year was started I hadn't got much free time. I know, that it wasn't perfect, but I am keen to try once again to write something in GSOC. So I would be grateful if you may tell me, do I still have any chance to participate in GSOC 2008? I'm also keen to write some qualifying task (last year I wrote TIFF encoder and LZW compression), so I have a question, is any of the following tasks free: "Optimal huffman tables for (M)JPEG encoding", demuxer RL2 or Psygnosis YOP ? Regards, Bartek -- Bartlomiej Wolowiec
On Sat, Mar 15, 2008 at 12:23:05PM +0100, Bartlomiej Wolowiec wrote:
On czwartek, 13 marca 2008, Michael Niedermayer wrote:
Hi
Id like to remind SOC students that everyone should select a seperate qualification task. Having 2 students work on the same task is not good. We had 2 last year who did and it caused problems, i would like to avoid that this year.
Currently we have (if i interpreted everyones mails correctly) Sascha VIVO demuxer (or vivo audio?) Marcondes VIVO demuxer (said so after sascha) andi metadata or MLP patch cleanup ? thilani MLP patch cleanup? (said so after andi)
Also maybe students should add a note to the wiki below the qualification task they selected.
Hello, in GSOC 2007 I wrote part of the code of E-AC3 decoder. Unfortunately, because of incomplete documentation and lack of samples for a long time I wasn't able to write all of it in the time of holidays, then, when the academic year was started I hadn't got much free time. I know, that it wasn't perfect, but I am keen to try once again to write something in GSOC. So I would be grateful if you may tell me, do I still have any chance to participate in GSOC 2008?
You do, it all of course strongly depends on the number of slots google will give us. As well as your last year mentors oppinion ...
I'm also keen to write some qualifying task (last year I wrote TIFF encoder and LZW compression), so I have a question, is any of the following tasks free: "Optimal huffman tables for (M)JPEG encoding", demuxer RL2 or Psygnosis YOP ?
What about getting the EAC3 code into SVN? It likely wont be as easy as the other qualification tasks but if you succeed that could have a strong effect on your chances of being accepted again (especially if we have many more qualified students than slots) Anyway the current list of qualification tasks: Sascha RL2 Marcondes VIVO demuxer andi MLP patch cleanup thilani MLP patch cleanup? (said so after andi) Ramiro mimic Alexander Strange SSE2 IDCT Deep Pal optimal mjpeg huffman table [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If a bugfix only changes things apparently unrelated to the bug with no further explanation, that is a good sign that the bugfix is wrong.
Michael Niedermayer wrote:
On Sat, Mar 15, 2008 at 12:23:05PM +0100, Bartlomiej Wolowiec wrote:
On czwartek, 13 marca 2008, Michael Niedermayer wrote:
Hi
Id like to remind SOC students that everyone should select a seperate qualification task. Having 2 students work on the same task is not good. We had 2 last year who did and it caused problems, i would like to avoid that this year.
Currently we have (if i interpreted everyones mails correctly) Sascha VIVO demuxer (or vivo audio?) Marcondes VIVO demuxer (said so after sascha) andi metadata or MLP patch cleanup ? thilani MLP patch cleanup? (said so after andi)
Also maybe students should add a note to the wiki below the qualification task they selected. Hello, in GSOC 2007 I wrote part of the code of E-AC3 decoder. Unfortunately, because of incomplete documentation and lack of samples for a long time I wasn't able to write all of it in the time of holidays, then, when the academic year was started I hadn't got much free time. I know, that it wasn't perfect, but I am keen to try once again to write something in GSOC. So I would be grateful if you may tell me, do I still have any chance to participate in GSOC 2008?
You do, it all of course strongly depends on the number of slots google will give us. As well as your last year mentors oppinion ...
The code from last year was good. There were a few hard-to-find bugs, but that's par-for-the-course. Most of the work I've had to do has been reducing code duplication, which there was a lot of. Maybe I did not stress this requirement enough, though I certainly tried. You did give a good effort last year and were certainly hindered by the late arrival of better samples. I agree that we should give Bartek the same chance as any other student, based on the same criteria.
I'm also keen to write some qualifying task (last year I wrote TIFF encoder and LZW compression), so I have a question, is any of the following tasks free: "Optimal huffman tables for (M)JPEG encoding", demuxer RL2 or Psygnosis YOP ?
What about getting the EAC3 code into SVN? It likely wont be as easy as the other qualification tasks but if you succeed that could have a strong effect on your chances of being accepted again (especially if we have many more qualified students than slots)
I agree that this would be a good task, and also that it won't be as easy as the others. The qualification task is so that we have some example of your coding abilities and dedication to the task. Having another sample of your code won't really help us. We already have that. :) I would like to see your dedication to last year's task by helping to get it ready-for and into FFmpeg SVN. I have just been very busy lately with other stuff. If I can get help with getting these things done, and then a final patch made which makes it into SVN, that would go a long way. I do want to be clear that this would not guarantee a spot, but it would qualify you to be considered on the merits of your proposal and all of the other factors we use to decide which projects get chosen. Here is my current plan of action regarding AC3 and E-AC3, which is subject to change if needed. 1. Get the fast, simple AC3 downmixing working based on Rich's suggestion of doing the short-block downmixing after the IMDCT but before the overlap/add/window. I want to do this first because it will likely change the structure of the decoder a bit, which will be easier before E-AC3 is integrated. Right now I'm getting artifacts. My plan is to analyze a single frame, in depth, to find out where the problem lies. 2. Right now AC3 is suffering from a major stability problem. There are many coded values which affect how many bits are read, and the bitstream reader does not have any built-in protection from reading past the input buffer. So malformed or damaged streams can (and do) cause memory access problems (detected by valgrind) and/or segfaults. I have several ideas for solutions to this, but I need time to test each one to see which is the fastest. 3. Go through the list of invalid bitstream conditions in the specs and add as many of those checks as possible. Some may not be needed if they significantly decrease decoding speed and do not affect stability. I have already started on this...it just needs to be tested and applied. 4. Do the same condition checks for E-AC3 as well, but we don't have a nicely prepared list to work from. 5. Update the E-AC3 decoder to include all the changes since last update and any subsequent changes. 6. There are a couple of samples which seem to be 7.1-channel. It would be nice to get this working before SVN inclusion. 7. Error conclealment. Simple error concealment is fairly trivial. For more robust detection and concealment, Michael made some great suggestions for guidelines. It would require some reworking of the AC3 parser. 8. Prepare a final patch and go through the ffmpeg-devel review process. So that's about it. :) If anyone feels I should skip any of these steps or change the priority, I am open to suggestions. That said, I think a good SoC qualification task would be to work on #4 to #7 while I concentrate on #1 to #3. Then once that's all ready, do #8. I will, of course, help with all of this and would make sure to prioritize this over my other on-going projects. Thanks, Justin
On sobota, 15 marca 2008, Justin Ruggles wrote:
I agree that this would be a good task, and also that it won't be as easy as the others. The qualification task is so that we have some example of your coding abilities and dedication to the task. Having another sample of your code won't really help us. We already have that.
:) I would like to see your dedication to last year's task by helping
to get it ready-for and into FFmpeg SVN.
I have just been very busy lately with other stuff. If I can get help with getting these things done, and then a final patch made which makes it into SVN, that would go a long way. I do want to be clear that this would not guarantee a spot, but it would qualify you to be considered on the merits of your proposal and all of the other factors we use to decide which projects get chosen.
Here is my current plan of action regarding AC3 and E-AC3, which is subject to change if needed.
1. Get the fast, simple AC3 downmixing working based on Rich's suggestion of doing the short-block downmixing after the IMDCT but before the overlap/add/window. I want to do this first because it will likely change the structure of the decoder a bit, which will be easier before E-AC3 is integrated. Right now I'm getting artifacts. My plan is to analyze a single frame, in depth, to find out where the problem lies.
2. Right now AC3 is suffering from a major stability problem. There are many coded values which affect how many bits are read, and the bitstream reader does not have any built-in protection from reading past the input buffer. So malformed or damaged streams can (and do) cause memory access problems (detected by valgrind) and/or segfaults. I have several ideas for solutions to this, but I need time to test each one to see which is the fastest.
3. Go through the list of invalid bitstream conditions in the specs and add as many of those checks as possible. Some may not be needed if they significantly decrease decoding speed and do not affect stability. I have already started on this...it just needs to be tested and applied.
4. Do the same condition checks for E-AC3 as well, but we don't have a nicely prepared list to work from.
Ok. Unfortunately, most of the conditions from AC3 hasn't much in common with E-AC3, but I'll try to think of some correctness tests of the stream.
5. Update the E-AC3 decoder to include all the changes since last update and any subsequent changes.
I should do it before or after those 3 points which I was given?
6. There are a couple of samples which seem to be 7.1-channel. It would be nice to get this working before SVN inclusion.
I haven't seen 7.1 files. Where can I find them?
7. Error conclealment. Simple error concealment is fairly trivial. For more robust detection and concealment, Michael made some great suggestions for guidelines. It would require some reworking of the AC3 parser.
Can you give me some more explanations on this topic, because I think I don't understand what do you mean properly
8. Prepare a final patch and go through the ffmpeg-devel review process.
So that's about it. :) If anyone feels I should skip any of these steps or change the priority, I am open to suggestions.
That said, I think a good SoC qualification task would be to work on #4 to #7 while I concentrate on #1 to #3. Then once that's all ready, do #8. I will, of course, help with all of this and would make sure to prioritize this over my other on-going projects.
Ok, so I treat #4 to #7 as a qualification task, I'll try to do them as soon as I have some free time:) -- Bartlomiej Wolowiec
Bartlomiej Wolowiec wrote:
On sobota, 15 marca 2008, Justin Ruggles wrote:
4. Do the same condition checks for E-AC3 as well, but we don't have a nicely prepared list to work from.
Ok. Unfortunately, most of the conditions from AC3 hasn't much in common with E-AC3, but I'll try to think of some correctness tests of the stream.
The design of E-AC3 actually gets rid of most of the invalid conditions from AC3, but there are still a handful that will need to be checked for.
5. Update the E-AC3 decoder to include all the changes since last update and any subsequent changes.
I should do it before or after those 3 points which I was given?
You can wait until after.
6. There are a couple of samples which seem to be 7.1-channel. It would be nice to get this working before SVN inclusion.
I haven't seen 7.1 files. Where can I find them?
I'll upload to mphq samples.
7. Error conclealment. Simple error concealment is fairly trivial. For more robust detection and concealment, Michael made some great suggestions for guidelines. It would require some reworking of the AC3 parser.
Can you give me some more explanations on this topic, because I think I don't understand what do you mean properly
I will elaborate more in another email later today. Basically, the complex part is in when to trust the header info. A damaged header can give all sorts of problems that make it hard to conceal errors and lead to losing sync.
8. Prepare a final patch and go through the ffmpeg-devel review process.
So that's about it. :) If anyone feels I should skip any of these steps or change the priority, I am open to suggestions.
That said, I think a good SoC qualification task would be to work on #4 to #7 while I concentrate on #1 to #3. Then once that's all ready, do #8. I will, of course, help with all of this and would make sure to prioritize this over my other on-going projects.
Ok, so I treat #4 to #7 as a qualification task, I'll try to do them as soon as I have some free time:)
Sounds great. I'll devote more time to getting this done as well. Thanks, Justin
Bartlomiej Wolowiec wrote:
On sobota, 15 marca 2008, Justin Ruggles wrote:
6. There are a couple of samples which seem to be 7.1-channel. It would be nice to get this working before SVN inclusion.
I haven't seen 7.1 files. Where can I find them?
http://samples.mplayerhq.hu/A-codecs/AC3/eac3/ 7_pt_1.eac3 7_pt_1.txt -Justin
On Sat, Mar 15, 2008 at 08:30:40PM +0100, Bartlomiej Wolowiec wrote:
On sobota, 15 marca 2008, Justin Ruggles wrote: [...]
7. Error conclealment. Simple error concealment is fairly trivial. For more robust detection and concealment, Michael made some great suggestions for guidelines. It would require some reworking of the AC3 parser.
Can you give me some more explanations on this topic, because I think I don't understand what do you mean properly
Now if i would remember what i said in that mail or could find that mail ... Anyway E-AC3 says: E3.2 Error Detection and Concealment Enhanced AC-3 decoders are required to implement error detection based on the bit stream CRC word. Enhanced AC-3 bit streams contain only one CRC word, which covers the entire frame. When decoding bit streams that use the Enhanced AC-3 bit stream syntax, Enhanced AC-3 decoders must verify the CRC word prior to decoding any of the blocks in the frame. If the CRC word for an Enhanced AC-3 bit stream is found to be invalid, all blocks in the frame must be substituted with an appropriate error concealment signal. For most applications, this can be easily accomplished by simply repeating the last known-good block (before the overlap-add window process). ---- And thats a good goal ... Besides this it would be nice if we could detect errors faster than checking crcs (wrong vlc, too long/ short bitstream), but i do not know if this can be done. If not forget about it and just implement error concealment per CRCs. Thats IMHO as i dont remember what i said about E-AC3 EC and maybe justin has some comments as well, i just replied as it seems justin didnt exactly reply. [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Breaking DRM is a little like attempting to break through a door even though the window is wide open and the only thing in the house is a bunch of things you dont want and which you would get tomorrow for free anyway
Michael Niedermayer wrote:
On Sat, Mar 15, 2008 at 08:30:40PM +0100, Bartlomiej Wolowiec wrote:
On sobota, 15 marca 2008, Justin Ruggles wrote: [...]
7. Error conclealment. Simple error concealment is fairly trivial. For more robust detection and concealment, Michael made some great suggestions for guidelines. It would require some reworking of the AC3 parser. Can you give me some more explanations on this topic, because I think I don't understand what do you mean properly
Now if i would remember what i said in that mail or could find that mail ...
From what I remember, the original email was basically me being paranoid and you offering some good solutions. But I was aiming for a more fully robust decoder that would eliminate a/v sync issues as much as possible. So that involved determining when to trust the various header values, specifically the sync word, frame size, and number of channels. This is a good goal, but not an immediate requirement.
Anyway E-AC3 says: E3.2 Error Detection and Concealment Enhanced AC-3 decoders are required to implement error detection based on the bit stream CRC word. Enhanced AC-3 bit streams contain only one CRC word, which covers the entire frame. When decoding bit streams that use the Enhanced AC-3 bit stream syntax, Enhanced AC-3 decoders must verify the CRC word prior to decoding any of the blocks in the frame. If the CRC word for an Enhanced AC-3 bit stream is found to be invalid, all blocks in the frame must be substituted with an appropriate error concealment signal. For most applications, this can be easily accomplished by simply repeating the last known-good block (before the overlap-add window process). ----
The first item to address is error robustness. For typical streams with moderate damage, the CRC check will catch pretty close to everything.
And thats a good goal ... Besides this it would be nice if we could detect errors faster than checking crcs (wrong vlc, too long/ short bitstream), but i do not know if this can be done. If not forget about it and just implement error concealment per CRCs.
Adding the bitstream condition checks is what takes care of the damaged frames that happen to make it through the CRC. Each condition check should be evaluated to see if it is really necessary. For example, an invalid exponent value will very likely trigger another error further along in the bitstream, but if it doesn't the worst you'll get is a blip of noise. A wrong mantissa value will never generate another error, and may or may not be audible. So you have to take each one and weigh the benefits vs. slowdown.
Thats IMHO as i dont remember what i said about E-AC3 EC and maybe justin has some comments as well, i just replied as it seems justin didnt exactly reply.
Yeah...I forgot that I had said I would explain it better. I hope this email helps. I was going to go into the nitty-gritty of catching errors at the parser level that would affect sync, but I don't think that's really necessary at this point. -Justin
Justin Ruggles <justinruggles@...> writes:
7. Error conclealment. Simple error concealment is fairly trivial. For more robust detection and concealment, Michael made some great suggestions for guidelines. It would require some reworking of the AC3 parser. Can you give me some more explanations on this topic, because I think I don't understand what do you mean properly
Now if i would remember what i said in that mail or could find that mail ...
http://lists.mplayerhq.hu/pipermail/ffmpeg-soc/2008-March/002742.html
On Thu, Mar 20, 2008 at 11:47:58PM +0000, compn wrote:
Justin Ruggles <justinruggles@...> writes:
7. Error conclealment. Simple error concealment is fairly trivial. For more robust detection and concealment, Michael made some great suggestions for guidelines. It would require some reworking of the AC3 parser. Can you give me some more explanations on this topic, because I think I don't understand what do you mean properly
Now if i would remember what i said in that mail or could find that mail ...
http://lists.mplayerhq.hu/pipermail/ffmpeg-soc/2008-March/002742.html
no that was not the one i was searching for ... it was longer ago and possibly a different ML [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB While the State exists there can be no freedom; when there is freedom there will be no State. -- Vladimir Lenin
Michael Niedermayer wrote:
On Thu, Mar 20, 2008 at 11:47:58PM +0000, compn wrote:
Justin Ruggles <justinruggles@...> writes:
7. Error conclealment. Simple error concealment is fairly trivial. For more robust detection and concealment, Michael made some great suggestions for guidelines. It would require some reworking of the AC3 parser. Can you give me some more explanations on this topic, because I think I don't understand what do you mean properly Now if i would remember what i said in that mail or could find that mail ...
http://lists.mplayerhq.hu/pipermail/ffmpeg-soc/2008-March/002742.html
no that was not the one i was searching for ... it was longer ago and possibly a different ML
http://lists.mplayerhq.hu/pipermail/ffmpeg-cvslog/2008-January/010914.html
On Thu, Mar 20, 2008 at 08:18:11PM -0400, Justin Ruggles wrote:
Michael Niedermayer wrote:
On Thu, Mar 20, 2008 at 11:47:58PM +0000, compn wrote:
Justin Ruggles <justinruggles@...> writes:
> 7. Error conclealment. Simple error concealment is fairly trivial. For > more robust detection and concealment, Michael made some great > suggestions for guidelines. It would require some reworking of the AC3 > parser. Can you give me some more explanations on this topic, because I think I don't understand what do you mean properly Now if i would remember what i said in that mail or could find that mail ...
http://lists.mplayerhq.hu/pipermail/ffmpeg-soc/2008-March/002742.html
no that was not the one i was searching for ... it was longer ago and possibly a different ML
http://lists.mplayerhq.hu/pipermail/ffmpeg-cvslog/2008-January/010914.html
Yes thats the one i meant :) [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If you really think that XML is the answer, then you definitly missunderstood the question -- Attila Kinali
On sobota, 15 marca 2008, Michael Niedermayer wrote:
What about getting the EAC3 code into SVN? It likely wont be as easy as the other qualification tasks but if you succeed that could have a strong effect on your chances of being accepted again (especially if we have many more qualified students than slots)
Anyway the current list of qualification tasks:
Sascha RL2 Marcondes VIVO demuxer andi MLP patch cleanup thilani MLP patch cleanup? (said so after andi) Ramiro mimic Alexander Strange SSE2 IDCT Deep Pal optimal mjpeg huffman table
Since December 2007 my mentor from GSOC 2007, Justin Ruggles, has been working on improving code. Just like in the summer, there still are no samples which may allow to continue the work on the decoder. I wouldn't like to spoil his conception of developing the decoder by changing something in the code, but if he wishes, I can work on getting the EAC3 code into SVN. Moreover, as an additional work, I would like to work on YOP Playback System, as it's still free. -- Bartlomiej Wolowiec
On Sat, Mar 15, 2008 at 05:39:01PM +0100, Bartlomiej Wolowiec wrote:
On sobota, 15 marca 2008, Michael Niedermayer wrote:
What about getting the EAC3 code into SVN? It likely wont be as easy as the other qualification tasks but if you succeed that could have a strong effect on your chances of being accepted again (especially if we have many more qualified students than slots)
Anyway the current list of qualification tasks:
Sascha RL2 Marcondes VIVO demuxer andi MLP patch cleanup thilani MLP patch cleanup? (said so after andi) Ramiro mimic Alexander Strange SSE2 IDCT Deep Pal optimal mjpeg huffman table
Since December 2007 my mentor from GSOC 2007, Justin Ruggles, has been working on improving code. Just like in the summer, there still are no samples which may allow to continue the work on the decoder. I wouldn't like to spoil his conception of developing the decoder by changing something in the code, but if he wishes, I can work on getting the EAC3 code into SVN. Moreover, as an additional work, I would like to work on YOP Playback System, as it's still free.
See Justin's detailed answer, but I think showing dedication is more valuable than another code sample in your case. EAC-3 would be quite valuable. Diego
Hi, On Samstag, 15. März 2008, Bartlomiej Wolowiec wrote:
On czwartek, 13 marca 2008, Michael Niedermayer wrote:
Hi
Id like to remind SOC students that everyone should select a seperate qualification task. Having 2 students work on the same task is not good. We had 2 last year who did and it caused problems, i would like to avoid that this year.
Currently we have (if i interpreted everyones mails correctly) Sascha VIVO demuxer (or vivo audio?) Marcondes VIVO demuxer (said so after sascha) andi metadata or MLP patch cleanup ? thilani MLP patch cleanup? (said so after andi)
Also maybe students should add a note to the wiki below the qualification task they selected.
Hello, in GSOC 2007 I wrote part of the code of E-AC3 decoder. Unfortunately, because of incomplete documentation and lack of samples for a long time I wasn't able to write all of it in the time of holidays, then, when the academic year was started I hadn't got much free time. I know, that it wasn't perfect, but I am keen to try once again to write something in GSOC. So I would be grateful if you may tell me, do I still have any chance to participate in GSOC 2008? I'm also keen to write some qualifying task (last year I wrote TIFF encoder and LZW compression), so I have a question, is any of the following tasks free: "Optimal huffman tables for (M)JPEG encoding", demuxer RL2 or Psygnosis YOP ?
I'm working on RL2 Regards Sascha
participants (8)
-
Bartlomiej Wolowiec -
Benjamin Larsson -
compn -
Diego Biurrun -
Justin Ruggles -
Michael Niedermayer -
Ramiro Polla -
Sascha Sommer