Issues saving C3 parameter HX3_firmw_3841

[clp560]

Hi Ramon,

I also had this vib issue on changing to #3841, though not the audio or rev. Setting C3 as organ default in the Editor and saving this didn't help. For the moment, because of a problem with my USB interface on the HX3, I can't check this again - I'm on FW#383/FPGA05072015 currently and I have to say I prefer the sound/chor-vib of this setup through my gear (v#383 also has the new taper files which are a big improvement). When I get a new interface I'm going to have another look at v3841.

Maybe some others had the same vib reset issue? It wasn't a big deal on my XK-3 setup as one twist of the knob put it back on C3 until the next restart. Still, it didn't happen on the older FW.

Paul

[odd meter]

Have no Expander near me to recheck, but also faced some troubles while saving Chorus and Percussion values on 3.841.

[Valpurgis]

Sorry: My fault, no problems any longer. Problem was probably due to the Voce Drawbar unit itself. During test I unpowered the expander but not the Voce. When testing today the activation of V/C is fine! So please ignore the following description:

Mine problem after upgrading the expander to 3.841

Using Voce Drawbar to control the expander it is no longer possible to activate the V/C. When using the Voce V/C selector I see the display scrolls between C1, V1, C2 etc. But problem is that the expander does only respond to pushing the V/C on/off button by showing V/C off. Shortly said, it is not possible to activate the V/C from the Voce any longer. This worked in previous firmware.

[PortlandMike]

I had the same issue with C/V settings not saving in 3,84. I love the sound of the new C/V, but am waiting for bugs and tapering files to be worked out before upgrading from 3,83.

[clp560]

I've finally been able to reinstall FW#3841/FPGA16102015 and the C/V is definitely reverting to V1 on restart. Reverb, Audio Out selection and everything else is remembered ok so it's not a big deal, though I'm sure this can be fixed in a future update.

Paul

[bovist]

The Vibknob issue was solved with firmware 3.842. The bug did not appear on Expander modules.