On 04/13/2013 09:01 PM, Florian Jung wrote:
could you please try to describe (maybe by creating a GUI draft on
paper)*in detail* how you'd like all this to work?
Especially:
- Do you see the sense for part controllers?
- Do you see the senso for track controllers?
- How would part-controllers be handled in the mixer?
is this possible at all?
hhmm, yeah ... i have had ideas about the gui for years actually,
however it's not a re-invention - rather the implementation of existing
paradigms. the mixer should offer what a HW mixer does - the ability to
control the amplitude/pan/dsp of anything that can be a member of the
mixer pane.It does this quite well atm but needs to become the centre
piece of general I/O within MusE which it currently isn't due to
lacking features such as Midi automation and HW routing omissions..
audio and mid HW should not be tracks on the timeline; just available to
the tracks in a list form - same as we have for midi HW now, and could
be better controlled from the mixer via these lists.
for me, track controllers are mixer members. part controllers are not.
one is a macro solution the other a micro one.
It is an extremely useful model of course,however there is a problem in
that you can have very (too?) complex mixes very quickly - and two
different places where they exist - one in the mixer the other on the
timeline... and the mixer will affect both. i used such a model in a
previous (horrible) life using Samplitude (TM) under "The Unspeakable
Crap Operating System of America" (also TM) - powerful but not
necessarily ideal.
The simple answer to your last question is they are not ! Not
meaningfully anyway - when you work on the micro level like that your
mixes quickly become very, very complex and you end up using an
either/or approach to mixing... which is cool of course - you can decide
which mix model you want to use. but a combination can be quite
difficult to manage.
Where it can be useful is when working (as i did for years) for
film/video/TV/radio. I think the best solution is If you can add dsp's
to a track object you can do wonders. Add automation to their
controllers and you can do anything at all!!
that's the key. make it possible to add a plugin to an object then you
can do anything you like. Add volume handles and a panner line to an
object (not just a track) and that's it imho - a complete DAW has these
features.
I can see it is easy to spend a lot of time doing conceptual development
that may not produce a particularly valuable outcome here, whilst things
like crossfades and object volume handles for audio and midi objects and
midi automation go undeveloped. I know Tim is working on the groundwork
for all this but I want to re-enforce the importance of them here for
the sake of argument :) MusE lacks some very basic audio tools atm
which when added will make it a real contender in all aspects of audio
production under Linux not just midi.
MusE will not mature as an audio platform without them... and they just
aren't there. Midi automation too is sadly lacking - for me these are
the kinds of things that should be absolutely number one on the list...
and they probably are. Here's a priority list for me anyway..
1. Volume handles on timeline objects for fade in / fade out (and maybe
a panner) and crossfades between objects.
2. More logical naming convention for audio tracks (and maybe a 'take
list' for each audio track with full keep/delete options?)
3. Midi automation.
4. Remove audio HW tracks and replace with a HW list box like existing
midi HW system.
5. Replace Synth tracks with a special "plugin rack" - maybe a dockable
floating window?
6. Add Groups for tracks.
7. Anything else I can think of ;)
hope that is of some use
best
g
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
