On 04/07/2014 07:42 PM, Tres Finocchiaro wrote: > I believe this is a bit over my head, but I want to know this isn't > falling on deaf ears. > > From your work with Monstro and Watsyn (which I've yet to try) I'm > glad to see this dialog. I'm terribly sorry I am unable to provide > any useful feedback, so moral support is the next best offering! :)
Well thanks. So far I've had some success with this endeavour... I've now implemented a dummy class which only contains static methods, plus a function that gets called in main.cpp that pre-generates the waveform mipmaps, plus inline functions for accessing these mipmaps... Saw and square work pretty well already. With triangle, and by extension moog saw (which is basically just a phase-shifted saw + triangle) there's some weird artifacting from which I don't know what is causing it, yet. But I'm working to iron out all the kinks. I also have bandlimited wavegeneration working in Monstro. They do take a bit more CPU than simple digital waveforms, so I'm not sure if I should just make them optional - so the user could choose either "Saw" or "Bandlimited saw" in the waveform selector... would that be ideal? ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ LMMS-devel mailing list LMMS-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lmms-devel
