problem:
We made a lot of single layer soundfonts (.SF2) in Awave Studio 7.1 - most of them are drumkits.
When i load a .SF2 into a STS-4000 programslot, the samplenames of the program (soundfont) are partly scrambled - maybe the samplenames are too long but this seems unlikely... (20-30 chars)
Anyway, that's not the big issue because when i export this crappy program (.SF2) to .STS format, as always STS-4000 will (try to) load this .STS file from it's new location into memory...then after that there's no sound anymore - because the samples in the program are gone... (why?????)
After spending ages to find out what's going on, i decided to open the soundfont file in Awave Studio again, save the particular sample to a .wav file and load this wav into the crappy STS-4000 program.....finally this worked but it took much more time and it's insane to go on like this...!! a SF2 should work properly !
Another anoying bug of STS-4000 is when you close Pulsar or load another project and you haven't saved all programs (this happens often), a reminderbox will appear and ask you to save every unsaved program in the multi. This reminderbox also has a buggy "apply to all" option which probably ends up in a "nil reference on left side of == " error after saving 1 or 2 programs automatically.
Can anybody help us or does anybody recognize these problems?
(Creamware, please take a look at these for the next bugfix patch)
Thanx + greetz,
Miguel Vasconcellos
STS-4000 bugs in v2.04a
You might consider emailing this to support@creamware.de if you want Creamware to actually see this.