Page 1 of 1
Jaegermeister Und Scope
Posted: Sun Mar 11, 2007 10:06 am
by dawman
I can't say that someone else did this, as I was the only person playing this rig till the wee hours.
I somehow load up my projects and get all sorts of weird shit. The only thing different I did was loaded Nuetrons synths and fx late last night. As I love to hear new synths.
But my pointer for my mouse is different, a little scope gif. spins around now, never saw that b4, and the tabs in the routing window will not allow me to gain access to synths. They are Gone !! Instead I have cookies, Pepbase, and everything but my Creamware tabs. I do have the hardware I / O, as well as the software, but no mixers, synths, basically all of our building blocks.
I Am In A World Of Shit,
Posted: Sun Mar 11, 2007 10:36 am
by hubird
you occasionally have a backup of the ini file?
Posted: Sun Mar 11, 2007 10:45 am
by dawman
Yeah, but I recently updated my projects and didn't store them yet. I want to store the files somewhere seperately first. Then take advice from my European brethren.
Posted: Sun Mar 11, 2007 10:47 am
by dawman
I am ready Brotha' Man Hubird.
Posted: Sun Mar 11, 2007 11:14 am
by Immanuel
I once went through a very huge bunch of old 3rd party plug-ins. I think I was searching for a VU-meter (not a peak-meter). Many of the devices where quite buggy (in Scope 3, 3.1 and 4 anyway). After that full thing (and not finding, what I was searching for, since some people don't know the difference between VU- and peak-meters), I could no longer write text in ie the channels in the mixers. I might also have had trouble entering numbers in parameters.
I did different things to my PC in those days, so it could be something else fucking it up, but my feel was, that it was some of the old devices.
Posted: Sun Mar 11, 2007 11:37 am
by dawman
I tend to agree. This DAWg has hunted w/o problens 4 a long time. I shall erase the recent freebies, as I noticed 2 of the synths had problems right away locating DSP files.
Thank You,
Posted: Sun Mar 11, 2007 12:03 pm
by Crickstone
I had that happen at one time, but can't remember the context. I only loaded a few of the Neutron files last night without the DSPs but took them out until I found out what was going on> i haven't tried loading the DSPs with the rest of the files yet. When that happened to me I just reloaded Scope and all seemed fine (no uninstall- which may have some of my more experienced Scopers cringing) Let us know how you get on with the Neutron stuff. I loath to load it if I gonna get all Pepbasey and Queer Mousey.
Posted: Sun Mar 11, 2007 12:07 pm
by Mr Arkadin
Odd, i use the Neutron synths all the time, no problem. i did have a problem with Sonic Attack crashing but found another version that works OK - that's the version in the download. i have been through the Pep Base thing many times on Mac, but i think i only got it once on my PC set up. i think i just reinstalled Scope from scratch (ie. with uninstall) and it fixed it. i used to get the Pep Base thing a lot on Mod2 and III menu bars too.
It's a pity these can't be updated but there seems to be a problem with them. However i wouldn't have thought it would do all that Pep Base stuff, maybe crash but not that. However if that's the only thing you've done differently then it points to that.
Maybe try re-introducing the synths one by one (if you have the time) and you may track down the culprit.
PS. If you can't find any DSP files give me a shout and i'll mail them to you (and append the package. i'll put a warning in the download page too.
Posted: Sun Mar 11, 2007 1:03 pm
by dawman
It won't allow me to re install, and it has hidden my cset.ini file on me now. Well hey, the path 4 new sounds isn't always easy. The DAW still functions fine, but I have all of the wrong options atop my routing window. I maintain that's it's my Jaegered head that caused this, so no booze tonight. It's Cubase / GVI night on DAW#2 anyway.
Thank God for a multi-DAW rig.
Posted: Sun Mar 11, 2007 1:36 pm
by Immanuel
Hi Jimmy
This is a far out try, but it can in no way harm you system to investigate it.
Check out your cset.ini file. In mine, I find this:
Code: Select all
[ReferenceResolver]
All files_Paths=E:/Scope_4_5/;
Modules/Devices_Paths=E:/Scope_4_5/Devices/;
Presets_Paths=E:/Scope_4_5/Presets/;
All files_AutoUse=1
Modules/Devices_AutoUse=1
Presets_AutoUse=1
[StaticPath]
Modules=
Modular=E:/Scope_4_5/Modular2 Modules/
Projects=E:/Scope_4_5/Projects/Examples/
Effects=E:/Scope_4_5/Devices/Effects/
Presets=E:/Scope_4_5/Presets/
HardwareIOs=E:/Scope_4_5/App/Application/IOs/Hardware/
SoftwareIOs=E:/Scope_4_5/App/Application/IOs/Software/
Bitmaps=E:/Scope_4_5/MRC Skins/
Devices=E:/Scope_4_5/Devices/
Samples=E:/Scope_4_5/Samples/
I once tried "installing" Scope by just copying the whole lot over to my (new) desired location. It gave different sorts of problems. So maybe check, if these lines point to the right places.
Posted: Sun Mar 11, 2007 1:38 pm
by Immanuel
About your cset.ini file. Do a file search to find out, if you still have it somewhere. You really need that one. It handles some basic things in Scope. You can even modify some of the settings for a slightly different feel in Scope.
Posted: Sun Mar 11, 2007 4:31 pm
by dawman
It is the root of the problem. I shall return to that DAWg later. I'm having too much fun musically to let some little file stop me now. But you are absolutely right. I found it briefly by re clicking the hidden folders, and spotted it. But it's a sneaky little bastard with a short lived victory.