Problems With Soundiver 3 Options

[kaboombahchuck]

I have soundiver running on an iMac 350 indigo using OS 9. Here is the problem, I get the probram to recognise my alesis nanosynth, recieves the data, loads library, the whole nine yards. Everythings works great! Killer program. Untill I quit, and put the computer into the sleep mode. When I go back to soundiver, it says that it is not recieving data from the nano, check midi cables, so on and so forth. No matter what I do, it is a no go.
If I restart the computer, start up soundiver, I can then reload the nano info and every thing is fine, untill I put the computer back to sleep. Any ideas what the problem is? Restarting the computer every time is a pain.

[Francois Déchery]

it sound's like an USB midi interface problem instead of a SoundDiver problem.
I suspect that this is the same with any MIDI applications

The problem is known: when the mac 'wake up' after sleeping , it just "loose" it's midi interface, most of the time

Solutions:
1) desactive energy saving ... (set to 'never') and you will never get into problems anymore

2) when your mac is wake up, be sure to be in the finder, unplug your USB cable (to the MIDI interface), wait a few seconds (10 sec), then plug-it again: the system should automatically relaunch the driver, and the MIDI will be back again.. Sometimes, and depending on your midi software, you may have to quit the midi applications first, then disconnect/reconnect, then start your software again..

You should be abble to avoid restarting your mac

HTH

[kaboombahchuck]

Actualy the problem only happens to soundiver. I do not have the problem with my midi seqencer (meto 5). After awakening the mac, the metro 5 sequencer will connect to the midi devices no problem, but soundiver won't. Kinda strange, don't ya think?
I'm gonna try your suggestions and see what happens.

[lepetitmartien]

First it's SoundDiver… Daddy Apple will spank you if he can catch you .)

next, in the energy saver control pannel, set "suspension of system activities" to never if the hint of Soif is right. it mays be only touch to do. else disabble it completely as he said.

If you have a USB hub try without, some are not totally compatible in fact with Apple material and some software (can't be more precise, the troubles I had with USB freezing peripherals disapeared a few month ago but I don't know why…

[CeJeRo]

Some Macs (might be all) have problems with USB MIDI interfaces and sleep mode. I know that if I leave my studio machine alone and it goes to sleep, upon wake up, Logic receives no more input/output in the transport from my MIDI controller keyboard. My solution..... I know this will be tricky..... see if you can follow this........ you might need to sit down.......


Turn off Energy Saver....

And there you have it folks. Problem gone!

Sorry for the sarcasm, but this is the only way to fix this problem that I know of, until MIDI interface drivers are updated to resolve this problem.

-Chris-

[kaboombahchuck]

OK, SoundDiver SoundDiver SoundDiver

Well I have done some experimentation and here is what I have discovered my options are:

1, It will work if I unplug the USB cable for a bit, and replug

2, Leave the computer alone and let it go into power save mode.

These 2 options work just fine. Only when I put it to sleep manually I get the problem. So there is no need to dork around with my Energy Saver.

The error message stated that the program was having problems deciding if the QS6 device was a module or what. I have noticed that they have an update for the Alesis QS 6 platform, which is the NanoSynth's platform. So I'm gonna see if the update will fix the problem.

This is a unaceptable bug, and I am determined to find a real fix. For the price of the program, it should be rock solid. I know if I were running Logic and this problem was occoring, it would not be a program that I would be using long. As I stated before, I run other midi syncing programs with absolutly no problems. {waves, and steps off soapbox}

So anyway, I'm gonna check out the update and will advise.

Thanks for all solutions so far..........

[lepetitmartien]

Maybe SoundDiver goes on a regular check of devices and has an incompatibility with the control pannel, but the control pannel has been in scrutiny for some time a potential and convicted bugload

Maybe Logic has a clever workaround the bug, and SoundDiver not… But then what Emagic is doing (except coding like mad under Steve's whip to release something too soon for Jaguar)

As it works if you unplug/plug, it's just a minor reset of the USB port loosing trace of peripherals… I'd say: write a gentle but firm letter to Emagic AND Apple (the bag can be either sides) just to recall them that whatever they say about X, some people WORK with 9, not X and that things like that should simply NOT exist.

We are not supposed to be "moutons de Panurge" as we say in french.

(Hey steve! I still want my 10 G5 2 AGP 6 PCI monster…)

i´m not quite shure if i can help with this one:

i had exactly the same problems with my midi-usb-interface (which uses OMS) and Logic on my PowerMac - but i can´t remember any problems as i used the same interface with Logic on my iMac (G3).

i "solved" the problem with the PowerMac by using the emagic MT 4 Midi-Interface - no "sleep-problem" at all.
Sounds like an OMS-"Error" in combination with newer Macs, doesn´t it?
(OMS has not been developed for a while...)


p.s.: sorry for any miss-spelling - not a native speaker.