There's a lot here, but almost no implementation of any kind yet. The only class with any real logic in it is CompressionPipeline. To get a sense of what is going on, first take a look at the StrippedDownMP3 class. That should be our main point of contact from our analysis code.
The code structure is roughly like this:
src: All main source files
audioCompression: our main package
algorithm: all the individual algorithmic components
compressors: the actual compressors we will build
types: data class definitions
test: testing code with mirrored package structure
Please feel free to mark up the code with comments, which you can do by opening the "Files Changed" tab above and clicking on the little "+" that appears when you hover your mouse over a line of code.
If you guys like this stuff, then we can merge it in and start fleshing out the individual pieces, i.e. the data types and algorithm steps. If this is all garbage, then you can learn me up on some of your professional knowledge!
Hey guys,
There's a lot here, but almost no implementation of any kind yet. The only class with any real logic in it is
CompressionPipeline. To get a sense of what is going on, first take a look at theStrippedDownMP3class. That should be our main point of contact from our analysis code.The code structure is roughly like this:
Please feel free to mark up the code with comments, which you can do by opening the "Files Changed" tab above and clicking on the little "+" that appears when you hover your mouse over a line of code.
If you guys like this stuff, then we can merge it in and start fleshing out the individual pieces, i.e. the data types and algorithm steps. If this is all garbage, then you can learn me up on some of your professional knowledge!