For a synth like Diva, that displays patch information along side the patch browser, it could be useful that this displayed information would actually be a text editor enabling quick comments to be added/entered and just as quickly saved.
Nothing major, just a little thing.
Cheers.
Cool patch documentation add-on ?
-
- KVRAF
- 3729 posts since 3 Nov, 2015
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
-
Funkybot's Evil Twin Funkybot's Evil Twin https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=116627
- KVRAF
- 12495 posts since 16 Aug, 2006
I'd be all over that. A one window approach to comments and tagging would be fantastic.Howard wrote:I like the idea, but I'm skeptical about how many people would actually use it.
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
One use, for me, is that when I browse sounds for a project I could create a temp directory where prospect patches would be saved. No need to do anything special to do that. But then, if it was possible to quickly enter comments as a patch is explored (changing octaves, playing chords, leads, making suggestions for the project, possible tweaks, etc...) then it would make it easier to go forward. For the time being I use a text editor to write comments as I play a patch. It works, although it would be quite convenient to simply type in that description box in Diva and then save the patch when done.Howard wrote:I like the idea, but I'm skeptical about how many people would actually use it.
Cheers.
-
- KVRAF
- 3817 posts since 8 Mar, 2006
hmm... this gives me an idea, for all u-he synths especially Zebra
how about a simple automation recorder that auto-pauses when nothing is touched/tweaked ?
Give the ability to switch it on/off to be saved on patch save. (near options like "save only active modules" ) .. it should make the file-size bigger but still small overall.
Then we'll have play/pause/rewind etc. buttons, a speed control and time position for the automation player.
This would be great way to document/capture a sound design process for a given patch!
.. can open a new possibility for "tutorial" patch banks and of course not only! Also a way to save a patch's undo/redo history forever and scroll effortlessly through.
how about a simple automation recorder that auto-pauses when nothing is touched/tweaked ?
Give the ability to switch it on/off to be saved on patch save. (near options like "save only active modules" ) .. it should make the file-size bigger but still small overall.
Then we'll have play/pause/rewind etc. buttons, a speed control and time position for the automation player.
This would be great way to document/capture a sound design process for a given patch!
