I have also found out that rolling back to v1.9 fw on the JTV fixes this popping issue with the HD500 patch change that also forces a JTV model change. It is something introduced with v2.0 fw of JTV. I am about to raise a support ticket now.
Jtv59 To Hd500 Vdi Getting A Pop When I Change Patchs That Also Change Variax Model
Posted 16 April 2014 - 12:05 AM
Line 6 have acknowledged receipt of the audio file demonstrating the issue and have forwarded it to engineering for review. The representative looking after my ticket has still been unable to reproduce the problem with a JTV at Line 6. He has suggested that I double check that it is not a gain issue swapping from a low volume patch to a high volume and vice versa and to ensure all my patches are levelled volume wise and he has also suggested that perhaps it could be a latency issue and to try a different Cat5e cable for the VDI connection. My patches are fairly even regarding volume and I have tried two different VDI cables and the Cat5e cables that come with the JTV and still get the problem, however, those suggestions may help someone else.
I will let you know when I get a further update with news from engineering.
Posted 18 April 2014 - 11:09 AM
I know that this problem started happening when I moved to fw 2.0, I know I get the problem even when I mute the strings between patch changes, I know the problem goes away or diminishes significantly when you go back to fw 1.9, I also know that I am not the only one that has had this problem and surely everyone who has reported it can't have just happened to have changed their playing style and forced the issue. Furthermore, if it was as simple as attacking the note and pressing the footswitch then surely anyone can recreate it - yet my Line 6 support rep said he cannot recreate it.
And how do they explain that the problem only happens when HD500 patch forces a model change on the JTV and goes away if you set HD500 patches to DONT FORCE or if you use a standard guitar? Surely if it was playing style it would occur all the time.
I have pointed all these issues out and have asked that they look at it again - and I have asked what the engineers say about the problem - but if anyone else would like to chime in and raise a support ticket to add substance to the case for fixing this bug then I would greatly appreciate your help.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users