End of the Line for SFP

craighuddy · Post by **craighuddy** » Mon Mar 27, 2006 10:22 am

Right, I really was not trying to light a flame war here, as I said, I really am quite happy with scope as it is, other than the fact it locks now, when it did not used to. It is not that big a deal to shut down the sequencer before changing scope projects, but that is what led me to write CW about it upon when they told me there was not to be an update in the foreseeable future. I simply was passing on the info given to me.

If I really wanted to start a nasty rumor about CW, I would do it in the Cubase and Sonar and Live (etc. ) forums, not in a forum specifically dedicated to Scope users. That makes no sense at all. The ideal demographic to hurt CW would be those looking for an interface, not those of us that have already invested in Scope.

Anyways, we are past this ( I hope ) I for sure in the future will not post any info that CW gives me in this forum, or any other. Good Luck.

dawman · Post by **dawman** » Mon Mar 27, 2006 10:36 am

I think you did us a favor by passing on info that just confirms our suspicions. CWA has always took care of previous customers, so this is overdue IMHO. But SFP will never die. It will be carried on in the new form of SHARCS somehow. These are such powerful chips, that I can't see dual core doing anything except giving VST programmers more power to make their platform better. I myself am going to buy DSPs, crush them up and snort them for years to come. Where ever CWA/John Bowen go, I will follow.

To Us, And Those Of Us Like Us,

_________________
Jimmy V.

[ This Message was edited by: scope4live on 2006-03-27 10:51 ]

H-Rave · Post by **H-Rave** » Mon Mar 27, 2006 12:24 pm

But wait, does this mean I cannot use my lethal galactic destruction waveform which relies heavily upon... dual processor technology.I will not be able to reach the required 1280Mhz Waveform to be able to SPLIT ENTIRE PLANETS IN HALF!!!!!.Oh well I suppose I'll have to continue making normal earth music.
Butters.

H-Rave · Post by **H-Rave** » Mon Mar 27, 2006 12:40 pm

Either way it says clearly on my box THE LAST AUDIO CARD YOU'LL EVER NEED.And I believe it, Except maybe a 14 dsp Powerpulsar.

arela · Post by **arela** » Mon Mar 27, 2006 12:48 pm

where and when are the funeral?
do we have to bring beer to the party?

Good peaople; same discussion last year too!
Also next year, i hope

What happend to OSX support, tell me that Scope isn't the horse they gonna ride into the sunset! Anyway i guess they do a lot to keep us users satisfied for a long time.

First Noah, then the 3 ASB's - then??

Shroomz~> · Post by **Shroomz~>** » Mon Mar 27, 2006 12:51 pm

Make that 4 ASB's

arela · Post by **arela** » Mon Mar 27, 2006 1:03 pm

sh¤t - i'm late as usual

craighuddy · Post by **craighuddy** » Mon Mar 27, 2006 2:27 pm

On 2006-03-26 22:38, AndreD wrote:

Scope IS stable on dualcore, 5 month without any crash! are you using an old "copy" of windows xp?
Old Versions of xp are not compatible with latest mainboards, at least, if you cannot run any xp-update...

Hey Andre,
Of course I have a legit licence of XP, I may be stupid but a theif I am not

Seriously, I just found out my issue ( not the topic at all of this thread..) If ASIO drivers and config is unchanged, you can open and close SFP all day long while the seq is open. After I reinstalled XP a month or so ago, when setting up my default project, I selected a different ASIO DEST module than what I had been using prior. Thus the freeze whenever Sonar tried to release the driver.

Scope is dead, Long live Scope

CH

nprime · Post by **nprime** » Mon Mar 27, 2006 5:55 pm

Hmmm...learn something new everyday.

All I had to do was close Sonar to stop those crashes.

Thanks.

BTW, nothing lasts forever...but I can't imagine my studio without Scope.

Rod

valis · Post by **valis** » Mon Mar 27, 2006 7:46 pm

I've never tried to keep the main DAW app open while changing scope drivers, just seemed to make sense that yanking drivers out from under an app would cause a crash. Interesting to know that there are some situations where it works (Sonar). Logic & Cubase/Nuendo certainly bomb the entire machine quite nicely when you do it (Steinberg apps will often cause bsod).

wayne · Post by **wayne** » Mon Mar 27, 2006 8:05 pm

Whew! Basic stuff!

Dunno about Sonar, but cubase has a "disable audio" function if you wanna rip the drivers out while it's running.

