Preference and Document Settings cleanup?

[Kirkwood West]

Is there any clean method to clear all preference and document settings? For example if I rename or change some they stick around if I save the document.

Seems like the only way so far is to unload the controller for preferences and for document settings to create a new document.

Screen Shot 2020-10-04 at 12.27.01 AM.png

[moss]

You simply add a button "Reset" and then set all your fields to their default values?

[Kirkwood West]

Sure... that can be done... but what about deleting them from the bitwig file all together... it seems like once these settings are created for a document... there is no way to delete them. I guess its a just an annoying thing to go through during development and these issues don't stick around long term once the extension is in a more finalized state.

[moss]

Sure... that can be done... but what about deleting them from the bitwig file all together... it seems like once these settings are created for a document... there is no way to delete them. I guess its a just an annoying thing to go through during development and these issues don't stick around long term once the extension is in a more finalized state.

You mean a setting appears, even if it got removed from your script?!
If this is the case you should report it to Bitwig.

[Kirkwood West]

Sure... that can be done... but what about deleting them from the bitwig file all together... it seems like once these settings are created for a document... there is no way to delete them. I guess its a just an annoying thing to go through during development and these issues don't stick around long term once the extension is in a more finalized state.

You mean a setting appears, even if it got removed from your script?!
If this is the case you should report it to Bitwig.

Yup. thanks for saying so. its been reported by me. I ran into another user here on a Bitwig discord who experienced the same thing. Soooo... I figured some discussion here would be helpful and maybe even some cool work arounds.

Not all of us can define document parameters in one take!

[spenza]

did you get any news on this or did you find a workaround yet?
thanks, steve

Sure... that can be done... but what about deleting them from the bitwig file all together... it seems like once these settings are created for a document... there is no way to delete them. I guess its a just an annoying thing to go through during development and these issues don't stick around long term once the extension is in a more finalized state.

You mean a setting appears, even if it got removed from your script?!
If this is the case you should report it to Bitwig.

Yup. thanks for saying so. its been reported by me. I ran into another user here on a Bitwig discord who experienced the same thing. Soooo... I figured some discussion here would be helpful and maybe even some cool work arounds.

Not all of us can define document parameters in one take!

[moss]

Sadly, this issue is still present. Will need to bring it up again...

[spenza]

one way worked for me. but i am not sure if it is consistent is to generate a new UUID here:
https://www.uuidgenerator.net/version1
and paste it in your document. after that you still have to remove the extension in the preferences.

Sadly, this issue is still present. Will need to bring it up again...

[Kirkwood West]

one way worked for me. but i am not sure if it is consistent is to generate a new UUID here:
https://www.uuidgenerator.net/version1
and paste it in your document. after that you still have to remove the extension in the preferences.

Sadly, this issue is still present. Will need to bring it up again...

Thats a great solution. it will cause you to redo the controller preferences all together and those settings will still be stored with the document as long as its "alive" but at least its in a skeleton closet.

[spenza]

one way worked for me. but i am not sure if it is consistent. you can generate a new UUID here:
https://www.uuidgenerator.net/version1
and paste it in your document. after that you still have to remove the extension in the preferences.

Sadly, this issue is still present. Will need to bring it up again...

Thats a great solution. it will cause you to redo the controller preferences all together and those settings will still be stored with the document as long as its "alive" but at least its in a skeleton closet.