Hi fellas. I must put this to you all as it is essential that these few things get some priority imho. There's a lot of dev going on behind the scenes, at whatever pace, that may very well prove to be important to Muse2 in later development but to me there are a couple of real biggies that hold it back for me for anything other than midi work.
They are: 1. LV2 support 2. Better audio management. It's just too cumbersome overall atm. We need a bteer way to add (n) tracks, hardwired inputs, no tracks for hardware I/O etc. 3. Better use of the mixer as the center of audio throughput - this is what a mixer is for! In Muse I hardly ever use it because of it's shortcomings as I have described before. 4. Midi automation. 5. Automatic port re-assignment - that is when a midi device has been put into the midi devices list and connected, if the client crashes or goes away, when it returns it should just re-connect automatically and not have to be re-assigned. 6. In a system with many I/O channels (64 here for eg.) the device list becomes way too big to view and you can't move it and the contents don't scroll. Therefore, you can't assign outputs - It's useless. In the mixer you can however as it tends to be able to show them all. Still a pita ;) These to me are why I have had to go back to Ardour 3 for audio and use Muse for midi only. Just one users take on it. best g. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
