At the risk of scope creep, any chance of multiple lanes per parameter to facilitate “takes” for automation?
@pernst wrote:
At the risk of scope creep, any chance of multiple lanes per parameter to facilitate “takes” for automation?
:-k Hmm. Fair enough to get all automation ideas on the table while I’m already revising the system.
I guess I could add the “use as composite track” option for parameter tracks as well. That should make it possible to manually compose a parameter track using take lanes, just like the current composite track feature. To make it automatically create new takes on recording requires a bit more work.
Can you describe a situation where you would use multi-take parameter tracks?
Out of curiosity: Are there any other hosts which support a multi-take feature for automation?
Before find Podium I tested tons of host: FL Studio, Orion, Reaper, Live, EnergyXT, Sonar (only a little)… and no, no one support this feature.
I don’t know about the “big” host as Cubase, Logic… but I can imagine that no, or it would be too complex with too many options, killing my workflow.
For me it would be useful if I could link my edirol pcr 300 controls to Podium controls/synths/effects as other hosts (the way for link controls of Orion to hardware controllers is the best, move the soft knob, press ctrl&L, and move your controller knob: done)
Then I would record a complex automation loop several times (by example the cutoff of a distorted 303) and I would join the best part of that loop.
btw, if you’re revising it, please allow only parameter recording when track is armed and master record is on.
It’s pretty weird for me when I move a fader in the mixer and the movement is recorded, without have track record or master record on even.
@Zynewave wrote:
:-k Hmm. Fair enough to get all automation ideas on the table while I’m already revising the system.
Thanks for being open minded about it and considering more additions…I can think of a few that will help…
1. Read / Write buttons controls per track. Global Read / Write as well.
2. A central Automation control point within Podium. An Additional Panel maybe or an addition to the Group Panel. Perhaps something that replaces the Group panel when in view. “Show automation control centre” or “Show arrangement automation”.
Nuendo and now Cubase 5 use this…
Watch the first minute or so of the video on this page to see it in action.
You can find out more detail about the central Automation management in Cubase here[/url:ls7n4z2h] Page 190 onwards.
3. Optional larger sized points. They can require a very steady hand when editing automation points.
4. Additional Automation types Touch, Latch…(more info on these in the Cubase link above Page 191 onwards).
I guess I could add the “use as composite track” option for parameter tracks as well. That should make it possible to manually compose a parameter track using take lanes, just like the current composite track feature. To make it automatically create new takes on recording requires a bit more work.
I think I would be quite happy for a longer than normal release time frame for 2.15 if you need more time to get it right and revise the automation in Podium. Please take as much time as you need.
Can you describe a situation where you would use multi-take parameter tracks?
Personally I would use it to choose from a few takes of a cut off parameter being automated. Of course there are many other parameters that can creatively benefit from this feature. Various Mix knobs, Wet e.t.c It could easily be very creatively used. Pernst may have yet another way, or maybe this was what he had in mind. I think it is a very clever idea either way.
Out of curiosity: Are there any other hosts which support a multi-take feature for automation?
I think there may be but then again maybe not. It’s not something I have heard of before not like this anyway. Podiums track hierarchy seems to in theory provide a pretty good framework for Pernst’s suggestion.
@LiquidProj3ct wrote:
I don’t know about the “big” host as Cubase, Logic… but I can imagine that no, or it would be too complex with too many options, killing my workflow.
That is where a central point for controlling automation in Podium (as in Nuendo and recently Cubase 5) comes in. It really is necessary as it simplifies Automation management making it very easy indeed. Quite a few cubase users wanted the new Automation controls from Nuendo. Initially I could not see why. What is the big deal? I can see why now after reading more about it. It is pretty slick IMO.
@Zynewave wrote:
[
Can you describe a situation where you would use multi-take parameter tracks?Out of curiosity: Are there any other hosts which support a multi-take feature for automation?
When I am recording a string or brass part and adjusting Expression as I play, or Wah position with a foot controller while playing guitar, the automation becomes an integral part of the midi or audio take. FL studio creates Automation clips, which does allow for different “takes” of automation.
You showed me how to create an Automation lane, then remap the lane to a parameter that already had an automation lane, causing the first lane to be muted. This allows for multiple takes, I was just hoping for something more elegant, as you have done with audio and midi takes. Possibly a solution that would play the previous take an associated automation until the “punch in” point was reached.
Thanks for your consideration.
4. Additional Automation types Touch, Latch…(more info on these in the Cubase link above Page 191 onwards).
Not sure about this. One of the things I always liked about Podium’s approach to automation was that when you click record it records all you play including knob tweaks – no having to decide type of automation wanted or setting up of params to record in advance which really kills the creative juices for me. The last thing I would want would be to lose that and be given an array of confusing automation options and types like in some apps (Reaper was terrible for this for a while). All I really want is for it to record those knob tweaks etc more faithfully than it currently does.
@aMUSEd wrote:
4. Additional Automation types Touch, Latch…(more info on these in the Cubase link above Page 191 onwards).
Not sure about this. One of the things I always liked about Podium’s approach to automation was that when you click record it records all you play including knob tweaks – no having to decide type of automation wanted or setting up of params to record in advance which really kills the creative juices for me. The last thing I would want would be to lose that and be given an array of confusing automation options and types like in some apps (Reaper was terrible for this for a while). All I really want is for it to record those knob tweaks etc more faithfully than it currently does.
I’m totally agree with this. I’d like that Podium would be an inmediate sequencer, not a full-options for record sequencer. I hate Reaper due to overbloating.
Hi guys… π
Believe me I have posted so many ways on this forum to simplify Podium over the years. Loads. I too want things to be as simple as possible but I think Frits will have to strike a balance between adding features in certain areas in Podium and avoiding complexity. (I think he has done a great job doing this so far especially as a one man operation).
The feature addition part is to please existing customers but IMO more importantly to draw in more users.
I think for music making purposes Podium IMO has long since passed the point of being more than capable (processing, mixing e.t.c) but there will always be a need to add more features (to stay competitive and maintain interest) or the development of Podium stands still. Adding more features can be done while maintaining simplicity.
I think the real time pop up you get when using Podiums Gridβ’ π and the central point for automation control in Cubase 5 are excellent examples of well designed, easy to use interfaces that provide access to very powerful features. In any case lets see what Frits cooks up π
A bump for aMUSEd and of course anyone else watching this thread that is not already aware of the new 2.15 automation thread discussing the new changes to it. π