Hello all. Back in 1990 I was a very happy Wavestation owner, and a couple of weeks ago my new Wavestate arrived, and I gotta tell you: I love this thing.
There is one thing that I won't call a "complaint", but: the Wavestate Sound Librarian (WSL) is (currently) not highly functional. I've seen people asking about uploading new sounds into the Wavestate[1], but I think that the easiest and most logical best next step would be for Korg (or someone) to build function into the WSL that allows for easy construction of new Performances and Layers.
I don't know if Korg is planning to do this. Regardless, it would be really really nice if Korg released the file formats for all of the various .ws* files that are used by the WSL.[2] This would allow people to hand-edit new .wsperf / .wssetlist etc files, or even build custom editors to build new performances. I'm really jazzed by the randomization features - imagine a utility that would input a set of .wsperf files and output a .wssetlist file full of new 'random' sounds based on the input Performances?
Okay, I'll quit my ranting. But - does anyone agree that this would be a nice thing? Does anyone know what Korg has planned for the future of the WSL?[3]
fstructure
[1] Don't get me wrong, that would be great - but methinks there is a vast unexplored space of interesting new sounds just waiting to be discovered with the stock unit.
[2] I dislike embarrassing myself in public, but - I've peeked and the .ws* files don't look like SYSEX to me. I could be wrong. They might be flattened C++ or Python structures - I can't tell. But while I'm on the topic, what would be ideal would be if Korg would make the source code for reading and writing the .ws* files Open Source. (I know there is some OS code out on GitHub now, but I'm pretty sure it's not this). If we had OS Python bindings to the WSL file I/O we could do all kinds of really cool stuff.
[3] Yes, it's probably possible to reverse engineer the .ws* file formats. It's the kind of thing I might have attempted back when I was 16yo. Alas - I'm not 16yo anymore.
Wavestate Sound Librarian (WSL)
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Real interesting read for us that did not have a Wavestation, thank you.
I also speculated over what this github wavestate_oss is.
Is internals like open source or what?
Or librarian approach externally?
Having no clue probably means I am not target audience for it.
I also speculated over what this github wavestate_oss is.
Is internals like open source or what?
Or librarian approach externally?
Having no clue probably means I am not target audience for it.
MIDI gear: Sequential REV2.16, Prologue-8, Hammond XK-3C, Kawai MP7SE piano, Nord Lead 2X, Roland D-05
-
- Posts: 3
- Joined: Wed May 13, 2020 5:15 pm
Thank you for your response!Narioso wrote:Real interesting read for us that did not have a Wavestation, thank you.
I also speculated over what this github wavestate_oss is.
Is internals like open source or what?
Or librarian approach externally?
Having no clue probably means I am not target audience for it.
I do not know for sure, but I believe that the code modules out on GitHub are Open Source additions to the Raspberry Pi Linux-based operating system upon which the Wavestate is built. I hope that is correct, and also I hope I'm expressing that clearly - my (perhaps incorrect) understanding is that the core of the Wavestate is essentially a Raspberry Pi with a nice DSP module.
I do not think the code out on GitHub is related to the Wavestate Sound Librarian.
All of that said: if Korg (or someone) made the .ws* file formats available (or some code to help with reading/writing those files), I would personally love to take a shot at writing some freeware utilities that could be used by you or anyone who wanted to dig a bit more deeply into the Wavestate.
fstructure
I've done quite a bit of reading and writing sysex formats mostly - but then there were specs what goes where in most cases.
I've done for cx-3 v2 where there were proper specs
Hammond xk1 and xk3c were reverse enginered since nrpn addresses corresponding to offset in sysex or the preset file xk3c.
So I could copy all leslie and percussion parameters into CX-3's all presets as I wanted them everywhere and similar with hammond. Hell of a job doing on every preset.
So Korg need to feed us something to work with, I think.
Are the possibly such structures in the github kit?
I've done for cx-3 v2 where there were proper specs
Hammond xk1 and xk3c were reverse enginered since nrpn addresses corresponding to offset in sysex or the preset file xk3c.
So I could copy all leslie and percussion parameters into CX-3's all presets as I wanted them everywhere and similar with hammond. Hell of a job doing on every preset.
So Korg need to feed us something to work with, I think.
Are the possibly such structures in the github kit?
MIDI gear: Sequential REV2.16, Prologue-8, Hammond XK-3C, Kawai MP7SE piano, Nord Lead 2X, Roland D-05