PlanetZ forums - scopeusers.com

yes, since both synths behave as independent pieces of hardware, they can be used together in any way you like. SpaceF made a cool, free midi keysplitter and there is also one in Scope already. using the keysplitter, you can have two devices on the same midi channel behaving like a split keyboard on your controller very easily.

John Bowen has some really cool Solaris demos for the Scope plugin on his site, which would tell you a lot about his filters. the modular modules have a number of nifty filters, especially in Adern's Flexor and Flexor3. there are probably demos on the Adern site. also, there are demos on youtube, i believe.

sync to midi clock will work great on some devices and not as well on others. it depends on who made them and what they intended, with modular, no problem. also, there are some nifty things like BC modular and Scope Sync, which extend possibilities.

Scope isn't perfect and it doesn't do everything exactly the way you might want, but it does make everything that you might imagine POSSIBLE. even if Scope isn't directly involved, it will make connecting things that shouldn't be connected easy. without it, your computer is an island, unable to effectively connect to the mainland directly.

about wavetable synths- most of these will only be useful in 32bit windows, as far as the Scope plugins go. really, only wavetable stuff is affected, for the same reason that there are no Scope samplers in 64bit.

Hmm,

Let me have a try. I swear I had the Pro Wave working with Waldorf oscillators on x64. I think when I selected a preset that was using wavetables, it would load fine. Then when you changed the 'table', the sound did change. But if you selected the patch that uses regular oscillators then switching to a wavetable, the sound wouldn't change. Really odd, hmm.

-Tom

Sorry, I had a long day. I meant LightWave. It works fine. Vectron just crashes Scope for me.

I will record some of the presets for you. It comes with Scope. Filter sound pretty good actually!

-Tom

Hi,

Please excuse my crappy playing. I stopped keyboards for some 10 years and just started again...

mp3 but set to extreme in Lame encoder. I don't know why but some sounds are extremely quiet and other overload. But who cares. These are just the presets. You can always tweak them or create your own. Some of these sounds you will not be able to get out of an analog. Oh, bonus is that it uses very little DSP.

http://www.thomaslaskowski.com/Lightwave_demo.mp3

Cheers,

-Tom

garyb wrote: about wavetable synths- most of these will only be useful in 32bit windows, as far as the Scope plugins go. really, only wavetable stuff is affected, for the same reason that there are no Scope samplers in 64bit.

Wait... are you saying that I can't use a wavetable Scope synth like Solaris or Vectron if I'm running Windows 10 64 bit? I run a 32 bit version of Live because there are a few plug ins that haven't updated to 64 bit yet... Samplers, I don't care much about, as I like Kontakt, but wavetable synths... and synths like Solaris which have wavetable oscs and sample based oscs... they are a crucial part of what I want to do with the XITE-1. I if you're telling me they won't work, then that's a deal breaker for me.

If you have 64 bit Winblows, that's right, the sample based oscillators will NOT work. I am saddened

-Tom

tlaskows wrote:If you have 64 bit Winblows, that's right, the sample based oscillators will NOT work. I am saddened

-Tom

Oh... well then I'm out of here. I'm not going to go to a 32 bit OS just so I can run wavetable synths on an XITE-1. WTF? It's not like 64 bit operating systems just came out last month. If they haven't fixed this by now, I guess they don't plan on it.

Whew! That was a close one. I'd have been really pissed if I had gotten one into my home and found I couldn't run Solaris correctly. I guess I'll go back to my original plan and buy a Modal .002. Perhaps it's for the best.

Cheerio!

Wavetables (Vectron, Lightwave, Modular etc.) works fine under Scope 64-bit.

Sampleplayers does not work under Scope 64-bit.

Solaris works on XITE but only with 1 or 2 voices most of the time if the preset is complex. Solaris was only designed to run on the PCI cards. So Solaris does not run as well on the XITE as on PCI cards. This is due to technical restraints within XITE. Solaris for Scope was developed before XITE arrived, and there has not been an update for Scope Solaris and prolly never will. John Bowen said that it wasn't possible to redo Solaris 5 completely on XITE, he would have to make it "simpler" and seems to have made the decision to leave it as it is now.

petal wrote:Wavetables (Vectron, Lightwave, Modular etc.) works fine under Scope 64-bit.

Sampleplayers does not work under Scope 64-bit.

