Korg WAVESTATION Legacy - Patch always resets itself after reloading project

[Caine123]

hey guys, i wondered myself why suddenly there is an arpeggio sound and rechecked myold mp3 file and there is only the Slow strings, so i just switched these on, then it sounds identical, but saving and reloading the project all layers are on again! any ideas why this is like that? normally it should be saved with the project file? FL20

[beely]

The project restores the plugin state, which is the RAM banks loaded. If you made edits, but didn’t save those edits back to the RAM bank, those edits won’t be preserved.

[Caine123]

The project restores the plugin state, which is the RAM banks loaded. If you made edits, but didn’t save those edits back to the RAM bank, those edits won’t be preserved.

back to it, i never replied and continued, thx beely !

so shall i save the bank first (i dont want to overwrite my factory banks) and then save the preset?

[beely]

If you want to preserve the existing RAM banks, save those out as bank files, either to your drive, or just save the plugin state in your DAW as "Factory RAM" or something. Now you can always easily recall them.

Then I would suggest if you want to make your own edits, load in an init bank to clean out the RAM/s for your own use (save these as presets to your DAW for easy quick recall too), and make all your edits there. As you go and edit sounds, saving the performances/patches/wave sequences bank to the internal RAM bank, keep saving that edited RAM bank you're working on to a file - something like "User Bank 1", etc, and/or to a DAW preset, which ever is more convenient.

But the bottom line is, when you save the state of the plugin as a DAW preset, it saves the state of all the RAM banks. So when you edit a sound, and "write" that sound back to the RAM bank in the WS, to actually preserve the state of that edited bank, it has to be saved somewhere, either to disk, or as a plugin preset, otherwise the next time the plugin loads, it will load whatever the default state of the RAM banks is, and your edited banks and sounds will be lost.

The RAM banks are for your own use, if you never want to overwrite the contents of them, you'll never be able to to make and save your own WS sounds. The RAMs just happen to come with more presets, rather than being empty, which is a good thing, but you can save and load the contents of these at will - this shouldn't inhibit anything.

