A question about STS

[Eiffel65Fan]

Hello,

I am aware that the STS samplers (as well as STS reliant presets on certain Scope synths) don’t work on 64 bit Windows. However, I have a bit of a strange question I want to ask. If you were to buy a used Windows 10 machine (desktop or laptop) with a 64 bit OS and x64 processor and then clean install the 32 bit version of Windows 10 on that machine (with the x64 processor), would you still encounter the BSOD every time you tried to load the STS stuff?

[garyb]

not if you contact support about the 32bit files. STS works in 32bit.

[nebelfuerst]

Does this also apply to Scope7 in Win7/32 ?
I get the attached message there.

[Bud Weiser]

"KBParam3" exists as .sys file in the 32Bit files Gary mentions above.
VxD not necessary anymore,- I just backupped these as also the ones originally delivered w/ John Bowen/ZARG synth installation files.
I deleted all .VxD and ARIALN.TTF files from my Scope v7 32Bit PCI installation.

So,- I got STS to run w/o warning messages in Scope 7 32Bit / Win 7 Pro SP1 (32Bit) on my HP xw server machine.
I have the files but will leave delivery to S|C support or Gary.
But I can upload when I get permission ...



Bud

[garyb]

sure, upload, or people can contact support.

[Bud Weiser]

sure, upload, or people can contact support.

Thx Gary ... done !

sts files 32bit.zip

(89.06 KiB) Downloaded 935 times

Bud

[nebelfuerst]

Wow ! STS now loads on my Xite/W7-32 system.
Thank you very much

[Bud Weiser]

Wow ! STS now loads on my Xite/W7-32 system.
Thank you very much

Congrats,- good to know !

Yes, the files work for PCI and XITE.



Bud

[Eiffel65Fan]

Since the STSs don't work in 64 bit, I bought a Sonic Core Expresscard and a Lenovo W540 laptop (which I have "downgraded" to 32 bit Windows 10 from the original 64 bit that was installed), downloaded the STS 32 bit files from Bud, installed Scope v7, put those files in the appropriate folder, plugged in my Xite, loaded up the STS 5000, and viola! No annoying BSOD!

However, I have a couple of wav files that I would like to test out with the STS so that I can go through the presets of the Vocoder III and Vocodizer with those samples. When I try to drag and drop any one of them in, nothing happens at all. I have converted the samples into AKAI S1000 S files with Awave Studio and tried again, but that didn't work either. Can you load wavs into the STS samplers? How does importing audio files into the STS work?

Another thing, this YouTube video https://www.youtube.com/watch?app=desktop&v=-_oTDVOSC88 has a module called "MIX 2 M Out" connected between the Analysis in of the vocoder and the left and right outputs of the STS. That module however doesn't seem to be included in Scope v7 by default. Are there any other modules that can be used as an alternative to the MIX for analysis? What is the simplest way to route the Vocoder modules?

[astroman]

The Mix 2 M(ono) Out can be replaced by a MicroMixer.
Send Left and Right source to 2 channels and use only 1 of the mixer’s output. Visually not as smart as Mix2MOut, but functionally the same.

Iirc you must at least create 1 keygroup (or program ?) in the STS sampler to get any sound out of it via keyboard.

cheers, Tom

[Eiffel65Fan]

I have tried to use the MicroMixer as a replacement for the MIX module, but I am not getting an audio output when using the Vocoder. Here are some screenshots:

Screenshot 1.png (287.14 KiB) Viewed 114807 times

Screenshot 2.png (546.48 KiB) Viewed 114807 times

Please tell me if I made any mistakes with routing.

My sound comes out through the headphones on the Xite, and I have discovered a handy tool from way back when called STS Creator for converting wavs to STS format.

[astroman]

You misunderstood about the purpose of Mix-2-M-Out: it‘s about summing a stereo signal to mono, so that both left and right channel are considered by the Vocoder‘s Analyzer input.
It‘s not strictly necessary at all, you could as well use ANY single channel.

In my replacement you‘d have to use MONO inputs on MicroMixer, left to channel 1, right to channel 2.
(your screenshot shows stereo input, which will be exactly the same as feeding the left channel straight to the Vocoder)

For simplicity use an(y) example program for the STS sampler, like the drum sounds provided.
In your case there‘s no Analyzer input, because the STS doesn’t output for the lack of a sample program.
Before the sampler plays a sample via keyboard, there MUST be a program with at least 1 keygroup definition.

Check the drum sample (f.e) for content and arrange your own samples in a similar way with keygroup(s) etc.

[Eiffel65Fan]

