PlanetZ forums - scopeusers.com

Just a quick response to the missing files I seem to have.
I downloaded Scope 4 so I don't have the CD.
Plus I have copied everything into Logic's vst folder.

Thanks again for all your responses. Especially Voidar and GaryB!!

AstralFridgeMagnet..

Glad youre getting there, sorry my tip didnt help, but youre getting there. See if you can download the Scope4 again , maybe the files were missing in your original download...Im not sure if you can tho, I never have, Igot the CD

AudioDan.
I cant remember the extent of all the problems i had, when I had the xSource on the same drive as scope. But I do remember that cubase wouldnt pick up the effects as VSTs and the whole thing was just wrong. So I realized what I had done, I knew I had done it when it was installing, but i thought it wouldnt matter. I just uninstalled everything and started again.
I didnt explore the issues. On my comp the xSource is aslo sent to the D drive automatically, however I also directed the comp to install scope there, accidentally


any way

cheers
-Me$$iah

Me$$iah,

I will try downloading again to see if it helps. It is possible by the way if you go to:

http://www.creamware.de/

There you will see a link to download.

Copying the XTC files to Logic VST folder doesn't work still. Logic sees nothing!

Copying the XTC files to Logic VST folder doesn't work still. Logic sees nothing!

By XTC-files you mean the .dll-files and not the .dev/mdl-files, right?

On 2005-10-28 03:26, voidar wrote:

Copying the XTC files to Logic VST folder doesn't work still. Logic sees nothing!

By XTC-files you mean the .dll-files and not the .dev/mdl-files, right?

That's right. I only copied the .dll files. Logic sees absolutely nothing XTC related.

Hi again,

From my experience, SFP installation will almost certainly make mistakes and leave bits out if the the installation files are on the hard drive of the computer. It will also make mistakes if the installation is coming off a CD and you don't have the latest ASPI drivers installed in the system (download from Adaptec).
A way to reduce the problem is to copy some files down to the Scope directory on the hard drive before you do the installation. Find on either you SFP disc or in the installion folders, the folder called "Optional Plugins". Copy out of that, all the ".oxe" versions of the plugins that are relevant to you and place them in the:
c:ScopeAppOxe (I think!!) folder. Then do the SFP installation again, making sure to make XTC active and that you set up the link to the correct "Vstplugins" folder. After the installation, when you boot SFP the .oxe files will install and on doing this will install the necessary files into the necessary folders to get XTC working properly. It might also be a good idea delete you current cset.ini file (if you're not too attached to it) before you do the installation.

Be aware that the XTCproject.pro doesn't need to have either the "Directmixercontainer" module or the "Merge" module connected to anything to work properly. Unless you like use ASIO Direct Monitoring - meaning the invisible monitoring function built into some ASIO drivers - then you won't need to use the Directmixercontainer. It's Creamware's own version of ASIO direct monitoring and Creamware drivers deliver a low enough latency that you can use the direct monitoring on the channels in Cubase instead.
The Merge Module was only applicable to versions of Cubase before 2.0 that couldn't do a "Realtime" Audio Export. Cubase SX 1 could not export at playback speed and the Creamware FX didn't like that (if you think about them as a physical external FX unit and consider that in the case of Cubase SX 1 the audio would be passing through at variable speeds well above playback speed, you can imagine what a terrible mess of the audio it would make....and it did!) However! Now that Cubase will export in "Realtime" there is no need for the Merge Module either.

To setup the I/O's of the Audio Interface in XTC mode, while in Cubase go to:
Devices - Device Setup - VST Audiobay and make sure the Scope ASIO driver is active, then click on the entry below VST Audiobay which should be called "Scope ASIO" and click on the "Control Panel" button. From there you'll be able to activate all your hardware I/O's in XTC.

The mighty Gonzoft will now explain about buffer sizes:

XTC mode does not remember your ULLI settings unless you do the following:

Add the following entry into your /SFP/App/Bin/Cset.ini under item
[XTC-config]:

intBlkSize=x

whereby x is a values out of 64, 128, 256, 512 or 1024 and translates as follows to the card's latency:

64: latency = 3 ms
128: latency = 4 ms
256: latency = 7 ms
512: latency = 13 ms
1024: latency = 25 ms

A wrong latency will still be displayed in the ULLI Settings of the ASIO Control Panel, but you can ignore this.


XTC should, after all that, work fine in Cubase. Logic is another story all together and I'm probably not qualified to help you there.

Hope that helps though,

Cheers,

AudioDan


<font size=-1>[ This Message was edited by: AudioDan on 2005-10-28 20:05 ]</font>

Thanks AudioDan (and everyone else who has responded) for your lengthy response.

Some things I don't understand, such as "cset.ini file". I have to admit I am a bit scared of dabbling in the unknown (such as .ini files) as I may do irreversible damage if I get it wrong.

Another thing I haven't done is install ASPI Drivers. How crucial are they? I thought it was only to prevent problems in reading Akai sample discs (which I don't have any of anyway).

I'll try all of these things later this weekend.

Thanks all for your help!!

Just backup the files you modify (cset.ini, project files) and the recovery files (scope.rgy etc) before you edit anything, and you should be able to reverse your changes fast. Worst case, backup you whole SFP directory, then you can just recopy it over if you break anything.

dont be afraid to tangle with the cset.ini file. of course you should back it up first. the cset file however, will recreate itself if it is deleted. so theres nothing to worry about!

Again, thanks to everyone who has responded. It's very much appreciated!!!!

I haven't installed ASPI Drivers. How crucial are they? I thought it was only to prevent problems in reading Akai sample discs (which I don't have any of or use). Do I really need to install ASPI or can it be left out? I should add I don't like installing stuff that isn't necessary (I realise it's terribly anal-retentive. I can't help it!!)

Thanks.

as far as i know, you wont nees aspi drivers if you dont use AKAI disks.

get a cd from your dealer. the cd never has caused me trouble, the downloaded version has.

I've had to set up SFP way too many times and I have actually had problems installing from the CD that I'm pretty sure were solved by the ASPI driver install. I'm also pretty sure I read about this in a special 'System Optimization' manual that Creamware emailed me once.
I could be wrong...it's been a while, but I'm pretty sure, and I'm also pretty sure that even if the ASPI drivers don't help in this situation, it certainly won't hurt to have them there.
Anyway, hope I've been of some help to you.

Cheers,

AudioDan

<font size=-1>[ This Message was edited by: AudioDan on 2005-10-30 06:05 ]</font>