Zen - and here is 1.5.3
-
- KVRAF
- 3388 posts since 29 May, 2001 from New York, NY
You're going to love this.... Here is a new version for the universal presets manager. Also, don't forget to check the roadmap to see what's coming next…
New features
------------
* Added an option to extract/expand tags list with no matches
* Extended virtual banks slots to 127
* Added a dot indicator to identify untagged presets
* Added support for Audjoo Helix
* Added infobox messages and credits in the config page
Bug fixes
---------
* Fixed tooltip message for the previous preset button
* Fixed - sometimes tagging a preset would not be uploaded properly
* reduced CPU usage with UI refreshes
* fixed bug with uploading icon (would keep flashing after uploads were finished)
New features
------------
* Added an option to extract/expand tags list with no matches
* Extended virtual banks slots to 127
* Added a dot indicator to identify untagged presets
* Added support for Audjoo Helix
* Added infobox messages and credits in the config page
Bug fixes
---------
* Fixed tooltip message for the previous preset button
* Fixed - sometimes tagging a preset would not be uploaded properly
* reduced CPU usage with UI refreshes
* fixed bug with uploading icon (would keep flashing after uploads were finished)
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
And here is how the main new 2 features look like:

The tags list expand/contract feature is accessed through the down/up pointing arrows at the left of the list titles. Clicking the down arrow expands the list, so that all tags (including the one with no matching presets) are displayed. Clicking the up arrow contracts the list, showing only the relevant tags.

The dot next to some presets indicates that the preset hasn't been tagged yet. A preset is considered untagged until at least one tag from the instruments category is assigned to it.

The tags list expand/contract feature is accessed through the down/up pointing arrows at the left of the list titles. Clicking the down arrow expands the list, so that all tags (including the one with no matching presets) are displayed. Clicking the up arrow contracts the list, showing only the relevant tags.

The dot next to some presets indicates that the preset hasn't been tagged yet. A preset is considered untagged until at least one tag from the instruments category is assigned to it.
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
Yes, I like it too - the only little downside is that you need to expand the list if you want to tag a preset, and the tag you want is not listed.
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
Probably not - 1.5.3 was released today. Make sure you install the update.
- KVRian
- 622 posts since 12 Mar, 2005
I also notice some new behavior (I think). If I double-click in Zen on a preset to open the plugin's GUI, the GUI comes to the forefront. If I then single- or double-click in Zen on another preset which uses the same plugin, the sound loads ok, but the GUI disappears into the background. I don't remember it behaving like this before. I would prefer to leave the plugin visible if I have specifically opened it with a double-click. What do you think?
I love the way this project has turned out. Zen's database is about to bypass the size of my Kore database. I have the feeling that Zen is bound for great things.
I love the way this project has turned out. Zen's database is about to bypass the size of my Kore database. I have the feeling that Zen is bound for great things.
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
I've been trying various things to see if I could bind the opened plugin window to the host window, so that it would behave as if it had been opened in the host. I wasn't so successful, though, and thus commented (or thought I did) it out. Maybe I left some unwanted code somewhere, and inadvertently changed something.ZombyWoof wrote:I also notice some new behavior (I think). If I double-click in Zen on a preset to open the plugin's GUI, the GUI comes to the forefront. If I then single- or double-click in Zen on another preset which uses the same plugin, the sound loads ok, but the GUI disappears into the background. I don't remember it behaving like this before. I would prefer to leave the plugin visible if I have specifically opened it with a double-click. What do you think?
I love the way this project has turned out. Zen's database is about to bypass the size of my Kore database. I have the feeling that Zen is bound for great things.
My own database has more than 23000 presets. Things get a bit sluggish when downloading new presets (but perfectly usable if the UI refresh rate control is turned down a bit). At least it seems able to handle the load. That's good, because I expect databases with 200000 presets to be the norm.
Zen has indeed come a long way, but there's still plenty ahead. How exciting ! One thing is sure, whatever new features I add, I want to keep its overall feeling of simplicity.
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
Nothing in the log file ?
Runtime error can be caused by something missing in the skin file definition. Maybe something went wrong with the update, and you updated the .exe and .dll, but not the skin data.
Maybe you can you try to:
1. backup your zen.s3db file, presets/ and assets/ directory
2. delete your entire Zen folder
3. install Zen from scratch
4. replace the default s3db, presets/ and assets/ directories from the backup in step 1
Runtime error can be caused by something missing in the skin file definition. Maybe something went wrong with the update, and you updated the .exe and .dll, but not the skin data.
Maybe you can you try to:
1. backup your zen.s3db file, presets/ and assets/ directory
2. delete your entire Zen folder
3. install Zen from scratch
4. replace the default s3db, presets/ and assets/ directories from the backup in step 1
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
Well, I'll have to fix the message anyway - runtime error is not really explicit 
