PlanetZ forums - scopeusers.com

I'd like to know this, even though I have a Windows 7/Cubase 6.5.5 system set up.

no, but that's not a problem. certification is helpful in that malicious internet software can't be installed in win8 without it. a driver for that you know the source of and that is for hardware you intentionally installed, it's not needed. in win8, you will need to disable driver signing during installation. once installed, driver signing doesn't come into play.

Theres some notes here - Win 8 - havent tried 8.1

http://www.hitfoundry.com/issue_20/w8_mast.htm

8 and 8.1 are the same.

The plugins under VST-IM are only VST 2.0, which in Cubase 7 is deprecated.

I guess I have my answer, not from the forum but from paying for and installing myself but hang on, lets wait for the excuse makers to tell me how awesome scope environment is and why I should not worry about the sequencer.

If you're referring to XTC mode, I would have thought that was deprecated along with Creamware.

Maybe it can work with a sequencer other than Cubase but it is a bit disappointing that I can't use it in this way due to the use of a decades old SDK.

Presets do not work, and in fact the plugins simply won't instance in Cubase 6.5.5 on Windows XP. As well there was no blacklisting of any scope plugins so in other words it will not run because that's right, it's too old.

If it was "deprecated" then why were the options left in the software?

I would guess that XTC mode was not worked on by SC like some other aspects of the platform that were not their priority. But just because they didn't 'turn off' XTC doesn't imply intention to support it through every iteration of OS or Cubase. There were some users happy to use it unsupported so I suppose they left it turned on for them.

This whole thing about XTC, Protools and UAD is this : these platforms can't run without a sequencer, and are therefore bound to the native CPU.

Scope (in Scope mode) - unlike these platforms - can run independently. You can plug a MIDI keyboard into it and play synths and do mixing without any host VST sequencer. Like real hardware.

Then, you can add a multitrack recorder to it. Again just like real hardware.

And this is the natural state for Scope.

Maybe Creamware did the platform a disservice by introducing XTC, but people wanted it, even though it wasn't Scopes intent. So I don't think SC should be held accountable for that.

I actually remember downloading the software some time ago and unpacking it with an exe extractor and as I recall, there were VST 2.4 plugins, so I don't understand what the situation is there, which in fact was part of the reason why I purchased it in the first place.

if you depend from cubase and vst3 then scope is not for you.
If you are more creative and open minded, then scope is a must have.

I know it can be used regardless, so the notion of it is or is not for me or you is a replete false assertion.

so it's for you too.

I guess.

I was just waiting to purchase the software at a reasonable price and all of a sudden got the email.

I probably would have liked to have gotten the synth pack but I don't know if it's worth it.

I am a bit confused by the 2x synth packs at the bottom and the standard synth package so if anyone can shed any light there it would be great.

The S|C Classic Synths near the top are two synths that aren't included normally with Scope.

The two bundles at the bottom, are Zarg synths made by John Bowen - also not included with standard Scope.

dante wrote:The S|C Classic Synths near the top are two synths that aren't included normally with Scope.

The two bundles at the bottom, are Zarg synths made by John Bowen - also not included with standard Scope.

Hi,

Do you think what's included in 5.1 would be enough to compose with?

I have (or had) powercore, never got the V-station because of :yes: no VST 2.4 compatibility but I know Scope can be used with the Sequencer (hence why I bought it) but this is where it begins for me, I have no idea of even how to set it up and must read unless there are some tutorials anyone is aware of.

there's a good manual explaing in detail how to connect audio and midi to the native sequencer.
In Scope project window you load the source and destination 'modules' from the project's main menu and put them into your project (=virtual studio).
The sequencer will 'see' these when available, they appear in the usual listing.
Modules are small (or big) graphical boxes with In/Out 'connectors' to connect cables to by clicking on the symbols.
That's the way of building your applied studio anyway, the same goes for a mixer or synth

emotive wrote: Do you think what's included in 5.1 would be enough to compose with?

I have (or had) powercore, never got the V-station because of :yes: no VST 2.4 compatibility but I know Scope can be used with the Sequencer (hence why I bought it) but this is where it begins for me, I have no idea of even how to set it up and must read unless there are some tutorials anyone is aware of.

The standard synths are good and I use for leads,but I love ProWave for pads - one of the Zarg synths.

For Cubase integration lesson, you can start here :

http://www.hitfoundry.com/issue_01/cubase.htm

There are integration articles on ScopeRise for other sequencers as well.

dante wrote:For Cubase integration lesson, you can start here :

http://www.hitfoundry.com/issue_01/cubase.htm

There are integration articles on ScopeRise for other sequencers as well.

Thank you for that information.

I was not aware of that resource so I will look at further articles.