Pulsar 2 - Newbie needs help
Pulsar 2 - Newbie needs help
I have just bought a Pulsar 2 card. I just wanted a card to manage my system sounds and midi keyboard better than my creative X-Fi card. The latency was a huge problem. Anyway I bought this pulsat on eBay and did not realise how huge it is. Now I feel like I've turned up at the Queen's dinner party in my pygamas!
As I said, I want my PC's sound to run off this card by using the PC's sound 3.5mm port but I can't get the PC System audio settings to see the card. It shows as 'working properly' under Sound, Video, and Game Controllers (Creamware Pulsar 2) Later I will explore some plugins when I get the Keyboard working. This is a USB controller but can also hookup with it's Midi ports
I launch Scope with the desktop Icon - Scope Platform v4.5 - The Scope platform New Projects screen comes up showing plugins.
The Readme(Important Notes) File states "For your convenience, the manual is copied onto your hard disk during the software installation." The Manual folder is there but it is empty!
I obtained the User Manual from The Sonic Core site but the item named "Installation" says 'see printed version', whatever that means.
The chap who sold this card to me has had it from new and he says that there never was a printed version.
If someone will kindly point me to the Installation Guide, it will go a long way to getting me started. (and preserving my sanity to boot!)
Many thanks
As I said, I want my PC's sound to run off this card by using the PC's sound 3.5mm port but I can't get the PC System audio settings to see the card. It shows as 'working properly' under Sound, Video, and Game Controllers (Creamware Pulsar 2) Later I will explore some plugins when I get the Keyboard working. This is a USB controller but can also hookup with it's Midi ports
I launch Scope with the desktop Icon - Scope Platform v4.5 - The Scope platform New Projects screen comes up showing plugins.
The Readme(Important Notes) File states "For your convenience, the manual is copied onto your hard disk during the software installation." The Manual folder is there but it is empty!
I obtained the User Manual from The Sonic Core site but the item named "Installation" says 'see printed version', whatever that means.
The chap who sold this card to me has had it from new and he says that there never was a printed version.
If someone will kindly point me to the Installation Guide, it will go a long way to getting me started. (and preserving my sanity to boot!)
Many thanks
Re: Pulsar 2 - Newbie needs help
CreamWare Audio SCOPE Platform
Version 4.5
Siegburg, September 2005
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 \Setup\Bin 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 ..\SFP\device\ folder, the preset files (*.pre) must be copied from the \preset\ folder into the ..\SFP\presets\ 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 ..\SCOPE\App\Bin\cset.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 …\SCOPE\App\Application\IOs\Software 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:\programs\MusicPrograms\ CreamWare\DSPApplications\Sfp\) 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 (..\Sfp\App\Bin) 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.5!
Your CreamWare Team
_______________________________________________________________________________
I Hope This Helps. Scope must be played.
Version 4.5
Siegburg, September 2005
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 \Setup\Bin 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 ..\SFP\device\ folder, the preset files (*.pre) must be copied from the \preset\ folder into the ..\SFP\presets\ 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 ..\SCOPE\App\Bin\cset.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 …\SCOPE\App\Application\IOs\Software 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:\programs\MusicPrograms\ CreamWare\DSPApplications\Sfp\) 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 (..\Sfp\App\Bin) 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.5!
Your CreamWare Team
_______________________________________________________________________________
I Hope This Helps. Scope must be played.
Re: Pulsar 2 - Newbie needs help
Thankyou for this detailed input.
"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)."
On my Avant browser this link brings up 'page not found'. On my PDA'S IE the link goes to Adeptec's homepage where a page not found note is displayed.
Do you perhaps have the current download address?
Does this download work on computers not running SCSI HDs?
Thanks again.
"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)."
On my Avant browser this link brings up 'page not found'. On my PDA'S IE the link goes to Adeptec's homepage where a page not found note is displayed.
Do you perhaps have the current download address?
Does this download work on computers not running SCSI HDs?
Thanks again.
Re: Pulsar 2 - Newbie needs help
ASPI is likely not necessary at this date.
Re: Pulsar 2 - Newbie needs help
the ASPI thing has nothing at all to do with SCSI disks in this context - afaik it's (may be) needed to read physical AKAI sampling CDs into the STS sampler. The functionality may even be contained in one of the Windoze service packs today, but I'm not eaxactly sure as I haven't used that sampler for ages...
You may have a careful look at the release date of any installation and configuration instructions...
Some of that stuff is really old (!) and may not apply today.
Anyway - it's not that complicated if you stick with the 'first things first' method - i.e. setup the basic system and only then(!) - not at any earlier point in time (!) - configure your options.
Don't try the infamous ...I just wanted to have a look... approach of the impatient - it will most likely end in confusion.
This is in fact not another 'soundcard' - it's an independant audio subsystem that provides Windows multimedia functionality only as a sideeffect (well, kind of...).
Once you've setup the basic system the multimedia part will be a snap
the most important (and probably confusing) point is that all and everything on this card is closely tied to the board's physical ID - you cannot even run the basic software without the proper keys.
Don't worry, they are free of charge, but they have to be provided...
possibly the seller mentioned a file named allkeys.skf and provided it on a disk (?)
that would be the proper way and you could import the requiered keys when asked during install.
if you did not get that file, you'll have to request it from SonicCore, providing the board's serial number.
... I'll stop at this point, as further proceeding depends on the keyfile or not, and I wouldn't want to bore you with something you already know...
cheers, Tom
You may have a careful look at the release date of any installation and configuration instructions...
Some of that stuff is really old (!) and may not apply today.
Anyway - it's not that complicated if you stick with the 'first things first' method - i.e. setup the basic system and only then(!) - not at any earlier point in time (!) - configure your options.
Don't try the infamous ...I just wanted to have a look... approach of the impatient - it will most likely end in confusion.
This is in fact not another 'soundcard' - it's an independant audio subsystem that provides Windows multimedia functionality only as a sideeffect (well, kind of...).
Once you've setup the basic system the multimedia part will be a snap

