Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Serious Bug In Workbench And Jtv


Recommended Posts

I decided to open a topic because the problem of my workbench and my jtv appear serious

.I often have received this message when I try to make a WB Operating,  "failed to write data to the guitar" and the sound of that model I'm changing mutes ., and now I can not get sound to come back in all positions of TELE or strat, the workbench repeats this error message

 

Now, Several models are dumb and a strange writing on the workbench

 

I tried to reinstall the firmware 2.0 but also get the error message, (error midi opening ports)  I'm having serious problems, ,

 

The names of the models were all changed and are now all are with strange letters

 

after many attempts I managed to reinstall 2.0 and returned my previous bundle, but still keeps giving bug, reinstalled the workbench but also not fixed.

switched from pc to notebook and my wife also not resolved.

In the workbench, question marks appear over the pickpus

anyone imagine what might be happening?
I have attached some pictures.

 

Thanks

Link to comment
Share on other sites

strange is that our communications between pod hd and jtv is perfect, the problem is when I connect with pc

It could be a bad VDI cable... Are you using the cable that came with the Workbench interface or are you using the longer VDI cable?

Link to comment
Share on other sites

That cable does not have the protective housing at the ends that a VDI cable provides. Regular use of an unprotected cable like this usually results in damage to the connections on the Variax and/or the HD500.

 

Here is the VDI cable. Note the protective housing on the cable ends:

https://www.globalfulfillment.net/gfsnet/line6/10Expand.aspx?ProductCode=98-030-0004

 

It is very possible, if not likely, that you have damaged your ports.

Link to comment
Share on other sites

i have this original cable but it is also very thick and heavy, so I do not use.

 

the cable that I use I've attached a photo for you to see.

a question, if my cable not suitable it should not work, right? but as said before, communication jtv with the pod is perfect, the problem happens only in the workbench

Link to comment
Share on other sites

you do not think the problem may be with usb interface or usb cable?

That cable does not have the protective housing at the ends that a VDI cable provides. Regular use of an unprotected cable like this usually results in damage to the connections on the Variax and/or the HD500.

 

Here is the VDI cable. Note the protective housing on the cable ends:

https://www.globalfulfillment.net/gfsnet/line6/10Expand.aspx?ProductCode=98-030-0004

 

It is very possible, if not likely, that you have damaged your ports.

Link to comment
Share on other sites

The problem could be the interface or the USB cable, but I'd be more suspicious of the Cat5 cable... This is just me speculating, but I believe the data being sent from the Workbench interface when updating and using Workbench is essentially MIDI sysex data, or something very much like it. When you're using the Variax with a POD, the data is more like MIDI PC and CC commands. Sysex data is more like a data stream and the MIDI commands are more like bursts of data being repeated. Sending commands is more forgiving than sending sysex. So I think it's likely that a bad cable could show up when using Workbench and not with the POD.

Link to comment
Share on other sites

Yes - it may be a usb problem. It may also be your CAT5 cable. Since you have the original cable (at least protected on one end) why not test it? But remember - if this does not work that doesn't mean that it is a usb problem - it may be (and likely is) damage to the VDI connections/ports within one of the devices.

 

Long term you should definitely be usinga VDI cable protected at both ends.

Link to comment
Share on other sites

Long term you should definitely be usinga VDI cable protected at both ends.

 

 

Well, at least at the Variax end... The cable that comes with the JTV is only protected at one end.

Link to comment
Share on other sites

I have 2 cables vdi here and 2 are giving the same problem, now jtv is no sound, only one or another model is sounding, I'm very upset because I have a gig tomorrow and my guitar is muted. what is your suggestion Phill?

Link to comment
Share on other sites

the original cable that came in the jtv I have no more, but I bought this one

http://www.ebay.com/itm/Line-6-25-Variax-Digital-Interface-Cable-/331024477628?pt=Guitar_Accessories&hash=item4d1298adbc from the link, which is also original. the 2 cables give the same problem

 

I'm going crazy here, also already tested two usb cables, the only thing I do not have two is the usb interface.

Link to comment
Share on other sites

but it is possible to install the 2.0 with the pod?

 

 

Yes, it is... I actually would recommend using that people POD to do the update as standard operating procedure if they own one. It seems like a more robust connection to me. The only thing you can't use the POD for yet is connecting to Workbench HD.

Link to comment
Share on other sites

Should I reinstall the models button on or off?

Yes, it is... I actually would recommend using that people POD to do the update as standard operating procedure if they own one. It seems like a more robust connection to me. The only thing you can't use the POD for yet is connecting to Workbench HD.

Link to comment
Share on other sites

Should I reinstall the models button on or off?

 

 

I honestly don't think it matters that much when you do the update with a POD. You do need to make sure the volume knob is turned up. But as long as Monkey recognizes the guitar, you should be fine. I probably had the models turned on when I did mine. To be honest, I didn't pay attention to it when I updated. I just did what the Monkey told me to do.

Link to comment
Share on other sites

I succeeded in reinstalling the 2.0 trough the pod, sounds again , but when I open the workbench gives the same problems, strange letters, models muted, what you think I should do phil?

Yes, it is... I actually would recommend using that people POD to do the update as standard operating procedure if they own one. It seems like a more robust connection to me. The only thing you can't use the POD for yet is connecting to Workbench HD.

