Hello - After asking if there were issues with running SoundDiver under XP, I decided to give it a try. I have never been able to crash my XP system until I started using SoundDiver. Lots of "SoundDiver has experienced a problem and needs to close" messages as well as one really hard crash that restarted my system and then gave me a "the system has recovered from a critical error." Any ideas on how to stop or debug these? Also, I'm trying to use AutoLink w/Logic 5.3. I read the manual and have setup the following test scenario: 1.) Start Logic and create a multi-instrument for my Alesis QS8.1 in the environment. Set it's MIDI port. 2.) Start SoundDiver and hear the 'Autolink' pop sound. Add a QS8.1 to my setup and set it's MIDI port. 3.) Go back to Logic and select the QS8.1 in the arrange page. Check "prg" box and then try to move the mouse over the program number -- the patch names that come up are for a GM instrument -- not the ones for the QS8.1. What am I doing wrong? How do I get the QS8 patch names to come up? Thanks... -- Natalia __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com

Hi All, I am still having the same problems with SoundDiver and XP. I have tried everything that's been suggested so far on this site to no avail. SoundDiver freezes up constantly, it will not recognize my Korg T3, Roland TD-10 or my Lexicon LXP-1. I record my instruments via MIDI into Sonar, so I know the MIDI connection is OK. I am open for any more suggestions that anyone might have....... Jeff --- In sounddiver-users@y..., Natalia Rakowski <goosefan@y...> wrote: > Hello - > > After asking if there were issues with running > SoundDiver under XP, I decided to give it a try. > > I have never been able to crash my XP system until I > started using SoundDiver. Lots of "SoundDiver has > experienced a problem and needs to close" messages as > well as one really hard crash that restarted my system > and then gave me a "the system has recovered from a > critical error." Any ideas on how to stop or debug > these? > > Also, I'm trying to use AutoLink w/Logic 5.3. I read > the manual and have setup the following test scenario: > > 1.) Start Logic and create a multi-instrument for my > Alesis QS8.1 in the environment. Set it's MIDI port. > > 2.) Start SoundDiver and hear the 'Autolink' pop > sound. Add a QS8.1 to my setup and set it's MIDI > port. > > 3.) Go back to Logic and select the QS8.1 in the > arrange page. Check "prg" box and then try to move > the mouse over the program number -- the patch names > that come up are for a GM instrument -- not the ones > for the QS8.1. > > What am I doing wrong? How do I get the QS8 patch > names to come up? > > Thanks... > > -- Natalia > > > __________________________________________________ > Do you Yahoo!? > New DSL Internet Access from SBC & Yahoo! > http://sbc.yahoo.com

Natalia Rakowski wrote: > > > I have never been able to crash my XP system until I > > started using SoundDiver. Lots of "SoundDiver has > > experienced a problem and needs to close" messages as > > well as one really hard crash that restarted my system > > and then gave me a "the system has recovered from a > > critical error." Any ideas on how to stop or debug > > these? > > Jeff (thumper 72756) wrote: >I am still having the same problems with SoundDiver and XP. I have >tried everything that's been suggested so far on this site to no >avail. SoundDiver freezes up constantly, it will not recognize my >Korg T3, Roland TD-10 or my Lexicon LXP-1. I record my instruments >via MIDI into Sonar, so I know the MIDI connection is OK. I am open >for any more suggestions that anyone might have....... I also used to have TERRIBLE trouble, along the lines suggested by Natalia. The whole computer used to shake and moan in a most distressing manner and just froze so hard. I cannot remember exactly the steps I took that fixed things, but I think they were the following Go into the WIN ini file, and totally delete everything there to do with both Logic and SoundDiver. They will be in sections beginning: [Logic], [SoundDiver]. If you have installed Unitor Control, delete everything to do with that as well. I suspect that SoundDiver and Emagic problems cause this hang to happen when there is different information, and different listings of ports, in these sections. To load your WIN.ini file, click on Start, enter "sysedit", and close out the various editors until you get to the one entitled win.ini. Then just page down to the relevant section. I also have compatibility mode set for Windows 2000. Be very careful to do this both on the .exe programme itself in the C:blah blahemagicblah folder, as well as on any shortcuts you may have around the place. I know it seems weird, but SoundDiver didn't like it when I had different compatibilities set in different places. Don't ask me why. I cannot think what else I did, but if that doesn't do it for you, I'll rethink again what I did. I know it took me an AGE and much grief with totally no help from anywhere, but I got it to work eventually. Hope this helps. Good luck to the both of you. Kool Musick Keep Musick Kool .

Hi, Colin. I've found the culprit, and my rig now works as you describe. Turns out that on my box (Win98 SE), SoundDiver doesn't play nice with Hubi's Loopback, which I'd been using with Cakewalk. When SoundDiver talks directly to the midi ports, everything's groovy, but when I use Hubi as an intermediary, I get the symptoms I've been describing. I wouldn't have made it to that level of debugging if I hadn't received so much feedback here describing what was normal & expected behavior with a 2080 (and all the other things folks suggested that I verify), so I just wanted to say thanks for all your help! You know, every now and then, I stop to realize and appreciate just how cool the current state of the art is these days for project studios. 10 years ago, I would've killed to have the toys I have today. In fact, so would most million dollar studios! My, but how I love technology... Thanks! --- In sounddiver-users@y..., Colin Shapiro <musos@i...> wrote: > Hi Chris, > >.......However, if I read correctly, you're saying that when you > >double click on a patch in SD, the 2080 changes to that patch? Is > >this what happens in your environment, or did I get that part wrong? > > That's correct. > If I click on a patch (or performance) in SD, the 2080 changes to the > patch/perf. > Also, whatever changes I make in SD's editor's go to the 2080. > > I can't imagine what else I'm doing that I haven't described......... > > Regards - Colin

