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

Serious Bug In Workbench And Jtv


Recommended Posts

THE ONLY THING NOT TRIED YET, BECAUSE I DO NOT OWN, IS ANOTHER USB INTERFACE, I ALREADY CHANGED CABLES COMPUTER. A WEEK AGO I USED MY ETHERNET CABLE INTERNET AND WORKED PERFECTLY, SO I concluded that SHOULD BE TROUBLE CABLE, BUT TODAY WAS TESTED WITH CABLE AND EVEN HAD THE SAME OLD PROBLEMS

Link to comment
Share on other sites

I changed the usb cable and ethernet cable for new and nothing, the problem remains, the strange thing is that I do not have any problem to reinstall 2.0 through the pod, I just have a problem when I use the workbench through the usb interface

Link to comment
Share on other sites

  • 1 month later...

I have the same problem and line6 support seems to have no idea about this issue. Too bad because I really can't be sure if I have to return USB interface only or the guitar too. And it is really a problem, since the dealer is located 2000km away (how about $200 for a return shipping?)!

Why do I think it is interface or guitar problem? I tried:

1. Swapping USB cables

2. Swapping Cat5 cables

3. Swapping PC (another OS version, another usb port)

4. Using powered USB hub (bad idea, snhirsch, really - it made strings and cable jack energized)

5. Reflashing many times

6. Using POD HD500 as an USB interface

 

And after 5 and 6 I still have questions. There were a couple of times when I've managed to upload changes to the guitar (fw 1.9) via USB interface, but most of the time it failed. There was an error while I was trying to upload a change for the first time via HD500, but then it worked. I actually not quite sure about how well does it work with a HD500 compared to an USB interface, because my testing with the HD500 was rather brief (in a store), and it still worked some times with the supplied USB interface. Anyway no testing I was able to make with another USB interface and fw 2.0, that leaves me in doubt about actual problem cause.

Link to comment
Share on other sites

  • 2 weeks later...

I've seen a lot of the same issues you have. Tried to update multiple times and kept getting that same connection error. It finally worked, but now my presents change randomly. I can't rollback to a different version either because of the connection errors. I'm going to have to send the thing back to Line6 and I just got it yesterday. Should I even keep this guitar? It kind of seems like more trouble than it's worth.

Link to comment
Share on other sites

its just a matter of what you are calling it...

it *IS* a seriously annoying limitation...

 

so really we're not disagreeing with your sentiment... we are only clarifying the nature of your complaint.

 

 

 

 
many people are having serious problems, but the experts say that this is not bug, so I'm not understanding anything

 

Link to comment
Share on other sites

its just a matter of what you are calling it...

it *IS* a seriously annoying limitation...

 

so really we're not disagreeing with your sentiment... we are only clarifying the nature of your complaint.

 

It's ridiculous to call hardware defect in a lot of usb interfaces a limitation. Especially for an "expert".

Again: I've got mine replaced and it works well now.

Link to comment
Share on other sites

Yeah that would have been ridiculous... if that's even remotely what i said...

i said the inability to use a pod as a means of accessing workbench was the limitation...

nothing to do with broken interfaces...

okay cowboy... ease up.

 

It's ridiculous to call hardware defect in a lot of usb interfaces a limitation. Especially for an "expert".

Again: I've got mine replaced and it works well now.

Link to comment
Share on other sites

Yeah that would have been ridiculous... if that's even remotely what i said...

i said the inability to use a pod as a means of accessing workbench was the limitation...

nothing to do with broken interfaces...

okay cowboy... ease up.

 

This limitation has exposed a show stopper defect. That's why the situation in overall is not just a limitation. (but I'm sorry for being too harsh)

Link to comment
Share on other sites

you're drawing a whole lot of conclusion from your own personal experience...

myself and many others have perfectly working interfaces...

sorry that obviously wasn't the case for you...

not much showstopper IMO, since i could update with the pod and never touch workbench, and still been very happy with the quality of v2.0

 

if you have no pod and only a broken interface... then yes it was a showstopper.

but i'd not say that affected the majority of users.

 

This limitation has exposed a show stopper defect. That's why the situation in overall is not just a limitation. (but I'm sorry for being too harsh)

Link to comment
Share on other sites

you're drawing a whole lot of conclusion from your own personal experience...

myself and many others have perfectly working interfaces...

sorry that obviously wasn't the case for you...

not much showstopper IMO, since i could update with the pod and never touch workbench, and still been very happy with the quality of v2.0

 

if you have no pod and only a broken interface... then yes it was a showstopper.

but i'd not say that affected the majority of users.

 

Those broken interfaces do an update. But after update you can't edit a patch neither via interface (broken) nor via pod (here comes that 2.0 limitation). And an existence of this, maybe not widespread, problem must be admitted.

Link to comment
Share on other sites

Perhaps I've missed something but as I understand it, Krom_, you had a fautly usb interface - a hardware problem that you said you have resolved. That certainly was a problem for you, though it's not widespread as far as I know. I'm not sure that's a problem that 'must be admitted'.

 

Is there another problem you are having now that points to something serious?

Link to comment
Share on other sites

the broken interface apparently does not correctly apply the update... because if it did workbench HD would work through the interface.

the other limitation has already been admitted....

and you could have applied the update via pod... just not use workbench.

anyway....  no sense in arguing... the pod limitation will eventually be addressed and your interface has already been addressed from the sounds of it.

 

Those broken interfaces do an update. But after update you can't edit a patch neither via interface (broken) nor via pod (here comes that 2.0 limitation). And an existence of this, maybe not widespread, problem must be admitted.

Link to comment
Share on other sites

I really can't understand what are you arguing about.

There are several posts about problems caused by usb interfaces. This cause is not obvious: it might be a guitar electronics or a software problem (and this tread is an example of such confusion).

I solved mine and I'm sure that there must be clear conlusion: if one have problems after switching to 2.0 (and so, being unable to use a pod instead of an interface), it is likely an interface problem.

People coming to the forum with a problem are not for reading coneptual chats about limitations, but for a help.

Link to comment
Share on other sites

ok... but the basis of the thread is not about the usb interfaces... and a bad interface is not a bug... its a bad interface.

you're the one arguing...

i'm giving you facts.

 

I really can't understand what are you arguing about.

There are several posts about problems caused by usb interfaces. This cause is not obvious: it might be a guitar electronics or a software problem (and this tread is an example of such confusion).

I solved mine and I'm sure that there must be clear conlusion: if one have problems after switching to 2.0 (and so, being unable to use a pod instead of an interface), it is likely an interface problem.

People coming to the forum with a problem are not for reading coneptual chats about limitations, but for a help.

Link to comment
Share on other sites

ok... but the basis of the thread is not about the usb interfaces... and a bad interface is not a bug... its a bad interface.

you're the one arguing...

i'm giving you facts.

The basis of the thread is about the problem, caused by the usb interface - of course it isn't a workbench bug. And *this* is the main fact and the conclusion of the thread :)

Link to comment
Share on other sites

This thread was resolved and marked answered long ago.

 

if you have a bad interface contact support.

http://line6.com/support/tickets/

 

The basis of the thread is about the problem, caused by the usb interface - of course it isn't a workbench bug. And *this* is the main fact and the conclusion of the thread :)

  • Downvote 1
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...