redlogic Posted January 28, 2013 Share Posted January 28, 2013 In the section of the Logic Manual about Selecting Automation Nodes and Lines, at the bottom of the page, it says: There are two choices available when changing the values of several selected nodes: Clicking a line or node allows you to change all values by the same absolute amount. Clicking outside a line, within the selected area (a node or outside a node), changes all values proportionately, by a percentage value. I'm not seeing a difference. Say I have automation stair-stepped 0.0 for 2 bars then -2.0 for 2 bars then -4.0 for 2 bars then -6.0 for 2 bars. If I select all those nodes/line and pull it all down 6 db, it stays 2dB stair-stepped no matter if I click ON a node or line, or OUTSIDE a node or line. Am I missing something? Link to comment Share on other sites More sharing options...
django Posted January 28, 2013 Share Posted January 28, 2013 out on a limb here.... especially telling you of all people redlogic *Nervous Face* this is by no means the answer I played around a little and noticed exactly what your saying to be true... until... you decrease (or increase) the size of the screen vertically then the numbers show that grabbing the line is stepped differently. Not only that but grabbing the nodes seems to stay at the original 'stepping' formula.... hope that makes sense, just have a play around and let us know what you think Link to comment Share on other sites More sharing options...
Jope Posted January 28, 2013 Share Posted January 28, 2013 [...]Am I missing something? I don't know... But I do know examples where there is a difference if you click either on a node or above the automation line in order to change values. I use my breath controller a lot, it gives perfect control for dynamics. Sometimes I want to change the overall volume of a note afterwards, meaning I have to change the height of the "hill" of controller data in Hyperdraw, so I shift-click-drag a rubberbox to select the whole "hill". If I click-drag directly on a node, the whole "hill" is moved up or down without changing its shape, meaning the nodes that were almost zero hit the ground very soon (when moving down). If I instead click drag above the curve, the "hill" flattens - the higer nodes move faster than the lower ones do. Link to comment Share on other sites More sharing options...
redlogic Posted January 29, 2013 Author Share Posted January 29, 2013 I played around a little and noticed exactly what your saying to be true... until... you decrease (or increase) the size of the screen vertically then the numbers show that grabbing the line is stepped differently. Not only that but grabbing the nodes seems to stay at the original 'stepping' formula.... I'm not getting that here with several sizes of increasing/decreasing the size of the screen vertically. Everything stays locked 2 db (my original example) apart. Link to comment Share on other sites More sharing options...
Jope Posted January 29, 2013 Share Posted January 29, 2013 Are you trying to get a finer resolution for dragging? This has nothing to do with the absolute-proportional-stuff. Press while dragging. Link to comment Share on other sites More sharing options...
redlogic Posted January 29, 2013 Author Share Posted January 29, 2013 No, I know about Control for finer resolution. Actually, this is purely academic curiosity. I was researching the Manual for another post, and ran across that info in my original post. I seem to remember it working as stated, but now it's not (unless I'm just blindly missing something or confused...quite possible). Link to comment Share on other sites More sharing options...
django Posted January 29, 2013 Share Posted January 29, 2013 ok, i used the test on apples pitch control because i find its automation to be very sensitive to movement with the mouse. makes sense to me that clicking and dragging the nodes is proportionate to the height of the screen and clicking the lines will always be absolute regardless of the screen size. (or is it the other way round...) or maybe i'm missing something here too... numerically i had pitch control not set to 0 to begin the test (-400ish) to be very precise automation was ontop of an audio file, not that it would matter. Interesting scour of the book though, i like the jope thanks for the reminder Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.