|
|
|
06-16-2009 06:13 PM | |||
|
|||
Great idea, spelled out once again. Perhaps this is a good way to manage multiple passes of automation, and advanced stuff like Preview modes.
|
06-17-2009 05:14 AM | ||
|
||
For me, this is absolutely essential. I make (and always have made) absolutely minimal use of automation in REAPER (and the DAW with which I previously had most experience, Cubase), simply because it's an absolute nightmare to manage it.
This is particularly true for the sort-of loopy projects I'm often working on, where lots of parts can be expected to repeat, then repeat with slight changes, etc. Needless to say, automation items, like our desires for audio items, should be "ghostable"/capable of existing as "shared copies"! Thanks. |
07-04-2009 03:30 AM | ||
|
||
I worked on a song yesterday with lot of automation, and remembered those issues. Just wanna give devs a hint that if reaper will have automation items, it will solve and make much-much easier lot of stuffs like:
* Copy envelopes when copying items and even... * Loop automation * Automation Ripple |
07-04-2009 01:56 PM | |||
|
|||
Quote:
The problem with automation items is how to link them to audio items. Podium does it in its "hierarchic" manner, but it is rather restricting since when moving items. I have managed in Reaper to use MIDI items with control change datas to automate plugins, which is far from being perfect, but partialy solves the problem of linking envelopes to plugins parameters. The Logic way is elegant and efficient and could be perhaps a good model for automation items ? |
07-19-2009 04:46 AM | |||
|
|||
One interesting consequences would be that we could handle data in automation lanes like items, but how would that fit with selecting and editing the automation itself ?
The editing functions are great, but how is this going to fit in ? One idea is to have a global automation-item mode. To edit automation disengage the automation-item mode and it's like it is now. Engage it, and automation cannot be edited directly but only handled as items. |
07-23-2009 06:43 PM | |||
|
|||
Just wanted to re-mention that this would give us very cool things like multiple takes, time stretching, easy copying and saving for later use, reversing? ;)
Just in case someone skips to the end! ;) |
07-24-2009 04:59 AM | |||
|
|||
+1000000000000000000000000000000000000000000000000 00000000000000000000000.
Seriously. Mentioned before many times, but we'll keep on asking for it until we get it. :P Ideally one should be able to use the same automation (in clips) for sending values to several outputs, should be able to send both MIDI (CC#, aftertouch, pitch bender, and *notes* too) and VST(i)/AU(i) parameters, and should have user configurable scaling and GUI display values. Once this will happen, I will finally begin to take Reaper seriously as a sequencer / music production tool / live performance tool (as opposed to audio recording / mixing / playback tool) as well. Something I have been hoping for ever since I started using Reaper. |
07-25-2009 03:47 AM | |||
|
|||
Maybe that is a good way to copy automation between lanes very quickly.
You could look at automation on a per-envelope level and simply copy the automation items between the envelope tracks. Automation items of envelope lanes would be auto-grouped per plugin, which would be important for keeping parameter sets together. Complicated stuff. |
11-16-2010 04:43 AM | |||
|
|||
[New] Discussion thread:
http://forum.cockos.com/showthread.php?t=68790 |
Issue Tools |
---|
Subscribe to this issue |