Scope 4 problem
Hi, need a little help. Setup: Mac + pulsar1
This setup was working just fine, and on a dark cold afternoon...
First, when the starup project is loaded, in the routing window, the only options I've got are Hardware IO and SoftIO, and 2 empty squares giving me a menu with the files present in the scope App/bin folder. At the same point if I open the file browser it gives me D:/xSource/ , which doesn't exist on my hard drive.
On the other hand I'm suffering several graphical problems: I'm stuck in classic mode (got the confirmation windows, but it doesn't change), the screenset feature doesn't work at all, and finally in the setting it never remembers the directories I give him (even if I try to save them as startup/default...)
I tried deleting all the .ini, my preferences, installing/deinstalling Scope, starting from a new archive of the software, installing a all new system folder...
My musical life is flushing down the toilets.
HELP, please
This setup was working just fine, and on a dark cold afternoon...
First, when the starup project is loaded, in the routing window, the only options I've got are Hardware IO and SoftIO, and 2 empty squares giving me a menu with the files present in the scope App/bin folder. At the same point if I open the file browser it gives me D:/xSource/ , which doesn't exist on my hard drive.
On the other hand I'm suffering several graphical problems: I'm stuck in classic mode (got the confirmation windows, but it doesn't change), the screenset feature doesn't work at all, and finally in the setting it never remembers the directories I give him (even if I try to save them as startup/default...)
I tried deleting all the .ini, my preferences, installing/deinstalling Scope, starting from a new archive of the software, installing a all new system folder...
My musical life is flushing down the toilets.
HELP, please
The only file that I know of that contains paths, is cset.ini. (pc also has scopevst.cfg for xtc)
For Mac, I heared something about changing the extension of cset.ini file to .txt before editing, and renaming it back after saving. Don't know if you are fimiliar with that. Then check if all your paths under at least [staticpath] are correct. That's all that I know of that matters for your problem...
Good luck!
For Mac, I heared something about changing the extension of cset.ini file to .txt before editing, and renaming it back after saving. Don't know if you are fimiliar with that. Then check if all your paths under at least [staticpath] are correct. That's all that I know of that matters for your problem...
Good luck!
more has been done with less
https://soundcloud.com/at0m-studio
https://soundcloud.com/at0m-studio
-
- Posts: 2464
- Joined: Tue Jun 05, 2001 4:00 pm
- Location: Warsaw to Szczecin, Poland
- Contact:
Just to make sure, move your SP4 folder in the main root of MacHD as Hubird suggested. The second thing to remember is not to have spaces in the path name - neither the disk name nor the folder name can't contain blanks.
I don't remember which mode is which (classic/standard - too similar names to remember their differences) but one mode is so bugful I tried it once
As for remembering the projects/presets etc paths - AFAIK the software never remembered it. So each time I want to open/save a project (and a while earlier I opened a preset) I have to switch to the proper folder and vice versa.
I don't remember which mode is which (classic/standard - too similar names to remember their differences) but one mode is so bugful I tried it once

As for remembering the projects/presets etc paths - AFAIK the software never remembered it. So each time I want to open/save a project (and a while earlier I opened a preset) I have to switch to the proper folder and vice versa.
you should!On 2004-07-26 08:56, jules wrote:
I didn't try to install it on top of my HD.

Atomic has right, you can text-edit the ini file by making it .txt.
I never needed to do this tho.
BTW. the name of your HD(partition) should also have no spatials in it or in front of it...
hope you find a solution...

Thanks for your answers.
I'll try to have a look at the csnet.ini manually. I tried to trash it, and it was regenerated automatically, with the same problem. So there must be something dictating the paths somewhere else.
However I'm sure to never have put any spaces or signs in the folder names.
Does somebody knows if Scope is sensible to partition settings? (I've 3 on the disc I'm working with)
Concerning the mode Classic / Standard: my problem is that unfortunately, I can't change them. If I specify to go to standard, it will give me a warning window (changes will take place once restarted...) but it still is the same...
Does somebody have an idea about "screenshots"? In my case, this function is just great for crashing the application..
I'll try to have a look at the csnet.ini manually. I tried to trash it, and it was regenerated automatically, with the same problem. So there must be something dictating the paths somewhere else.
However I'm sure to never have put any spaces or signs in the folder names.
Does somebody knows if Scope is sensible to partition settings? (I've 3 on the disc I'm working with)
Concerning the mode Classic / Standard: my problem is that unfortunately, I can't change them. If I specify to go to standard, it will give me a warning window (changes will take place once restarted...) but it still is the same...
Does somebody have an idea about "screenshots"? In my case, this function is just great for crashing the application..
-
- Posts: 2464
- Joined: Tue Jun 05, 2001 4:00 pm
- Location: Warsaw to Szczecin, Poland
- Contact:
About partitioning - it's ok, I have 4 partitions and it was never problematic. Do you have a Pulsar3 sotware installed? If so and you don't use it anymore (or if you haven't one but had a while ago) look in your system folder/preferences and locate the 'creamware' folder - trash it, perhaps something in there spoils your efforts to work properly 
[edit]
But you said you installed a new system folder...
_________________
Sir samplaire scopernicus
<font size=-1>[ This Message was edited by: samplaire on 2004-07-26 09:53 ]</font>

[edit]
But you said you installed a new system folder...
_________________

<font size=-1>[ This Message was edited by: samplaire on 2004-07-26 09:53 ]</font>
No I'm on Scope 4.0 now. So I was expecting my pulsar carpet to fly me over a not stop flow of music pleasure 
And yes I've trashed all my preferences several times (and then the final solution of the new system).
I'm not familliar with the notion of a "default folder" in my control panel/extension. What do you mean? Is it an extension, an hidden option?

And yes I've trashed all my preferences several times (and then the final solution of the new system).
I'm not familliar with the notion of a "default folder" in my control panel/extension. What do you mean? Is it an extension, an hidden option?
-
- Posts: 2464
- Joined: Tue Jun 05, 2001 4:00 pm
- Location: Warsaw to Szczecin, Poland
- Contact:
I meant if you have both Pulsar3 and SP4 (I do have Pulsar3, SFP3.1c and SP4
) because I still use my old sessions and the Scope software isn't down compatible 100%.
But returning to the topic... Default Folder is a 3rd party stuff ao if you didn't install it you are 100% sure you don't have it. It's good and bad - good because it causes problems - bad - because this is not the cause of your present problem.
Could you specify the full pathname containing the diskname of your SP software?
Did you install the software in the partition you work or from another partition? It should be installed from the partition you work in!
_________________
Sir samplaire scopernicus
<font size=-1>[ This Message was edited by: samplaire on 2004-07-26 10:16 ]</font>

But returning to the topic... Default Folder is a 3rd party stuff ao if you didn't install it you are 100% sure you don't have it. It's good and bad - good because it causes problems - bad - because this is not the cause of your present problem.
Could you specify the full pathname containing the diskname of your SP software?
Did you install the software in the partition you work or from another partition? It should be installed from the partition you work in!
_________________

<font size=-1>[ This Message was edited by: samplaire on 2004-07-26 10:16 ]</font>
Well I suspected the installation from another partition would be the first source of problem. So, it was the first thing I tried: everything from the beginning on the destination partition (unpacking the archive and installing SCOPE)
And I don't think there's anything fancy in my path, it's kind of mac/jules/Scope/App/...
But, afterall, it doesn't make sense to me because it happened suddenly, from day one to day two, without me modifying anything. Appart from plugging and unplugging a firewire disk to transfer some files (not related to Scope). I can't see anything else.
And I don't think there's anything fancy in my path, it's kind of mac/jules/Scope/App/...
But, afterall, it doesn't make sense to me because it happened suddenly, from day one to day two, without me modifying anything. Appart from plugging and unplugging a firewire disk to transfer some files (not related to Scope). I can't see anything else.
-
- Posts: 2464
- Joined: Tue Jun 05, 2001 4:00 pm
- Location: Warsaw to Szczecin, Poland
- Contact:
Huh! Is "Mac/jules" your disk (partition) name"? If so then you have to change the "/" to "_" (underline) or delete it. Your Scope software understands the sign "/" in the name as if it was a disk and a folder.
If it's called "Mac" and the folder is called "jules" and the next folder is called "Scope" then you don't have your SP4 install in the root folder, then it should be (in this case) Mac/Scope/
After the changes you should install the Scope software once again to ensure everything works smoothly
_________________
Sir samplaire scopernicus
<font size=-1>[ This Message was edited by: samplaire on 2004-07-26 10:44 ]</font>
If it's called "Mac" and the folder is called "jules" and the next folder is called "Scope" then you don't have your SP4 install in the root folder, then it should be (in this case) Mac/Scope/
After the changes you should install the Scope software once again to ensure everything works smoothly

_________________

<font size=-1>[ This Message was edited by: samplaire on 2004-07-26 10:44 ]</font>
I'm writing mac/jules/scope, as in a terminal path.
It is on a disk called mac, in a folder called jules, and in a folder called scope. There's no complicated folder or hard drive name.
Edit: didn't get your message the first time.
But yes I've tried to move my "scope folder" under the root (Mac). No differences. Perhaps your right, should reinstall there. A lot of pleasure in perspective.
<font size=-1>[ This Message was edited by: jules on 2004-07-26 12:05 ]</font>
It is on a disk called mac, in a folder called jules, and in a folder called scope. There's no complicated folder or hard drive name.
Edit: didn't get your message the first time.
But yes I've tried to move my "scope folder" under the root (Mac). No differences. Perhaps your right, should reinstall there. A lot of pleasure in perspective.
<font size=-1>[ This Message was edited by: jules on 2004-07-26 12:05 ]</font>
Don't know if this is relevant, but there's a controll panel 'Memory'.
Here 'Virtual memory' should be turned off.
You're sure you deleted the old Alloc and CrossDev.dll files from the extensions folder, as well as the Creamware Audio Driver?
You said so, but sometimes, while re-installing and trying unusual things you can mess things easily
Here 'Virtual memory' should be turned off.
You're sure you deleted the old Alloc and CrossDev.dll files from the extensions folder, as well as the Creamware Audio Driver?
You said so, but sometimes, while re-installing and trying unusual things you can mess things easily

right, back to square one...
I deleted the old software (including extensions, ASIO drivers, and preferences), and reinstalled in a fresh scope directory just under the root /mac folder.
Guess what?? It doesn't work...
Then I had a look at csnet.ini ; install.ini and all the files that sounded interesting, but all parameters looked ok. They were not mentioning a single time a D:/xSource or whatever.
I'm going to eat my mouse. That's probably the solution
I deleted the old software (including extensions, ASIO drivers, and preferences), and reinstalled in a fresh scope directory just under the root /mac folder.
Guess what?? It doesn't work...
Then I had a look at csnet.ini ; install.ini and all the files that sounded interesting, but all parameters looked ok. They were not mentioning a single time a D:/xSource or whatever.
I'm going to eat my mouse. That's probably the solution
maybe reseat the card? whip connected?
for you to consistantly get the same problem even when using a fresh install from the original cd on a system that used to work, i start to wonder if it isn't a hardware problem masquerading as a software problem...i can't imagine the os going belly up(then again)...
may the solution soon become obvious and simple..
for you to consistantly get the same problem even when using a fresh install from the original cd on a system that used to work, i start to wonder if it isn't a hardware problem masquerading as a software problem...i can't imagine the os going belly up(then again)...
may the solution soon become obvious and simple..