Pages: [1]   Go Down
  Print  
Author Topic: Anyone tried XGPad and SW1000XG?  (Read 2223 times)
0 Members and 1 Guest are viewing this topic.
Locutus
Senior Member
*
Offline Offline

Posts: 133



View Profile WWW
« on: February 07, 2007, 08:51:19 AM »

Hello everyone,

I just got myself an SW1000XG from eBay and I am now trying to get a decent editor for SYSEX parameters and such. I stumbled over XGPad, which is now free thanks to its generous author.

On the page, it says that Windows XP is supported, however when I start the tool it asks me to "choose MIDI in and out devices" and after that message it immediately throws a "runtime error 57" at me. Seems to be done in Visual Basic, that thing.

Did anyone here make the same experience?

Thanks!
Logged

Juho Sippola
Senior Member
*
Offline Offline

Posts: 294


View Profile WWW
« Reply #1 on: February 07, 2007, 09:54:58 AM »

I've used XGPad with my MU50 and UM-2EX MIDI interface in Windows XP. I haven't had any prohibitive problems with the software apart from few random crashes. You might want to try the software on another computer to see whether your issue is computer setup specific.
Logged
BlueMax
Senior Member
*
Offline Offline

Posts: 916



View Profile WWW
« Reply #2 on: February 07, 2007, 04:08:20 PM »

Cool card - what'd it cost you?
Logged

AAAAAAAAUUGHH!!!! - Charlie Brown
Locutus
Senior Member
*
Offline Offline

Posts: 133



View Profile WWW
« Reply #3 on: February 07, 2007, 04:37:26 PM »

About 130 USD
Logged

Cloudschatze
Moderator
Senior Member
*
Offline Offline

Posts: 1,895



View Profile
« Reply #4 on: February 10, 2007, 04:42:54 PM »

Yamaha's XGworks v3.0 sequencing package has a fairly nice XG editor, not to mention some additional features that would complement your SW1000XG quite nicely. The program has been discontinued for several years, though it may pop up from time-to-time. Wink
« Last Edit: February 10, 2007, 04:55:19 PM by Cloudschatze » Logged
Locutus
Senior Member
*
Offline Offline

Posts: 133



View Profile WWW
« Reply #5 on: February 11, 2007, 12:37:06 AM »

Thanks for the info.

I also came accross "XG Wizard" (seems to work well) and XGEdit95, which has been very popular, I guess. As of now, I am quite happy with these.
Logged

Locutus
Senior Member
*
Offline Offline

Posts: 133



View Profile WWW
« Reply #6 on: February 11, 2007, 10:59:54 PM »

Eventually, I solved the problem and I thought, I'd let you all know how I did it:

The procedure might be suitable for getting rid of "dead" MIDI outs or remains from old drivers, that didn't uninstall completely. But it might also trash your Windows, who knows, so don't do this at home:

I figured, there must be something wrong with the Windows registry and MIDI outs. So I searched for some keywords and found the following registry keys that have something to do with MIDI outs and mapping:

(HKLM = HKEY_LOCAL_MACHINE)

HKLM\Software\Microsoft\Windows NT\CurrentVersion\Drivers32

This part seems to correspond to the win.ini of Windows 3.x where all the MIDI devices (e.g. MIDI1 to MIDI9) are assigned to specific drivers. Anyway, there were 9 MIDI devices assigned to "wdmaud.drv", so there seemed to be something wrong. (I compared the folder to that one on a working setup on another computer and decided to delete everything in it. :-)

HKLM\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Midi

I deleted everything here too.

HKLM\System\CurrentControlSet\Control\Class\00[XX]

This folder seems to identify device drivers of the soundcard... I deleted those that looked like they have something to do with MIDI devices.

Then I reinstalled every device driver (soundcard, virtual devices, like softsynths (Yamaha S-YXG 50) etc.) that would install MIDI devices that show themselves in the MIDI mapper.

Since then, XGPad comes up with the dialog where I can choose MIDI devices and it seems to work fine. Runtime error 57 has gone away.

Thanks again for trying to help me.
Logged

Pages: [1]   Go Up
  Print  
 
Jump to: