Search the Community
Showing results for tags 'hd500 dt25 bright volume'.
Found 1 result
I already posted this in the HD500 forum but did not get much response, so I am reposting here just in case there are some DT25 users on this forum who have experienced same issue. I have a JTV59, and HD500 and a DT25. The HD500 and DT25 are on latest levels of flash and drivers and the JTV is still back on 1.71. I connect the JTV via VDI to HD500 and the HD500 via L6 Link to DT25. Other than sometimes not getting any sound of the DT25, which is cured by switching everything off and then back on, I have not had any issues until now, just after I updated the HD500 to the latest level of drivers for the HD500X support, which I didn't need but I like to keep the software up to the latest levels. Now, when I switch from a patch with an AC15 PRE to a PLEXI LEAD 100 NRM PRE, most times I get a very bright sound, almost like it has switched to the PLEXI LEAD 100 BRT PRE on steroids, and when I press the FS again it returns to the expected warm PLEXI LEAD 100 NRM PRE sound. Sometimes it will work correctly first time, but most times I have to press the FS twice because first push results in this bright sound and apparently louder volume and second push gives me the expected saved patch sound. I thought at first it was something to do with FS8 which is where the PLEXI LEAD patch is assigned, but I tried moving it to FS5 in a different bank, and it still did the super bright sound on first switch when swapping from an AC15 PRE patch, and then a second press resulted in normal sound. I have tried reinstalling the drivers and reinstalling the flash memory, resetting global parameters, and also reloading the SET LIST patches from my PC backup. But the problem remains. I have also reproduced it using the AC30 TB PRE, and have reproduced it going to PHD PRE, JT45 NRM PRE, and BF LUX VIB PRE. Weird. It is almost as if some component on the DT25 has either switched in or forgotten to switch off for the patch change, but on a second request it gets it right. I have raised a support ticket with Line6 but thought I would see if anyone else experienced this or had a similar problem? Thanks.