Can't load Sysex files into Wavestation plug-in
-
- KVRist
- 128 posts since 10 Jan, 2005
I have a load of Wavestation Sysex files I downloaded from (among other places) The Wavestation Patch Archive a few years ago when I had a Wavestation SR. They imported fine into the SR, but they don't do anything when I try to import them into the Korg Legacy plug-in. They show up OK (ie not greyed) in the browser, but they don't seem to do anything when I click OK. They look like text files and have the .syx suffix.
-
- KVRist
- Topic Starter
- 128 posts since 10 Jan, 2005
All fixed - I just downloaded a bank from The Patch Archive and the format is different to the ones I downloaded several years ago. The bank works well in the plug-in.
-
- KVRAF
- 3030 posts since 12 Mar, 2002 from Central NY
No problems here! 
Wavestation and M1 both load .syx just fine.
Wavestation and M1 both load .syx just fine.the secrets to old age: Faster horses, Richer Women, Bigger CPU's
https://soundcloud.com/cristofe-chabot/sets/main
https://soundcloud.com/cristofe-chabot/sets/main
-
- KVRAF
- 9217 posts since 23 Jul, 2002 from Pequot Lakes, MN
You're right. Maybe it was an earlier version that didn't (or maybe I've got it mixed up; that the older versions only imported sysex and not native formats).
ew
A spectral heretic...
-
- KVRAF
- 4229 posts since 9 Apr, 2003 from Right here, in front of my computer...
The first versions of the WS did import syx files, but they only supported individual dumps.
As one complete RAM bank requires three dumps (performances, patches, and wave sequences), and this is how all the WS syx files on the net are strctured (including all the ones on my site), people had difficulties importing sysex in the first versions, and some even created little utilties to split these files into three individual files which could be imported.
Korg realised this was pants, and upgraded the sysex import in the next minor WS update so it would now load in those combined dumps, and it's been like this ever since.
Note that data which points to card waveforms isn't correctly imported by the Legacy WS, you have to manual go in and assign the card waves to any patch/WS that uses them. This is bad...
As one complete RAM bank requires three dumps (performances, patches, and wave sequences), and this is how all the WS syx files on the net are strctured (including all the ones on my site), people had difficulties importing sysex in the first versions, and some even created little utilties to split these files into three individual files which could be imported.
Korg realised this was pants, and upgraded the sysex import in the next minor WS update so it would now load in those combined dumps, and it's been like this ever since.
Note that data which points to card waveforms isn't correctly imported by the Legacy WS, you have to manual go in and assign the card waves to any patch/WS that uses them. This is bad...
-
- KVRist
- Topic Starter
- 128 posts since 10 Jan, 2005
It must be something to do with my computer, because I downloaded those with an OS9 machine and when I look at the files they appear as text edit files. But when I download a 'fresh' one, they have a different logo with a little star in the middle and the word 'syx.' The newly downloaded files appear in preview as a 'SysEx Librarian Document,' whereas the files downloaded from a few years ago just say 'Plain text document'
-
- KVRAF
- 4229 posts since 9 Apr, 2003 from Right here, in front of my computer...
Sounds like you downloaded them as text files. They are not text, they are binary files, and downloading them as text files will corrupt them.
All my SYX files are in zip archives to avoid this, but if you downloaded uncompressed syx files randomly using a browser, you probably got them in text mode, so they will be useless.
All my SYX files are in zip archives to avoid this, but if you downloaded uncompressed syx files randomly using a browser, you probably got them in text mode, so they will be useless.