Wrong STS sampler

An area for people to discuss Scope related problems, issues, etc.

Moderators: valis, garyb

BrianB
Posts: 2
Joined: Fri Aug 10, 2001 4:00 pm

Post by BrianB »

When loading a project that includes the STS 5000 (in V3.0) I get the error message: "Detected old version of STS device. Please replace it by the new sampler version now." I then point Pulsar to the STS 5000, reload my STS programs, and save the project. Each time I reload the project it still gives me the same error. Does anyone know what might be going wrong here?

Thanks in advance,

Brian
ronaldmeij
Posts: 138
Joined: Mon Aug 20, 2001 4:00 pm

Post by ronaldmeij »

same thing here with the sts 4000

Pisses me off big time
User avatar
sandrob
Posts: 1122
Joined: Fri Sep 28, 2001 4:00 pm
Location: Slavonski Brod - Croatia
Contact:

Post by sandrob »

same thing with sts3000! i try to reinstal all software and clear registry but can't help!
this is anoyning!!!!!!!

now i work wit 2.04a because i don't know how to fix it.

i loose my program pool too!!
DivarU
Posts: 14
Joined: Thu Aug 30, 2001 4:00 pm
Location: the Low Lands

Post by DivarU »

yeah, i had the same thing. it turned out i had to download a new version (sts 4000) from creamware's 'my page'.
ronaldmeij
Posts: 138
Joined: Mon Aug 20, 2001 4:00 pm

Post by ronaldmeij »

YEAH BUT I DOWNLOADED A NEW VERSION AT MY PAGE AND I STILL HAVE THE SAME ERROR....

AND STS 3000 HAS MORE FILTERS THAN THE STS 4000 THAT IS REALLY CRAZY , I PAID MONY FOR THIS SAMPLER.

AND NOW THE PULL THIS OFF
ronaldmeij
Posts: 138
Joined: Mon Aug 20, 2001 4:00 pm

Post by ronaldmeij »

Ans i cant open the sample editor is sts 4000.

Give's everytime a error .......

but the filter thing really pisses my off

a free sampler with more filters than the 4000

ITs like e cheaper version of a bmw with a better engine and more extra's

No this aint right Creamware !!!!
User avatar
sandrob
Posts: 1122
Joined: Fri Sep 28, 2001 4:00 pm
Location: Slavonski Brod - Croatia
Contact:

Post by sandrob »

i download sts3000 2 times but it's the same stupid "old sts device message".
i write to creamware and they don't say nothing - no response!!
i made thread in creamware forum 2 times - no response from nobody!
ronaldmeij
Posts: 138
Joined: Mon Aug 20, 2001 4:00 pm

Post by ronaldmeij »

I think it's outrages that people who buy offical plugins

Are not being informed oubt errors or updates

We pay mutch mony and time in to creamware..

I want this problem fixed and as mutch filters or more as the sts 3000.

This is not the way to tread clients
User avatar
sandrob
Posts: 1122
Joined: Fri Sep 28, 2001 4:00 pm
Location: Slavonski Brod - Croatia
Contact:

Post by sandrob »

somebody solve this problem or any feedback from creamware!?!?!
Michaelj
Posts: 92
Joined: Thu Jul 12, 2001 4:00 pm

Post by Michaelj »

same prob here
lets all email CW so they
FIX THIS FAAAAST.
I love the V3 but this is no goood.

i did solve it this way.
I opened the 2.04 and from the (old)
sampler there I saved a new program.

then I opened pulsar 3.0
I cancel when it ask for the new sampler.
I manually drag in the STS 2000P
and load my saved program. it works.
this is ok for me, but for you out there that have alot of older projects its no fun !!!!.

New somgs composed from start with 3.0 there is no problem.
subhuman
Posts: 2573
Joined: Thu Mar 29, 2001 4:00 pm
Location: Galaxy Inside

Post by subhuman »

For old projects, simply run Pulsar 2.04a & your old projects there.

For new projects run Pulsar 3.0...

Yes, 2.04a does work with the 3.0 driver, you might have to copy (after you make backups!) the Pulsar3/driver directory to Pulsar2.04/driver, and also Pulsar3/sim.dll to Pulsar2.04a/sim.dll. MAKE BACKUPS, but this does work on my machine, so switching between versions is a snap. Did I say MAKE BACKUPS already? (Just of the files you're overwriting.)

Of course, I have always said "don't upgrade in the middle of projects" and I still think thats good advice, if you don't want to have any problems. Finish your work with 2.04a (you've heard me say that how many times here? hehe), then install 3.0 and create new projects from scratch... they will work fine.

I need to play a little more with old projects with STS4000 so I can give some additional advice here, but I haven't had the "Old version of sampler" message yet. I'll see if I can get that tonight.
User avatar
dbmac
Posts: 622
Joined: Sun Mar 25, 2001 4:00 pm
Location: Toronto

Post by dbmac »

Another point with the new V3.0 samplers - NONE of them respond to Midi CC#64-sustain pedal (HEX-B0 40 xx), which makes them useless for piano sample programs. The old v2.04 series sample players do respond to sustain pedal messages. These are now relegated to a "Pulsar2Stuff" folder, as if the sts2000p was an adequate replacement.

I don't understand CW's decision to exclude this essential piece of midi spec from their latest Sampler/players. This can't be simply an oversight since it has been pointed out ever since the STSxxx came out. And like I say, the old sample players include this spec.
/dave
User avatar
dbmac
Posts: 622
Joined: Sun Mar 25, 2001 4:00 pm
Location: Toronto

Post by dbmac »

Ok, sustain pedal (CC#64)DOES WORK if "AllNotesOFF" (CC#120)messages are filtered. I can set Cubase to filter this data, but not Pulsar's midi filter. An option to choose midi CC message filtering in the Samplers would be a solution.
At least I can now use pedal sustain with all Pulsar samplers if I'm running Cubase. All notes off - sheesh. What's up with that?
/dave
subhuman
Posts: 2573
Joined: Thu Mar 29, 2001 4:00 pm
Location: Galaxy Inside

Post by subhuman »

And maybe the reason I'm not having any problems with Sustain is because I have this filtered at my Midi Interface? Because when I read about your problem a few weeks back and we passed a few messages back and forth, I couldn't understand why it was working for me and not you.

Interesting discovery. I guess this is to fix the "stuck notes" problem that people were having? (Which, incidently, I haven't had problems with really)

_________________
<a href=http://infinitevortex.com>Infinite Vortex Audio</a>

<font size=-1>[ This Message was edited by: subhuman on 2001-10-02 13:23 ]</font>
User avatar
sandrob
Posts: 1122
Joined: Fri Sep 28, 2001 4:00 pm
Location: Slavonski Brod - Croatia
Contact:

Post by sandrob »

bdw, if you use gigastudio or halion you need note off for pianos, rhodes, upright bass.... but i don't have problem with sustain - not jet;)

i have problem with v3 and i'm still on 2.04a. maybe i'm stupid but i can't find how to solve problem with sts.

1. before i instal v3 i do format disk and make new windows instalation (98se) and do v3 instalation with xtc function enable.

2. i try v3 in custom and xtc mode and it's work, but i found that i can't use giga, sts and wavelab (external editor) in xtc mode and i do reinstal v3 with "xtc functions disabled" - then i instal sts3000 and made new pulsar defoult project with sts included.

3. every time when i try to open this project, or any projekt with sts3000 included i have message "found old sts device, replace with new..."

4. i try with full reinstalacion of v3 include drivers and clean registry, i download sts3000 again but can solve it!?

5. i make trhread on pulsar forum and send mail to creamware but i don't have response from anybody and i feel little frustration!

hope understand my english...and what i feel;)
thanks very much!!

sandro
subhuman
Posts: 2573
Joined: Thu Mar 29, 2001 4:00 pm
Location: Galaxy Inside

Post by subhuman »

sandro, I'll see what I can come up with, that is definitely frusterating. A few tips,

1. You don't need to reinstall to enable/disable XTC. This is in the Settings pulldown inside the Pulsar software -- there are "tabs" each which have options, one of the pages (can't remember which) has a "XTC Mode Enable" (or similiar) checkbox. Simply check/uncheck, and restart Pulsar OS.

2. When you install the V3 software, it should ask you for keys right at the beginning -- are you typing your keys in then? It accepts them?

3. Now, are the projects you are loading 2.04a projects, or 3.0? Some people have been reporting similiar problems when loading 2.04a projects. The obvious (or not so obvious) work around, is to finish those projects using 2.04a, or rebuild them under 3.0. If you need help running both versions at the same time, someone can help you with that.

I don't have the STS3000 yet (just the STS4000), but it did work for me just fine in my (limited) testing of it in V3 so far... no such messages. But then, I haven't tried loading 2.04a projects under V3 yet either.
samplaire
Posts: 2464
Joined: Tue Jun 05, 2001 4:00 pm
Location: Warsaw to Szczecin, Poland
Contact:

Post by samplaire »

Hi,

I also get the 'wrong sts 3000 sampler' with my mac... (you know, old project on the updated soft (3.0) - I know , Subhuman, what you said... but sometimes you need to go back to a project finished for example 2 years ago (I work with advertisement spots) - I don't want to waste my disk space to keep all the 2.0, 3.0 ... 5.0 versions ready for such situations (but in general I agree with you). My problem (mac one?) is bigger because if I click cancel button in the search dialogue box pulsar crashes with os#2 error (illegal instruction or wrong memory block)... Don't know what to do...

<font size=-1>[ This Message was edited by: samplaire on 2001-10-03 11:51 ]</font>
User avatar
sandrob
Posts: 1122
Joined: Fri Sep 28, 2001 4:00 pm
Location: Slavonski Brod - Croatia
Contact:

Post by sandrob »

i try to make "winstart project" with sts3000 included and when i start windows have question "find old sts device, replace with new..."
then i try to browse for sts folder and when i try to load them my windows crached too!!
User avatar
sandrob
Posts: 1122
Joined: Fri Sep 28, 2001 4:00 pm
Location: Slavonski Brod - Croatia
Contact:

Post by sandrob »

.... and yes! i do v3 instal corectly with all serial numbers and make brand new project with sts3000 device which i download from "my page" on creamware!
and it was all working corect!!

but, after i do reinstal of v3 i must do new project again, save it and when i try to open then "old sts device" problem start's.

uf, uf... my english!!! uf, uf...
subhuman
Posts: 2573
Joined: Thu Mar 29, 2001 4:00 pm
Location: Galaxy Inside

Post by subhuman »

Your english is great actually... I will see if I have the same problem with STS4000 shortly and let you know, it could be some bug.
Post Reply