(I'll check back in 6 months for the reply... )

[rafa1981]

I never understood why they do emulate the quirks of hardware bank/patch saving and recalling.

[Caine123]

If you want to preserve the existing RAM banks, save those out as bank files, either to your drive, or just save the plugin state in your DAW as "Factory RAM" or something. Now you can always easily recall them.

Then I would suggest if you want to make your own edits, load in an init bank to clean out the RAM/s for your own use (save these as presets to your DAW for easy quick recall too), and make all your edits there. As you go and edit sounds, saving the performances/patches/wave sequences bank to the internal RAM bank, keep saving that edited RAM bank you're working on to a file - something like "User Bank 1", etc, and/or to a DAW preset, which ever is more convenient.

But the bottom line is, when you save the state of the plugin as a DAW preset, it saves the state of all the RAM banks. So when you edit a sound, and "write" that sound back to the RAM bank in the WS, to actually preserve the state of that edited bank, it has to be saved somewhere, either to disk, or as a plugin preset, otherwise the next time the plugin loads, it will load whatever the default state of the RAM banks is, and your edited banks and sounds will be lost.

The RAM banks are for your own use, if you never want to overwrite the contents of them, you'll never be able to to make and save your own WS sounds. The RAMs just happen to come with more presets, rather than being empty, which is a good thing, but you can save and load the contents of these at will - this shouldn't inhibit anything.

(I'll check back in 6 months for the reply... )

hey beely, thx so much, this time im faster

oh man, i dont get it at all.... i just used this option and saved as FACTORY RAMs


but, if i now write the edited patch (you can only save to RAM 1,2 or 3) on Card6 i need to choose RAM 1,2 or 3. but if u now overwrite it, are the other projects where i use WAVESTATION also changed with the RAM settings? e,g, i use WAVESTATION RAM 1 Sound 0 Ski Jam and overwrite it. will this also sound now altered/overwritten in other projects where i used Sound 0 Ski Jam?

sorry to ask so stupid!

i saved the STATE with FL Studio


and then dragged it in on another instance, sadly all other layers were again on, not the solo one only :/ so this didnt work. otherwise i would have used this method now.

I never understood why they do emulate the quirks of hardware bank/patch saving and recalling.

yes, i think they should update it and give a modern touch, let the old mode in of course too! but also offer a newer style of preset handling...

[beely]

oh man, i dont get it at all.... i just used this option and saved as FACTORY RAMs

Ok, so you saved RAM1-3 as a file, which you can always restore by loading it back into the plugin, incase you overwrite the contents of RAM1-3 with your own sounds and want the presets back.

but, if i now write the edited patch (you can only save to RAM 1,2 or 3) on Card6 i need to choose RAM 1,2 or 3.

Correct, because you always store your edited sounds in a RAM bank. (And need to make these edits permanent on disk by either saving the a disk file, or saving the project which should save the current state of the plugin, including the contents of all three RAM banks.

but if u now overwrite it, are the other projects where i use WAVESTATION also changed with the RAM settings? e,g, i use WAVESTATION RAM 1 Sound 0 Ski Jam and overwrite it. will this also sound now altered/overwritten in other projects where i used Sound 0 Ski Jam?

If you're not sure - take five minutes to test!

By default, the WS loads with RAM1-3 as the factory presets. When you save you project, it should save the state of the plugin, which includes the three RAM banks as they were when you made that project.

Anything you do in the plugin in a different project, won't affect the contents of the plugin when you made a previous project.

i saved the STATE with FL Studio

I've no idea what a "Channel State" is.

Presumably you should be using "Save preset as..." to save the state of a plugin as a preset.

When you save the state of a plugin as a preset in your DAW, it should save the entire state of the plugin (the same as what's saved when you save the project). All DAWs I know of work like this. I don't know FL Studio, but I'm sure you can save both plugin presets, and when you save a project, the plugins should be saved as they were in that project, otherwise no projects with plugins would ever be recallable.

[EvilDragon]

Disable responding to Program Change messages in Global section, then it won't reset patches on loading project. Not sure if that's a bug or not - but I suppose if you set a Bank Select and a Program Change message at the beginning of your project it'd also work fine.

[Caine123]

thx guys, @beely, will test shortly!

Disable responding to Program Change messages in Global section, then it won't reset patches on loading project. Not sure if that's a bug or not - but I suppose if you set a Bank Select and a Program Change message at the beginning of your project it'd also work fine.

thx man! i just set these first the 2nd and then the 1st option to disable, both times saved the project and reloaded, sadly again the layers were reset :/ from active layer
1 off
2 on
3 off

all were on again

[T-CM11]

all were on again

Have also you tried it in the latest version?

[EvilDragon]

Why aren't you using the latest update with the much better GUI

[Caine123]

oh man, i dont get it at all.... i just used this option and saved as FACTORY RAMs

Ok, so you saved RAM1-3 as a file, which you can always restore by loading it back into the plugin, incase you overwrite the contents of RAM1-3 with your own sounds and want the presets back.

but, if i now write the edited patch (you can only save to RAM 1,2 or 3) on Card6 i need to choose RAM 1,2 or 3.

Correct, because you always store your edited sounds in a RAM bank. (And need to make these edits permanent on disk by either saving the a disk file, or saving the project which should save the current state of the plugin, including the contents of all three RAM banks.

but if u now overwrite it, are the other projects where i use WAVESTATION also changed with the RAM settings? e,g, i use WAVESTATION RAM 1 Sound 0 Ski Jam and overwrite it. will this also sound now altered/overwritten in other projects where i used Sound 0 Ski Jam?

If you're not sure - take five minutes to test!

By default, the WS loads with RAM1-3 as the factory presets. When you save you project, it should save the state of the plugin, which includes the three RAM banks as they were when you made that project.

Anything you do in the plugin in a different project, won't affect the contents of the plugin when you made a previous project.

i saved the STATE with FL Studio

I've no idea what a "Channel State" is.

Presumably you should be using "Save preset as..." to save the state of a plugin as a preset.

When you save the state of a plugin as a preset in your DAW, it should save the entire state of the plugin (the same as what's saved when you save the project). All DAWs I know of work like this. I don't know FL Studio, but I'm sure you can save both plugin presets, and when you save a project, the plugins should be saved as they were in that project, otherwise no projects with plugins would ever be recallable.

thx a lot again, ok this is strange it doesnt work :/

my steps:
created a test project with 1 instance of WAVESTATION.
i chose RAM 1 and Patch 3


i then solo'ed layer 2


then hit WRITE and OK. Again i resaved the project. didnt work after reloading.

i did step 2 again and hit WRITE and OK and SAVED addtitionally to RAM 1 and saved the bank. after reloading again all 3 layers on :/

[Caine123]

all were on again

Have also you tried it in the latest version?

not yet

Why aren't you using the latest update with the much better GUI

i wanted to export all stems, save all settings before i update/upgrade (i already bought it in december the new collection upgrade) but i dont want that it might mess my current/old projects, bad experiences with other plugins ;D

[beely]

i did step 2 again and hit WRITE and OK and SAVED addtitionally to RAM 1 and saved the bank. after reloading again all 3 layers on :/

This is working as designed. On the Wavestation "Solo" is not something that is saved in a performance/patch - it's purely a temporary edit tool to help you focus on the various items you're editing. It's not a sound parameter and its status can't be saved. If you don't want to hear other patches in a performance, remove them, or turn their volumes down.

Try actually changing a patch reference in a performance instead while testing this.

[Caine123]

i did step 2 again and hit WRITE and OK and SAVED addtitionally to RAM 1 and saved the bank. after reloading again all 3 layers on :/

This is working as designed. On the Wavestation "Solo" is not something that is saved in a performance/patch - it's purely a temporary edit tool to help you focus on the various items you're editing. It's not a sound parameter and its status can't be saved. If you don't want to hear other patches in a performance, remove them, or turn their volumes down.

Try actually changing a patch reference in a performance instead while testing this.

aaaahhhh this is great! thx this worked and was saved in the session . thx so much!

last thing is, the joystick position however isnt saved, do you maybe know if there is a way to save it? it resets always when reloading the project.