From: Paul G. <dr...@gm...> - 2007-04-01 09:34:13
|
Cool. I hope PolyLB302 is cool. I can no longer compile LMMS successfully, my plugin never worked right due to errors in LMMS's monophonic implementation, and EVERY plugin clicks or pops in some form. To top it all off, I cannot complete work on a song without getting damn segfaults! I'm over this project. Good luck in the future! I may revisit some time when it actually behaves correctly. Until then, I am moving back to Windows or Mac for my music needs. Unfortunately. And I had so many big plans for lb303..... -Paul On 3/26/07, Javier Serrano Polo <ja...@te...> wrote: > El dl 26 de 03 del 2007 a les 23:41 +0200, en/na Tobias Doerffel va > escriure: > > > The CFLAGS/CXXFLAGS change in the last revision is unintentional, isn't > > > it? > > This one overrides optimization-flags with our own. I don't know whether this > > helps, so we can also revert this change, no problem ;-) > > Precisely, it overrides user flags. That means no debugging, force > optimization. I'll revert this. > > > Concerning PolyLB302: is there a way to use more common code from lb302 and > > only implement the actual differences between these two plugins? I guess it's > > very hard to keep those two plugins synchronous... Furthermore I generally > > dislike redundancy like this... ;) > > Me too, but a fork was the best choice left. It isn't that hard to port > changes from lb to polyb, though don't expect a "backport". Anyway, I > need a lb302 update to assess the effort. > > Bye. > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > LMMS-devel mailing list > LMM...@li... > https://lists.sourceforge.net/lists/listinfo/lmms-devel > |