MSF : save device not editable

[nbyte]

Hi,
I have created own Instruments and saved with "save device".
I can reload my own devices from main menu but the edit button stay grey!!

I'm doing something wrong? Or is it a bug?

I'm on windows 10 Pro, using VST3 version of MSF in Bitwig 2.5!

Thank you for your help....

[nbyte]

Ok, I found out that I have to check editable before saving the device!
Is it possible to make Instruments that I saved without the editable flag - editable again?

[Tagirijus]

Just wanted to answer you, but you were faster than me, haha. You found it out on yourself, nice!

Regarding to your question: I guess that the only option could be Vojtech himself. Maybe he will be able to resave a "locked" device? He might "open" the preset anyway as the head developer, hm?

[jmg8]

Try this.....

Load the device, save it as a normal preset (named A).

Load a different device that IS editable.

Go into the edit screen and load the preset (A)

Now save it as a device but remember to make it editable this time

[Tagirijus]

Wait WHAT? ... this is some kind of hack, right? When the "Editable" tag is not set, it is supposed to be locked for the public, or not? With your trick user could hack a locked device, right? Or am I misunderstanding something here regarding the "Editable" tag?

[nbyte]

Cool - that works!
Thank you.

[David]

Me to Vojtech:
"Quick question: Is there any way to reopen for editing a device saved without Editable being selected?"

He to me:
"Hi David,

first hold ctrl+alt+shift and click Editable to set the flag . This feature will be removed at one point ."

[jmg8]

Already removed I think.
I tried that at one point but it did nothing.

[Tagirijus]

Already removed I think.
I tried that at one point but it did nothing.

For me it worked like this: I chose the device, which had no tag "Editable". Then I opened another device and switched back to the "non-editbale" device, which had this tag now. So the trick is to change the device after Ctrl+Shift+Alt-Clicking the "Editable" tag, I think.

[MeldaProduction]

All correct, right now it is like this for sake of backwards compatibility. But from the final release it won't be possible to use the ctrl+shift+alt hack anymore, so that people cannot open closed stuff for future 3rd party devices .

[nbyte]

@Vojtech: It is understandable that people cannot open 3rd party devices! But it should be editable for the creator of the devices!

[David]

@Vojtech: I don't see why the default for this isn't Editable. Regardless of how likely anyone is to want to NOT to allow it, the consequence of being inadvertently locked out from your own work by simply forgetting to set this is surely less desirable than the opposite. Or how about at least a warning pop up before it happens?

[nbyte]

Maybe it should be always editable by default when you save a device.
There should be something like publishing the device with the possibility to set the restriction.
Publishing is for giving away the device for sharing or selling!

[dmbaer]

+1 to both of the latest posts. This bit me yesterday, and I managed to figure out the hack by just messing around. But we shouldn't have to do this. A third idea would be to add a sound-creator-defined password for overriding the non-edit attribute.

[Tagirijus]

Regarding the last ideas: a default for "Editable" would be nice indeed.

Vojtech: will this kind of hack jmg8 wrote also be "fixed" in the final release? And what about the preset itself. Is it saved in a secure way so that no one will be able to just modify the plain preset file and set the tag "Editable" with a text editor or similar? In the end I am just wondering how "secure" this "lock method" is for 3rd party device creators. For me it is not important, since I fully support the open source idea and I most likely would not want to lock my devices anyway ... I am just curious about the system and how secure it is in the end.