Is it true that a hi-level vsti like Wavestation cannot save presets in fxp format?
Is it true that WS only can save complete RAM banks and inside these banks two presets don't have to use the same wavetables?
I read it in a music magazine and cannot believe it.
Or did I get something wrong?
Saving Wavestation presets
-
- KVRist
- 254 posts since 4 Nov, 2004
The source of light is darkness
-
- KVRAF
- 8677 posts since 24 May, 2002 from Tutukaka, New Zealand
Dunno about the .fxp thing. I have a h/w WS, and it should be the same, I figure, as Korg's blurb is that the VSTi is a direct copy of the h/w.
You can use the same wavesequence in several patches...a problem can be that if you are inside patch1 and you edit wavesequenceA, when you go to patch2 that also uses wavesequenceA...it is also changed in this patch. Just the nature of the beast. A patch is a complicated thing in a WS ... it's made of upto 8 parts ... each part can use any oscillator or wavesequence. Wavesequences are saved independently...you can save parts independently too - but the part only saves the reference to the wavesequence and all of the keyboard, filter, envelope, pitch settings etc, not the actual wavesequence data itself. You change the wavesequence, you also change the sound of that part and any other part that uses that wavesequence, but you can change a part without changing the wavesequence, and consequently all other parts using that wavesequence don't get changed.
A way around that is to copy and rename any wavesequence before you start mucking around with it, and bugger it up for all eternity.
Sounds funny, but it has definite advantages as well as disadvantages. You have to remember that a wavesequence is not an oscillator as such (although it's treated as an oscillator within a part) - it is a collection of individual oscillators all chained together - that's why it saves differently to the usual synth. Wavetables are different to wavesequences.
Hope I've not confused you even more
You can use the same wavesequence in several patches...a problem can be that if you are inside patch1 and you edit wavesequenceA, when you go to patch2 that also uses wavesequenceA...it is also changed in this patch. Just the nature of the beast. A patch is a complicated thing in a WS ... it's made of upto 8 parts ... each part can use any oscillator or wavesequence. Wavesequences are saved independently...you can save parts independently too - but the part only saves the reference to the wavesequence and all of the keyboard, filter, envelope, pitch settings etc, not the actual wavesequence data itself. You change the wavesequence, you also change the sound of that part and any other part that uses that wavesequence, but you can change a part without changing the wavesequence, and consequently all other parts using that wavesequence don't get changed.
A way around that is to copy and rename any wavesequence before you start mucking around with it, and bugger it up for all eternity.
Sounds funny, but it has definite advantages as well as disadvantages. You have to remember that a wavesequence is not an oscillator as such (although it's treated as an oscillator within a part) - it is a collection of individual oscillators all chained together - that's why it saves differently to the usual synth. Wavetables are different to wavesequences.
Hope I've not confused you even more
-
- KVRist
- Topic Starter
- 254 posts since 4 Nov, 2004
Thank you, kritikon! I'm not more confused as before. The thing is I don't own this Wavestation. We just had a discussion about it. I couldn't believe the lack of such a usual option like saving presets as .fxp. And the wavesequence thing is adapted from old times when RAM was most expensive. The translation into a software synth had to be more intelligent!
Hey, Korg, meanwhile we live in the 21. century!!!
Hey, Korg, meanwhile we live in the 21. century!!!
The source of light is darkness