Can't access or select OASYS PCI in audio/MIDI program


FAQ Index

Technical Support

Troubleshooting


OASYS PCI Website

Contents

Make sure that no other audio/MIDI programs are using OASYS PCI

Make sure OASYS PCI software and drivers are installed

Make sure that the OASYS PCI card is seated properly

Temporarily de-select OASYS PCI in Sound control panel (MacOS)

Cannot select as ASIO device in Windows 95/98/ME

Installing ASIO drivers

See also:

Apple G4 - OASYS PCI not recognized on startup

 

Back to Troubleshooting


Make sure that no other audio/MIDI programs are using OASYS PCI

When an ASIO program is using OASYS PCI, it "owns" the audio I/O until it quits, or otherwise signs off from the OASYS PCI drivers.

While OASYS PCI is "owned" by that ASIO program, other audio programs cannot access the card. This includes programs which use ASIO, Sound Manager, or Windows MME.

Conversely, when OASYS PCI is being used by Sound Manager or Windows MME programs, ASIO programs cannot access the card.

So, if you try to run an audio program and receive a message that OASYS PCI is unavailable, make sure that no other audio programs are using the card.

Top of Page


Make sure OASYS PCI software and drivers are installed

Make sure that the audio/MIDI software is configured correctly

Generally, you will need to make some settings in the audio/MIDI software in order for it to work with the OASYS PCI.

For instance, you may need to set the software to use OMS or FreeMIDI, or to set it to use ASIO as the audio I/O format.

For information on particular audio/MIDI programs, see Software-specific information.

Make sure that all OASYS PCI extensions are installed (MacOS)

The OASYS PCI Driver, the OASYS PCI Engine, and the OASyS PCI Objects Library, must be installed in the System Extensions folder order to use the OASYS PCI.

Audio: Make sure that the OASYS PCI ASIO driver is installed

For the OASYS PCI to appear as an audio card within ASIO-compatible digital audio programs, the OASYS PCI ASIO driver must be installed in the proper place for the program.

Most MacOS programs require that ASIO drivers be installed in a folder named "ASIO Drivers," in the same level as the application program. If in doubt, consult your program's manual for more information. For more information, see Installing ASIO drivers (MacOS), below.

On Windows computers, ASIO devices are entered in the Registry. If OASYS PCI does not appear as an ASIO device, check out the advice under Cannot select as ASIO device in Windows 95/98/ME.

MIDI: Make sure that the OMS or FreeMIDI driver is installed (MacOS)

For the OASYS PCI to appear as a MIDI device in a MIDI sequencer, the appropriate MIDI driver - OMS or FreeMIDI - must be installed correctly, in the System->FreeMIDI and System->OMS folders, respectively.

The OASYS PCI Installer will place the drivers in these locations by default.

Top of Page


Make sure that the OASYS PCI card is seated properly

Is the OASYS PCI card seated properly in the PCI slot? Cards can sometimes become unseated if the computer is moved, or if the card is jostled during installation of another card (or RAM, disk drives, etc.). If you think this might be the case, turn off the computer and re-seat the card, following the safety instructions in the users manual.

Top of Page


Temporarily de-select OASYS PCI in Sound control panel (MacOS)

If OASYS PCI is selected as the Sound Manager device, you may get an error message when switching an application's audio I/O from Sound Manager to OASYS PCI's ASIO driver. This may be due to an overlap between sign-on and sign-off, so that the application is still signed on to OASYS PCI via Sound Manager as it is attempting to sign on to OASYS PCI via ASIO. This can be solved very easily by temporarily de-selecting OASYS PCI as the Sound Manager hardware. To do this:

1. Quit any application which is currently using the Sound Manager, including all audio programs.

2. In the Sound control panel, select a source other than OASYS PCI for both Input and Output. Built-In or CD are good choices.

3. Open the ASIO program.

4. Select OASYS PCI as the ASIO device.

5. If you like, return to the Sound control panel and re-select OASYS PCI for both Input and Output.

Top of Page


Cannot select as ASIO device in Windows 95/98/ME

With OASYS PCI version 1.0 and 1.02, some users reported difficulty in selecting OASYS PCI as an ASIO device in certain Windows programs, including Logic Audio and Reaktor, when Cubase VST was *not* installed on the computer.

This was fixed in OASYS PCI software version 2.0. However, if you have not yet upgraded to version 2.0, there is a simple workaround:

1. Download the Cubase VST demo from one of Steinberg's websites:

http://www.steinberg.de
http://www.steinberg.net

(Choose "Demo Software" from the "Where do you want to start?" menu.)

2. Install the Cubase VST demo.

3. In the OASYS PCI installer, use the "Custom Installation" option to re-install the OASYS PCI ASIO driver.

After this, the OASYS PCI should be available as an ASIO device to all ASIO-compatible programs.

Top of Page


Installing ASIO drivers (MacOS)

On MacOS computers, the OASYS PCI installer will place an OASYS PCI ASIO driver into each folder named "ASIO Drivers." You will also need to manually add an OASYS PCI ASIO driver if you install new ASIO-compatible software after installing the OASYS PCI software.

(If you have a copy of the ASIO driver on your hard disk already, you can add it manually simply by dragging a copy of the driver into the folder.)

You can use the OASYS PCI Installer program to install individual ASIO drivers. To do this:

1. Open the OASYS PCI Installer.

2. Follow the on-screen instructions until the main installer screen appears.

3. Choose Custom Install from the menu at the upper left of the window.

A window appears which allows you to select individual components for installation.

4. Select only the Additional ASIO Driver option.

5. Follow the rest of the instructions, selecting the desired location for the ASIO driver.

Top of Page

Back to OASYS PCI FAQ Index

 

Copyright 1999-2002 Korg Inc. FAQ Version: 8/19/02