Page 1 of 1

Posted: Mon Jan 02, 2006 3:34 pm
by Nestor
Hello there friends... :smile:

Well, I've got a new instalation recently as I have changed HD, but when installing SFP and trying to load Saturn, Inferno and Celmos' BAM plugins, I get the following message:

"Can't find DSP file Overdrive Amp R4 - Please check installation.

I don't want to install again, as everytyhing is going quite well, and it's a lot of work already done. Can I find this file somewere? I have searched in the SFP4.0 CD, but I don't have it, Thank you.

Posted: Mon Jan 02, 2006 3:56 pm
by astroman
hi Nestor,

it's called OAMPR4.DSP and is on 3.1 as well
drop me a line with your current mail adress if you still can't find it

happy New Year, Tom :smile:

Posted: Mon Jan 02, 2006 5:36 pm
by huffcw
I am having a similar problem with B2003. It says it can't find a Parametric EQ DSP. This is after I just installed v4.5 on a new machine. I tried to reinstall several times, but I consistently get a DSP file can't be found error. Any ideas?

Posted: Mon Jan 02, 2006 5:52 pm
by huffcw
just got it to work by going into the install files and copy all the files from the DSP folder to the DSP folder where it installed on my computer.

Posted: Mon Jan 02, 2006 7:29 pm
by Nestor
Thanks Astro :smile: , I do have the DSP file already installed. I have overwrited it to see if could solve the problem, but it didn't. If the file is there, but the system searches for it, I don't know what else can I do...

Posted: Mon Jan 02, 2006 8:02 pm
by garyb
make sure the file is not marked "read only".

Posted: Mon Jan 02, 2006 9:59 pm
by psionic
Okay... First enable display of hidden files in windows. Then open the DSP folder on the installed Scope (tipically 'c:/scope/app/dsp') and try to find the file in it. When you find the file, you will notice a black sign in the bottom-left corner of the icon. Do you see it ? Okay, now delete the file. Open your downloaded SCOPE installation folder ('scope_4_5_install' - from wich you have started the installation) and locate the .dsp file in /APP/DSP wich you have deleted from installed scope version. You will see that there is no black mark on it. Copy it on the installed version on your hard ( c:/scope /app/dsp ) and it will work 101% !

The files with black sign (in the place of shortcut arrow) are marked hidden, and in the properties dialog cannot be reset (hidden status is grayed) I don't know what does it mean, but I've noticed them and the only cure is to delete them and manually copy from the installation folder.
Warning: It is not enough just to overwrite, you have to delete them and after that copy in the same place!

Please reply if this solution is working for you.

...and GaryB... please don't tell me that my system is screwed up. See? I am not the only one with (scope) problems. Funny thing is that whenever I install it, I got that mark on different .dsp files. This is not something which you get from malufuncioned system!






<font size=-1>[ This Message was edited by: psionic on 2006-01-02 22:07 ]</font>

<font size=-1>[ This Message was edited by: psionic on 2006-01-02 23:05 ]</font>

Posted: Tue Jan 03, 2006 1:01 am
by garyb
you know psionic, i've seen a lot of people claim to have these strange problems. some are the fault of the scope system(nothing's perfect) but most are not. regardless, 995 of problems are fixable. there is no 100% bug free software and it's idiotic to expect it. could it be better? always. i've built a large number of these systems now, and all mine work dependably and well enough to get work done. if you want me to straighten out your troubles, i'd be happy to. feel free to private message me if you want to send me your computer or if you want to fly me there.....

on the other hand, that looks like good info on the hidden files. that may be his problem. the only time i've EVER seen the "missing dsp file xxx" message personally was when i installed to a system with antivirus running. i don't know that this is everybody's problem who has this thing happen, however. you don't have to like what i'm saying, or you can think that i'm lying or whatever. my experience is not like yours, it seems....

one thing i can assure you, however. the scope cards work. a man like hans zimmer wouldn't be wasting time on them if they didn't(or winning oscars). bmw wouldn't use the sdk to mock up audio system components if they didn't. there is a user who visited this forum who was nominated for a grammy for best instrumental two years ago who mixed 70% of the album on scope. if the cards didn't work, that wouldn't be possible. because YOURS doesn't work, doesn't mean the product doesn't work.

if you want help, fine. i'll do my best and so will a number of others in this forum. if you want to bitch and moan, go ahead, but do it and be gone. if you want to fight, i've been looking for someone to practice with my new taser.... :wink: no really, if you want to fight, p*ss off. i don't want to. when i said your system was fuxxed, i wasn't dissing you, just stating the obvious facts.

Posted: Tue Jan 03, 2006 3:07 am
by astroman
On 2006-01-02 21:59, psionic wrote:
... I don't know what does it mean, but I've noticed them and the only cure is to delete them and manually copy from the installation folder.
Warning: It is not enough just to overwrite, you have to delete them and after that copy in the same place!...
probably Window's mystery handling of what it considers 'file access rights'
imho it will never be understandable :wink:

I've recently (test) run a program with special search algorithms over a part of my HD and the Scope folder just happened to be included.
There were quite some (20 or so ?) 'file skipped due to access denial' errors with no obvious pattern.

looks like we have to live with it - and thanks for the not so obvious finding of the 'first delete - then replace' sequence

cheers, tom

Posted: Tue Jan 03, 2006 4:53 am
by psionic
Hello to all

