XEdit Bug Report: Delay's Ducking Threshold
I have noticed that the THRESHOLD dial on the DELAY section of XEDIT (Effects Tab) does not get set properly when you pull up a patch. It resets to 0... even if you set it, save, exit, and come back - it resets.
It happens repeatably on my system. Can anyone else check it out and confirm/deny?
Hopefully the Digitech software guys pop in and read this! 8)
It happens repeatably on my system. Can anyone else check it out and confirm/deny?
Hopefully the Digitech software guys pop in and read this! 8)
Comments
It would be most beneficial if you reported directly to tech support. They foward the problem to the corresponding engineer.
http://www.digitech.com/software/GNX4/GNX4ReleaseNotesv13.pdf
Is it on any type of delay? And which version of X-Edit are you using?
So the sequence is
1. Bring up patch from file system and/or GNX
2. Change the THRESHOLD value
3. Save the patch under file system and/or GNX.
4. Bring up patch from file system and/or GNX again
5. THRESHOLD is 0.
Is that right? specifically is the patch saved to the file system or the actual GNX? or both?
v1.3 of Xedit
Saved both to disk and to device. I can double check if the behavior happens when opening both. I believe I noticed it first when opening .g3kp files from disk.
You have the process to repeat the problem in the right order.
Also NOTE: XEdit will crash intermittantly with no specific errors. I have Visual Studio 2003 on the same box (I am a developer), but I doubt that should matter. I cannot seem to duplicate the error on demand. It appears to happen when I am opening/closing patches to/from disk.
I suspect a memory leak or something... (?)
I'm at work so I can't go do anything right now... :?
Ever since I installed Visual Studio as well, one of my laptops is unstable, and slow... ha ha... It think it definetely makes a difference..
Hrm...
Exactly my toughts, but now MATLAB gives me exceptions and errors on that laptop.
Maybe it installs extensions to the .NET framework. Who knows.
In any case, I'll try to replicate the problem once I get home...