Solaris works on XITE but only with 1 or 2 voices most of the time if the preset is complex. Solaris was only designed to run on the PCI cards. So Solaris does not run as well on the XITE as on PCI cards. This is due to technical restraints within XITE. Solaris for Scope was developed before XITE arrived, and there has not been an update for Scope Solaris and prolly never will. John Bowen said that it wasn't possible to redo Solaris 5 completely on XITE, he would have to make it "simpler" and seems to have made the decision to leave it as it is now.

Yeah, I had heard that about the polyphony issues in Solaris... big sounds like that are often fine with low polyphony.

So what does this mean then?

garyb wrote:about wavetable synths- most of these will only be useful in 32bit windows, as far as the Scope plugins go. really, only wavetable stuff is affected, for the same reason that there are no Scope samplers in 64bit.

Is there a list somewhere of plug ins that do not work when used on a 64 bit operating system?

petal wrote:Wavetables (Vectron, Lightwave, Modular etc.) works fine under Scope 64-bit.

Sampleplayers does not work under Scope 64-bit.

Solaris works on XITE but only with 1 or 2 voices most of the time if the preset is complex. Solaris was only designed to run on the PCI cards. So Solaris does not run as well on the XITE as on PCI cards. This is due to technical restraints within XITE. Solaris for Scope was developed before XITE arrived, and there has not been an update for Scope Solaris and prolly never will. John Bowen said that it wasn't possible to redo Solaris 5 completely on XITE, he would have to make it "simpler" and seems to have made the decision to leave it as it is now.

Are you sure about Vectron? It crashed my Scope (PCI) when I tried to load it last night... Lightwave works fine, I did a demo of the presets with my professional playing of a 6-year old.

Let me try to load it again...

-Tom

zerocrossing wrote:

petal wrote:Wavetables (Vectron, Lightwave, Modular etc.) works fine under Scope 64-bit.

Sampleplayers does not work under Scope 64-bit.

Solaris works on XITE but only with 1 or 2 voices most of the time if the preset is complex. Solaris was only designed to run on the PCI cards. So Solaris does not run as well on the XITE as on PCI cards. This is due to technical restraints within XITE. Solaris for Scope was developed before XITE arrived, and there has not been an update for Scope Solaris and prolly never will. John Bowen said that it wasn't possible to redo Solaris 5 completely on XITE, he would have to make it "simpler" and seems to have made the decision to leave it as it is now.

Yeah, I had heard that about the polyphony issues in Solaris... big sounds like that are often fine with low polyphony.

So what does this mean then?

garyb wrote:about wavetable synths- most of these will only be useful in 32bit windows, as far as the Scope plugins go. really, only wavetable stuff is affected, for the same reason that there are no Scope samplers in 64bit.

Is there a list somewhere of plug ins that do not work when used on a 64 bit operating system?

If not sure if there is a list, but there should definitely be a a list on S|C website so people know what they are getting... hmm...

I couldn't give a damn about sample players. I'll just use software or cheap hardware that I have. The wavetables work FINE, it's the samples/wav files that do not work at all.

-Tom

zerocrossing wrote: Yeah, I had heard that about the polyphony issues in Solaris... big sounds like that are often fine with low polyphony.

So what does this mean then?

Deciding for XITE or not is not matter if Solaris runs well or not.
Even on a 15 DSP Scope PCI card, Solaris is limited to about 2 or 3 voices of polyphony.
You´d need several cards to change that to some point.

Read here ... http://forums.johnbowen.com/viewtopic.p ... 736#p20736 and follow up posts.

All the big SCOPE stock synths run well on XITE-1 and Minimax is the only one showing a minor GUI issue in regards of OSC#1 octave (footage) switch where you might been irritated visualy when switching between 16' and 8', but sonically it works correct.
I always hoped that would have been fixed though.

All the smaller ZARG synths,- SC versions of Ambient, Dark Star and Orion custom and even the discontinued CombPlus Pro (except the biggest ZARG Solaris v5, Quantum Wave and Rotor EX) work fine too.

All the synths sound very good and extremely close if not on par w/ the original hardware, even @44.1K !
You´d be fine @48K always IMO.

I tell you because I´m a old pro musician since mid 70th and owned, played and worked with almost any dinosaur synths in the past decades in studios and live.
I sold a lot of hardware synths already mid 80s but still own a (my last out of 3) Minimoog D and Oberheim Xpander.

