This project is for a utility that will silence sections of multiple wave files. Up to four stereo wave files - all of them identical - will be loaded to the app. All of them will be silenced for 4 milliseconds except one - the left channel of file "A". . Then all will be silenced for 8 milliseconds except the right channel of file "A". . Then all will be silenced for 12 milliseconds except the left channel of file "B". . Then all will be silenced for 16 milliseconds except the right channel of file "B". . Then all will be silenced for 20 milliseconds except the left channel of file "C". . Then all will be silenced for 16 milliseconds except the right channel of file "C". . Then all will be silenced for 12 milliseconds except the left channel of file "D". . Then all will be silenced for 8 milliseconds except the right channel of file "D". . Then all will be silenced for 4 milliseconds except the left channel of file "A". AND SO FORTH. Four stereo files offer eight channels. In the example above, five different numbers are used (4, 8, 12, 16, 20). Five is the NUMBER OF CHANGES. You will notice that they are multiples of four. Four is the RATE OF CHANGE (which sets the number by which the non-silenced portions are multiplied). The user for the app must be able to enter the NUMBER OF CHANGES, and a RATE OF CHANGE (including decimals for the RATE OF CHANGE - so that [url removed, login to view] milliseconds *for example* is a valid entry). If The NUMBER OF CHANGES is ONE, then all sounds remaining in the files will have the same length. A further entry is a variation for the RATE OF CHANGE in percent. 100% would be no variation. 99% would shorten the rate of change, and 101% would lengthen the rate of change. All files will be stereo, 16-bit, 44100hz, so that each millisecond will be composed of 44 samples. In cases where the rate of change requires fractions of a sample, the app should "round it off" the same way in all cases. In cases where fewer than four wave files are loaded, the app should cycle through the left and right channels exactly as above. The app will have to contain an "ABOUT" box that shows my name as the copyright holder for the app, as well as the year. There is a file attached to this posting. MAKE SURE YOU LOOK AT IT, PLEASE. . Feel free to ask any questions you may have before bidding. I have posted projects in the past that received bids for thousands of dollars, but were completed for only a few bucks. Please be competitive in your bidding. Bids accompanied by comments to the effect that "we are programmers who can handle all jobs. Please furnish details, etc." will not be answered. If your comments are not addressed specifically to this project, and this project alone, I will probably won't respond. I deal only with straight-talking programmers whose initial comments show their ability to handle the specific project. Read my feedback, and rest assured that I will read yours. If you have no feedback, please don't be worried. Your comments that show your ability to handle the project will outweigh all other factors. I'll give you as much time as you need to complete the project, without reopening it, provided you communicate with me as we go along, and send me your initial drafts as soon as they are ready. I'm not too concerned which platform it's done on.