the most important (and probably confusing) point is that all and everything on this card is closely tied to the board's physical ID - you cannot even run the basic software without the proper keys.
Don't worry, they are free of charge, but they have to be provided...
possibly the seller mentioned a file named allkeys.skf and provided it on a disk (?)
that would be the proper way and you could import the requiered keys when asked during install.
if you did not get that file, you'll have to request it from SonicCore, providing the board's serial number.
... I'll stop at this point, as further proceeding depends on the keyfile or not, and I wouldn't want to bore you with something you already know...
cheers, Tom
Re: Pulsar 2 - Newbie needs help
nicely put astro-
one addition, the keyfile may also be called scope.rgy....
one addition, the keyfile may also be called scope.rgy....
Re: Pulsar 2 - Newbie needs help
Thanks astroman and gary,
The only reason I was going to instal the was that a previous post said that I should!
I installed the AllKeys file a few days ago and had no problem with that.
What I am looking for is sound from my system port. I am doing the 'first things first' thing, as astroman suggested, then I will explore the modules.
Sonic core have assured me that the card will run my system sound and right now that is what is not happening!
The modules load and I must say they look very impressive. I even downloaded a few module (bought seperately) and installed them via the OXE directory.
Question - In Control Panel>Sounds and Audio Devices>Audio>Sound Playback do I select Creamware Ply/Rec 1 or Creamware Ply/Rec 2 ?
When I install either the Volume button is disabled.
Same for Sound recording!
Question - I am not using the Nest of ports which plug into the Pulsar 2 card. In fact I have not plugged them into the card yet. Can it that they must be plugged in for the card to work? Even if they are not connected to anything?
Anyway I must back to the grindstone and see if I can get some co-operation from the Card!
The only reason I was going to instal the was that a previous post said that I should!
I installed the AllKeys file a few days ago and had no problem with that.
What I am looking for is sound from my system port. I am doing the 'first things first' thing, as astroman suggested, then I will explore the modules.
Sonic core have assured me that the card will run my system sound and right now that is what is not happening!
The modules load and I must say they look very impressive. I even downloaded a few module (bought seperately) and installed them via the OXE directory.
Question - In Control Panel>Sounds and Audio Devices>Audio>Sound Playback do I select Creamware Ply/Rec 1 or Creamware Ply/Rec 2 ?
When I install either the Volume button is disabled.
Same for Sound recording!
Question - I am not using the Nest of ports which plug into the Pulsar 2 card. In fact I have not plugged them into the card yet. Can it that they must be plugged in for the card to work? Even if they are not connected to anything?
Anyway I must back to the grindstone and see if I can get some co-operation from the Card!
Re: Pulsar 2 - Newbie needs help
Thanks stardust. This is what I like. Tell it like it is.
I wanted to let Scope handle all the sound that's made in this place and that includes the system sound. I realise that Creative is Mickey Mouse stuff and that is why I wanted to ditch it. But now, in line with your advice, I will let Creative handle the system sounds and let Scope do the Midi, Mike and Speakers!
Q's - It seems to me that the Card is installed properly. Do I have to route this wav file through one of the modules? Which wav file do you recommend? Can I ask you to describe a simple routing scenario from scratch MIdi > Card > Speakers? Would I need a preAmp or will Dynatube VX do the trick? (I hope I am not displaying too much ignorance!) I will need to get good Speakers.
I have just finished my new Studio (bedroom) with a huge Bench, and move my goodies in tomorrow (Tuesday) DV.
I wanted to let Scope handle all the sound that's made in this place and that includes the system sound. I realise that Creative is Mickey Mouse stuff and that is why I wanted to ditch it. But now, in line with your advice, I will let Creative handle the system sounds and let Scope do the Midi, Mike and Speakers!
Q's - It seems to me that the Card is installed properly. Do I have to route this wav file through one of the modules? Which wav file do you recommend? Can I ask you to describe a simple routing scenario from scratch MIdi > Card > Speakers? Would I need a preAmp or will Dynatube VX do the trick? (I hope I am not displaying too much ignorance!) I will need to get good Speakers.
I have just finished my new Studio (bedroom) with a huge Bench, and move my goodies in tomorrow (Tuesday) DV.
Re: Pulsar 2 - Newbie needs help
First of all let me apologise for getting back to you so late after your last very welcome post. The fact is that I was waiting for a notification mail which never arrived. Not everyone suffer newbies gladly but your posts showed a genuine concern which why I had a look on the site.
I have just printed your reply and will now digest it and if I don't get the studio on it's 'basic' feet now then I don't deserve to own a good Card like Scope. I would just like to clarify one or two things, if I may.
I have a USB Keystation61 Midi Controler at present and will upgrade when appropriate.
The Midi has only one USB and one Keyboard midi OUT socket. The manual diagram shows USB cable is connected to the PC and the PC sound is routed to an Audio Mixer, while the Midi Out of the keyboard goes to the Midi IN of a Sound module from where it is fed Via Audio out to the same Audio Mixer. It seems I will need special cables to commect to the Sound sockets on the Card Hraness?
I take it that by "App like Kontact" could also mean like Samplitude, which is what I have.
I have just printed your reply and will now digest it and if I don't get the studio on it's 'basic' feet now then I don't deserve to own a good Card like Scope. I would just like to clarify one or two things, if I may.
I have a USB Keystation61 Midi Controler at present and will upgrade when appropriate.
The Midi has only one USB and one Keyboard midi OUT socket. The manual diagram shows USB cable is connected to the PC and the PC sound is routed to an Audio Mixer, while the Midi Out of the keyboard goes to the Midi IN of a Sound module from where it is fed Via Audio out to the same Audio Mixer. It seems I will need special cables to commect to the Sound sockets on the Card Hraness?
I take it that by "App like Kontact" could also mean like Samplitude, which is what I have.
Re: Pulsar 2 - Newbie needs help
Hi,
In your case, The scope card will replace the internal PC sound, SO:
Connact your USB keyboard to the PC, it will be your midi in source for Samplitude.
Launch SFP.
Open software IO menu and select ASIO2 source
Open hardware IO menu and select Scope ->Analog Dest
connect ASIO2 source R1 and L1 (red triangles) respectively to your Scope Analog Dest Rin and Left In.
You have created the Audio outgoing stream
Open Software IO menu and select Sequencer Midi Source
Open Hardware IO menu and select Scope->Midi A dest
connect Sequencer midi source to scope midi A dest
You have created the midi outgoing stream.
Keep SFP running and launch Samplitude
Under samplitude, select scope as your ASIO audio card
2 cases now:
You use a Vsti: in samplitude your midi in will have to be tied to your vsti input, the Audio output of samplitude should be tied to the Scope ASIO.
You use an external synth: in samplitude your midi in will have to be tied to scope midi in/out 1
Your external synth must be connected (midi in) to the scope midi out (breakout cable).
Hope that help!
cheers
In your case, The scope card will replace the internal PC sound, SO:
Connact your USB keyboard to the PC, it will be your midi in source for Samplitude.
Launch SFP.
Open software IO menu and select ASIO2 source
Open hardware IO menu and select Scope ->Analog Dest
connect ASIO2 source R1 and L1 (red triangles) respectively to your Scope Analog Dest Rin and Left In.
You have created the Audio outgoing stream
Open Software IO menu and select Sequencer Midi Source
Open Hardware IO menu and select Scope->Midi A dest
connect Sequencer midi source to scope midi A dest
You have created the midi outgoing stream.
Keep SFP running and launch Samplitude
Under samplitude, select scope as your ASIO audio card
2 cases now:
You use a Vsti: in samplitude your midi in will have to be tied to your vsti input, the Audio output of samplitude should be tied to the Scope ASIO.
You use an external synth: in samplitude your midi in will have to be tied to scope midi in/out 1
Your external synth must be connected (midi in) to the scope midi out (breakout cable).
Hope that help!
cheers
Re: Pulsar 2 - Newbie needs help
MD69, thanks for this reply.
I don't see this kind of help in the Manuals that came with the CD! Incidently In the Scope Platform Dialog, under the '?' it brings up 'Manual' and 'About'. The Manual is completely blank. Very uncharacteristic for such an expensive card, I would have thought. If it wasn't for chaps like you I would be sunk and the card would be doing time as a doorstop!. As it is now, I am confident that it will more than prove it's worth.
Can you please elaborete on the following:-
I have selected the Asio2 source but have a problem finding HW IO Menu ! What I have found is the Routing window but no Scope, only Pulsar 2 pops up when I hover over the IO Hardware Tag. The Analog Dest button is disabled. For that matter, looking further down your reply, Midi A Dest button is also disabled.
Visti? Is this a Scope Module? I'll get it if it is not included in Scope.
External Synth? Does this refer to a physical Synth device, or something like Microsoft GS Wavetable SW Synth?
I don't see this kind of help in the Manuals that came with the CD! Incidently In the Scope Platform Dialog, under the '?' it brings up 'Manual' and 'About'. The Manual is completely blank. Very uncharacteristic for such an expensive card, I would have thought. If it wasn't for chaps like you I would be sunk and the card would be doing time as a doorstop!. As it is now, I am confident that it will more than prove it's worth.
Can you please elaborete on the following:-
I have selected the Asio2 source but have a problem finding HW IO Menu ! What I have found is the Routing window but no Scope, only Pulsar 2 pops up when I hover over the IO Hardware Tag. The Analog Dest button is disabled. For that matter, looking further down your reply, Midi A Dest button is also disabled.
Visti? Is this a Scope Module? I'll get it if it is not included in Scope.
External Synth? Does this refer to a physical Synth device, or something like Microsoft GS Wavetable SW Synth?
- the19thbear
- Posts: 1499
- Joined: Thu Feb 20, 2003 4:00 pm
- Location: Denmark
- Contact:
Re: Pulsar 2 - Newbie needs help
the only reason why they should be disable would be that they are already inside the project.. that is, already in the routing window.
have an extra look in the routing window
have an extra look in the routing window

- Mr Arkadin
- Posts: 3283
- Joined: Thu May 24, 2001 4:00 pm
Re: Pulsar 2 - Newbie needs help
You can safely re-install the Scope software over itself at any time (although backup any presets or projects you may have made) and see if the manual reappears. If not then just manually drag it into C:Scope_4_5>Manual>English (or whichever language you prefer). It should pop up in your "?" drop down now.draynum wrote:Incidently In the Scope Platform Dialog, under the '?' it brings up 'Manual' and 'About'. The Manual is completely blank. Very uncharacteristic for such an expensive card, I would have thought. If it wasn't for chaps like you I would be sunk and the card would be doing time as a doorstop!. As it is now, I am confident that it will more than prove it's worth.
Pulsar2 is just the name of your card (this is what the 6 DSP card was called before Scope Project). This is perfectly normal and that is where you'll find you hardware in/outs. Any items that are 'greyed out' are likely already in your Scope Project window (they are often in the default boot up project). If you don't see them them make you project window bigger to fill the screen or if it already is then check the bottom and right edges for a scroll bar (it's just a blue line - no arrows) and see if those modules you can't select are actually hidden off-screen.draynum wrote: I have selected the Asio2 source but have a problem finding HW IO Menu ! What I have found is the Routing window but no Scope, only Pulsar 2 pops up when I hover over the IO Hardware Tag. The Analog Dest button is disabled. For that matter, looking further down your reply, Midi A Dest button is also disabled.
VSTi= VST Instrument. Synths, samplers, effects that run natively in your host (Samplitude). Nothing to do with Scope.draynum wrote: Visti? Is this a Scope Module? I'll get it if it is not included in Scope.
Physical synth - usually to control your software synths (could just as easily be a controller with no sound).draynum wrote: External Synth? Does this refer to a physical Synth device, or something like Microsoft GS Wavetable SW Synth?
Last edited by Mr Arkadin on Thu Jul 31, 2008 3:07 pm, edited 1 time in total.
Re: Pulsar 2 - Newbie needs help
Thanks to stardust, Mr Arkadin, and the19thbear.
Like you said, they were already in the project.
I must get that printed manual but I doubt the seller of the card still has it. I'll try the web.There are subtle differences in the naming protocol between the Pulsar2 and later cards. Just enough to throw a novice!
Like you said, they were already in the project.
I must get that printed manual but I doubt the seller of the card still has it. I'll try the web.There are subtle differences in the naming protocol between the Pulsar2 and later cards. Just enough to throw a novice!
- the19thbear
- Posts: 1499
- Joined: Thu Feb 20, 2003 4:00 pm
- Location: Denmark
- Contact:
Re: Pulsar 2 - Newbie needs help
actually it isnt that hard
you have sources and destinations... wave, asio, pulsar2 etc.
you go from input to output on whatever you have, and then place a mixer in between..
i think someone made a video tutorial once??
who?
where?

you have sources and destinations... wave, asio, pulsar2 etc.
you go from input to output on whatever you have, and then place a mixer in between..
i think someone made a video tutorial once??
who?
where?
Re: Pulsar 2 - Newbie needs help
Thanks to all the great guys that contributed to this topic, I have now got my sound basics right, and what a difference!
I will now try to become more proficient with Scope and see what develops.
I have been looking at a used pair of standup speakers, TDL Studio 5, which I will probably buy tomorrow for £50. Does anyone know whether the TDL Studio 5's are good? Or should I go for something else? I really need to get my finances straight again after the cost of the card so I would not like to spend much more than this.
Also the reviews are very critical of the Studio 10's as many reviews say that they are built around the TDL nameplate. There appears to have been a change of ownership after the Studio 5's so I am hoping that the Studio 5's are OK.
Thanks again all!
I will now try to become more proficient with Scope and see what develops.
I have been looking at a used pair of standup speakers, TDL Studio 5, which I will probably buy tomorrow for £50. Does anyone know whether the TDL Studio 5's are good? Or should I go for something else? I really need to get my finances straight again after the cost of the card so I would not like to spend much more than this.
Also the reviews are very critical of the Studio 10's as many reviews say that they are built around the TDL nameplate. There appears to have been a change of ownership after the Studio 5's so I am hoping that the Studio 5's are OK.
Thanks again all!

Re: Pulsar 2 - Newbie needs help
hello, actually, that's certainly a very poor speaker. a good pair of powered monitors will cost in the $400 range, a little more or less, for the lowest level of real gear meant for working with. the idea is not to get a great sounding speaker(one that flatters what you are listening to), but an accurate speaker(so that it's less likely to lie to you and give you an embarrassing surprise on another system).
the thing is, even with the "best" speaker, the room needs to be corrected for optimum results. even with a perfect room, you still need to know the speaker you are mixing on, because no speaker is truly neutral. they all emphasize some things and hide others. after doing mixes on any speaker, you'll want to hear it on a nuber of other systems, to see what happens, and adjust accordingly. eventually, you'll get a better idea of what your monitors need to sound like in order to be assured of a well balanced mix everywhere else. this follows for any speaker you may choose to use.
so-
my advice is to follow your budget. if you can reasonably save up $500 for monitors before you explode, DO IT. it's always better to buy the right thing the first time and spend less money in the long run.
if you just can't wait, spend the $150 now. it's better to have something than nothing, and a good ear can still do something pretty nice. i'm sure that they work. now that you've seen the difference in sound with some real gear(Scope cards have won an Oscar for sound and a couple of grammy nominations, so they can be used for big time work), you may want to step up your game. if not, then i'm sure that the cheaper speaks will do. you have to define your goals to make a good choice, although something good is almost(but not quite) always valuable and throwaway technology usually is not, especially used....
the thing is, even with the "best" speaker, the room needs to be corrected for optimum results. even with a perfect room, you still need to know the speaker you are mixing on, because no speaker is truly neutral. they all emphasize some things and hide others. after doing mixes on any speaker, you'll want to hear it on a nuber of other systems, to see what happens, and adjust accordingly. eventually, you'll get a better idea of what your monitors need to sound like in order to be assured of a well balanced mix everywhere else. this follows for any speaker you may choose to use.
so-
my advice is to follow your budget. if you can reasonably save up $500 for monitors before you explode, DO IT. it's always better to buy the right thing the first time and spend less money in the long run.
if you just can't wait, spend the $150 now. it's better to have something than nothing, and a good ear can still do something pretty nice. i'm sure that they work. now that you've seen the difference in sound with some real gear(Scope cards have won an Oscar for sound and a couple of grammy nominations, so they can be used for big time work), you may want to step up your game. if not, then i'm sure that the cheaper speaks will do. you have to define your goals to make a good choice, although something good is almost(but not quite) always valuable and throwaway technology usually is not, especially used....
Re: Pulsar 2 - Newbie needs help
Thank you garyb. Just shows what I know about sound! Your advice is worth following but at this stage I may have to 'stoop to conquer'.
I think that if I make the seller aware of these facts then he may want to drop the price! As you agree that 'a half an egg is better than an empty shell', as you indicated toward the end of your input.
So - I'll go for these speakers, if he drops the price. Then I can bide my time and keep a skinny out for when I stumble over a really good pair. When my bank balance comes out of intensive care then I would easily pay 6 or 700 pound for a pair. (We married men have to tread softly when it comes to buying more toys!)
I think that I should also mention that, having been a building contractor for 40 years with all the attendant machinery noises, my hearing is not as good as it needs to be to really appreciate a very top class speaker.
Some say that I have a good singing voice and I mostly want to record a few disks for the family. (and whoever else can bear to listen!).
So these TDL speakers should do for now.
Thanks again for your input.
I think that if I make the seller aware of these facts then he may want to drop the price! As you agree that 'a half an egg is better than an empty shell', as you indicated toward the end of your input.
So - I'll go for these speakers, if he drops the price. Then I can bide my time and keep a skinny out for when I stumble over a really good pair. When my bank balance comes out of intensive care then I would easily pay 6 or 700 pound for a pair. (We married men have to tread softly when it comes to buying more toys!)
I think that I should also mention that, having been a building contractor for 40 years with all the attendant machinery noises, my hearing is not as good as it needs to be to really appreciate a very top class speaker.
Some say that I have a good singing voice and I mostly want to record a few disks for the family. (and whoever else can bear to listen!).
So these TDL speakers should do for now.
Thanks again for your input.
Re: Pulsar 2 - Newbie needs help
although you've certainly got hearing loss, don't worry. all audio engineers have hearing loss too, you can imagine why...
i'm sure that you will have lots of fun!

i'm sure that you will have lots of fun!

Re: Pulsar 2 - Newbie needs help
Hi Draynum
Tried several times to PM you but the PM thingy is acting up.
I keep getting a page not found error.
Expect a reply when it finally works.
Neil
Tried several times to PM you but the PM thingy is acting up.
I keep getting a page not found error.
Expect a reply when it finally works.
Neil