First I load in the init bank to all rams.
Then I go in to patch edit and open up the waveform list.
I then doubleclick on one of the waveforms, for eample rom 4 wave 32.
Then ws crashes.
How should I do if else I want to make a sound from scratch?
I'm on a mac OS 4.11 with ws 1.6.5. This was not a problem when I used the dongle version. But I want the res filter and extra waves.
Is there some other way to initialize a patch? Like in the legacy M1?
Wavestation crash
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
wavestation crash
I'm having a similar problem.
When designing a sound, I managed to get this much done:
1. I can load the init patches.
2. I can edit and write a waveseq to RAM.
3. I can write a PATCH to RAM.
4. I can even save a PERFORMANCE to RAM
5. Most importantly, I can save ALL RAMS and MAKE CURRENT DEFAULT.
The instant I try to change the name of the Performance, Wavestation crashes.
The instant I try to make changes to AEG and filter settings, it crashes. In fact, it crashes any time I try to edit any kind of modulation, including any EG, filter, and env.
Any hope for a fix in the near future?
When designing a sound, I managed to get this much done:
1. I can load the init patches.
2. I can edit and write a waveseq to RAM.
3. I can write a PATCH to RAM.
4. I can even save a PERFORMANCE to RAM
5. Most importantly, I can save ALL RAMS and MAKE CURRENT DEFAULT.
The instant I try to change the name of the Performance, Wavestation crashes.
The instant I try to make changes to AEG and filter settings, it crashes. In fact, it crashes any time I try to edit any kind of modulation, including any EG, filter, and env.
Any hope for a fix in the near future?
-
deadsinatra
- Posts: 3
- Joined: Sun Feb 14, 2010 5:51 pm
Re: Wavestation Crashes
I have just bought it and have exactly the same problem. To be honest I want my money back as I am not into editing presets, I like to create patches from scratch, and this software won't allow me to do this due to it's instability. I'm on snow Leopard 10.6.5, but this problem does seem to exist on earlier versions of OSX as well.