I have problems with the sts4000 and sts5000 sampler. The timing is terible. I have tried the pulsar on 3 different motherboards but no succes. I did the latest chipset updates but.... When I ad a sts2000 sampler it becomes much more stabel. Is this a bug?!. Tried different latency's on pulsar software. Pulsar helpdesk gives me no solutions. Is there somebody who has the same problems? ore knows how to solve this.
Pulsar 1 card (2times)
1800+ AMD
Via 266a chipset
sts4000 and sts5000 have timing problems with VST
Are you sending:
1. Active Sensing
2. Lots of CC data
3. Lots of Sysex data
4. Midi Clock?
If so, disable them until your timing improves, so you can figure out if it's MIDI overload.
Next, do you have your STS connected to "Sequencer Midi Source" or from the hardware midi port "Pulsar Midi Source"? I have excellent success using the hardware midi ports connected to my eMagic AMT8 midi interface, which has the benefit of the Active Midi Transmission, which also makes your other midi hardware perform better ... it will track really fast (180bpm) 16th notes without glitching just fine, for example.
Hope this helps; if you have more info on how to reproduce your problem then maybe we can offer more advice.
1. Active Sensing
2. Lots of CC data
3. Lots of Sysex data
4. Midi Clock?
If so, disable them until your timing improves, so you can figure out if it's MIDI overload.
Next, do you have your STS connected to "Sequencer Midi Source" or from the hardware midi port "Pulsar Midi Source"? I have excellent success using the hardware midi ports connected to my eMagic AMT8 midi interface, which has the benefit of the Active Midi Transmission, which also makes your other midi hardware perform better ... it will track really fast (180bpm) 16th notes without glitching just fine, for example.
Hope this helps; if you have more info on how to reproduce your problem then maybe we can offer more advice.
