New Tool (3.0, 3.1): Track Comments

Fun tool!

First off, great tool, having fun taking some of my paper notes and digitizing them inside all my Renoise files.

Now on to the possible bug, I don’t know yet what’s causing it but I uninstalled the Track Comments xrnx and the bug is gone.

1 open song.xrns
2 edit, save
3 load a different xrns or new xrns
4 Renoise keeps asking if I should save changes

The song.xrns does get saved but somehow Renoise thinks there are edits made after saving the xrns.

nice one

I will look into that in the weekend.

Okay, new version is in the first post!

Most bugs should be fixed now. Renaming, inserting, removing, swapping should all work now, even with the default track names!
The code is probably pretty unefficient, but this is due to the fact that I could not figure out how to have a track refer to itself (or to know its own position in tracks[]), thus, all tracks will be renamed in the song comments, if the name of one track changes.

Something I could/should still do in the future is some error checking: I you mess around with the track comments part in the global song comments things might go wrong!

Has anyone experienced any problems so far?
If not, I would probably put it up on the tools page.

So far so good. I’ve got a lot of notes, but most of it is separated track by track to avoid scrolling.

There is one little thing, although maybe its not a bug.

If I select all and cut a note from one track, then paste it on another track, then click “X” to exit, not all of it gets pasted, a couple of lines from the end are missing.

But if I hit Enter after I have pasted, all is well.

That is weird! Sounds to me like if the notifier is not called correctly after pasting and exiting the window or something. Maybe a bug in the scripting API?

I just updated this tool to work with Renoise 2.7. Have a look at the original post.

Do you guys think this is ready for the tools page?

did you manage to iron out the last-mentioned bug? (your previous post)
in my own experience i’ve had no trouble with it, but have not used it extensively either. i suppose it’s your call whether to put it on the tools page or not.

I am afraid that this is nothing I can fix, but has to be fixed in the API. Maybe someone from the dev team can look into this?

Now available at the tools page and compatible with Renoise 2.8!

http://www.renoise.com/tools/track-comments

‘C:\Users\x\AppData\Roaming\Renoise\V2.8.1\Scripts\Tools\de.fladd.TrackComments.xrnx’ failed to execute in one of its menu entry functions. Please contact the author for assistance… main.lua:259: attempt to index upvalue ‘current_song’ (a nil value) stack traceback: main.lua:259: in function main.lua:246

edit: I am using Win7 64bit

Mmh…strange…current_song is nil…
And you get this message when you do what exactly? Open a song? Open Renoise? Open the track comment window?

Hmm, it started working now, strange. i just opened renoise and tried it without loading a song. Tried second time and it worked.

The tool perhaps is initiated while there is no song-data there yet? Without looking at the code i can understand current_song will be nil if an expression “if not renoise.song() == nil then current_song=renoise.song()” is executed during the startup of Renoise, because then renoise.song() will always be nil (tools start faster than a new empty song has been initiated).

Updated for 3.0!

Updated for Renoise 3.1

Just tried this out. Tempted now to hack on it so I can save comments per pattern in a track.

I started hacking on fladd’s code (very nice!) and have been looking into a Renoise fx column hack as a way to anchor comments to patterns.

I’ve posted a new topic to discuss possible flaws with my idea.

https://forum.renoise.com/t/using-custom-fx-numbers-values-for-storing-tool-data-thoughts/47559