Scope SRB

[synthguy]

Hey guys!

I'm thinking about getting a Scope SRB 15 DSP.

Does anyone know if all of the DSP's can be used or is it always go to waste and how did it work in old Creamware time...

[siriusbliss]

Yes, all the DSP's get used - and cascaded across your whole system when you load large or multiple devices.

Greg

[synthguy]

It seems you had some experience that you need to share

Hello, well I was going to try scope mode but since 5.0 offers it (xtc) natively then I guess I should try that instead, but the problem is I don't know enough about the plug ins since I'm also using a VST 2.4 compliant host for audio type tasks.

Anyway I'm a bit confused as to the 15th chip and can't understand why it would be for control related purposes only when I've read nothing to this end, so any research materials would be helpful here or if someone can explain how it was in the early days of creamware technology that would be appreciated muchly.

dank e

@greg, are you saying they can in fact all be used for DSP related purposes. A friend told me that in one section of the control panel it shows as 15 but in another it only shows as 14 but likely they were using really old soft, so if the 15th DSP can be absorbed, eg scalable technology, then SC must have mad devs

[siriusbliss]

@greg, are you saying they can in fact all be used for DSP related purposes. A friend told me that in one section of the control panel it shows as 15 but in another it only shows as 14 but likely they were using really old soft, so if the 15th DSP can be absorbed, eg scalable technology, then SC must have mad devs

Unfortunately I'd have to back through years of searching this forum to find any discussion regarding the phantom 15th DSP usage. My recollection is that with Scope 4.5 and now 5 that distribution is throughout all DSP's on the SRB and Pro cards. If the 15th was allocated to anything, it may have been for front-end I/O handling/assigning, or GUI overhead, but I can't remember.

All I know is that I've loaded a lot of devices and I/O on my Pro over the years, and it barely complains.

Scope is it's OWN system, and doesn't do any transcoding. It only shakes hands with the CPU to handle some graphics interface to the computers' mouse/keyboard, and monitors, and that's about all AFAIK.

So, you should get a lot of overhead with the SRB without much concern for hitting the wall on big, dense projects.

Greg

p.s. And yes, I'm pretty impressed as well by what the devs have been able to do with Xite and the AD21369 DSP's. I think even Analog Devices is impressed. Engineers I work with couldn't immediately determine how they managed to do it.

[synthguy]

All XTC plugins are listed as VST 2.0 plugins and dont get blacklisted.

That is not the info I get from HQ (fortunately).

The 15th DSP should not worry you. It is totally hidden in the scope OS for the user.

Well I still would like an answer if possible.

I still do not understand what app you are launching in the install folder and what for. Can you help me to understand what you are doing ?

SetupVSTIMScopePci.exe

Honestly I dont think that there is something like 'trancoding DSP code to native code'
That would mean that all scope devices are running on the cPU and you would see that definitely on CPU load

No, it's just a process, like FL wrapper, it's still VST but is stripped down in order to run in native VST hosts, there is no equal or opposite here. Personally I don't know what any of the acronyms mean because there are no FAQ pages at sonic-core.net but that's ok since they have 24/7 email support.

Thanks guys

[garyb]

yeah, all 15 chips appear in the dsp meter. no dsp system loads 100%, not even Pro Tools HD for $40,000. that's not how it works. the word was, when the 15 chip cards became 14 chip cards, that since the 15th chip was always reserved for on board functions, that at max load the other 14 chips could still handle all or most of those functions, so the 15th chip was removed to save money(less redundancy). this may or may not be fact, but Sonic /Core need not explain Creamware. the cards are what they are and do what they do, which is pretty cool.

Scope is not at all related to the world that is only in the sequencer, it is something that can make connections with the entire computer and the real world at the same time. it's not a windows sound card. it can be used as a windows sound card however, and also, because the users requested it, it can be used like a UAD or TC card and it's plugins can be accessed inside the sequencer via vst protocol. of course, just using Scope as a windows sound card or as a vst card really eliminates the coolest and most creative possibilities of the cards(and especially XITE!), but sometimes expediancy or convienience are more important. the nice thing is that it's very flexible.

naturally, everything must be setup and operated properly for correct function and happiness, but it DOES work.

it seems like there's some confusion...i apologise if i rant unecessarily.

[synthguy]

the word was, when the 15 chip cards became 14 chip cards, that since the 15th chip was always reserved for on board functions, that at max load the other 14 chips could still handle all or most of those functions, so the 15th chip was removed to save money(less redundancy). this may or may not be fact, but Sonic /Core need not explain Creamware.

