Raul, let me see if I can try to explain this as I understand it… Let us say simply you want to read a line from a track ‘in real time’ with what is under the cursor as the Renoise transport is playing, and according to if there is a note or not under the cursor, flash a button (or ‘piano key’) that represents said note. Sounds simple doesn’t it? And you would think that the Renoise LUA api would supply a notifier that when the Renoise transport moves from one line to the next a function is called. Now AFAIK there isn’t such a notifier (as Danoise points out in the other thread. Probably due to slowing the Renoise transport down awful?)
…
Yes, in 2010-2011 are several comments from other users that deal with this issue.What I have observed…
-- The currently edited pattern. Never nil.
renoise.song().selected_pattern, _observable
-> [read-only, renoise.Pattern object]
renoise.song().selected_pattern_index, _observable
-> [number]
-- The currently edited pattern track object. Never nil.
-- and selected_track_observable for notifications.
renoise.song().selected_pattern_track, _observable
-> [read-only, renoise.PatternTrack object]
-- The currently edited sequence position.
renoise.song().selected_sequence_index, _observable
-> [number]
-- The currently edited line in the edited pattern.
renoise.song().selected_line
-> [read-only, renoise.PatternLine object]
renoise.song().selected_line_index --<------ Does not exist "_observable"!!!!
-> [number]
It’s probably a decision to avoid dropping performance…
… Either the ‘idle notifier’ …
How can this case be?
On the other hand. creating a function with a timer that bombs constantly could be very beast, right?