--- Kool Musick <koolmusick@...> wrote: > Natalia Rakowski wrote: > > > > > I have never been able to crash my XP system > until I > > > started using SoundDiver. Lots of "SoundDiver > has > > > experienced a problem and needs to close" > messages as > > > well as one really hard crash that restarted my > system > > > and then gave me a "the system has recovered > from a > > > critical error." Any ideas on how to stop or > debug > > > these? > > > > > > Jeff (thumper 72756) wrote: > >I am still having the same problems with SoundDiver > and XP. I have > >tried everything that's been suggested so far on > this site to no > >avail. SoundDiver freezes up constantly, it will > not recognize my > >Korg T3, Roland TD-10 or my Lexicon LXP-1. I > record my instruments > >via MIDI into Sonar, so I know the MIDI connection > is OK. I am open > >for any more suggestions that anyone might > have....... > > > I also used to have TERRIBLE trouble, along the > lines suggested by Natalia. > The whole computer used to shake and moan in a most > distressing manner and > just froze so hard. > > I cannot remember exactly the steps I took that > fixed things, but I think > they were the following > > Go into the WIN ini file, and totally delete > everything there to do with > both Logic and SoundDiver. They will be in sections > beginning: [Logic], > [SoundDiver]. If you have installed Unitor Control, > delete everything to do > with that as well. I suspect that SoundDiver and > Emagic problems cause this > hang to happen when there is different information, > and different listings > of ports, in these sections. To load your WIN.ini > file, click on Start, > enter "sysedit", and close out the various editors > until you get to the one > entitled win.ini. Then just page down to the > relevant section. > > I also have compatibility mode set for Windows 2000. > Be very careful to do > this both on the .exe programme itself in the > C:blah blahemagicblah > folder, as well as on any shortcuts you may have > around the place. I know > it seems weird, but SoundDiver didn't like it when I > had different > compatibilities set in different places. Don't ask > me why. > > I cannot think what else I did, but if that doesn't > do it for you, I'll > rethink again what I did. I know it took me an AGE > and much grief with > totally no help from anywhere, but I got it to work > eventually. > > Hope this helps. > > Good luck to the both of you. > > Kool Musick > Keep Musick Kool > Ok. So, before I got SoundDiver, I asked if there were issues with WinXP and I was told that the only one was to change the buffer size. Now, it looks like there are some serious problems that myself and others are having. Has anyone called tech support in the U.S. about these problems? Were they any help? I would like to work with someone at Emagic about this so that we can have some hope of it working at some time. I've heard it said that at least 3.0.5 would be available for us PC users. I would hope that I'm not told to switch to a Mac!!! :-( -- Natalia __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com

Natalia Rakowski wrote: >Ok. So, before I got SoundDiver, I asked if there >were issues with WinXP There are ... as you've discovered. >and I was told that the only >one was to change the buffer size. Probably because there's only an unlucky few ... and those unlucky few are either not members of this list or else are lurkers. >Now, it looks like there are some serious problems >that myself and others are having. In my case, it's used to be having. I did get it to work eventually. >Has anyone called tech support in the U.S. about these >problems? Were they any help? I called them. They were absolutely no help at all. >I would like to work with someone at Emagic about this >so that we can have some hope of it working at some >time. Good luck. But the problem you will find yourself with, I think, is that most people get it to work most of the time. Meaning, as far as Emagic are concerned, that it is a bug that is going to be very hard for them to document or reproduce because it could depend on such extraneous factors as what MIDI interface you are using and what other ports you've got and who knows what else. Until it is faultlessly reproducible in the Emagic labs they can't fix it, and are probably going to keep on saying that "it's our fault". Look at it from their point of view ... they've sold thousands of these programmes with a goodly number working just fine on WindowsXP, so it's unlikely that it's their programme. They'll keep with that attitude until the problem can be definitely shown to be their fault through a reproducible scenario. > I've heard it said that at least 3.0.5 would be >available for us PC users. I have heard that too. We are all just waiting patiently. > I would hope that I'm not >told to switch to a Mac!!! :-( That, also, is not particularly helpful to me. I feel stuck, to be honest. I do not much like Cakewalk. I have 6 PC's here. Plus a bundle of software acquired over many years that it would cost me a FORTUNE to replace never mind the hardware. Why don't you just try the remedy I suggested to see if it works, namely, deleting absolutely everything in the Win.ini file that has anything to do with any Emagic products so that everything can be rebuilt from scratch. I really do think that that is what did it for me. If it doesn't work, just report back and I shall try hard to think what else I did that might have resolved this issue for me. Kool Musick Keep Musick Kool

Hi there, >I've found the culprit, and my rig now works as you describe. Turns >out that on my box (Win98 SE), SoundDiver doesn't play nice with >Hubi's Loopback, which I'd been using with Cakewalk. When SoundDiver >talks directly to the midi ports, everything's groovy, but when I >use Hubi as an intermediary, I get the symptoms I've been >describing. > >I wouldn't have made it to that level of debugging if I hadn't >received so much feedback here describing what was normal & expected >behavior with a 2080 (and all the other things folks suggested that >I verify), so I just wanted to say thanks for all your help! You're most welcome. People have helped me so often here, it's the least I can do to "pay it forward". >You know, every now and then, I stop to realize and appreciate just >how cool the current state of the art is these days for project >studios. 10 years ago, I would've killed to have the toys I have >today. In fact, so would most million dollar studios! My, but how I >love technology... So right. I have to keep reminding myself that I have enough toys.....now make some music! :-) Best regards - Colin

Okay - I deleted my Preferences file, deleted references to SoundDiver in win.ini and started from scratch. I was able to select a device from the supported devices list and 'scan' it. All of my synths are now setup in SoundDiver and SoundDiver knows about all of their patches. I then closed SoundDiver. Started Logic and created an environment layer with my synths as multi-instruments. I selected the proper MIDI ports for my synths and then started SoundDiver. Heard the little 'pop' sound for AutoLink mode. Then, I checked the 'Prg' option under one of my synths, and then double-clicked its icon in the environment to have the patch name list pop up. I then selected 'Update using AutoLink' and I got an error that the patch names were not available on that channel and port. My MIDI channels are set to: All and my ports match the ports that my synths are on and that SoundDiver sees them on. What am I doing wrong? I would really like to have my patch names show up in AutoLink. Also, I've seen now that when SoundDiver crashes, the program window goes away but 'SoundDiver.exe' stays in the task list and will not die -- even when forced! :) The only way to have it go away is with a system reboot. Finally, I had written to support@... about my crashes and the person who wrote back claimed that SoundDiver is known to not be XP-compliant! What's up with that? -- Natalia __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com

Using Sounddiver (Win) 3.04 with Proteus 2000 V1.24 Have just installed Siedlaczek Rom and done a rediscovery of all presets / riffs / names. SoundDiver identifiies the new rom but reports it as unknown rom and shows the instruments. If I go to try and use one of the instruments in a patch using the patch editor the only ROM selectable is the Composer Rom, the Siedlaczek Rom is now visible or selectable. Does any member in this forum have any clues on how this can be overcome. The ROM is visible on the Proteus and can be selected from the Proteus sound expansion controls. Thnks in advance.

I will have to modify the module so that it recognizes the Siedlaczek ROM ID. To help me find out which ID that ROM uses, please send me a copy of your "SoundDiver 3.0 Preferences.PRF" file (please compress it using WinZip) and I will adapt the module for use with the Siedlaczek ROM. Thanks, - Jens emagic > -----Original Message----- > From: markptimms [mailto:yahoogroups@...] > Sent: Freitag, 27. September 2002 08:06 > To: sounddiver-users@yahoogroups.com > Subject: [SoundDiver] Proteus 2000 + Siedlaczek Rom > > Using Sounddiver (Win) 3.04 with Proteus 2000 V1.24 > > Have just installed Siedlaczek Rom and done a rediscovery of all > presets / riffs / names. SoundDiver identifiies the new rom but > reports it as unknown rom and shows the instruments. If I go to try > and use one of the instruments in a patch using the patch editor the > only ROM selectable is the Composer Rom, the Siedlaczek Rom is now > visible or selectable. Does any member in this forum have any clues > on how this can be overcome. The ROM is visible on the Proteus and > can be selected from the Proteus sound expansion controls. > > Thnks in advance. > > > > > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

At 3:26 PM -0700 9/26/02, Natalia Rakowski wrote: >Finally, I had written to support@... about >my crashes and the person who wrote back claimed that >SoundDiver is known to not be XP-compliant! What's up >with that? He is right. SoundDiver is officially incompatible with Windows XP. -- Beste Gruesse - best regards, Michael Haydn - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Dipl.-Inform. Univ. Michael Haydn mhaydn@... SoundDiver Group Executive http://www.emagic.de/ Logic Developer (Logic Control integration) Emagic Soft- & Hardware GmbH - Germany Phone: +49 4101 495 0 Halstenbeker Weg 96, 25462 Rellingen Fax : +49 4101 495 199 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

--- Michael Haydn <mhaydn@...> wrote: > At 3:26 PM -0700 9/26/02, Natalia Rakowski wrote: > >Finally, I had written to support@... > about > >my crashes and the person who wrote back claimed > that > >SoundDiver is known to not be XP-compliant! What's > up > >with that? > > He is right. SoundDiver is officially incompatible > with Windows XP. > -- > > Beste Gruesse - best regards, > Michael Haydn So, is this why the AutoLink doesn't work? Or am I doing something wrong in that regard...refer to my original mail for what steps I was taking. Thank you... -- Natalia __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com

Hi Natalia, >Okay - > >I deleted my Preferences file, deleted references to >SoundDiver in win.ini and started from scratch. Good! Glad you decided to try it. >I was able to select a device from the supported >devices list and 'scan' it. All of my synths are now >setup in SoundDiver and SoundDiver knows about all of >their patches. So ... it worked then! >I then closed SoundDiver. Started Logic and created >an environment layer with my synths as >multi-instruments. I selected the proper MIDI ports >for my synths and then started SoundDiver. Heard the >little 'pop' sound for AutoLink mode. So far so good. >Then, I checked the 'Prg' option under one of my >synths, and then double-clicked its icon in the >environment to have the patch name list pop up. I >then selected 'Update using AutoLink' and I got an >error that the patch names were not available on that >channel and port. My MIDI channels are set to: All >and my ports match the ports that my synths are on and >that SoundDiver sees them on. Not so good! Won't solve problems but monitoring signals might assist. Monitoring synth outputs ... Set ports of all synths (i.e. multi's) back to none. Create dedicated port object. Use 'New' menu, second from bottom. One for each synth port. Set drivers of above port objects to whatever. Under New menu, create monitor. Cable a monitor into each port object. Cable each multi into monitor preceding its port object. Voila. All synth exit messages captured. Monitoring synth inputs ... Go to the 'Clicks and Ports' layer. All individual MIDI inputs available are listed under 'SUM'. Leave the 'SUM' output alone. Create monitor. Carefully select cable of desired input port and cable into monitor. Cable monitor into whatever you wish. Voila. All synth entry messages captured. Try to change channels and see if you have two-way communication, and if so what messages are being sent. Simply clicking in the monitor window will clear it. >What am I doing wrong? I would really like to have my >patch names show up in AutoLink. I do not know what you are doing wrong ... and doubt you are in error. But at least with above setup you can see whether or not any messages are going back and forth, and if so which ones. Notice though how your position has changed. Congratulations for you have moved from being a ''WindowsXP just won't work' person to being an 'Autolink won't work' person. Those people are much more common, and this is not necessarily anything to do with XP. There are lots of known problems -- but not necessarily known solutions -- with Autolink regardless of platform, synth, version of Logic version etc. I have no statistics for how many of such problems have a specific XP origin. But a generalized Autolink problem is more common so someone might help, but I don't notice anyone so far. Perhaps ... you could try being a bit more specific. Which synths. Model No. What ports. What MIDI interface. And ... have you checked in Win ini to see if each port has a 0, a 1, or a 7? Maybe if you listed those someone would have an idea. >Also, I've seen now that when SoundDiver crashes, the >program window goes away but 'SoundDiver.exe' stays in >the task list and will not die -- even when forced! :) > The only way to have it go away is with a system >reboot. When you do Ctl-Alt-Del and raise Task Manager, go to second tab which says 'Processes'. You can often stop things there. Make a mental note of opened processes both before and after loading SD so you know which ones are SD related. >Finally, I had written to support@... about >my crashes and the person who wrote back claimed that >SoundDiver is known to not be XP-compliant! > What's up >with that? Well ... probably just a sneaky way of saying that if you've bought SD for usage under XP then more fool you and you're on your own. Probably ... SoundDiver has not been beta-tested and recompiled specifically for the XP engine. I believe SD is official under Windows 2000. Emagic are not the only company who seem to pursue the policy that if it's OK under 2000 it should be enough OK under XP to make it not worth specific developmental effort right now. They seem to feel it's better to focus on a newer version. There's only 3 or 4 people, I think, working on SD. Possibly ... there are some XP issues being addressed for 3.05. I don't know. Could be why it's being held up??!!! This is a very clever system. Since most of the time most people can get it to work (lucky them), Emagic are not required to print up on the boxes that SoundDiver is "known" to be incompatible with XP. I try to think of it in a charitable way. I regard myself as an unpaid and unsung beta tester. Then I can get all excited when another Situation comes up whenever and the proverbial hits the fan. "Well, well, well ... what have we here". Helps me not get TOO frustrated. (If smoking some thing works for you instead ... !!) I also found, unfortunately, that posting XP questions here got no response, so I tried kludging on my own. But do post if you have problems again. Even if I can't resolve it I might send you something attempting to be ironic and humourous and dry. Hoping that it might help a little. When you've set up those diagnostic monitors for your Environment and clicked on your synths report back with those messages as well as specifying the synths and models and kind of Interface etc and maybe someone can help you further. Good luck. Kool Musick Keep Musick Kool

Hi all, I jut joined this group because I also am having troubles with SD and win XP. I installed the oem version that came with my access virus and then installed a patch for my model. When I fire up SD it attempts to do some form of scan for midi hardware, but this always hangs. I believe this can be fixed by setting the buffer to 1k, but I can't get into SD to change this setting because the scan always hangs!! *pulls hair out* Any thoughts? :) Cheers, Steve B -----Original Message----- From : Natalia Rakowski <goosefan@...> To : sounddiver-users@yahoogroups.com Date : 27 September 2002 14:46:13 Subject : Re: [SoundDiver] More SoundDiver Fun! >--- Michael Haydn <mhaydn@...> wrote: >> At 3:26 PM -0700 9/26/02, Natalia Rakowski wrote: >> >Finally, I had written to support@... >> about >> >my crashes and the person who wrote back claimed >> that >> >SoundDiver is known to not be XP-compliant! What's >> up >> >with that? >> >> He is right. SoundDiver is officially incompatible >> with Windows XP. >> -- >> >> Beste Gruesse - best regards, >> Michael Haydn > >So, is this why the AutoLink doesn't work? Or am I >doing something wrong in that regard...refer to my >original mail for what steps I was taking. > >Thank you... > >-- Natalia > > >__________________________________________________ >Do you Yahoo!? >New DSL Internet Access from SBC & Yahoo! >http://sbc.yahoo.com > > > >Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ > > > -- Personalised email by http://another.com

--- Kool Musick <koolmusick@...> wrote: > Not so good! > Won't solve problems but monitoring signals might > assist. > > Ok...changing patches works. My synths repond to patch changes through Logic. But getting the patch names via AutoLink does not. > > Perhaps ... you could try being a bit more specific. > Which synths. Model > No. What ports. What MIDI interface. And ... have > you checked in Win ini to > see if each port has a 0, a 1, or a 7? > Maybe if you listed those someone would have an > idea. > > My setup is as follows: Delta 1010 interface & MidiSport 8x8 SE. Until I can get things sort of working, I have an Alesis QS8.1 hooked up to the Delta1010 MIDI port, a Waldorf MicroQ hooked up to Port 1 of the 8x8, and an MS2000R hooked up to Port 8 of the 8x8. Here's the SoundDiver section of my win.ini: [SoundDiver] MidiIn_In_1_USB_MidiSport_8x8=1 MidiIn_In_2_USB_MidiSport_8x8=1 MidiIn_In_3_USB_MidiSport_8x8=1 MidiIn_In_4_USB_MidiSport_8x8=1 MidiIn_In_5_USB_MidiSport_8x8=1 MidiIn_In_6_USB_MidiSport_8x8=1 MidiIn_In_7_USB_MidiSport_8x8=1 MidiIn_In_8_USB_MidiSport_8x8=1 MidiIn_In_SMPTE_USB_MidiSport_8x8=1 MidiIn_MPU_401=1 MidiIn_Delta_1010_MIDI=1 MidiOut_Microsoft_GS_Wavetable_SW_Synth=1 MidiOut_Out_1_USB_MidiSport_8x8=7 MidiOut_Out_2_USB_MidiSport_8x8=1 MidiOut_Out_3_USB_MidiSport_8x8=1 MidiOut_Out_4_USB_MidiSport_8x8=1 MidiOut_Out_5_USB_MidiSport_8x8=1 MidiOut_Out_6_USB_MidiSport_8x8=1 MidiOut_Out_7_USB_MidiSport_8x8=1 MidiOut_Out_8_USB_MidiSport_8x8=7 MidiOut_Out_SMPTE_USB_MidiSport_8x8=1 MidiOut_MPU_401=1 MidiOut_Delta_1010_MIDI=7 And...just for good measure, here's the Logic section: [Logic] MidiIn_MPU_401=1 MidiIn_Delta_1010_MIDI=1 MidiOut_Microsoft_GS_Wavetable_SW_Synth=7 MidiOut_MPU_401=7 MidiOut_Delta_1010_MIDI=7 MidiIn_In_1_USB_MidiSport_8x8=1 MidiIn_In_2_USB_MidiSport_8x8=1 MidiIn_In_3_USB_MidiSport_8x8=1 MidiIn_In_4_USB_MidiSport_8x8=1 MidiIn_In_5_USB_MidiSport_8x8=1 MidiIn_In_6_USB_MidiSport_8x8=1 MidiIn_In_7_USB_MidiSport_8x8=1 MidiIn_In_8_USB_MidiSport_8x8=1 MidiIn_In_SMPTE_USB_MidiSport_8x8=1 MidiOut_Out_1_USB_MidiSport_8x8=7 MidiOut_Out_2_USB_MidiSport_8x8=7 MidiOut_Out_3_USB_MidiSport_8x8=7 MidiOut_Out_4_USB_MidiSport_8x8=7 MidiOut_Out_5_USB_MidiSport_8x8=7 MidiOut_Out_6_USB_MidiSport_8x8=7 MidiOut_Out_7_USB_MidiSport_8x8=7 MidiOut_Out_8_USB_MidiSport_8x8=7 MidiOut_Out_SMPTE_USB_MidiSport_8x8=7 > >Also, I've seen now that when SoundDiver crashes, > the > >program window goes away but 'SoundDiver.exe' stays > in > >the task list and will not die -- even when forced! > :) > > The only way to have it go away is with a system > >reboot. > When you do Ctl-Alt-Del and raise Task Manager, go > to second tab which says > 'Processes'. You can often stop things there. Make a > mental note of opened > processes both before and after loading SD so you > know which ones are SD > related. I'm aware of this. The only process that gets added when SoundDiver is launched is: "SoundDiver.exe" and as I said, it will not die when I select it and click on 'End Process.' <rant>On a sidenote, I would just like to say that I would really love to stop nagging people and get this working so that I can actually make music instead of debugging software issues!!! The only music I've made recently has been with the demos to Sonar and Cubase SX because getting the patch names in is trivial (although not as cool as the AutoLink way since they can't be dynamically updated at runtime if I make a programming change to the synth).</rant> -- Natalia __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com

Hi Natalia, >Ok...changing patches works. My synths repond to >patch changes through Logic. But getting the patch >names via AutoLink does not. OK This bit looks interesting ... notice the long list of 1's here and only a couple of 7's >[SoundDiver] >MidiIn_In_1_USB_MidiSport_8x8=1 >MidiIn_In_2_USB_MidiSport_8x8=1 >MidiIn_In_3_USB_MidiSport_8x8=1 >MidiIn_In_4_USB_MidiSport_8x8=1 >MidiIn_In_5_USB_MidiSport_8x8=1 >MidiIn_In_6_USB_MidiSport_8x8=1 >MidiIn_In_7_USB_MidiSport_8x8=1 >MidiIn_In_8_USB_MidiSport_8x8=1 >MidiIn_In_SMPTE_USB_MidiSport_8x8=1 >MidiIn_MPU_401=1 >MidiIn_Delta_1010_MIDI=1 >MidiOut_Microsoft_GS_Wavetable_SW_Synth=1 >MidiOut_Out_1_USB_MidiSport_8x8=7 >MidiOut_Out_2_USB_MidiSport_8x8=1 >MidiOut_Out_3_USB_MidiSport_8x8=1 >MidiOut_Out_4_USB_MidiSport_8x8=1 >MidiOut_Out_5_USB_MidiSport_8x8=1 >MidiOut_Out_6_USB_MidiSport_8x8=1 >MidiOut_Out_7_USB_MidiSport_8x8=1 >MidiOut_Out_8_USB_MidiSport_8x8=7 >MidiOut_Out_SMPTE_USB_MidiSport_8x8=1 >MidiOut_MPU_401=1 >MidiOut_Delta_1010_MIDI=7 And then ... notice the long list of 7's here..... >[Logic] >MidiIn_MPU_401=1 >MidiIn_Delta_1010_MIDI=1 >MidiOut_Microsoft_GS_Wavetable_SW_Synth=7 >MidiOut_MPU_401=7 >MidiOut_Delta_1010_MIDI=7 >MidiIn_In_1_USB_MidiSport_8x8=1 >MidiIn_In_2_USB_MidiSport_8x8=1 >MidiIn_In_3_USB_MidiSport_8x8=1 >MidiIn_In_4_USB_MidiSport_8x8=1 >MidiIn_In_5_USB_MidiSport_8x8=1 >MidiIn_In_6_USB_MidiSport_8x8=1 >MidiIn_In_7_USB_MidiSport_8x8=1 >MidiIn_In_8_USB_MidiSport_8x8=1 >MidiIn_In_SMPTE_USB_MidiSport_8x8=1 >MidiOut_Out_1_USB_MidiSport_8x8=7 >MidiOut_Out_2_USB_MidiSport_8x8=7 >MidiOut_Out_3_USB_MidiSport_8x8=7 >MidiOut_Out_4_USB_MidiSport_8x8=7 >MidiOut_Out_5_USB_MidiSport_8x8=7 >MidiOut_Out_6_USB_MidiSport_8x8=7 >MidiOut_Out_7_USB_MidiSport_8x8=7 >MidiOut_Out_8_USB_MidiSport_8x8=7 >MidiOut_Out_SMPTE_USB_MidiSport_8x8=7 Try changing the 1's in the SoundDiver section to 7's so that they match the 7's in the Logic section. As far as I know, a 0 means 'disabled', a 1 means on and OK to use, while a 7 means OK and tested for sysex. So ... possibly SoundDiver thinks the vast bulk of your output ports are unavailable and unusable for the lengthy sysex strings it is prone to sending. Try that and see how it works. Best I can suggest for now. >I'm aware of this. The only process that gets added >when SoundDiver is launched is: "SoundDiver.exe" and >as I said, it will not die when I select it and click >on 'End Process.' I apologise. I was not trying to treat you like a buffoon. Really I wasn't. It is impossible to know, though, what people know and do not know. My computer knowledge is VERY limited indeed, and I simply suggested it in case you had overlooked it. I am NOT an expert. ><rant>On a sidenote, I would just like to say that I >would really love to stop nagging people and get this >working so that I can actually make music instead of >debugging software issues!!! The only music I've made >recently has been with the demos to Sonar and Cubase >SX because getting the patch names in is trivial >(although not as cool as the AutoLink way since they >can't be dynamically updated at runtime if I make a >programming change to the synth).</rant> Feel free to rant whenever. Hope my above suggestion works for you. If not, I'll try to think of something else. I have to go earn my daily bread now, so any other messages you send might have to keep for a while. Kool Musick Keep Musick Kool

--- Kool Musick <koolmusick@...> wrote: > Try changing the 1's in the SoundDiver section to > 7's so that they match > the 7's in the Logic section. As far as I know, a 0 > means 'disabled', a 1 > means on and OK to use, while a 7 means OK and > tested for sysex. So ... > possibly SoundDiver thinks the vast bulk of your > output ports are > unavailable and unusable for the lengthy sysex > strings it is prone to sending. > > Try that and see how it works. > > Best I can suggest for now. > I'll try that tonight, when I'm done coding software for 'THE MAN.' ;-B Can someone tell me what sets these values in win.ini to a '1' or '7' in Logic? The environment? Some other place? Should I try to make the Logic and SoundDiver sections identical just to test things out? Also, are most people getting WinXP to work in 'compatibility mode?' Which one? 2000? 98? Thanks again... -- Natalia __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com

Kool - 'Can't believe it; you keep on showing up wherever I go! Nice to come across you again. Is the posttonality list still alive and kicking? I haven't purchased SoundDiver yet; I'm lurking here to decide if trying to run it on XP is worth the (apparent) aggravation! Take care, Stu McIntire -----Original Message----- From: Kool Musick [mailto:koolmusick@...] Sent: Friday, September 27, 2002 10:44 AM To: sounddiver-users@yahoogroups.com Subject: Re: [SoundDiver] More SoundDiver Fun! Hi Natalia, >Ok...changing patches works. My synths repond to >patch changes through Logic. But getting the patch >names via AutoLink does not. OK This bit looks interesting ... notice the long list of 1's here and only a couple of 7's >[SoundDiver] >MidiIn_In_1_USB_MidiSport_8x8=1 >MidiIn_In_2_USB_MidiSport_8x8=1 >MidiIn_In_3_USB_MidiSport_8x8=1 >MidiIn_In_4_USB_MidiSport_8x8=1 >MidiIn_In_5_USB_MidiSport_8x8=1 >MidiIn_In_6_USB_MidiSport_8x8=1 >MidiIn_In_7_USB_MidiSport_8x8=1 >MidiIn_In_8_USB_MidiSport_8x8=1 >MidiIn_In_SMPTE_USB_MidiSport_8x8=1 >MidiIn_MPU_401=1 >MidiIn_Delta_1010_MIDI=1 >MidiOut_Microsoft_GS_Wavetable_SW_Synth=1 >MidiOut_Out_1_USB_MidiSport_8x8=7 >MidiOut_Out_2_USB_MidiSport_8x8=1 >MidiOut_Out_3_USB_MidiSport_8x8=1 >MidiOut_Out_4_USB_MidiSport_8x8=1 >MidiOut_Out_5_USB_MidiSport_8x8=1 >MidiOut_Out_6_USB_MidiSport_8x8=1 >MidiOut_Out_7_USB_MidiSport_8x8=1 >MidiOut_Out_8_USB_MidiSport_8x8=7 >MidiOut_Out_SMPTE_USB_MidiSport_8x8=1 >MidiOut_MPU_401=1 >MidiOut_Delta_1010_MIDI=7 And then ... notice the long list of 7's here..... >[Logic] >MidiIn_MPU_401=1 >MidiIn_Delta_1010_MIDI=1 >MidiOut_Microsoft_GS_Wavetable_SW_Synth=7 >MidiOut_MPU_401=7 >MidiOut_Delta_1010_MIDI=7 >MidiIn_In_1_USB_MidiSport_8x8=1 >MidiIn_In_2_USB_MidiSport_8x8=1 >MidiIn_In_3_USB_MidiSport_8x8=1 >MidiIn_In_4_USB_MidiSport_8x8=1 >MidiIn_In_5_USB_MidiSport_8x8=1 >MidiIn_In_6_USB_MidiSport_8x8=1 >MidiIn_In_7_USB_MidiSport_8x8=1 >MidiIn_In_8_USB_MidiSport_8x8=1 >MidiIn_In_SMPTE_USB_MidiSport_8x8=1 >MidiOut_Out_1_USB_MidiSport_8x8=7 >MidiOut_Out_2_USB_MidiSport_8x8=7 >MidiOut_Out_3_USB_MidiSport_8x8=7 >MidiOut_Out_4_USB_MidiSport_8x8=7 >MidiOut_Out_5_USB_MidiSport_8x8=7 >MidiOut_Out_6_USB_MidiSport_8x8=7 >MidiOut_Out_7_USB_MidiSport_8x8=7 >MidiOut_Out_8_USB_MidiSport_8x8=7 >MidiOut_Out_SMPTE_USB_MidiSport_8x8=7 Try changing the 1's in the SoundDiver section to 7's so that they match the 7's in the Logic section. As far as I know, a 0 means 'disabled', a 1 means on and OK to use, while a 7 means OK and tested for sysex. So ... possibly SoundDiver thinks the vast bulk of your output ports are unavailable and unusable for the lengthy sysex strings it is prone to sending. Try that and see how it works. Best I can suggest for now. >I'm aware of this. The only process that gets added >when SoundDiver is launched is: "SoundDiver.exe" and >as I said, it will not die when I select it and click >on 'End Process.' I apologise. I was not trying to treat you like a buffoon. Really I wasn't. It is impossible to know, though, what people know and do not know. My computer knowledge is VERY limited indeed, and I simply suggested it in case you had overlooked it. I am NOT an expert. ><rant>On a sidenote, I would just like to say that I >would really love to stop nagging people and get this >working so that I can actually make music instead of >debugging software issues!!! The only music I've made >recently has been with the demos to Sonar and Cubase >SX because getting the patch names in is trivial >(although not as cool as the AutoLink way since they >can't be dynamically updated at runtime if I make a >programming change to the synth).</rant> Feel free to rant whenever. Hope my above suggestion works for you. If not, I'll try to think of something else. I have to go earn my daily bread now, so any other messages you send might have to keep for a while. Kool Musick Keep Musick Kool Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Steve writes: >Hi all, I jut joined this group because I also am having troubles with SD >and win XP. I installed the oem version that came with my access virus >and then installed a patch for my model. When I fire up SD it attempts to >do some form of scan for midi hardware, but this always hangs. I believe >this can be fixed by setting the buffer to 1k, but I can't get into SD to >change this setting because the scan always hangs!! > >*pulls hair out* > >Any thoughts? :) Delete the *.prf file from your SoundDiver folder. Open up win.ini in sysedit. Delete everything underneath [SoundDiver] (i.e. listings of MIDI ports) If you also use Logic Audio, delete everything underneath [Logic] Try to load SoundDiver. It will probably hang. Open up win.ini again. Put a zero beside every single port you see, both MIDI ins and MIDI outs. Now try to load SoundDiver. It should now load without trying to scan anything at all because you have disabled all ports. Set the buffer. Reload SoundDiver to see it works OK. Exit. Re-edit win.ini and enable ONE PORT AT A TIME (both its in and its out) so that you can scan and test the synth attached to that port. Focussing on one device at a time will allow you to see whether you not have one offending gadget in particular. Hope this helps. Good luck. Kool Musick Keep Musick Kool >Cheers, > >Steve B > >-----Original Message----- > From : Natalia Rakowski <goosefan@...> >To : sounddiver-users@yahoogroups.com >Date : 27 September 2002 14:46:13 >Subject : Re: [SoundDiver] More SoundDiver Fun! > > >--- Michael Haydn <mhaydn@...> wrote: > >> At 3:26 PM -0700 9/26/02, Natalia Rakowski wrote: > >> >Finally, I had written to support@... > >> about > >> >my crashes and the person who wrote back claimed > >> that > >> >SoundDiver is known to not be XP-compliant! What's > >> up > >> >with that? > >> > >> He is right. SoundDiver is officially incompatible > >> with Windows XP. > >> -- > >> > >> Beste Gruesse - best regards, > >> Michael Haydn > > > >So, is this why the AutoLink doesn't work? Or am I > >doing something wrong in that regard...refer to my > >original mail for what steps I was taking. > > > >Thank you... > > > >-- Natalia > > > > > >__________________________________________________ > >Do you Yahoo!? > >New DSL Internet Access from SBC & Yahoo! > >http://sbc.yahoo.com > > > > > > > >Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ > > > > > > > > >-- >Personalised email by http://another.com > > > > > > >Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

--- Natalia Rakowski <goosefan@...> wrote: > > --- Kool Musick <koolmusick@...> wrote: > > Try changing the 1's in the SoundDiver section to > > 7's so that they match > > the 7's in the Logic section. As far as I know, a > 0 > > means 'disabled', a 1 > > means on and OK to use, while a 7 means OK and > > tested for sysex. So ... > > possibly SoundDiver thinks the vast bulk of your > > output ports are > > unavailable and unusable for the lengthy sysex > > strings it is prone to sending. > > > > Try that and see how it works. > > > > Best I can suggest for now. > > That did not help. What's worse is that I'll start SoundDiver once with my synths defined in its prefs and it will talk to them just fine. The next time I start SoundDiver, it claims that it can't communicate with the synths. When I try to re-scan, it won't find them. Even when I do have things scanned and communicating, when I launch SoundDiver in Autolink mode, it doesn't see a suitable Logic thru port even though my environment has my multi-instruments defined with the proper MIDI ports -- matching the ones in SoundDiver. So, I decided to try to call Emagic US support. I waited on hold for over 30 minutes (this is a long distance number). When the guy answered he told me that there is NOTHING he could walk me through and nothing he could suggest to try to fix my problems. He said that he hears problems about SoundDiver & XP and more so about SoundDiver & Autolink under all OS's every single day. He told me that I should consult with Mr. Haydn about getting any of my problems sorted out because he couldn't do anything for me!!! Great customer service, huh??? I told him that maybe I could tell him what my settings are in my win.ini and that may point to a solution and he said that it would not. He then said that I should nag Mr. Haydn to get these issues ironed out because so many people have them and Emagic US can't even get answers! What is up? I paid for a program and even the support people aren't even making an attempt to help me or talking to Germany about the issues that they are getting calls about every day??? This is all very frustrating... So, Mr. Haydn...do you have any comments? Thank you... -- Natalia __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com

Will this ever be released and will it be XP-compatible? Regards M

Michael, I sent to you version 2 of the five adaptations I wrote for the Supernova series four months ago but they have yet to appear on the Emagic site. It seems that the entire database is probably out of date, but will you no longer accept contributions from PC users? I for one hope to continue using SD on a PC for as long as I can. Regards M

I'm running Windows XP Pro, Logic Platinum 5.3 and SD 3.04. I couldn't get Autolink working as such, but if I build a library from a particular device, make sure that library is selected as the current window, then switch to Logic - getting the patch names into Logic environment seems to work. The down side is, that you have to keep refreshing the library on SD, and then the banks on Logic each time you add a new patch / performance on your keyboard. One irritating trate that I keep comming up against, is that I open Sound Diver or an existing Logic song, and find that my assigned midi channels have slipped by one (i.e. Instrument that was on Unitor 8 port 8, is now assiged to port 7) right accross the board. How ? Why ? --- In sounddiver-users@y..., "Stu McIntire" <smcintire@e...> wrote: > Kool - 'Can't believe it; you keep on showing up wherever I go! Nice to > come across you again. Is the posttonality list still alive and kicking? > > I haven't purchased SoundDiver yet; I'm lurking here to decide if trying to > run it on XP is worth the (apparent) aggravation! > > Take care, > > Stu McIntire > > -----Original Message----- > From: Kool Musick [mailto:koolmusick@y...] > Sent: Friday, September 27, 2002 10:44 AM > To: sounddiver-users@y... > Subject: Re: [SoundDiver] More SoundDiver Fun! > > > Hi Natalia, > > >Ok...changing patches works. My synths repond to > >patch changes through Logic. But getting the patch > >names via AutoLink does not. > OK > > This bit looks interesting ... notice the long list of 1's here and only a > couple of 7's > > >[SoundDiver] > >MidiIn_In_1_USB_MidiSport_8x8=1 > >MidiIn_In_2_USB_MidiSport_8x8=1 > >MidiIn_In_3_USB_MidiSport_8x8=1 > >MidiIn_In_4_USB_MidiSport_8x8=1 > >MidiIn_In_5_USB_MidiSport_8x8=1 > >MidiIn_In_6_USB_MidiSport_8x8=1 > >MidiIn_In_7_USB_MidiSport_8x8=1 > >MidiIn_In_8_USB_MidiSport_8x8=1 > >MidiIn_In_SMPTE_USB_MidiSport_8x8=1 > >MidiIn_MPU_401=1 > >MidiIn_Delta_1010_MIDI=1 > >MidiOut_Microsoft_GS_Wavetable_SW_Synth=1 > >MidiOut_Out_1_USB_MidiSport_8x8=7 > >MidiOut_Out_2_USB_MidiSport_8x8=1 > >MidiOut_Out_3_USB_MidiSport_8x8=1 > >MidiOut_Out_4_USB_MidiSport_8x8=1 > >MidiOut_Out_5_USB_MidiSport_8x8=1 > >MidiOut_Out_6_USB_MidiSport_8x8=1 > >MidiOut_Out_7_USB_MidiSport_8x8=1 > >MidiOut_Out_8_USB_MidiSport_8x8=7 > >MidiOut_Out_SMPTE_USB_MidiSport_8x8=1 > >MidiOut_MPU_401=1 > >MidiOut_Delta_1010_MIDI=7 > > And then ... notice the long list of 7's here..... > > >[Logic] > >MidiIn_MPU_401=1 > >MidiIn_Delta_1010_MIDI=1 > >MidiOut_Microsoft_GS_Wavetable_SW_Synth=7 > >MidiOut_MPU_401=7 > >MidiOut_Delta_1010_MIDI=7 > >MidiIn_In_1_USB_MidiSport_8x8=1 > >MidiIn_In_2_USB_MidiSport_8x8=1 > >MidiIn_In_3_USB_MidiSport_8x8=1 > >MidiIn_In_4_USB_MidiSport_8x8=1 > >MidiIn_In_5_USB_MidiSport_8x8=1 > >MidiIn_In_6_USB_MidiSport_8x8=1 > >MidiIn_In_7_USB_MidiSport_8x8=1 > >MidiIn_In_8_USB_MidiSport_8x8=1 > >MidiIn_In_SMPTE_USB_MidiSport_8x8=1 > >MidiOut_Out_1_USB_MidiSport_8x8=7 > >MidiOut_Out_2_USB_MidiSport_8x8=7 > >MidiOut_Out_3_USB_MidiSport_8x8=7 > >MidiOut_Out_4_USB_MidiSport_8x8=7 > >MidiOut_Out_5_USB_MidiSport_8x8=7 > >MidiOut_Out_6_USB_MidiSport_8x8=7 > >MidiOut_Out_7_USB_MidiSport_8x8=7 > >MidiOut_Out_8_USB_MidiSport_8x8=7 > >MidiOut_Out_SMPTE_USB_MidiSport_8x8=7 > > Try changing the 1's in the SoundDiver section to 7's so that they match > the 7's in the Logic section. As far as I know, a 0 means 'disabled', a 1 > means on and OK to use, while a 7 means OK and tested for sysex. So ... > possibly SoundDiver thinks the vast bulk of your output ports are > unavailable and unusable for the lengthy sysex strings it is prone to > sending. > > Try that and see how it works. > > Best I can suggest for now. > > > >I'm aware of this. The only process that gets added > >when SoundDiver is launched is: "SoundDiver.exe" and > >as I said, it will not die when I select it and click > >on 'End Process.' > I apologise. I was not trying to treat you like a buffoon. Really I wasn't. > It is impossible to know, though, what people know and do not know. My > computer knowledge is VERY limited indeed, and I simply suggested it in > case you had overlooked it. I am NOT an expert. > > ><rant>On a sidenote, I would just like to say that I > >would really love to stop nagging people and get this > >working so that I can actually make music instead of > >debugging software issues!!! The only music I've made > >recently has been with the demos to Sonar and Cubase > >SX because getting the patch names in is trivial > >(although not as cool as the AutoLink way since they > >can't be dynamically updated at runtime if I make a > >programming change to the synth).</rant> > > Feel free to rant whenever. > > Hope my above suggestion works for you. If not, I'll try to think of > something else. > I have to go earn my daily bread now, so any other messages you send might > have to keep for a while. > > Kool Musick > Keep Musick Kool > > > > > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Cheers man! Just deleting the .prf and removing the midi port info from win.ini was enough to kick start sound diver. Thanks for the insight :) Steve -----Original Message----- From : Kool Musick <koolmusick@...> To : sounddiver-users@yahoogroups.com Date : 27 September 2002 19:51:33 Subject : Re: [SoundDiver] More SoundDiver Fun! Steve writes: >>Hi all, I jut joined this group because I also am having troubles with SD >>and win XP. I installed the oem version that came with my access virus >>and then installed a patch for my model. When I fire up SD it attempts to >>do some form of scan for midi hardware, but this always hangs. I believe >>this can be fixed by setting the buffer to 1k, but I can't get into SD to >>change this setting because the scan always hangs!! >> >>*pulls hair out* >> >>Any thoughts? :) > >Delete the *.prf file from your SoundDiver folder. >Open up win.ini in sysedit. >Delete everything underneath [SoundDiver] (i.e. listings of MIDI ports) >If you also use Logic Audio, delete everything underneath [Logic] > >Try to load SoundDiver. It will probably hang. >Open up win.ini again. >Put a zero beside every single port you see, both MIDI ins and MIDI outs. >Now try to load SoundDiver. It should now load without trying to scan >anything at all because you have disabled all ports. Set the buffer. > >Reload SoundDiver to see it works OK. > >Exit. > >Re-edit win.ini and enable ONE PORT AT A TIME (both its in and its out) so >that you can scan and test the synth attached to that port. Focussing on >one device at a time will allow you to see whether you not have one >offending gadget in particular. > >Hope this helps. > >Good luck. > >Kool Musick >Keep Musick Kool > > > > > >>Cheers, >> >>Steve B >> >>-----Original Message----- >> From : Natalia Rakowski <goosefan@...> >>To : sounddiver-users@yahoogroups.com >>Date : 27 September 2002 14:46:13 >>Subject : Re: [SoundDiver] More SoundDiver Fun! >> >> >--- Michael Haydn <mhaydn@...> wrote: >> >> At 3:26 PM -0700 9/26/02, Natalia Rakowski wrote: >> >> >Finally, I had written to support@... >> >> about >> >> >my crashes and the person who wrote back claimed >> >> that >> >> >SoundDiver is known to not be XP-compliant! What's >> >> up >> >> >with that? >> >> >> >> He is right. SoundDiver is officially incompatible >> >> with Windows XP. >> >> -- >> >> >> >> Beste Gruesse - best regards, >> >> Michael Haydn >> > >> >So, is this why the AutoLink doesn't work? Or am I >> >doing something wrong in that regard...refer to my >> >original mail for what steps I was taking. >> > >> >Thank you... >> > >> >-- Natalia >> > >> > >> >__________________________________________________ >> >Do you Yahoo!? >> >New DSL Internet Access from SBC & Yahoo! >> >http://sbc.yahoo.com >> > >> > >> > >> >Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ >> > >> > >> > >> >> >>-- >>Personalised email by http://another.com >> >> >> >> >> >> >>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ > > > > >Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ > > > -- Personalised email by http://another.com

Is there a module or adaptation for the E-mu Command Stations, XL-7 or MP-7? Thanks, Ravi