This is my experience with other platforms, there is always a bit of spare capacity on each chip, but my question will always be the same, can the last chip still be used for "normal" dsp operations.

Scope is not at all related to the world that is only in the sequencer, it is something that can make connections with the entire computer and the real world at the same time. it's not a windows sound card. it can be used as a windows sound card however, and also, because the users requested it, it can be used like a UAD or TC card and it's plugins can be accessed inside the sequencer via vst protocol. of course, just using Scope as a windows sound card or as a vst card really eliminates the coolest and most creative possibilities of the cards(and especially XITE!), but sometimes expediancy or convienience are more important. the nice thing is that it's very flexible.

That's right, very well put, cool thing is these plugins are compliant to base 64, which ultimately means they can and will become 64 bit. That's one thing that gives me confidence so I guess people can come at this thing from various angles and pardon if I'm being corny here "the beauty" of the platform, the potential and so on.

The fact you can make a preset in say Cubase via VSTIM and then re-use that preset in Scope is an absolute boon I feel, imagine, a quick mock up of a recording, no need for any other solution, record something providing of course there's enough native CPU cycles or GPU acceleration and then change to scope mode with a more elaborate hardware setup; your drums are tuned already and you are away, what a timesaver, what a completely versatile system, it's the future and not the past so I only ask about creamware because the future can only be known from the past, at least for technology and veteran users are the only ones who can say as you say "SC need not explain creamware" and that's partly why I'm here I guess.

Anyway, thank you for the explanation it's most helpful.

[Mr Arkadin]

Gary i think you're wrong on the 15 DSP appearing in the DSP meter. It seems no-one has mentioned this, not sure why. Because of the 'phantom' 15th DSP (ie. because it didn't show up in the meter), Creamware renamed their boards 14 DSP cards so that people wouldn't keep asking: "why are there only 14 DSPs showing in my meter?" So you could only ever use 14 DSPs from the get go.

Then S|C came along and now their lines are all called Scope 14 DSP Boosters (the old SRB), SCOPE Pro is described as a 14 DSP system. S|C never had their products described as 15 DSP systems.

It's a none issue, the card is a 14 DSP as described in the product pages: problem solved .

[synthguy]

http://sonic-core.net/en/products/scope5.html

The fact of a mention means alot when you are designing a new system, which obviously S | C are.

Look at TC for example, even getting down to tintacks such as icons and so on missing, readme's not appearing etc., it's the only way to go, complete quality control.

[Mr Arkadin]

Sorry what are you seeing in that link?

[at0m]

Synthguy, the 15th chip isn't useable for you as end user. To anticipate any possible ranters , the same card is nowadays sold as a 14DSP card. Get over it.

[Mr Arkadin]

Did you get the existing DSP setup to run meanwhile ?

i don't think he has an existing DSP system judging from the other thread.

[at0m]

Did you get the existing DSP setup to run meanwhile ?

i don't think he has an existing DSP system judging from the other thread.

He installed the software with no DSP cards in his machine, and now wants an SRB as pure XTC card!?
Recipe for disaster

[Mr Arkadin]

He installed the software with no DSP cards in his machine, and now wants an SRB as pure XTC card!?

But he only wants it if it has that extra one DSP, otherwise fergedaboutit.

[Fluxpod]

Is it even possible to enter xtc without any hw serial-keys?

Man....that must be a first in planet Z history.

[nightscope]

14 or 15?

Both!!

[garyb]

thanks!

[synthguy]

14 or 15?

Both!!

Thank you for the graphic, so can someone explain why that is the situation or is the collective "brain" not powerful enough.

[Fluxpod]

14 or 15?

Both!!

Thank you for the graphic, so can someone explain why that is the situation or is the collective "brain" not powerful enough.

What card are you running.3-4-6-14-15 dsp gen 1-2 ? If you really want help...thats your last call before troll alert man.Really.

[synthguy]

Hi,

If I may ask a question here....

Those 4 DSP pulsar and 6 DSP pulsars, can the latter ever be generation 1 or were they all made as gen 2.

Another problem I'm having is understanding this ULLI thing (information is either scant, scarce or non-existent at HQ).

From stuff I've read here ULLI can be implemented in software as well as in hardware and the supposed test is 3 ms latency.

Now if you are running XTC or VSTIM how can you know if there is no ASIO driver?

Thanks & I hope someone can help