PODMAN32

Hi, I know this post is rather old, but I just noticed it. I am the programmer who wrote the Podman 32 software and I thought I would comment on your problem. This issue you are having with your midi interface seems to be that it is having trouble working with MIDI sysex commands (or in Windows MIDI terms, long midi messages). When programming with MIDI devices on Windows there are two different kinds of MIDI messages that can be sent between MIDI devices. Short midi messages and long midi messages. Short midi messages include commands to play notes, control change messages, program (or patch) change messages etc. These are the type of midi messages that are sent when you turn the pots on the POD such as turning up the drive on the POD etc. These seem to be working fine with your midi cable as you mentioned that using my Podman 32 software and turning the pots on the Pod causes the sliders to move on screen. Long midi messages however, are used when you need to send more complex information between devices and is used to send sysex messages (which is short for system exclusive messages). Just like it sounds, these messages are exclusive to a particular device. In other words, the POD's sysex messages are exclusive to the POD and are only understood by a Line 6 POD or software written to interface with a POD like Line 6 Edit or my Podman 32 software. These are more complex messages to send and receive via MIDI and can be different lengths. The POD uses sysex commands to send and receive entire patches between the POD and the computer. My Podman 32 program uses the sysex commands when you save a preset to the POD from the program. Since you said that part isn't working, that is what leaves me to believe that your midi interface is having issues with sysex commands or long midi messages. Also, Line 6 Edit and other programs use sysex commands to identify the POD. You say that Line 6 Edit doesn't see the POD. Since Line 6 Edit works with multiple Line 6 products, it has to identify which product it is hooked up to. HOw it does that is that it sends out sysex commands that ask connected devices to identify themselves. The POD would then respond with another sysex command back to the computer with a sysex message that contains information identifying itself so that Line 6 Edit knows which Line 6 product is connected (ie. POD 2.0 or POD XT, or Bass POD etc.) If either the message sent from Line 6 Edit doesn't get to the POD correctly, or, the response back from the POD doesn't get through, then Line 6 Edit doesn't detect the POD. My program doesn't have a problem since it is only designed to work with one Line 6 product, POD 2.0 and doesn't do any auto detecting of the device using sysex commands. It just assumes that you have a POD 2.0 hooked up and goes from there. Basically, your midi interface isn't working properly. It seems to be only working with regular short midi messages, but not long midi messages used for sysex commands. I am not a hardware expert, but I would tend to think it is driver issues. I would suggest trying to find new drivers or look for another midi interface. Myself, I am using the M-audio uno usb with just the built-in default Windows drivers and it works fine on several computers that I have tried. I hope this is helpful. Christopher