We explored this problem a couple of months ago, but re-reading that thread doesn't reveal an answer which will work for me.
http://www.planetz.com/forums/viewtopic ... 77&forum=1
I have STS5000, recently purchased (not as upgrade, but standalone) and downloaded well after the release of the V3 stuff.
Meanwhile, my Pulsar V3 was made to a clean installed OS on a wiped drive. In fact, ALL drives on my new system were reformated between 2.04 and 3, and I bought a new V3 CD from CW to do my Pulsar install. No v2.04 sampler devices, projects, or presets anywhere near this machine.
But somehow, this "wrong sampler version" message started coming up every time I open projects (created under the new system) containing STS5000. Again, I can browse around and point it to my STS5000 file and then go on working, but its a bloody pain in the backside to do this everytime.
The discussion on the previous thread centered on problems probably arising from either devices or projects carried over from a 2.04 install. What then to make of this message occuring on my machine?
Strange, eh? Any one else see this one? Any ideas?
wrong sampler version - AGAIN !
answer from cw for solving this in sts3000 is: "rename sts3000 to sts 3000"On 2002-02-04 00:21, sandrob wrote:
try to rename "sts5000" to "sts 5000"! that's works with sts3000!
but in my case i solve this (before cw's response) on this way!
1. instal pulsar software
2. instal sts3000
3. instal pulsar software again (without unistal)
4. delete old sts3000
5. move new sts 3000 to sampler's folder
this work for sts3000!!!
thanks, guys, I'll try all these suggestions and see what works.
for the record, my install procedure was
1) wipe HD, clean XP install, tweaks, etc
2) installed Pulsar v3 from CD, followed by 3.01b downloaded from CW, followed by powerpack
3) installed sts5000 and transient designer, both also downloaded from CW
BTW, I noticed that both sts5000 and transDesgnr got placed in Plugins folder, but I later moved it to sampler folder. I first had numerous error-free uses after initial STS5000 install; problem with "old sampler version" first occurred days or weeks before moving this file to different folder.
Finally, contrary to my intiating post above, I have now recalled that there were two minor incidences of v2.04 pollution in my v3 install, which possibly could have triggered this problem. First, I copied some samples into my new sample folder (but no devices) and these came from old v2 sample CD which came with original Pulsar v2 purchase. Perhaps loading one of these sample programmes got my setup confused as to what's in there.
Second, my registration page at CW has somehow dropped my STS3000 number (and emails to CW have not yet resolved this - grrrr). Thus I am unable to load STS3000. (By rights, I should have TWO, one I bought with Powersampler, one with Propack) None of my current S/W #s will work on STS3000 now. At one point, in frustration trying to load STS3000, I tried the old S/W # from Plsr v2 for that device - again, its no longer on my page, but I had written it down. This ploy failed to get my STS3000 working, but it could be that that action is what triggered the "old sampler version" problem. Can't now recall the exact timing.
I have to say, I think the whole approach to device registration CW uses is kind of klugey and bug-prone. Hope they revamp this in 3.1 .
Anyway, I'll try these ideas and report back. tks again
<font size=-1>[ This Message was edited by: dblbass on 2002-02-04 23:53 ]</font>
for the record, my install procedure was
1) wipe HD, clean XP install, tweaks, etc
2) installed Pulsar v3 from CD, followed by 3.01b downloaded from CW, followed by powerpack
3) installed sts5000 and transient designer, both also downloaded from CW
BTW, I noticed that both sts5000 and transDesgnr got placed in Plugins folder, but I later moved it to sampler folder. I first had numerous error-free uses after initial STS5000 install; problem with "old sampler version" first occurred days or weeks before moving this file to different folder.
Finally, contrary to my intiating post above, I have now recalled that there were two minor incidences of v2.04 pollution in my v3 install, which possibly could have triggered this problem. First, I copied some samples into my new sample folder (but no devices) and these came from old v2 sample CD which came with original Pulsar v2 purchase. Perhaps loading one of these sample programmes got my setup confused as to what's in there.
Second, my registration page at CW has somehow dropped my STS3000 number (and emails to CW have not yet resolved this - grrrr). Thus I am unable to load STS3000. (By rights, I should have TWO, one I bought with Powersampler, one with Propack) None of my current S/W #s will work on STS3000 now. At one point, in frustration trying to load STS3000, I tried the old S/W # from Plsr v2 for that device - again, its no longer on my page, but I had written it down. This ploy failed to get my STS3000 working, but it could be that that action is what triggered the "old sampler version" problem. Can't now recall the exact timing.
I have to say, I think the whole approach to device registration CW uses is kind of klugey and bug-prone. Hope they revamp this in 3.1 .
Anyway, I'll try these ideas and report back. tks again
<font size=-1>[ This Message was edited by: dblbass on 2002-02-04 23:53 ]</font>
okay, here's the update. Turns out - solution couldn't be simpler.
Started by trying the easiest of the above suggestions. I went into Win Explr, and renamed STS5000 Device to "STS 5000" (i.e., inserted a blank)
restarting Pulsar, on first open of a problem project, still got error warning, and had to browse to sampler location as before. Did this, then saved project, and upon re-opening - Voila ! Problem gone.
My guess is when you save a Pulsar project file it saves set of pointers to device names in a list This list is actually some kind of a registry (Pulsar or Win) file which keeps track of actual device install paths and software device serial numbers. When installing my STS5000 the entry in this file has the space but the actual device filename does not. Sounds plausible, but who knows? Anyway this trick worked for me.
Now, if I could just get CW to sort out my missing STS3000 software key . . . . !
Started by trying the easiest of the above suggestions. I went into Win Explr, and renamed STS5000 Device to "STS 5000" (i.e., inserted a blank)
restarting Pulsar, on first open of a problem project, still got error warning, and had to browse to sampler location as before. Did this, then saved project, and upon re-opening - Voila ! Problem gone.
My guess is when you save a Pulsar project file it saves set of pointers to device names in a list This list is actually some kind of a registry (Pulsar or Win) file which keeps track of actual device install paths and software device serial numbers. When installing my STS5000 the entry in this file has the space but the actual device filename does not. Sounds plausible, but who knows? Anyway this trick worked for me.
Now, if I could just get CW to sort out my missing STS3000 software key . . . . !