Do you think it might be useful to have the pattern loop indicator still visible somewhere though?
That element is about the only part of the transport I need to know about. Maybe it could be a small icon in the border somewhere.
Another critical info, in my view, is the current instrument. That could also be put into the border we see at the top and bottom of your screenshot.
I can’t think of anything else from the periphery of the main edit window that I generally need to know during the majority of normal usage.
Perhaps Renoise could be ran as an SQL server, all song data being stored in tables. We could build our own interfaces in any framework we’d like - the GUI just being a client. One fixed system table could be used for triggering common functions.
Sorry… being a bit too radical, but I thought it was a funny idea
I believe there are a plethora of sql and sqlite server software packets where you can communicate with. The Lua environment supports socket communication so you could theoretically send SQL messages across a tcp connection and have your database stuff being done.
(speaking about a music collab sharing idea, using a central SQL/SQLite database is not a bad idea)