On 2004-04-02 18:16, CaBaMaN wrote:
There is also this one :
CreamWare Audio SCOPE Platform
Version 4.0
Siegburg, März 2004
This README.RTF file contains important and useful information about the current release of the SCOPE Platform (SP) software. Please read this document carefully!
The “Important Notes” contain some important installation instructions and tell you how to get the required activation keys!
Contents of this file:
Important notes
Technical support
Important Notes
Installation
The setup will ask you to select your software package (e.g., home, project Mix´n´Master, project Synth´n´Sampler, professional). Next you must enter the required activation keys that are available to all registered users on your personal page of our homepage. Instead of entering the keys manually, we recommend to download the file allkeys.skf from your personal page and to import the keys with the import option of the setup. If you have forgotten your login password you can create a new one using only your hardware serial number (->My Page -> Create new password) so you can again access your data.
Under Windows 2000 / XP, make sure you have the latest (v4.70/4.71) Adaptec ASPI layer installed which is available at Adaptec's website. Otherwise the software may not install (
http://www.adaptec.com/worldwide/suppor ... i_v471.exe).
The ASPI driver is also important for the recognition of AKAI CDs. In some cases, even with the updated driver, it can take somewhat longer for the installation to start. If despite all measures the installation still does not proceed, try installing from drive C:. You can also try renaming the file “allkeys.skf” in “scope.rgy” and copying it into SetupBin of the installation directory. If you then start the installation all the activation keys should already be registered when the Key Input dialog appears.
If you own optional CreamWare Devices that are not installed with the selected software package - e.g. STS 3000 (PowerSampler), Modular2 (Elektra), or devices you purchased separately - you should select your software package and enter / import the keys you have. All devices you entered a key for will be installed then.
It is also possible to install optional devices after the software installation. In this case simply run the corresponding OXE file from the 'Shop Plug-Ins' folder of the CD and follow the instructions, or manually copy some files from the installation CD (or from the downloaded installation files) into your SFP directory:
The device files (*.dev) are located in the device folder and must be copied into one of the sub folders of the ..SFPdevice folder, the preset files (*.pre) must be copied from the preset folder into the ..SFPpresets folder, and the XTC plug-ins (*.dll) must be copied from the VSTPlugins folder into your folder for VST plug-ins (the one you have selected in the installation).
Some devices, such as the BigMixer, Dynamixer, FM One, Modular1 or the Luna Mixer, are not included in the current SP software. You can continue to use these devices, however, by loading them from an earlier installation or directly from the installation CD of the other version, or by copying them into the SP Device directory. The first time you load one of these devices you will have to supply the appropriate activation key (Pulsar key, Luna key,..). The DynamicMixer and MicroMixer devices are now part of Mixer Package 1. If you do not have this key, but have earlier versions of these devices, you can use the earlier versions as described above. They will require only the Pulsar key.
MAC: Please do NOT start SP with the "Start SCOPE" button at the end of the installation. Use the desktop icon instead (you might have to reboot MAC OS before).
Compatibility with older projects
We recommend you retain older, functioning installations of the CreamWare software as the SFP is installed, by default, into its own directory. This will let you complete important projects in the same environment in which you began them. Particularly with SCOPE /SP compatibilities can arise (e.g. older mixers cannot be moved with the status bar - only by grabbing the left or lower edge).
If you load projects created in an older version, the devices of the old version will be loaded (if the version is still installed) as the projects store a reference to the device path. To use a new device from the SP version, rename the file temporarily so the software cannot find the devices. The search dialog then appears when you load the project letting you select the SP devices automatically or manually.
If old projects are loaded into SP, you should exchange the devices (and hardware and software I/Os) one-by-one, and possibly backup the presets manually. Then save the project so that the new paths replace the old ones.
Miscellaneous
- This version includes new versions of the EDS16I and SB404 devices. If you open an earlier project that uses these devices the Reference Resolver search dialog appears. You must direct the program to load only the V2 versions of these devices.
- After changing AKAI CDs under Windows XP, you must clear the CD cache (context menu of File Browser).
- If another version of Pulsar with XTC functionality remains installed, and SFP is also installed with XTC functionality, you will find two directories in the VST plug-ins directory: Pulsar XTC and XTC. You can delete the Pulsar XTC directory.
- We generally recommend you create a new directory for each project in which to save all related files (presets, samples/programs (for Export as volume) etc.).
- In Windows XP the number of Sequencer source/dest modules present in the project must exactly match the number showing in the driver dialog in the Device Manager.
- The chipsets on the motherboards of some dual-processor systems can cause problems with the PCI performance.
- The hardware I/Os initially loaded with the default project depend on the order in which the operating system detected your hardware. Create for yourself a suitable default project and save it useint Settings->Projects->Save Project as Default.
- If the cursor flickers rhythmically after changing the ULLI settings, just restart SFP.
- If the system stops producing sound, you can reset the DSPs by opening the Samplerate Settings dialog, changing the Word Clock setting, and then changing it back to the original setting.
- If a project contains a Sonic Timeworks reverb, it will produce no sound when first loaded into the project. To fix this, first try resetting the DSPs (as above), or add the following entry
[HW]
fadeInOut=0
to the file ..SCOPEAppBincset.ini.
- The driver setup (Windows Device Manager) includes the option 'Always open device'. This option is important for the XTC mode. It should be enabled with Cubase VST and disabled with Logic Audio.
- If you are using Sonar with the WDM driver (default) under Windows 2000/XP you must adjust the setting Audio/Options/Driver profiles/Stream data > 16 bit as: the option “32 Bit Left-aligned”. The minimum latency of the WDM driver depends on your ULLI setting. After you change the ULLI setting you must again run Sonar’s Wave Profiler. The audio/MIDI sync is best when a different ULLI setting than 25 ms is used.
- Installation: SFP v4.0 is installed into a new directory. If parts of an existing installation are to be incorporated into the new installation (possibly before they are deinstalled) some of them may need to be reinstalled (devices which have been purchased separately) or transferred manually from the old directory to the new one (e.g., free devices without specific DSP files of their own).
- In versions earlier than v3.0 presets were often saved as part of the device. If you wish to continue using presets from earlier versions, you must first load the old versions of the devices which contain these presets under the old software and export the presets as preset-list files (more info about how to do this can be found in the User's Manual from the earlier software version). These preset-list files can then be imported and converted by the corresponding new device versions under v3.1. Make sure to do this for all of the devices for which you previously created presets before you delete these devices - otherwise your existing presets will be lost!
- The ASIO Flt modules are not appropriate for use with Logic Audio, since this program does not currently provide support for 32-bit recording.
- The following options are not yet fully functional under Windows 2000/XP:
- AC3
- The following functions are only possibly with admin rights in Windows 2000/XP:
- Loading Akai CDs
- Using the samplers
Note: The Windows 2000/XP driver is not "signed". There will be a warning message during the driver installation. Simply ignore this message.
- The Transient Designer does not appear in the Device menu. If you receive an error message when loading projects that include a Transient Designer v1.x, you should replace it with the new version v2.x that is available on your personal download page.
- The module tripleDAT source is protected with a key for the tripleDAT plug-in v3.11b. If you want to use SFP v4.0c with a version of tripleDAT earlier than v3.11b you must use the module from the folder tripleDAT Source 2.06 -> 3.1 of the installation source files. You can rename the modules and copy them into …SCOPEAppApplicationIOsSoftware IOs.
- If the installation path contains a blank (space) the background project will not load. Please avoid using spaces in the installation path specification.
-If the installation path is too long (for example, C:programsMusicPrograms CreamWareDSPApplicationsSfp) the application may likewise fail to start.
- Using the minimal ULLI setting of 3ms@44.1kHz may result in the ”blue screen of death” or the system freezing up when you try to start Windows. If this happens, start Windows (in ”safe mode” if necessary - start in safe mode by pressing F8 while starting Windows). Open the CSET.INI file (..SfpAppBin) and locate the following entry:
[hw]
intBlkSize=64
Edit the file to change the value from 64 to 128, 256, 512, or 1024. Save the edited file and restart Windows.
Language specification for MAC users:
- For the Help system to be available in the appropriate language you must edit, if necessary, the file CSET.INI (in ..:SCOPE:App:Bin) as follows:
First temporarily rename CSET.INI to CSET.TXT. Look in the file for the section [runpep] under which you will find an entry for ”Language”. Adjust this entry as appropriate (that is, ”Language=Deutsch”, ”Language=English”, ”Language=Francais”). Make sure the path to the manuals is specified correctly.
- Because with the Mac no backup folder is created, the startproject is not automatically used. Before updating your system, make a copy of your start project (..:SCOPE:App:Application:newproject.pro).
- Make sure your MAC OS is adjusted so that the monitor displays 16.7 million colors. Our graphics will not be rendered correctly unless this is adjusted properly.
- Loading Poison and EDS16i can provoke system crashes in XTC mode under Logic 5.0. We are working on that issue to solve this problem as soon as possible.
Technical support
Of course, with a product as complex as Scope Fusion Platform, you should be sure to read the manual thoroughly. For your convenience, the manual is copied onto your hard disk during the software installation. This is the best (and quickest) way to ensure that you will be able to work with Sfp as efficiently as possible. If you are nevertheless confronted with technical problems, you will find help in the support section of the printed Installation Guide which is included in the package and in the ”Support” pages of our website.
Important note: Please be sure to check all items in the support documentation for answers or solutions before contacting our hotline!
Our technical hotline for the US and Canada can be reached at (604) 435-5158 or via email to
support@creamware.com. For all other countries, our hotline is (++49)2241-595812, or you can send email to
support@creamware.de.
And don't forget to watch out for software updates on our homepage at
http://www.creamware.com.
Now go have some fun with Scope Platform v4.0!
Your CreamWare Team
Sir 
