Jump to content


Photo

Problem : Connecting Pod 2.0 With Usb2midi Cable

pod 2.0 connection edit usb midi cable

  • Please log in to reply
11 replies to this topic

#1 Vincent_042

Vincent_042

    Just Startin'

  • Members
  • Pip
  • 3 posts

Posted 04 January 2014 - 06:16 AM

Hello everybody,

 

For Xmas, i bought a new cable called USB to Midi (USB2MIDI) with 1 usb male, a small device (converting usb to midi) and 2 midi plug (IN and OUT)

 

like this one :

 

LogiLink Cable USB MIDI

http://www.amazon.fr.../dp/B000XRI3CC

 

and this cable works fine with some software like Reaper, Guitar Pro or MIDI-OX :

 

i can record commands from pod 2.0 with Reaper for instance, or send commands

BUT

i can't open Line 6 Edit to edit/save/import/export my own effects

 

 

1 - I can see other posts with same kind of problem : can't connect to line 6 Edit with LogiLink cable --> M-Audio recommended ok fine but i don't really want to buy another cable

 

2 - I have already tested my cable with MIDI-OX : seem to work fine : input & output are ok, with Reaper too : i can record when i change something on the pod, then, i can receive what i record previously

 

3 - My old computer with MIDI /GAME port and old midi cables (no USB) works fine with my POD 2.0, so the pod 2.0 is ok

 

4 - I have the latest version of Line 6 Edit & Java up to date too...  I have also tried some older version of Line 6 Edit just in case ...

 

 

 

5 - Help me please :-) i can see the talented people here !

 

6 - I'm french but i can understand English if it's simple :-)

 

 

 


  • 0

#2 Triryche

Triryche

    Uber Guru

  • Line 6 Expert
  • 5051 posts

Posted 08 January 2014 - 06:54 AM

I think you nailed it with number one on your list.

 

Unfortunately not all MIDI to USB cables are created equal.


  • 0

#3 Vincent_042

Vincent_042

    Just Startin'

  • Members
  • Pip
  • 3 posts

Posted 10 January 2014 - 11:28 AM

Are you sure ? what is different between those two cables ? My brother is pretty good in electronic and told me all this cable are the same : a simple converter and it's ok so no need to buy a brand ... you think it's not totally true, M-Audio would be 'more compatible' ?

 

 

 

i saw on this page 

http://line6.com/sup...udio#entry23159

 

that the last guy seems to have issues even with M-Audio device

 

 

Just see :

 

 

 

Ikar0s

Just Startin'

  • photo-thumb-1856119.jpg?_r=1385729463
  • Members
  • bullet_black.png
  • 2 posts
0 
Neutral
  • LocationCzech Republic

Posted 15 December 2013 - 09:19 AM

Hi again, I won a small battle. Now i try WIN xp and the FLASH memory was upgraded successfully, but the LINE 6 Monkey still doesn't recognize installed version. The probleme with LINE6 Edit still remains. it doesn't recognize my POD2.0.

Can somebody help me?

THX

 
 

  • 0

#4 Mr_Arkadin

Mr_Arkadin

    Guru

  • Line 6 Expert
  • 2610 posts

Posted 11 January 2014 - 04:53 AM

Regardless of someone else's issues, we're trying to fix your problem. Unless you try the suggested interface then it is impossible to rule it out. And yes, we are sure that not all interfaces are created equal.

I spent four months on another forum trying to help a guy get his SysEx working for his synth. The instant he tried a better MIDI interface as I had suggested in the first place it worked first time.

Sure, it may not fix your issue, but without eliminating it as the cause there is no way for us to move forward.
  • 1

#5 TheRealZap

TheRealZap

    Uber Guru

  • Line 6 Expert
  • 15481 posts
  • LocationClemmons, NC USA

Posted 11 January 2014 - 06:14 AM

the m-audio interface has more robust musician geared drivers...

most other midi interfaces use windows built in general drivers... 

that also is a pretty big difference, i do believe that the hardware itself is more reliable as well.

it is worth getting.


  • 1

#6 Vincent_042

