On 2003-01-18 03:33, jupiter8 wrote:
If you have midi working you should'nt change
anything. Otherwise it is Pulsar midi source to Seq dest. and seq source to Pulsar midi dest.
Hope this makes sense.
Thanks for the quick reply and yes it does make sense...but...
If I do as you suggest SoundDiver gives the following error on startup - twice;
While trying to open MIDI port CreamWare MIDI In/Out2 in function"midiInOpen". the error "Undefined external error". occured.
Make sure that the MIDI interface is connected and switched on.
To overcome this error I added a second Software I/O Sequencer MIDI Source2 and linked it to a second Sequencer MIDI Destination2 - not sure whether this is correct or not?
I'm guessing my problem lies here...
Now SoundDiver loads normally and when I select Trinity Plus and ask it to scan it goes through all my MIDI ports (SW1000XG 1 & 2 plus CreamWare MIDI In/Out1 & 2.
When it comes to CreamWare MIDI In/Out2 it then proceeds to scan all 16 MIDI channels with the progress bar reporting Waiting for incoming MIDI data. Press ESC to abort.
This process takes @15 minutes! then it will give the following error;
No new Devices found!
Please check MIDI cables and Devices.
I'm guessing it is something simple to do with the SFP Routing but I am stuck at this point.
Thanks & regards,
-=Glyn=-