I am having big problems with a somewhat strange situation. I have searched the forums for a solution and I can not find anything. It is the following error:
*** std::logic_error: 'invalid note_column index '1'. no note_column's are available.' *** stack traceback: *** [C]: in function 'note_column' *** main.lua:914: in function <main.lua:890> *** [C]: in function 'add_track_to_group'
This error appears in the following scenario:
1) A Function 1 with a notifier that requires continuous access to the selected note column. So changing column or track or group note, a value related to the column note is updated on a monitor, as the value of a note, or the value of the volume of that note...
2) On the other hand, a simple Function 2 that includes a group and several tracks within that group, all in the same function.
When executing Function 2, the Function 1 is also executed by changing the track (When you insert new tracks, change the index). Then, by inserting a group, it generates this error: 'invalid note_column index '1'. no note_column's are available.'
How can I avoid this error?
In the Function 1 I use if ( song.selected_track.type == renoise.Track.TRACK_TYPE_SEQUENCER ) then to prevent it from executing anything if the selected track is not a Sequencer Type (a group, master, send..., that do not include note columns).
It gives me the sensation that when adding several tracks and a group to later insert those tracks within the group, a specific scenario occurs with the index of the track that can "confuse" a group (group type) with a track (sequencer type)
The fact is that I want to have access to the information that contains the selected note column (notes, panning volume values, etc.) and that this is not a problem when adding tracks and groups in the same function.
Can anyone do some magic here with any idea?
Edited by Raul (ulneiz), 24 December 2017 - 13:35.