I have changed the MicroMixer inputs to mono and connected them (left to 1, right to 2), however I can only connect one of the mixer outputs to the Analysis In of the Vocoder; it won’t let me connect both the left and right outputs at the same time. Still no sound comes out when I use the Vocoder, but there is sound when I take it away from the routing (the default Beats 120 patch is used). Is there a way to change the mixer outputs to mono?

[astroman]

The MicrMixer output IS mono (which was intended because the Analyzer input is mono).
But you could use any single channel signal for that purpose, like the left OR right part of an Asio module. (Asio1,2).
In that case only sounds panned to the respective opposite panorama position wouldn‘t reach the Analyzer input.
The MicroMixer simply puts everything at center position.

For test play a loop via Asio into the mixer ( it‘s simpler ).
It will be silent until there‘s midi input. (press a key or feed a midi sequence)

I don‘t remember the setup of the default drum program on STS. (can‘t start the Scope PC atm)
It may not play over the full keyboard range.
Check the keygroup of that program and make it midi span the whole keyboard, in case there‘s only a small range of keys selected.

Did you read the STS2000 doc ? It‘s required and possibly a bit confusing initially, at least that was my impression back then.
Tbh I never used any of the STS samplers and only became aquired with the multi/program/keygroup/sample scheme by a real Akai sampler.

[Eiffel65Fan]

How is the MicroMixer’s output mono when you can see in my screenshot that there’s 2 outputs labelled L and R? (Which would likely indicate that it’s stereo?). By assigning the L and R outputs of the STS to 2 separate mono channels in the MicroMixer, you are correct that it combines them into a proper audio stream in the master channel, but if there was only one output of the MicroMixer labelled “Out”, then I would better see that it was mono.

And the STS drum program isn’t spread across every single key, just to let you know.

[drhardlove]

Since the STSs don't work in 64 bit, I bought a Sonic Core Expresscard and a Lenovo W540 laptop (which I have "downgraded" to 32 bit Windows 10 from the original 64 bit that was installed), downloaded the STS 32 bit files from Bud, installed Scope v7, put those files in the appropriate folder, plugged in my Xite, loaded up the STS 5000, and viola! No annoying BSOD!

However, I have a couple of wav files that I would like to test out with the STS so that I can go through the presets of the Vocoder III and Vocodizer with those samples. When I try to drag and drop any one of them in, nothing happens at all. I have converted the samples into AKAI S1000 S files with Awave Studio and tried again, but that didn't work either. Can you load wavs into the STS samplers? How does importing audio files into the STS work?

Another thing, this YouTube video https://www.youtube.com/watch?app=desktop&v=-_oTDVOSC88 has a module called "MIX 2 M Out" connected between the Analysis in of the vocoder and the left and right outputs of the STS. That module however doesn't seem to be included in Scope v7 by default. Are there any other modules that can be used as an alternative to the MIX for analysis? What is the simplest way to route the Vocoder modules?

Is this still a problem? I can open my STS 5000 in win7 64 bit, but I have not yet broken the code on how to load and use the samples.

[astroman]

STS Samplers do NOT work in 64bit... see the 1st sentence of your quote above.
That‘s why Eiffel65Fan used a 32bit system.
But the „problem“ wasn‘t related to the sampler in the 1st place, it was about routing of Vocoder signals.
You may in fact „load“ Scope plugins that are NOT 64-bit compatible and see them on screen, but they will fail to work.
(either crash or do nothing when fed with data)

[drhardlove]

STS Samplers do NOT work in 64bit... see the 1st sentence of your quote above.
That‘s why Eiffel65Fan used a 32bit system.
But the „problem“ wasn‘t related to the sampler in the 1st place, it was about routing of Vocoder signals.
You may in fact „load“ Scope plugins that are NOT 64-bit compatible and see them on screen, but they will fail to work.
(either crash or do nothing when fed with data)

Thanks Astroman.
Are there any sampleplayers or software emulations available, that will work within the scope arcitecture in 64 bit? I would like to play natural sounding instruments with the zero latency experience with my midi guitar setup.
Right now, I am looking for a good bass sample or emulation.
Or should I simply set up a 32 bit system for Scope?
I use it on a separate machine from my main daw anyway. I am running another machine with 48 channels of analogue inputs trough Motu Pro cards.
The scope is tapped into this with analogue output and midi.

[valis]

Setup a dedicated 32bit system separate from your 64bit system, imho. A 6 dsp card should be enough for STS samplers, and 2 cards (or a full sized 14/15dsp card) will serve almost all sampler needs.

[drhardlove]

Thanks a lot.
Will do. I have only the Xite-1.
I don't know how many dsp's it has actually.