Link to comment
Share on other sites

Is Workbench doing this after you load your existing bundle? If so, I'd say the presets in that bundle may be corrupted. It is probably best to start from a clean slate and not try reloading those patches.

Link to comment
Share on other sites

Through the pod???? I though to use the workbench HD it's possible only with the small Hub...

 

 

The only way to use Workbench HD at the present time is to use the Workbench interface. To do the update, though, you can use any device with a VDI interface.

Link to comment
Share on other sites

I want to thank the attention of all, I did find out, as Phil had said, The cable I use should probably be broken inside, but to connect to jtv in pod it works but does not work for the workbench. I was just picking up another ethernet cable and connect and worked, the problem was actually the cable. Thanks

  • Upvote 1
Link to comment
Share on other sites

yes, I didnt know it was not possible to install the 2.0 connected through the pod, I thought it was only possible by USB interface, but Phill warned me that it was possible

 

Through the pod???? I though to use the workbench HD it's possible only with the small Hub...

  • Upvote 1
Link to comment
Share on other sites

With v2.0 i got the same error mssg as guilhordas, but I reinstalled and that went ok, but now my high E and B string are like half the volume of my other strings - across all models. But wait - I have most of my patches saved with the JTV model and the tone set from 50-70% (all models just sounded harsh to me at 100%). If I set the tone to 100%, the string volume discrepancy goes away, but now I'm back to harshville and when I roll the tone back down, no top strings. Arrgg! This was NOT the case w/v1.9. I played a number of gigs before the "update" and everything sounded fine. I tried re-installing 2.0 but no help. Does anyone know if rolling back to v1.9 will fix this? I'm afraid of the Line6 Monkey now.

Link to comment
Share on other sites

It is normal for the version 2.0, you can do manually the correction...

 

 

I don't know that I agree that it's normal... I've not altered the volume of the strings on my JTV69 since doing the update, and it sounds fine to me. I don't know why some people seem to have this issue and others don't. I suspect there could be differences in the levels of piezo between the models.

 

But, yes, altering the volume of the strings is easy to do in Workbench.

Link to comment
Share on other sites

Today something strange happened, I went to fix the cable that was giving trouble in the workbench, but it worked in the pod, and to my surprise the cable is not defective, I used a device that measures 8 wiring cable and all were working, then I wonder why this cable does not work correctly with the uSB interface and workbench? and the strange thing is that standard cable network from my interenet works

Link to comment
Share on other sites

Just FYI if anyone cares... a crossover cable simply has the transmit and receive pairs swapped (orange and green) in the network context....

far more dangerous in the "use for anything other than network" context... as certain pairs will carry the power....

(as determined by engineering/manufacturer)

so under no circumstances should a crossover cable be used in a non-networking context unless you know the pinouts (not public to my knowledge) and assume the risk.

 

Some Ethernet cables are called 'crossover' cables. These do not work with the Line 6 products. You may have one of these; if so you need to use a standard (non-crossover) cable.

Link to comment
Share on other sites

the problem happened again, I'm going crazy, I already changed the pc, swapped cables, reinstalled the firmware, but I'm having the same problems again

 

 

Sounds like the only thing you haven't changed is the interface. It could be the port on the interface is damaged. Or it could be the port on the guitar itself.

Link to comment
Share on other sites

This really sounds like the USB port cannot supply enough current to run the interface reliably.  I know that the Line6 documentation says not to use a USB hub, but a powered USB hub (with wall wart) can likely supply more current than the computer.  If you have one or can borrow one, it may be worth a try.

Link to comment
Share on other sites

the line 6 might think the problem may be with the usb interface or with my jtv, but the interface seems to work well, turn lights properly, the workbench always recognize the JTV through it,

can you post a links of this product? thanks

Link to comment
Share on other sites

the line 6 might think the problem may be with the usb interface or with my jtv, but the interface seems to work well, turn lights properly, the workbench always recognize the JTV through it,

can you post a links of this product? thanks

 

Well, obviously it is not working correctly if your attempts to stream data to the instrument are terminating with errors.  Small voltage drops that are enough to cause digital circuit misbehavior might not be obvious from watching LEDs.  You would have to put a scope on the +5V line at the interface to have a chance at seeing it directly.

 

There are hundreds of powered USB hubs available.  Google is your friend ("powered usb hub" might be a reasonable search term).  Anything with an external supply and USB 2.0 compatibility is a good bet.  But please keep in mind that I am only throwing that idea out because I've had similar problems when, e.g. copying files to my Tascam guitar trainer.  The unit is always recognized and mounted by my computer, but if plugged into a rear-panel USB port it disconnects part way through any file transfer.  If I connect to my little powered hub, it works perfectly.  Other things to do (if you haven't already):

 

- Swap USB cable

- Check computer and Line6 interface box for bent or visibly tarnished pins (strong light and magnifying glass are helpful)

- Try a quick shot of non-residue electronics cleaner in the computer and interface box, then work cable in and out about a dozen times.  Do NOT use anything with lubricant in it (aka "tuner cleaner") or you'll definitely regret it. 

 

- Check your computer setup for the presence of any non-Line6 device driver that may be trying to listen to the USB ports.

 

(My money is on the current capacity issue)

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...