support document #2

The SCSI survival guide (or how to get your sampler working effectively with Windows and WaveSurgeon

Symptoms:

Problems when using a sampler with Windows and WaveSurgeon.

Solution:

  1. Use high quality leads

    Cheap leads are tempting after the expense of buying your sampler, but often cause problems with bad transfers, the PC not recognising the sampler, and the like. Even expensive leads can cause problems; sometimes the connection gets disturbed, and it is worth unplugging and replugging the lead in. TURN EVERYTHING OFF before removing or connecting a lead, too; although unlikely, this can blow your SCSI socket, leading to an expensive repair. Try also to keep everything short, no longer than 2 meters if possible; SCSI has recommended lengths for leads, otherwise problems may occur.

  2. Getting the computer to recognize the sampler

    Sometimes the computer will not recognise the existence of the sampler. This can be for a number of reasons. These include a bad connection (see above); conflicting SCSI ids (see below), or because the sampler was turned on at the wrong time. Generally, ensure your sampler(s) are turned on before turning on your PC. If you turn it on after you load Windows, the sampler might not be shown in WaveSurgeon. If this is the case, go to the System Control Panel (in My Computer->Control Panels), select the Device Manager tab, and click 'Refresh'. You will then have to wait for the PC to redetect attached devices, which it hopefully should do.

  3. SCSI ID's

    All SCSI devices have to have a SCSI id, which have to be different to the other devices on the chain. If this is not the case, you might get 'hangs' and problems detecting your sampler. The PC is always id 7; zip drives are on 5 or 6. You will find that once this setting is altered in your sampler (although refer to your manual), you have to restart to let the other devices find the new id.

  4. Help! Windows 95 keeps asking for a driver for my sampler...

    Simply click OK seven times until Windows loads; this message will not appear again.... and yes, it is a pain, but it only happens once!

  5. NT 2000

    Although not officially released, testing with RC3 has revealed long pauses after starting WaveSurgeon, caused by the ASPI driver (see below) scanning the SCSI chain. Also, error messages appear after a few uses, stating that devices have been disconnected and this is not advisable. This is known, so don't be too surprised if this happens. We suspect that an ASPI driver upgrade will solve it.

  6. ASPI

    ASPI is a standard way of accessing SCSI devices, including drives and samplers. Many errors can be cured by downloading the latest ASPI files (go to www.adaptec.com and search for ASPI).

  7. E-mu samplers (E64 / E4k series)

    E-mus use sample position 0 for processing internally, so you can't send or receive samples from there. Set the offset in the sampler profile to 1, and you should be able to transfer problem free.

wavesurgeon - news - download - order - support - search - links - contact