Hi Brian. Thanks for liking the idea. The code for doing this, could actually be fairly easy. If you start researching on what a Fast Fourier Transform (FFT) is, and understand how to implement a rough algorithm on this, you could easily add a test in the code, before the encoder kicks in, and prompt a message to the user, that it should be aware that the file could not be compressed, because it might already have been compressed. If you need help implementing a FFT, I'd be happy to help out. I think the codebase is frozen because the development have ceased? - J?rgen. On Jan 7, 2011, at 10:03 PM, Brian Waters wrote:> I like this idea. I've been looking for an open source project to get > my feet wet with. I'd love to work on the FLAC library, but I don't > know jack s**t about compression algorithms, and I've never worked on > a large project before. > > If someone would help guide me in the right direction, I'd love to do > some of that code. > > - Brian Waters > > PS, whats the deal with the codebase being frozen?
I'm busy 'till Monday morning but I'll break out the ole' diffy-q's textbook next week and do some background reading, thanks. Any clues on where in the code to look in order to put those hooks in? - Brian On Fri, Jan 7, 2011 at 4:08 PM, J?rgen Vigdal <jorgen at anion.no> wrote:> Hi Brian. > > Thanks for liking the idea. > > The code for doing this, could actually be fairly easy. If you start researching on what a Fast Fourier Transform (FFT) is, and understand how to implement a rough algorithm on this, you could easily add a test in the code, before the encoder kicks in, and prompt a message to the user, that it should be aware that the file could not be compressed, because it might already have been compressed. > > If you need help implementing a FFT, I'd be happy to help out. > > I think the codebase is frozen because the development have ceased? > > - J?rgen. > > On Jan 7, 2011, at 10:03 PM, Brian Waters wrote: > >> I like this idea. I've been looking for an open source project to get >> my feet wet with. I'd love to work on the FLAC library, but I don't >> know jack s**t about compression algorithms, and I've never worked on >> a large project before. >> >> If someone would help guide me in the right direction, I'd love to do >> some of that code. >> >> - Brian Waters >> >> PS, whats the deal with the codebase being frozen? > >
I have not studied the flac codebase, but I'll do some research and try to help you out. It might be stupid, but I guess a good place to start would be in the main() function, where the program receives its parameters from the command line? - J?rgen On Jan 7, 2011, at 10:15 PM, Brian Waters wrote:> I'm busy 'till Monday morning but I'll break out the ole' diffy-q's > textbook next week and do some background reading, thanks. Any clues > on where in the code to look in order to put those hooks in? > > - Brian >
haha. Sorry, I actually did not mean to offend you, but I see now that I did :) If you study main.c in flac/ -you'd probably be best off to start there. Perhaps one of the more experienced developers knows where it should be inserted, in order to be included in the library being used by third-party apps. - J?rgen PS: One complete different thing; does anyone know why it is called "third-party" apps? Why third? On Jan 7, 2011, at 10:23 PM, Brian Waters wrote:>> It might be stupid, but I guess a good place to start would be in the main() function, where the program receives its parameters from the command line? > > Haha, touche. I'll do that. This probably fits better in the > command-line program than in the library, but then other programs that > use the library won't pick up the feature... > > - Brian >