Although it was already mentioned in the Renoise 3.0 feature list, I would like to highlight this one.
User Kurtz mentioned there the following features:
- When releasing a xrns song, musicians can “lock/protect” their songs and samples, with a strong encryption mechanism
- protected songs can just be “played” through renoise but samples can’t be rendered, nor edited, comments can’t be edited, patterns can’t be changed… no LUA script can’t break the protection scheme.
The idea, that you get a “save” feeling of your protected songs out there, sounds great.
But my first skeptical thoughts are that it’s gonna be hacked (in the first week of release) anyway.
So how far should the devs go to actually make this a good working solid protection?
Or should it just be clear that everybody is responsible for their own stuff?
Since I’m no programmer I have no idea if this is even possible, but maybe there could be a Signed song system.
As your registered name is linked into Renoise, all songs you save could be automatically uniquely Signed (with a user defined key) like that too.
So when they are loaded into another/different registered version of Renoise:
- they just won’t load, since the username and key don’t match.
- Renoise goes into play-only mode.
- Renoise asks for the key/password for opening it for editing.
Since protection is a big thing nowadays I’m just curious who is also really interested in this kind of feature and what possibilities there are to make it happen.
Also to look for ways to bring back the songs section.
Thanks for reading