Minimax is a dead-on Minimoog D emulation and there´s only one little thing where all Minimoog Ds already behave different, the feedback loop trick when you feed it´s output back to the audio-input.
Minimax mimiks that too, but the way it behaves is the behaviour of the synth it´s modelled after,- and my original Minimoog D behaves different the way I can pump much more signal level back into the audio-in than I can do w/ Minimax the audio input level all the way up.
So, I guess, during modelling/coding proces, they used the original Minimoog low-level output instead of the hi-level one and that makes the big difference.
What´s also different is the keyclick when programming very short VCA attack and decay times.
There´s no keyclick like it comes from the original Pratt-Read keyboard action in a Minimoog D, but for such patches it´s part of the sound like the keyclick in a Hammond is.
Otherwise, Minimax nails a Minimoog D sound.

SC Prodyssey (optional), Profit-5 as well as ZARG Prowave 1.2.1 or SC ProTone and ZARG ProOne v3, they all sound authentic to my ears.
YouKnow 7 is cool too.

SC Lightwave (v5), Vectron and Vectron player are good wavetable synths.

Don´t underrate the Creamware/ SC small synth collection,- you´ll find many sounds working well in many music production/recordings too.

The STS sampers are AKAI type but way beyond a original AKAI S-1000.
Stay w/ 32Bit OS if you need it, if not, go 64Bit.

It´s worth to keep a machine running w/ XITE-1D/ XITE-1 and w/ 32Bit OS up to now and use it like any hardware soundmodule.

So, not everything works flawlessly, but you won´t lose much.

Since I sold my SCI Prophet-5, Oberheim OB-8, Roland MKS-80 and -70 as well as 3 Oberheim Matrix-1000, I´m happy to have a old Creamware SCOPE card and XITE-1 in the home studio.
Both running SCOPE 5.1.
There´s no SC stock device replacing a Oberheim synth, but I have my Xpander and the VSTi Sonic Projects OPX Pro II ...
But jhulk once came up w/ a Oberheim SEM type filter for BC Modular IIRC and we´ll see more near future.

For me, the main issue w/ SCOPE is MIDI preset system/ MIDI CC assignment and total recall,- not the sound or minor bugs of a very few devices.

Bud

What is wrong with the MIDI preset system? I've never saved any mapped controllers in a preset

-Tom

tlaskows wrote:What is wrong with the MIDI preset system? I've never saved any mapped controllers in a preset

-Tom

It doesn´t do total recall.

You don´t save assigned controllers in the synth´s "presets",- there´s a separate "MIDI preset" bank for every synth which unfortunately has to be "moved" to bank-number "0" in the synth´s preset bank list in addition to be recognized by the specific synth.

I recognized when I prepared my Kurzweil PC361 for controlling several SCOPE synths in a project.
Did a multi-zone setup in the KURZ using it´s sliders, control-pedals connected as well as wheels, buttons and into 3 parts devided ribbon controller, then assigned related MIDI CCs to the SCOPE synth´s GUI knobs and saved "MIDI presets" to the SCOPE synth´s related preset-banks where you find a "MIDI preset"-bank for every synth always.

For a long time I thought it´s my fault, but it doesn´t work the way I expected,- and it´s cumbersome notating all you do to make re-assignments every time you launch your project again.

While SCOPE was up, everything worked flawlessly, but next day, most controller assignments in SCOPE were gone when the project was recalled.

When using pitch wheel, mod wheel and sustain pedal only, it doesn´t become obvious because that´s the standard controllers working always and don´t need any special assignment.

I think that´s not only a issue w/ SCOPE 5.1 but was existing in previous versions already.

It would be great when SCOPE allowed to store (or recalls automatic) MIDI CC assignments on project level, so once you assigned everything in a given project and save that project, it will be reliable recalled once you load that project again.

When SC would fix that, I´d use SCOPE/XITE on the road as a synth module for sure.
It sounds too good not to do it,- and it could be used w/ some outdated and now cheap IBM/ Lenovo Core2Duo machine, running WinXP, offering PCIexpress slot and running the in SCOPE missing Oberheim as VSTi (Sonic Projects OPX Pro II) in addition and probably a lite-on-CPU sample player like Sampleloard and/or Plogue Sforzando (SFZ) too.

Bud

Well... I do'd it!

Wish me luck.

best of luck. i'm sure you'll find it useful and i'm sure you will love how it sounds.

what is do'd?

it is done.
by him.

Do'd = buyed

He changes his mind like a girl changes clothes

Sorry I just woke up and it's not even 4am, hmm...

-Tom