I actually had different ideas about the future of automation tracks
(The track is made and /then /you can attach it to different knobs)
But this seems fine too, but for one thing: some kind of projects would
have a lot of new tracks, and this would lead to confusion, even if you
put the tracks in a good order.
I don't see this as a great problem (maybe because I don't use a lot of
tracks nor a lot of automations) but we may start thinking about a new
feature in the Song Editor: you should be able to chose what kind of
tracks you want to see in two different ways.
These being:
- "Show type" tabs (by default, the Song-Editor will show all tracks,
but you may turn off "Piano-Roll" tracks, so they are not shown, or turn
off both "SampleTracks" and "AutomationTracks" to see only BB and
PianoRoll tracks)
- "Search tracks" field (imagine you want to see only tracks with the
name "Pad", then you write Pad and you will see all the tracks that
contain the word "Pad")
NOTE: when the program shows only some of the tracks, you may press Play
and hear the whole project. You could put the Solo in one of the shown
tracks and unmute the others to hear only what you see, or we may have
an "Unmute Shown Tracks" button, that would also fix this problem when
used while all the tracks are shown:
- Put Solo in one track
- Delete it
- Now you need to unmute all the other tracks manually
This said, I agree with this new kind of Automation Tracks.
Il 20/09/2014 10:29, Vesa ha scritto:
Ok, so here's again something I've been thinking about lately. And
which, again, may or may not lead to things eventually actually getting
done... ;)
See, there's currently a sort of inconsistency in the paradigms of the
different tracks. Instrument-, bb- and sampletracks all work with a
"per-track" paradigm: each track is connected to one thing (one
instrument, one bb-track, one sampletrack-fx-chain). Whereas automation
tracks work with a "per-pattern" paradigm, where each automation pattern
can individually be connected to different models.
I'm starting to think it would be a better idea to have automations also
work in a "per-track" paradigm. So that you'd connect a track to a knob,
and then all patterns on that track would always automate that knob.
Pros:
+ consistency with other track types
+ clarity: you'll know that a track connected to eg. "volume" only ever
has patterns that automate "volume"
+ ease of use: when you'd connect a track to a knob, you could then just
add new automations on the track with one click of the mouse. Compare to
current situation: you either have to clone an existing pattern (and
maybe clear it if you want to do a totally different curve) or hunt down
the knob you want to automate again and drag it to the new pattern
+ most people use automation tracks in this way anyway, I think (see:
clarity)
Cons:
- this might cause in some cases a need for more tracks in the project
(I don't see it as a big issue though, because again: clarity, most of
the time it's better to use a per-track system anyway)
- backwards compat might be a bit tricky to implement (should be doable
though)
This could also mean that we could discard the idea of a tempo track: If
we make it so that each model can only be connected to one track, then
it'll effectively mean that a tempo track could just be a normal
automation track connected to tempo.
There's also convenient features that could be implemented if automation
tracks worked in a per-track way: something which Tobiasz (Unfa)
suggested once is that we could draw the state of the automation as a
line between the patterns so that you could always see the automation,
and it could even be made so that the automation would be set at the
right value when playing from mid-song, eliminating the need to "burn
in" automations. This can only be done if automations work per-track,
though.
Opinions?
------------------------------------------------------------------------------
Slashdot TV. Video for Nerds. Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
------------------------------------------------------------------------------
Slashdot TV. Video for Nerds. Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
