End of the Line for SFP

craighuddy · Post by **craighuddy** » Sun Mar 26, 2006 5:41 pm

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

Not sure how this will affect the dual core technology .

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....

Post by **garyb** » Sun Mar 26, 2006 6:10 pm

this is NOT a bug!!!

[ This Message was edited by: garyb on 2006-03-26 18:10 ]

wayne · Post by **wayne** » Sun Mar 26, 2006 6:12 pm

Nuthin' bleak about the future of my Scope setup

craighuddy · Post by **craighuddy** » Sun Mar 26, 2006 6:21 pm

Drivers that lock some computers up but not others is not a bug? Hmmmm...

Besides the point of my post was to point out that future development is a no go, not debate if Scope.sys locking dual cpus up and not single cpus is a bug.

[ This Message was edited by: craighuddy on 2006-03-26 18:35 ]

Post by **garyb** » Sun Mar 26, 2006 7:01 pm

the drivers don't lock up computers! your "workaround"(closing sonar before opening a new scope project) is the way the thing is supposed to work!

craighuddy · Post by **craighuddy** » Sun Mar 26, 2006 7:16 pm

Drivers don't lock computers? ahh, OK.

Get over it Gary, as I said, my point was not to debate the pedastal you have placed the scope driver, but rather to inform that developement is done.

dawman · Post by **dawman** » Sun Mar 26, 2006 8:49 pm

>

[ This Message was edited by: scope4live on 2006-03-26 20:49 ]

Mr Arkadin · Post by **Mr Arkadin** » Sun Mar 26, 2006 9:29 pm

Rumour-mongering isn't particularly constructive is it? Wait for an official announcement before sounding any death knell.

AndreD · Post by **AndreD** » Sun Mar 26, 2006 10:38 pm

On 2006-03-26 17:41, 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

Not sure how this will affect the dual core technology .

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....

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...

Post by **garyb** » Sun Mar 26, 2006 11:46 pm

On 2006-03-26 19:16, craighuddy wrote:
Drivers don't lock computers? ahh, OK.

Get over it Gary, as I said, my point was not to debate the pedastal you have placed the scope driver, but rather to inform that developement is done.

i said THESE drivers are not the source of the lockup. period.
....and only YOU say developement is done. there is no need for a new driver at the moment, although there may be a new one if 64bit really becomes the standard.

here someone from cwa says that the thing works. what YOU are trying to do is not the way that the thing was meant to be used. YOU are causing the crash.

i am not saying this to insult you. i am not meaning to disrespect you. i am trying to correct you, as you are creating a rumor.

valis · Post by **valis** » Mon Mar 27, 2006 3:16 am

Your post was inflammatory and recieved as such by the other users. Just keep it where it originated:
http://www.planetz.com/forums/viewtopic ... &forum=1&7

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

rumor? I got this direct from creamware. I am starting nothing, just passing on info as it is given to me. If you have a problem with what I am saying, take it up with Creamware.

To say that I have a problem because I can't use the scope driver the same way as any other creamware user I know does, is well , silly to say the least.

I would be curious to see how many other CW users here experience lockup ups whenever they swap out .pro files. I bet there is not to many single CPU users who will see freezes, contrary to what you are reporting as the way it is "supposed" to work. The 4 other users I personally know that use scope on a single CPU don't see lockups at all.

bronYaur · Post by **bronYaur** » Mon Mar 27, 2006 3:55 am

I have 3 scope card,i have my p4 2.8 from 3 years,i use 20% of my cpu in my projet,I think use my singlecore cpu for the next 2 3 years...

AndreD · Post by **AndreD** » Mon Mar 27, 2006 4:43 am

On 2006-03-27 03:55, bronYaur wrote:
I have 3 scope card,i have my p4 2.8 from 3 years,i use 20% of my cpu in my projet,I think use my singlecore cpu for the next 2 3 years...

I´m using up to 99.9% native performance on my intel D930 , even with 3 boards

AndreD · Post by **AndreD** » Mon Mar 27, 2006 4:46 am

On 2006-03-27 03:22, craighuddy wrote:
rumor? I got this direct from creamware. I am starting nothing, just passing on info as it is given to me. If you have a problem with what I am saying, take it up with Creamware.

To say that I have a problem because I can't use the scope driver the same way as any other creamware user I know does, is well , silly to say the least.

I would be curious to see how many other CW users here experience lockup ups whenever they swap out .pro files. I bet there is not to many single CPU users who will see freezes, contrary to what you are reporting as the way it is "supposed" to work. The 4 other users I personally know that use scope on a single CPU don't see lockups at all.