GaryB you got it all wrong...

Sorry if I pissed you off or anyone else in any way on this forum...

First of all I didn't say that Scope is a bad system - on the contrary. It is near perfect, and that is the reason I am so determined to solve my problem. I am not claiming that the problem is with Scope in general, but I want to investigate because of other people complaying about problems. I don't think it is only my system, but I will find out.

I only want feedback on my problem, and to see if I am the only one with it. I found that I am not, there are a lot of users with similar problems on newer systems with XP.
And two of my general bug foundings were confirmed - the screwed labels in stm16s mixer, and installation 'black mark' issue.
I found some more bugs on my system,(will see if it is only on my system), but they are really small - like messed labels.

If you want, try the ControlRoom. Start connecting 'input 1' to some sound source and all of the outputs to the mixer.
Now start switching input to output 1,2,3,4,5,6. You should notice silence when you get to output 5. If not then I am wrong - it is not a bug. If it is - then maybie this midi freeze has something with bugs.

I need someone to try this to confirm my claims. I do not have the opportunity to try it on some other system, mine is the only one with the Scope.

If you give it a try for yourself, we will see if it is only on my system, don't be so exclusive. :smile:

cheers...

This thing needs a driver update. If you check the wdm driver, you will notice the date: 2002. Windows is everchanging system. I am going to need a driver for my mouse pad soon :grin: ( with administrative rights and multi-user interface )

p.s. The remixer with grammy didn't utilise midi, and probably none of them were utilising the control room :wink: ... just kidding, maybie it is my system - I am just trying to find out...

<font size=-1>[ This Message was edited by: psionic on 2006-01-03 04:57 ]</font>

Posted: Tue Jan 03, 2006 1:57 pm
by Nestor
Cheers guys for your replays!

I have to say that I never had missing files in SFP, even if I have installed it many times along 6 years of use...

The strange thing is that in fact, it seems that I miss the file, as I can't find it, even with "all extensions visible". Then if i through the file onto the DSP folder, it overwrites it, but I cannot find it... and Windows cannot find it either.

I have replaced all the DSP files so, to see what would happend, and everything is the same. Very strange problem... I don't have a clue, will continue experiencing with other posibilites I may think

Posted: Tue Jan 03, 2006 2:36 pm
by garyb
hey psionic, no problem.
yes, there is an issue with some midi controllers. in all cases i have seen, the problems revolved around active sensing and midi clock. a filter solved the problem in all the instances i have come across.

i don't think we'll see a driver update before the next hardware generation...i can verify the output 5 bug in the control room module(all inputs ok all outputs but 5 ok).

<font size=-1>[ This Message was edited by: garyb on 2006-01-03 14:37 ]</font>

Posted: Tue Jan 03, 2006 2:46 pm
by Nestor
Ufff, guys, listen at it:

This bloody file has been playing "catch me if you can", for a while... It was there, but you could not see it. You can overwrite it, but this does not solve the problem. Of course, I have enabled "see all hidden files".

Ok, now, when you see the amount of files and megabytes in your CD, they are 1.172 files, and the installed files are 1.173. Once installed, they become two MBs hevier than in the CD.

I decided to go wild, as I could not find any solutions, I got the entire DSP folder, and trashed it with a special app that destroys the data completely. Then I did a drag and drop from the CD, and Voila!, everything came to normal, PROBLEM SOLVED.

So, I guess, if you are dealing ONLY with DSP files of the original installation of SFP, you can do what I did without problems, as it works perfectly well. But... if you have already installed third party plugins, you should then do it, and finlally drop all the add files that were deleted, so you new devices can work.

Thank you for your ideas and support guys, it's alwyas encouraging to see so much good will among us, CHEERS!!! :grin:

Posted: Tue Jan 03, 2006 3:00 pm
by garyb
i'm glad you fixed it, Nestor.

Posted: Tue Jan 03, 2006 4:06 pm
by Nestor
Cheers...

Posted: Wed Jan 04, 2006 3:19 am
by psionic
Hi...

Ok, I got what I wanted... Thanks a lot for your replies and confirmation. My Luna 2 is obviously OK, It is just the way it is working. So scope is working fine, but some of the devices maybie have some minor bugs... There is always a replacement. That is the power of Scope modular approach :smile:

So my card isn't broken, I'll buy a midi filter and ( hopefully ) solve my problem

...and Nestor... Did you first delete the black marked file? It is very important. Not just overwrite - it is apparently a windows security issue. Maybie it isn't problem in your case. I had the 'black mark' experience, and the same error because of it, so I tought you had the same problem. Anyhow glad to hear that it is also solved...

cheers...


<font size=-1>[ This Message was edited by: psionic on 2006-01-04 03:21 ]</font>

Posted: Wed Jan 04, 2006 4:53 am
by Nestor
Hi Psionic

No, I docunt' see the black spot. The file was there, as it could be overwrited, but could not be seen, it doesn't matter what you did. Then what I did, remembering your explanatins, was to delete completely the entire DSP folder, as just overwriting did not work, as you said. Then I droped the DSP folder from the CD of the Scope 4.0 installation, and it worked.

Posted: Wed Jan 04, 2006 3:59 pm
by psionic
...I think that ~WINDOWS~, given enough time, will develop a self-awareness... You will do on your computer only what HE decides. That would be the only explanation of some system-related problems :smile: