Hello James There were several people who wrote about problems with Mac OS 9 and SD (including me). I have the same setup as you and got lost bytes by receiving big dumps. I also tried OMS with success like you. Then I installed the Mac OS 8.6 (had no problems with this system and SD 2.13) and SD 3 worked fine again. So I think SD has problems with OS 9. My conclusion now is to run OS 8.6 (can be any 8.x) on an other partition with SD 3 till Michael finds a solution or Mac OS X is out and works fine. Greetings Erich > Von: "James Thornton" <thornton@...> > Antworten an: sounddiver-users@egroups.com > Datum: Thu, 25 Jan 2001 00:20:16 -0000 > An: sounddiver-users@egroups.com > Betreff: [SoundDiver] Re: SD3 JV-2080 module crashes > > --- In sounddiver-users@egroups.com, Michael Haydn <mhaydn@m...> > wrote: >> >> I tried to reproduce this problem without success. It seems it >> occurs only with specific data. Please send me the contents of your >> user memory (e.g. recorded in Logic and exported as a MIDI file). > > Michael, > > Thanks for the quick reply. I did some more fooling around and > discovered that if I put SoundDiver in OMS mode, the Roland JV-2080 > module stops crashing, so it looks like there's a bug in the native > SoundDiver Midi driver when used with a Mac G3 hooked up to an Opcode > Studio 4 through a Stealth serial board (my setup). The funny part, > however, is that SoundDiver works fine in "native" mode with the rest > of my sound modules as does Logic Audio. My guess is that the Roland > JV dump is pumping the Midi channel harder than running Logic > or dumping my other devices and this is exposing some Midi timing > bug. > > At this point I can (reluntantly) go back to using OMS for now, but > given the defunct status of Opcode, this makes me very nervous for > the long term. (Also OMS seems to be significantly slower than the > native Emagic driver.) > > P.S. Do you still want the Midi file you asked for or does the above > discussion suggest a different approach. > > Thanks, > James > > > >