And for those who want to be involved in betatesting it... check here.
'Tick
.glo, .ksd, .h2p - why use your own format ?
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
-
- KVRian
- 538 posts since 23 Jan, 2008 from Hamburg, Germany
Really interesting project, thank you for this new approach. 
Will the internal format of zen be open or will it be another one of those .glo,.ksd,.h2p or .vstpreset formats?
Will the internal format of zen be open or will it be another one of those .glo,.ksd,.h2p or .vstpreset formats?
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
The internal format is indeed really simple - every preset has a numeric ID. Zen manages:
- the preset data which is a fxp file, named <numeric ID>.fxp
- the preset metadata which is stored in a sqlite database.
I guess I could document the database schema, if the project picks up enough momentum and there is an interest.
'Tick
- the preset data which is a fxp file, named <numeric ID>.fxp
- the preset metadata which is stored in a sqlite database.
I guess I could document the database schema, if the project picks up enough momentum and there is an interest.
'Tick
-
- KVRian
- 538 posts since 23 Jan, 2008 from Hamburg, Germany
Thanks for the info. That sounds great and it looks very future proof as the info is accessible with standard tools and not encrypted/obfuscated like most proprietary formats.
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
Well, not entirely. Commercial presets are obviously not stored as a plain fxp file, but as a .zen file, which is indeed an encrypted version of the fxp. Their metadata in the database, though, is not encrypted.Benutzername wrote:Thanks for the info. That sounds great and it looks very future proof as the info is accessible with standard tools and not encrypted/obfuscated like most proprietary formats.