It doesn’t but there ain’t much things that you can do per line in automation either. You have the interpolation of the amount of ticks settled, up till the next line, which is the only advantage you have.
If that is what you need, then forget my suggestion 
The advantage for me would be; a significant workflow boost in speed, losing the necessity to enter and look through the pattern editor and click automation points in accordingly to the programming.
The automated process of analyzing the pattern editor content / (sequencer)selection and be able to translate all note events to envelope values with a certain decay/ramp factor by the flick of a button is what I’m asking for. Didn’t even think about the key-tracking device to do similar things, so thanks for the tip!
Every time you hit a note? Why not use a Key/Velocity Tracking Device and an LFO with Custom waveform?
Yeah, this is what I do all the time.
This would be fine if the space between each note/event was exactly the same each time, but not if there were variations in the note structure. Assuming Jonas wants the automation to always be at maximum when a note hits, and always be at minimum just before the next note, then the LFO length will also have to be adjusted to make the curve fit each time. Still totally doable, but it does require a little extra legwork, which is obviously what he’s trying to avoid.
@Jonas: For what it’s worth, I started doodling a script after reading this thread the other night. I did get something basic working quite quickly, but in its current form I’m not sure how useful it would be, since it only creates automation within the same track and note column that contains the notes. I’m guessing you probably want something a lot more flexible, with an interface that lets you select where to pull notes from, where to dump the automation curves to, etc.
Anyway… I’ll try to iron out some of the bugs and post a little script here for you later on.
1 Like
You’re right, I slightly mis-read his first post. Knew he couldn’t be overlooking something that simple.
You could use another track, in it have a constant tone and a signal follower. Either note off/note on or pattern effect volume commands to get the changes. Not sure if that;s much less work than doing in it automation but at least you would always see it right next to the notes that you want the effect with.
Edit:
I’ve created a dedicated thread for this tool:
[quote=“dblue, post:9, topic:30860”]
@Jonas: Give this a try…
Attachment 1536 not found.
man, i just cannot believe you sometimes. someone comes up with an idea, and you’re like ‘maybe i could throw something together’, and next thing we know there’s a working script. i swear to god, people like you are proof of the coolness of Renoise LUA scripting.
Cheers mate! 
What can I say… I like solving problems and losing myself in an interesting task for a few hours, and naturally I enjoy helping out fellow Renoisers whenever possible. If I see a problem or feature request that I think I can figure out myself, then I’ll usually just give it a shot. I normally have Renoise running all day anyway, to experiment with DSP chains, to test my own VST plug-ins, etc., so scribbling down some basic scripts is not a big deal either.
It’s just too much fun goofing around in Renoise! I just wish I could apply the same level of enthusiasm to my other projects like Glitch, haha.
1 Like
Perhaps you can combine your Lua fun with your Glitch backlog by improving this one:
http://tools.renoise.com/tools/drum-processor
Feckin’ hell m8! I’m gone from this forum for a few seconds and booooom, Dblue ftw! Thnx this is exactly what I was looking for!
Yep, this
Dude, it is super useful in its current state!
Another thing that could be useful for a future update, is a third slider that sets some kind of decay time, maybe? So a max setting would give the results as seen now, and a smaller setting would make the envelope die out faster, relative to when the next note hits. You hopefully get what I mean
This!
There should be a donate button on the Renoise forum for script wizzards.
v1.02 Update: (Available in the earlier post)
The tool now has Curve and Decay parameters for extra tweaking. Let me know if this is closer to what you had in mind.
Wow this is incredible dblue. 
Hell yeah, I’m gonna try and find out how to set up a paypal account, look into if I can use the Dutch ‘Ideal’ system to transfer some beer money!
Oh yeah 
very cool!
+1! keep up the good work!
looks good,i am not in front of the computer the next 3 days,but think this will be great for basslines (and of course more)
Hope, I’m not to bold introducing a ‘last’ request 
, an option to somehow be able to interpolate between min/max values over the pattern length(selection?), so for example you can have the shark-fins gradually increase or decrease in amplitude within the automation window! By the way, the tool as it is now is already proofing much more useful then simple cutoff automation, the speed with which you can fill/draw in the dots for multiple parameters and make variations for all kind of effects is uber-win!
I’m bumping this with another suggestion 
this tool is so nice on fast bpm speeds & expanded patterns where it draws in dots on every line, having high resolution variations possible within curves derived from note placement. Like shown here:
1667 
I think it would be nice if we could somehow control the even and uneven dots separately. In the picture above I had to pull every uneven dot down manually for the second curve. Having a slider to set the min/max value for the uneven dots would definitely save time! Like this took me some time, but the wobble sounds sooo good :
1668 
edit:
what about an inverted trajectory, inverted curve for the uneven dots? That could be cool too!
bissump
was thinking how cool it would be to have other criteria for the ‘automation from notes’ tool to trigger envelopes. Turn ‘automation from notes’ to ‘automation from …’ and have a selection box like in the advanced editors content mask.
So you can trigger envelopes from selecting out of: 'note, instrument, volume, panning, delay, effect nr & effect value.
Haha. Sorry mate, I’ve obviously been quite distracted with other stuff lately and forgot all about this. I don’t mind hacking together a basic little script if I can, but it’s very much a spur of the moment ‘right place, right time’ thing for me, and I get distracted by other things too easily when that original moment has passed. But I’ll try to keep your latest feature requests in mind, for whenever I do manage to continue working on this tool.
In the meantime, why not take a look at the source code yourself? Just unzip the .xrns to get the .lua code inside. It’s not like black magic or anything, and Renoise LUA scripting is actually quite straightforward if you can dedicate a few hours of time to learning the basics. It’s certainly a lot easier to modify existing scripts than it is to write your own from scratch, but in general I think you could probably pick it up pretty quickly if you put your mind to it. Then you wouldn’t have to rely on dumbasses like me who take forever to add new stuff