Vincent_042

    Just Startin'

  • Members
  • Pip
  • 3 posts

Posted 11 January 2014 - 07:08 AM

Ok Ok, thanks for the help guys, no need to argue more, i'm convinced, but just a little bit annoyed to buy another cable :-/


  • 0

#7 mengel

mengel

    Just Startin'

  • Members
  • Pip
  • 2 posts

Posted 23 January 2014 - 02:24 AM

Try following:

   be sure that you connect midi out on cable with midi in on device

   if you have dialog boxes in the software be sure that you are choosing "usb midi cable" as a midi device you will use


  • 0

#8 marcin79w

marcin79w

    Just Startin'

  • Members
  • Pip
  • 7 posts

Posted 11 April 2014 - 11:30 AM

Hey! This problem again, but some solutions founded!

I've bought cheap MIDI<->USB

Using XP+SP3 newest Monkey and all the Line6 drivers.

 

Line6 Editor doesn't see POD 2.0

Monkey doesn't see POD 2.0

Midi Quest 11 doesn't see POD 2.0

 

BUT

 

I've found Podman 32 free software http://clients.teksa...tlee/podman.htm

and it see my POD 2.0 with no problem. I move pots in software - sound changes. I move pots in POD and pots on the screen moves along too.

Only problem - I can't save my preset using Podman32 software buttons, only pressing SAVE in my POD works... but still works, and each change may be added and saved :)

 

Interesting is - I do nothing with drivers, cables or other stuff. Just run Line6 Editor or Midi Quest11 and computer doesn't see POD2.0. Run Podman 32 after that and works well... POD2.0 magically appears. So far, I think cheap MIDI<->USB works well and this is a problem of software not device.


  • 0

#9 Mr_Arkadin

Mr_Arkadin

    Guru

  • Line 6 Expert
  • 2610 posts

Posted 15 April 2014 - 04:12 AM

Cheap cables are not recommended - you may just have a fluke. Another user posted this article he found on why cheap cables don't work well:

 

http://www.arvydas.c...ay-be-required/

 

Quite enlightening.


  • 1

#10 BillBee

BillBee

    Iknowathingortwo

  • Members
  • PipPip
  • 165 posts

Posted 15 April 2014 - 05:38 AM

Excellent post - explains the YMMV results those cables give.

 

Thanks!

B


  • 0

#11 PODMAN32

PODMAN32

    Just Startin'

  • Members
  • Pip
  • 1 posts

Posted 29 July 2014 - 09:37 PM

Hey! This problem again, but some solutions founded!

I've bought cheap MIDI<->USB

Using XP+SP3 newest Monkey and all the Line6 drivers.

 

Line6 Editor doesn't see POD 2.0

Monkey doesn't see POD 2.0

Midi Quest 11 doesn't see POD 2.0

 

BUT

 

I've found Podman 32 free software http://clients.teksa...tlee/podman.htm

and it see my POD 2.0 with no problem. I move pots in software - sound changes. I move pots in POD and pots on the screen moves along too.

Only problem - I can't save my preset using Podman32 software buttons, only pressing SAVE in my POD works... but still works, and each change may be added and saved :)

 

Interesting is - I do nothing with drivers, cables or other stuff. Just run Line6 Editor or Midi Quest11 and computer doesn't see POD2.0. Run Podman 32 after that and works well... POD2.0 magically appears. So far, I think cheap MIDI<->USB works well and this is a problem of software not device.

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


  • 0

#12 BillBee

BillBee

    Iknowathingortwo

  • Members
  • PipPip
  • 165 posts

Posted 30 July 2014 - 03:03 AM

Hi Chris!

 

Thanks for the information! I have noticed the same phenom on other midi devices using the cheaper cables (devices like R-Tron Chameleon, Voodu Valve, D-Tech 2101). The short messages get through but seem to time out on the longer ones (sysex dumps for ex.).

 

Excellent program btw I have used that one myself - still waiting for the XT version :)

 

-Bill


  • 0





Also tagged with one or more of these keywords: pod 2.0, connection, edit, usb, midi, cable

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users