There is no need to fix a non existing problem. DC works fine!
There will be a new scope, somedays, for shure

64 bit support is one major goal in future.

[ This Message was edited by: AndreD on 2006-03-27 05:06 ]

Mr Arkadin · Post by **Mr Arkadin** » Mon Mar 27, 2006 5:21 am

If you have a problem with what I am saying, take it up with Creamware.

Please could you post the email you received, not your changing interpretation of it:

Creamware head office won't be updating the Scope platform in the foreseeable future

has become

End of the Line for SFP

and

SFP future is bleak at best.

There's a difference: no update in the foreseeable future gives no specific time frame but does not imply they will be ending further development - which is what you're saying. So yes, that is rumour-mongering, unless you can produce the email which you have yet to quote.

Mr A

[ This Message was edited by: Mr Arkadin on 2006-03-27 05:27 ]

astroman · Post by **astroman** » Mon Mar 27, 2006 7:36 am

Craig, what's the problem with '...end of line for SFP' ?
all things once come to an end, even the good ones

I honestly do not see how anyone could improve SFP (significantly) with any reasonable amount beyond it's current functionality.
There's a couple of bugs, unquestioned, but those do not count in ten thousands (like in some well known OS...)

Showstoppers ??? according to Scope4Live's setup and performances it looks more like SFP is a show-starter

While I wouldn't expect too much on the SFP side - I'd expect even more from CWA building up on the SFP experience.
After their financial problems this couldn't be said, as the ice was really thin - most companies in a similiar situation just don't make it through.

They have a new successful product line, still have their broadcast foundation and I know at least 2 new OEM deals (beyond Fairlight) - that's not a sinking ship

if they extend the 'box-paradigm' to some guitar fx stuff (according to pre-fair rumor), great.

I have to admit I was pretty astound recently when 'decoupling' the feedback/distortion/fx section from the PythonPro as a 'guitar only' unit.
Did anyone say GuitarRig ? naahhh - we got better stuff

and mind you - that is stock Scope processing.

There are still some classics to be boxed...

Restore is probably a difficult product in the DAW context, but what about hi-end audiophiles ?

When revenues return as profits so will increase budgets for further developement - but it's more likely to be something new.

Does anyone have an idea what a sh*t it is to wade through the basements of a complex, but fairly old system to 'only' fix a couple of things ?
You're likely to introduce a multiple of 'inconveniences' in return

once they'll shout 'le roi est mort' CWA will add a vive le roi !' to introduce a successor - and didn't we always get nice upgrade offers

don't expect it the day after tomorrow, but I'm convinced it's on the way.
And I agree 110% with Wayne - my Scope system will never be outdated

cheers, Tom

Shroomz~> · Post by **Shroomz~>** » Mon Mar 27, 2006 8:36 am

As long as we can still buy components for our older PCs (which is becoming difficult due to manufacturers ditching not only production, but also support)

or

buy new mobos (single or dual) which our Scope cards are happy with, then we're sorted, period.

It looks at the moment that the Scope DSP cards will prove to have more longevity than any of our PC's (re: can't easily get reliable new parts to fix PC's older than 3 years)

Compatability with some brand new mobos has been proven here on Z in recent months, so while PC's are being deliberately made throwaway comodities by their manufacturers, CW & our existing Scope cards look to have a very bright future with a certainty of still being maintainable 4/5 years from now (no thanks to anyone but Creamware for that fact)

Post by **garyb** » Mon Mar 27, 2006 10:09 am

thank you.
the ONLY reason right now that the platform would be dead, is from a baseless rumor that destroyed demand. mature? yes. a forseeable end. sure, nothing lasts forever and computer manufacturers are determined to build obsolesence into all components. the current scope package should outlast almost every other product currently on the market(the manufacturers themselves will see to that!).

most companies would have already repackaged the old product into a new package that was completely incompatable with the old one(see apple computer or pro tools) making the old system useless, and with a product as old as scope, that would have happened several times. thanks cwa! you heard it here from AndreD, there ARE plans for the future. there is no work being done currently because the current drivers are working. the ONLY reason to do new ones is that the old ones don't work properly(reliably bridging hardware and software). these do. just close sonar before changing the project. you should ALWAYS do it that way regardless if it is single or dual cpu, sonar or cubase or samplitude. if you get away with not closing the sequencer while changing projects, fabulous. it is not SUPPOSED to work however. you are courting disaster, it is not a feature.

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

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

Siccum.