PlanetZ forums - scopeusers.com

On Windows 7, should I/must I downgrade to XP?

I want v5, so what do I need to do now?

i've you've read the oh so un-contemporary manual and thought a little bit about the content...
it should be quite clear that another card has no influence on the software side of installation.
The card is connected with a flat ribbon cable (STDM cable) to it's neighbour and the systems sees it as a DSP extension
(that's all about it and it's simple like that)
in case there are devices registered to the new card they are added to the current setup.
(if a keyfile is provided, unlikely with an SRB, tho)
All cards allways act as a flock, not individuals - for the user it looks as if the original one has grown.

cheers, Tom

I think I got this totally wrong...

I don't have SRB, I have 6 DSP with classic i/o.

I figured I'd use it as an SRB and installed 5.1 (driver installed, software won't work without a key) and found that it places .dll files in the Cubase directory which I guess is similar to the old VSTPlugins folder.

Probably a premature question, but I wonder, can I simply move the sonic core XTC/VSTIM plugin folder and my DAW will detect it or is there some special routine that Scope is using?

Thanks again and sorry for my bad

well, there is a section on this forum about XTC mode, which you probably noticed.
Check some of the posts and make up your mind if it appeals to you (the way to operate the card)
I've no idea about the details (except the very basic stuff) as it's never been my cup of tea at all.

As Gary fequently mentioned it's quite easy to operate the card parallel to the sequencer.
One just has to be aware about where Asio latency will show up.
Stuff is routed from Cubase via Asio into Scope and Scope's processing back into Cubase the same way.
Which basically means that Scope's realtime action is delayed twice the amount of the Asio latency.
This is what you enter into Cubase as compensation amount, so it delays all native tracks.
Then you can switch to Scope as to a physical hardware rack.
The big advantage is that you can build mixed processing paths (serial and parallel)
You could record only the final result or any intermediate 'node' if you send it to an Asio destination.
Which you'd set as a track source in Cubase.

As mentioned Scope is always realtime, you cannot render faster than realtime under no circumstances.
(with XTC mode or Scope SFP mode)
In XTC mode you'll have to close Cubase and open the Scope project file in SFP mode for any changes to be made.
Then quit SFP, start Cubase again and it will load the modified XTC project.
One pretty much looses most of Scope's 'on the fly flexibility', which makes XTC mode the 'unloved child' ... kind of
But for some folks it works rather well, so there's no general rule.

cheers, Tom

I'm not biased, for there is time to create sounds in any way I choose (PC only).

I don't expect I will bother much with XTC unless I'm using another interface but there is the point that I can use my Scope card as a stereo digital output, which is all I mostly need (my main interfaces are Roland UA-1G and novation x-station, which are both connected to a BMC-2) so I'm very likely to develop music inside the scope environment but sometimes native (instruments) is enough...

I just realized I cannot actually begin using the card until I have the allkeys file so although I've asked the previous owner I'm kind of thinking about getting 5.1 regardless as I'm on Windows 7 but if it (.skf) file arrives I may change my mind.

As I say it isn't much money for the platform, if you can obtain a reasonably priced card.

The thing is now, when I first became interested in Scope platform, there was no Scope 6. I am wondering of course what other costs there might be besides any plugins I could want.

--

As to these questions about latency, is it that when you record you don't actually use Cubase, something like VDAT instead?

@ your latest question: no, or yes in the case of VDAT, which I never use as I record in Cubase.
But the point is: you (should) listen (monitor) directly from the outputs of the card.
Even if you record in a native sequencer through ASIO.
If Cubase is the 'taperecorder', back in those days you also wouldn't monitor from the taperecorder Outs during recording
The route through ASIO for recording is a dead-end 'side street' from the main road which goes card-In directly to card-Out. Althus (almost) no latency, as the DSP card works as hardware

it doesn't matter what or if you record at all
any Signal coming from an Asio Host is 1 Asio latency unit delayed (from Scope's perspektive)
it will be 2 units late if it's send from Scope (a synth or a physical input), processed by a native plugin and then sent back to Scope for monitoring.
if ULLI in Scope's control panel (Asio latency) ist set to 4 ms, then a playback from Cubase is 4 ms 'late'
(close to irrelevant)
a native guitar amp simulation would deliver it's tone after 8 ms
(if the instrument is plugged into the Scope card)
which resembles the real world situation that you stand 2.5m from the cabinet, no biggie either

compensation only applies for stacked sounds with native and DSP processing mixed, drums are particularily sensitive.
one just needs to be aware of the presence of the (possible) delay
as long as it sounds cool noc action has to be taken.

cheers, Tom

astroman wrote:it doesn't matter what or if you record at all
any Signal coming from an Asio Host is 1 Asio latency unit delayed (from Scope's perspektive)

True of course, but the question looked to be related to a recording setting.
That's what starters in SFP more often seems to embarrass.
Mostly the idea of direct monitoring leads to an aha Erlebniss about the connection power of the cards/Xite

I get it now, we only use VDAT/Cubase to record things delayed and use direct monitor in all cases so we can have effects but they are only in the listen path.

it depends at what point in the audio chain of a sound you make a tap to an ASIO channel.
If the effect is included then you will record it.