By the way for pattern effects, please consider non-linear fading too (exponential, logarithmic etc)! Maybe have the shape icons serving a toggle-able double purpose in your tool? One for the current automation generation part and one for transforming existing automation, for example have gradual step-wise in/out fading for a patterns worth of automation using the staircase icons.
Also it would be nice if the pattern effects would work on a scope larger then 1 pattern, but maybe you’re treading too much automasher territory?
Another thing that could be interesting would be some kind of zig-zag effect (I’ve proposed a tool idea for this some time ago, though it concerns pattern command values, similar idea could be applied to the automation editor, maybe: [Tool Idea] Zig Zag Note Event Panning ).
Getting this every time I click ‘fadeout’ When having lots of points, I use 12LPB if thay means anything?
'C:\Documents and Settings\Ian\Application Data\Renoise\V2.8.0\Scripts\Tools\com.harold.Automatron.xrnx\main.lua' failed in one of its notifiers.
Please contact the author (harold | hhausman@gmail.com) for assistance...
std::logic_error: 'automation.point: invalid point value. value must be >= 0.0 and <= 1.0'
stack traceback:
[C]: ?
[C]: in function '__newindex'
[string "do..."]:22: in function
main.lua:307: in function 'process_points'
main.lua:252: in function <250><br>```
<br>
<br>
<br>
Also getting the same thing with fade in:<br>
<br>
<br>
```<br>'C:\Documents and Settings\Ian\Application Data\Renoise\V2.8.0\Scripts\Tools\com.harold.Automatron.xrnx\main.lua' failed in one of its notifiers.<br>
<br>
Please contact the author (harold | hhausman@gmail.com) for assistance...<br>
<br>
std::logic_error: 'automation.point: invalid point value. value must be >= 0.0 and <= 1.0'<br>
stack traceback:<br>
[C]: ?<br>
[C]: in function '__newindex'<br>
[string "do..."]:22: in function <br>
main.lua:307: in function 'process_points'<br>
main.lua:242: in function <240><br>```
</240></250>
Afraid it only does whole pattern and really needs some refining! (EG uses Record so will write to Automation or Pattern Effects depending on Renoise’s settings and makes it hard to adjust etc.)
yeah, it’s cool, but there’s something that doesn’t feel right to me, and that is the tool settings taking over the edit-step cursor behavior. I’d like my cursor navigating in the pattern editor always be 1, be separate from a shape’s size, so I can quickly go to a note.
another request: have the pattern effects work on a mouse selection made in the automation editor, so you can select a portion and apply fade’s to only that selected section!
Yes I agree this is a bit annoying, fixing this would certainly speed up the workflow.
In terms of other constructive criticism, I loved the simplicity and elegance of v4 and it’s interface. Whilst v5 is cool it does seem its starting to get a bit cluttered with all the pattern effect controls on there too, maybe some tabs to separate the pattern effects and automation would keep it looking more elegant.
It should be possible to have it only pick up Edit Step when the window is first opened and then a local variable used if you convince Harold it would be neater or write a patch.
I don’t think selection within automation editor is currently available to the API unfortunately.
I hear you guys. I’ll try to push out another version this weekend. (Last two weeks of school here, lots of work to do)
I think I have a fix for the fade-in fade-out Lua error. Though, I still haven’t seen it myself. Can anyone describe a way to reproduce it from scratch?
I will do a rev on the thinking around how long each inserted shape will be. I understand that tying it to edit-step so directly is a little awkward.
Could the error have anything to do with the fact I was automating a vst effect paramater? I don’t seem to be getting any errors when using it on native renoise stuff.
Thanks for the update! Fade’s seem to work properly now (haven’t had a notice yet).
The step length thing is still not ideal imo, but this might just be my workflow? I rather have ‘Step length’ in your tool become ‘Shape size’ and have changing the value in the number box in your tool not automatically influence the step length, amount of space travel when moving the cursor!
This way, you can for example set the shape size to 8, use the default current step size or define your own step size using the Renoise shortcuts (ctrl+1 in my case) and be able to quickly travel to a point/ note-event in the pattern. Right now if you want to trigger a similar length shape at note-events placed within the range of the ‘Step length’ this is cumbersome, because you’ll need to adjust the step length. Sorry for the verboseness, does it make sense?
I’d like to be able to generate shapes, while stepping through the automation/pattern line by line.
