Deep Editing & MIDI Control:  

S

OUND

D

IVER

 S

ETUP

 T

ROUBLE

-

SHOOTING

8•15

S

OUND

D

IVER

 S

ETUP

 T

ROUBLE

-

SHOOTING

There are a couple of considerations with SoundDiver and Windows sound card systems. 
Here are some troubleshooting hints, courtesy of Line 6’s own product support hero, 
George Van Wagner:

1. SoundBlaster type cards have more than one MIDI driver. The system will 
usually default to the driver for the built-in synth on the card, rather than the 
external MIDI port. This means that you must select the correct driver, before 
SoundDiver can see the POD.

2. MIDI cables must run from out to in and vice versa (don’t connect POD’s MIDI 
In to your computer’s MIDI In; connect POD’s MIDI In to your computer’s MIDI 
Out). Think of it in terms of the direction that information is flowing; out of the 
POD in to the computer. Out of the computer in to the POD.

3. MIDI channels must be set to the same value. The quickest way to ensure 
communication is to simply set the POD MIDI Channel to 

A

 for all (In MIDI-ese, 

this is known as Omni mode).

Here are some basic steps to ensure communication with the POD:

1. When you get the dialog box stating that no new device is found, click on the 
button that says 

Manually

. You will be dropped in the Memory Manager window 

of SoundDiver.

2. On the left hand side of the Memory Manager window, you will see a list of 
parameters. Make sure that the 

Out Port

 is set to the driver for the External 

MIDI. As different companies have different driver names, there's no one set 
name, but the selection should be fairly obvious.