Problem using Cake & SoundDiver

[MrLip]

Does anyone have this problem?

I'll be sitting around playing with SoundDiver and my POD( which is connected to the joystick/midi port on my sblive). I get a great sound which inspires an idea, so I want to record it.

So what do I do? I load Cakewalk Pro Audio! and guess what happens?

"You have not selected any MIDI output ports"

So I click on "Choose MIDI ports now"
a menu comes up showing all the available midi ports (which have all been deselected).

So I continue to choose my MIDI ports. I finish and click OK...


"You have not selected any MIDI ports"

So I click on "choose MIDI ports now"
a menu comes up showing all the available midi ports........

On and on and on.


Any solutions?

[MrLip]

Anyway...

I tried running Cake first and then running SoundDiver, but when I do this, SoundDiver doesn't see my POD, and when I click 'rescan' SoundDiver hangs.

No one else has these problems?

[Mountaineer]

I did have this problem before I got my Gadget 8/24 with separate MIDI ports. For some reason, and I don't know if it was CW or Sounddiver, when I used the MIDI ports off my main system soundcard I experienced similar problems.

Don't know what your rig is but if you're running multiple midi inputs to a single sound card and MIDI port, CW may be getting confused?? Just a guess. Sorry I can't be of more help.

Regards,
PAPicker

[c7sus]

Have you tried checking with SoundDiver's site or Line6 to see if there is a patch or update? Could be buggy software.

My own experience with SoundDiver was using a JV1010. The only way I could get CW to recognize the 1010 was with a direct connection- that is, no daisy chaining of MIDI devices. Once I got it up though it was a breeze to edit patches in real time and hear the result.

I'm using a MIDIman MIDIsport 2x2 USB. I gave up on using the SBLive MIDI ports.

[Capt. Snazzy]

when you load cakewalk with something else already using your midi ports, cakewalk cannot initialize them for its own use. to cakewalk, it is as if you don't have any ports.
the same is true in reverse, when you open the sound-driver software with cakewalk already opened and initialized, the pod software cannot look through the midi ports because cakewalk has claimed them. your options are, don't use the two at the same time. get some sort of midi multi-interface, or just let cakewalk run with no midi ports, it shouldn't make a difference unless you use them specifically for something, also, cakewalk has a studioware panel for line6 devices, this will allow you some control over your pod from inside cakewalk. hope this helps
Capt.

[AlChuck]

Is it just the apps, or does the MIDI hardware have to have special multiclient drivers?

[Capt. Snazzy]

my understanding is that this particular problem is brought about by the actual sound card's lack of multiclient midi support, only one application can be in possesion of midi control because it only has one midi port and controller.
if you've ever noticed, this can happen on multichannel interfaces as well, if an application is using one of the sets of channels, then another one will have access to all channels but the ones that are already taken. i believe that the root of this may actually lie in the midi protocol. at least in the computer realm, because i have a midi mixer and can have 3 devices all transmitting to a fourth device or 1 to 3 etc. etc. etc. but i've never gotten two applications to share midi channels transmitting or recieving to/from the same device. i've always just had cakewalk load with no midi devices anyway, it seems to run with more stability that way. and when i do use the soundiver software in the background, cakewalk will randomly lose audio tracks, gone, they just disappear, they are completely gone off the hard drive. this really ticks me off, if anyone has a solution to this one...