This is generally one of the simplest concepts in DAW-land, and logically would make it one of the first learnt

grrrrr! woof woof!

symbiote · Post by **symbiote** » Tue Mar 28, 2006 1:37 am

Mm loading a new project works fine here in Logic 5. It just says something about ASIO and there's a "Try Relaunch" button. Works fine here!

Admittedly I might live in a different dimension, where things are just ever so slightly different. Ever had that feeling? =P

Post by **garyb** » Tue Mar 28, 2006 2:31 am

no, logic handles it that way, cubase bluescreens...it's really not supposed to be done...

[ This Message was edited by: garyb on 2006-03-28 02:32 ]

valis · Post by **valis** » Tue Mar 28, 2006 3:26 am

That's actually true, Logic does give the 'try relaunch' but unlike Scope, large Logic projects tend to occasionally blow up on me when I do that so I don't think I've done that in a few years. Logic just gets stuck in ram and corrupts the asio driver, still not fun and usually needs a reboot.

Anyway the fact that changing the scope project affects the ASIO host app is such a non-issue really, isn't it?

Shroomz~> · Post by **Shroomz~>** » Tue Mar 28, 2006 5:07 am

I've tried & tried but can't get cuba*eSX to crash by changing SFP projects. Even ones with different asio configs.

Wayne, do you mean the 'release ASIO driver in background' checkbox in Cub's Device Setup or something else?

katano · Post by **katano** » Tue Mar 28, 2006 8:07 am

Wayne, do you mean the 'release ASIO driver in background' checkbox in Cub's Device Setup or something else?

'release ASIO driver in background' means that ASIO is disabled when you switch to another application, i.e. sfp. -> no sound -> not usable for me...

about the 'load a project while seq oder daw is running': if you load a project, all drivers (fundament of all) are unloaded and loaded again, so ASIO. Imagine what happens when you change the tyres from your car while you where driving. I think some car will crash, some not

Mr Arkadin · Post by **Mr Arkadin** » Tue Mar 28, 2006 9:21 am

Why are creamware bothering releasing dynatube? i mean really we all know this is a dead platform and they're not supposed to be developing anything new for it :rolleyes:

voidar · Post by **voidar** » Tue Mar 28, 2006 9:29 am

Well, I think new devices like that is what makes it a living platform.

H-Rave · Post by **H-Rave** » Tue Mar 28, 2006 9:38 am

In General what really pisses me off is mindless paranoia and rumours from people who don't know their arse from their own operating system and then to validate their own inexperience, they buy the latest toy.
Oh and by the way that was me when I'm annnoyed.
And for the dynatube If you compare the pro 53 to the pro 12,obviously no comparison and then native guitar rig to dynatube,personally I can't wait

[ This Message was edited by: H-Rave on 2006-03-28 11:50 ]

Counterparts · Post by **Counterparts** » Wed Mar 29, 2006 3:29 am

craighuddy wrote:
Just wrote Creamware tech support about a lethal Dual CPU driver bug and the reply was that Creamware is not compatible with dual CPU's and that CW is not updating SFP in the future.

The good news is it is very stable on a single CPU machine

When Scope was developed, single CPU machines were 'de riguer'. Strangely, I still use one myself. No, make that two...

Not sure how this will affect the dual core technology .

Not in the slightest - they are completely unrelated issues.

There is a simple workaround for my issue BTW, but thought you all deserved to hear my response right from CW that SFP future is bleak at best. Too bad....

What would have been more useful to hear perhaps would be what your work-around is.

Why does not supporting dual CPU or hyperthreaded machines make Scope's future bleak? My development machine at work is a single-CPU machine, does this mean my company's future is bleak? The Linux server which I am helping to reconfigure for a customer is only a single-CPU machine. Does this mean that our customer's future is bleak?

Eventually, yes changes in computer hardware will require Creamware to change their DSP cards, but the current Scope cards still have a lot of life in them yet.

I personally think it makes sense to wait until a consistent new PC architecture is in the marketplace before making any such changes, things are very much in a state of flux at the moment, changes to the main buss and bridge sets (PCI-X, PCI-E and the like), changes to CPUs (dual-core, hyperthreading, Intels for Macs etc.) Things have a way to go yet before they settle down.

The current ATX form-factor, single-CPU, PCI bus configuration has been about for a while now and has been pretty stable and consistent which is why the current set of Scope cards are still very valid. Most PCs out there still have this configuration.

Royston