You have chosen to sponsor your bid up to a maximum amount of .
I'm looking for a small, well-behaved, and well-compliant Win32 method for "listening" on the system sound-out channel. This code would simply write the PCM data to a cicular buffer so that, effectively, whatever goes out over the speakers will have passed through this buffer. The buffer would be treated as read-only (ie, there's no intention or desire to alter the sound output, only monitor it). The coder will receive a spec and we'll massage it further from there. I anticipate this is a 3-7 day job for any veteran Win32 developer.
The implementation must be robust, high quality, fairly documented, and well structured. Non-professional code and code that just "gets the job done" is unacceptable and, hence, we’re willing to pay professional rates. Further, we develop under Metrowerks CodeWarrior, so the implementation has to be independent of any Microsoft-only technologies/class-frameworks (such that the code is limited to be on a MS compiler). Cleanliness, elegance, performance, and low-overhead are paramount.
This is a small professional project--serious inquires only, please. If you think you're right for this project, be sure you to include pertinent experience, why you're a good fit for this project, and what suites you plan to use to implement it.
1) All source code files that implement the work description and any source files created for it's testing and/or evaluation.
2) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
3) The source will monitored during development to ensure it will ultimately compile under Metrowerks CodeWarrior and that a high standard of quality is maintained (it's understood that coder can compile using whatever, but it must be able to be brought to another dev environment without too much difficulty).
The implementation must run under environments running Windows 2k and XP (or later). If possible, the implementation should run under Win 9X.
The minimum CPU should be around a low-end PIII.