New to Scope, getting an old card soon (6DSP)

[emotive]

A couple of questions, firstly regarding XTC mode or VST-IM I was under the impression that it worked in a similar manner to other DSP solutions such as UAD and that I could use another audio card:

http://sonic-core.net/joomla.soniccore/ ... 56&lang=us

I have a suitable audio device, eg. a Focusrite 26 i/o but may want to switch between both setups (I have also Echo Audio cards).

Secondly does the RD drum machine allow triggering via MIDI or is it step sequencer based.

Cheers

[ShogunSpy]

A couple of questions, firstly regarding XTC mode or VST-IM I was under the impression that it worked in a similar manner to other DSP solutions such as UAD and that I could use another audio card:

http://sonic-core.net/joomla.soniccore/ ... 56&lang=us

I have a suitable audio device, eg. a Focusrite 26 i/o but may want to switch between both setups (I have also Echo Audio cards).

Secondly does the RD drum machine allow triggering via MIDI or is it step sequencer based.

Cheers

not to sure what you are asking? You would only need your scope card. To run xtr mode you need your Daw to run the scope audio drivers and have the scope startup screen closed. If you want to You could also run whatever other sound card you have on your daw and run scope independently you can send midi/audio back and fourth from your daw to scope this is the beauty of scope.
Sorry not to sure about RD drum.

[emotive]

If you want to You could also run whatever other sound card you have on your daw and run scope independently you can send midi/audio back and fourth from your daw to scope this is the beauty of scope.

Thanks for the reply.

Does this happen internally or will I need to use MIDI and audio via cabling of some sort?

As to drum machines, I am of the understanding that v5 of Scope platform provides synth & sampler + mix & master packs as standard for 6DSP cards.

[ShogunSpy]

Yes if it's on the same computer! you use virtual midi and audio connections...you build your own scope project to suit your needs

[emotive]

Yes if it's on the same computer! you use virtual midi and audio connections...you build your own scope project to suit your needs

Awesome, sounds like just what I need.

So am I correct that in XTC mode, Scope is running independently from Cubase, kind of like Rewire but are tied via an ASIO driver?

If I am wrong, please point this out

[ShogunSpy]

No for cubase to use xtc mode you would need to run the scope audio drivers. Why do you need a second sound card in your computer? Also search for a cubase project ect on this site it will give you more info on setups. New users become transfixed on XTC mode it's not the most creative way to use scope in my opinion. also sonic core does not support this mode anymore as far as I know it never fully worked 100%

[ShogunSpy]

just to give you an idea of my setup I am running live on a Mac mini I connect midi and adat to a pc running the scope platform from my audio card on the Mac mini a m-audio fw1814 I basically treat scope as a outboard synth and fx unit. Hope this helps

[emotive]

New users become transfixed on XTC mode it's not the most creative way to use scope in my opinion. also sonic core does not support this mode anymore as far as I know it never fully worked 100%

I have other DSP solutions that I use regularly, as well I wish to setup the VST System Link and those sound devices will be using Wordclock, i.e. via BNC.

So it's not possible to use SC devices as VST's?

I guess it may not matter if Cubase just interfaces to the scope environment via virtual MIDI cables and is routed back as an audio channel or do I not understand the concept?

Cheers and thanks again

[garyb]

sure it's possible. it's just not better than Scope mode imo.

[emotive]

I like UAD and Powercore and I'm sure there are Creamware equivalents.

What I suspect is, with V5, I will be working mostly in Scope mode but will occasionally use those other systems, and in fact I knew about Sonic Core even before then.

Besides I will only own a single card to begin, and then I must purchase software.

One thing I will say is, I do like the Sonic Core website, the wording is nice but the manual could do with a complete makeover since after all we are not just in a new millennium but also after the first decade of a new millennium.

[garyb]

well, it suffices as a reference for the system.

Scope mode desn't mean that you can't use your UAD or TC card. it doesn't mean that you can't use VSTs. it means you can use everything, including a cool piece of hardware that you own or borrowed all in your realtime mix.

[emotive]

My guess too is that it won't stop me from using Cubase but what I don't think I can do in any case is use more than one DAW at a time.

[garyb]

well, if one is using wave drivers and the other asio and the machine can handle it you probably can. there aren't many reasons to do that besides recording the playback of one app into another.

Scope is not inside the computer, from an audio viewpoint. the computer is inside Scope.

[emotive]

Supposedly my Echo hardware can support multi-client drivers, so I guess I am assuming that Scope can do this as well.

Thank you

[garyb]

no, there aren't multiclient drivers.

[astroman]

that depends on definition.
In the usual context 'multiclient' means exactly what you've written before:
one application is using Asio while another works on WDM.
I record with VDAT, edit under WDM and do (additional) FX processing via Asio in VST Host.
A Powercore completes Scope's sound flavour nicely.

cheers, Tom

[emotive]

Pity, I thought this would be a Scope strength.

[astroman]

well, you seem to misunderstand...
you just can't share the Asio channels, say 1-8 go to Cubase, 9-16 to Ableton... etc
afaik not even RME can do that trick - it's a design spec of Asio
you can have several apps on different Wave devices, tho.

cheers, Tom

[emotive]

Echo Audio products have multiclient functionality.

Even Karl Steinberg wrote a multiclient driver for non multiclient devices (not that I use it) so it's a mark against Scope in my view.

[astroman]

well, I'm not about rhethorics atm so let's see what ECHO writes in their own manual:

Q: What is “Multi-client audio”?
Multi-client audio is a feature that lets you use different inputs and outputs on your Echo card with different applications at the same time. This way, you can use several different audio applications with just one Echo card. Otherwise, you would have to use a different audio device for each audio application.
For example, suppose you own both Cubase VST (multitrack audio) and Reality (software synthesizer). You can now set Cubase VST to play out through outputs 1 through 6, and set Reality to play out through outputs 7 and 8. In previous Echo card drivers, you had to choose between one software program and the other.
Note that all of the various interfaces are multi-client. You could have an ASIO application, a wave application, and a DirectSound application all running at the same time. It's very flexible.

as you can see, multi-client is defined on the card level, and that's how the term is generally used
WDM devices are by default 'multiclient', as they act conceptually independant with a sufficient time frame for each pair
high performance stuff like Asio is different
(I would be aware for sure if the feature had been mentioned on my RME HDSP)
Scope is just like the rest - all use water for boiling

cheers, Tom