From: Paul W. <pa...@ma...> - 2008-03-17 04:32:49
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tobias Doerffel wrote: | LMMS 0.4.x is evolving very well, has gotten quite stable and currently is | being filled with a lot new cool features. I want to give a short overview of | what's done so far and what is planned to be done until 0.4.x release. I need to buy another 4 litre tub of Glee(tm) - I've run out of it to rub my hands with looking at all the new features for LMMS. | Paul added a very cool new plugin which allows to use SoundFont2-files within | LMMS which will make LMMS even more interesting for semi-professional users. Awesome - I've found a couple of excellent free SoundFont sites and downloaded some already. We should start sharing these as patches on the LSP. | As you've probably already heard, LMMS 0.4.x will be fully SMP-capable by | introducing worker-threads according to the number of cores detected. The | rendering-load (instrument- and effect-processing) is being distributed | amongst those threads. This works quite well after some work on core-classes | has been done to make them reentrant (for example the sampleBuffer-class) and | on my dual-core-system it scales up to 1.7 - the rest is | non-parallelizable "overhead". Anyways it's a great improvement - even more | on quadcore-systems (I at least expect up to 3.0x but can't test)! Isn't it already? How does it work in 0.3? I can set LMMS to have two processors and it seems to use both cores to render a track - I can get up to about 175% CPU usage across two procesors, so I suppose I'm getting about the same results you are. | Very recently I added the long-requested effect-mixer with 64 FX-channels - | you can add arbitrary effects to each individual FX-channel. Per default | instruments are being routed into master (FX 0) but you can easily change | that using the ominous LCD-Spinbox which existed for ages but never made any | sense at all. The FX-mixer completes LMMS' core tools for easy | music-production. Please note that the current FX-mixer-implementation is far | from being complete - neither the GUI nor the functionality! It's just a | first proof-of-concept being made up quickly. Well, it'll still be mind-bogglingly useful to me, at least, so it sounds great. | Another fundamental change will be a new internal resolution of 192th instead | of 64th allowing triplet-notes as well as other time-signatures than 4/4. | Hurray for all non-techno-song-writers! :) Yay! See http://tangram.dnsalias.net/transfer/lmms/Messenger.mmpz for what I've had to do up until now... | There were several contributions to the artwork-contest. Thanks to all | submitters! However Fabi is the only one who made up a complete, consistent | and modern theme for all plugins. So I consider him to be the winner. | Congratulations! I already mailed with him to get things integrated. Some | changes will be neccessary to the plugins, that's why nothing of this has | changed in SVN yet. I'm looking forward to have this new artwork integrated | within next few weeks. Looks good. | All those improvements so far are nice but I'd also like to make some basic | changes to LMMS' UI and the way you work with it. Now that the FX-mixer has ... snip ... | the editor-view. But what to do with FX-mixer, instrument-track-windows, | FX-control-dialogs ...? We need your ideas! Everybody who has some good ideas | is asked to share them with us and maybe also make up some mockups. Well, I like the idea of an 'editor' window just changing behaviour, but it's definitely handy to be able to view a rhythm, a piano roll and an automation side by side, so to speak. Likewise, it'd be really good if one could see two piano rolls simultaneously to compare timing of notes. One idea I'd suggest is to make ctrl-tab more like alt-tab. At the moment (on 0.3.2) it just cycles through the windows but seems to go off through 16 or so invisible windows before going through the list again. It'd be nice to see a list of windows, and reorder them so that the most recently used window was put next in the queue. Maybe another idea is for windows to deliberately 'get out of your way' by minimising themselves? Or have a 'shrink' mode where windows can take up less space by shrinking their view down? Realistically, this is the problem every half-decent $thing editor has - once you add enough parts, the controls start cluttering up the screen. Personally I think this is a situation where the editor's own discipline and methodology. ~ I find it bugs me less now that I have a 1680x1050 screen, since I can spread out the windows nice and wide to edit lots of notes. Sometimes I have everything in view all at once, at other times I only have one thing up at one time and it takes the entire window. I don't think is something that is a fault in LMMS. But I'm interested in this 'dock' idea - can you explain that a little further? Have fun, Paul -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFH3fRiu7W0U8VsXYIRAjgNAKCS63yncSmliJHG+/ZhrJGh8Ilo8ACfagDU 3rd/yCPfVPCTA5E2XoR5QWg= =NNut -----END PGP SIGNATURE----- |