I l ike where you are going wiht this. I think this would tie in with unit testing for the project as a whole. I am not sure how you woudl go about testing audio.
What you might have would be very unique at least from what i know and understand. But i think we really need to make a push to get unit tests in place. This will help us minimize regressions as well as allow us to find bugs before release. On Monday 20 January 2014 16:54:59 Raine M. Ekman wrote: > Please, shoot me down if this is bad idea, but I was thinking about > introducing some kind of fuzzy test script for comparing audio output > between two versions of LMMS. It would consist of something along > these lines: > > - A bunch of test projects, tailored to exercise different parts of > LMMS (one for each plugin, one for tempo automation and so on) > - A script that renders the projects with the LMMS versions and > settings chosen and checks the difference of the results. (could be as > easy as inverting one, mixing the files together and running 'sox > mix.wav -n stat' for a fast indication of something gone wrong) > > Maybe there's some software already out there that could be used? ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
