Hi,
I thought I'd try the program change feature in ST 2.5 stand alone with a via to evaluating Sampletank for live use. I am able to associate programs with program change numbers, but whenever I attempt to call one up ST2.5 crashes with an error message stating that some instruction referenced some memory that cannot be read and the program is terminating.
Has anyone else got this working?
Thanks,
Roger
Sampletank 2.5 Program Change Error
-
- KVRian
- Topic Starter
- 597 posts since 29 Nov, 2005
Thanks for that. I was hoping that the ST2.5 issue was just here. I'll raise this with IK. SaviHost did something nasty to my DAW when I tried to run it. It appeared to lock up and nothing I had available could kill off the process, not even kill.exe. I couldn't even shut down the PC, it was a power button press. I like the idea of using a mini-host as a workaround. But I'd have to be very confident in its controllability before taking it on stage. Sticking with hardware for now I guess. 
-
- KVRAF
- 1981 posts since 29 Feb, 2004
Now, that is very strange, I found SAVIhost and VstHost both to be very stable, are you using the latest releases ??cleverr1 wrote:SaviHost did something nasty to my DAW when I tried to run it. It appeared to lock up and nothing I had available could kill off the process, not even kill.exe. I couldn't even shut down the PC, it was a power button press.
What Windows version are you using ??
-
- KVRian
- Topic Starter
- 597 posts since 29 Nov, 2005
XP SP2 fully patched, and SaviHost 1.31 just downloaded from the link you provided. I do have a vast Sampletank Instruments directory containing two generations of both Sampletank and Sonik Synth along with many additional libraries, it could be that it was just busy whilst ST was parsing that lot. But still, I'd like to be able to decide when to kill off any non-system process. I might try a scaled down ST installation on my laptop to see if that's any better. When I get this working my biggest concern is load times. I'm not clear if ST caches any sounds in memory when a new patch is selected or if it's all loaded from scratch.asseca wrote: Now, that is very strange, I found SAVIhost and VstHost both to be very stable, are you using the latest releases ??
What Windows version are you using ??
-
- KVRAF
- 1981 posts since 29 Feb, 2004
XP SP2 should work fine, I am using the same ...
Have you disabled "Relist at Startup"? In some cases the relist can freeze certain hosts.
ST does not cache the sounds, so it only starts loading an instrument after it has received the PROGRAM CH message for that MIDI Part ...
If you are not using all 16 parts you can partially circumvent this by pre-loading into the reserve parts and change MIDI channel instead of using PROGRAM CH.
Have you disabled "Relist at Startup"? In some cases the relist can freeze certain hosts.
ST does not cache the sounds, so it only starts loading an instrument after it has received the PROGRAM CH message for that MIDI Part ...
If you are not using all 16 parts you can partially circumvent this by pre-loading into the reserve parts and change MIDI channel instead of using PROGRAM CH.
-
- KVRian
- Topic Starter
- 597 posts since 29 Nov, 2005
I tried renaming the Sampletank Instruments directory - no different so it's not ST. SaviHost seems to lock up when I select the Delta ASIO driver. I also have the RME ASIO driver installed on the system so this may be the cause of the problem. I'll try to install ST2.5 on my laptop which only has the RME driver to see if that works any better. I am a bit surprised that the issue with ST2.5 standalone wasn't picked up before now because it's been out for ages.
-
- KVRian
- Topic Starter
- 597 posts since 29 Nov, 2005
Got ST25 running under SaviHost on my laptop, and it's the business. Many thanks for the tip Asseca! Load times for most sounds are not that excessive so there's definitely some usefulness here in a live situation. Off to build some live maps now... 
p.s. I agree that setting up all the sounds across different MIDI channels is a good plan. It means zero load times and no noise coming off the reverb tails etc. during switching.
Roger
p.s. I agree that setting up all the sounds across different MIDI channels is a good plan. It means zero load times and no noise coming off the reverb tails etc. during switching.
Roger
