On 11/18/2014 02:23 PM, Vesa wrote: > Well, if you have old projects, you'll just have to finish them with 1.1 > or 1.2 and render them to wavs. Then publish them, forget about it, and > make new music with 2.0.
If this is the current development team's outlook, I really think LMMS 2.x needs to be called something other than LMMS (and the project file extensions should change too.) I can't speak for anyone else, but personally, I'm never, ever done with a piece of music. At a minimum, it should import the tracks' note events as though they're coming from a standard MIDI file, perhaps with an idiot dialog that says "Here's the notes, but now you're on your own". Most people on this list, myself included, could write something that lazy in an afternoon. The free software world, especially the multimedia side, is littered with the remains of projects that began to stagnate, only to have someone with a lot of energy show up with a bunch of commits and take a leadership role by default, say "This code is awful to work with, so let's toss out the cruft and redesign this from the ground up!", usually complete with a bunch of snazzy mockups, a website redesign and a thoroughly-documented architecture that decouples presentation from backend processing, only to have the latecomer lose steam (or depart in a puff of manufactured drama) when he realizes he's got hundreds of thousands of lines of code to rewrite from scratch, most of the features that sold the 1.x version never quite seem to make it to 2.x, the 1.x version gets removed from popular distributions because it's obsolete even though the entire ecosystem still revolves around it, and then the 2.x version gets removed too because it's so broken. Changing the name won't solve all these issues (look no further than xmms/xmms2/audacious, or ffmpeg/avconv, or gqview/geeqie, etc. to see why) but at least those of us who want to actually make music will still have LMMS 1.x (even if we have to load an old version of Ubuntu in Virtualbox to run it) while you guys are still messing around with JACK bugs and au courant UI redesigns in 2019. I understand many of the limitations of the current LMMS. I wrote a pile of one-off perl scripts to massage the raw XML of my project files to stuff that would have been tedious to impossible in the UI the last time I did something serious with it, and I always end up overdubbing/mixing down in Audacity. Nonetheless, what we have today is a working, powerful tool, and there's an enormous body of work out there that deserves to continue to live in better-than-snapshot form -- like every single project currently on the sharing site, for example. LMMS deserves better. Better than "bitrot", better than "overambitious laughingstock", Rob ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ LMMS-devel mailing list LMMS-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lmms-devel
