Preamp Tube Type doesn't change in Axe-Edit when switching modeling 3.03 to 4.00 more little bugs

[LPaulasBestFriend]

Gear:
Mac OS Mavericks
Axe-Fx II Mark II with Firmware 4.00
Axe-Edit 3.8.1

All bug-informations refer to the amp-block!

1)
When I change the modeling version in the Axe-Edit,
the displayed Preamp Tube Type will not be refreshed.
The display of the Axe-Fx correctly shows the resetted Preamp Tube Type.

For instance, I change the Preamp Tube Type to EF86 and store the preset.
The modelingversion is Q3.xx.
Then I change the modelingversion in Axe-Edit to Latest.
Nothing more.
A look on the Axe-Fx display shows me, that the Preamp Tube Type
has changed back to 12AX7A, as Cliff described in an other thread.
But the value in the display of Axe-Edit is still EF86 and doesn't refresh!

2)
By the way, there is another little bug for a while in the editor.
To call up Edit Modifier for a parameter, I can mark a parameter (which has a controller symbol)
in the Axe-Edit and use the keyboard shortcut M.
That doesn't work with the parameter Saturation Switch!

3)
I mark the Balance parameter (value = 0.0, control wheel=mid position), call up the Edit Modifier,
set Source = Scene 1 and close the modifier window, the value in the editor display
of the Balance parameter is still 0.0!
But the control wheel has changed to minimum, as it is correct.
Same effect, when I additionally set a Controller to different values.
The control wheel changes the positions correctly, but the displayed values are still 0.0
and do not refresh.
Important:
The Axe-Fx display shows the same incorrect values and the same
correct control wheel positions!

4)
The same effect as described above, I have with other parameters.
I.e. Input Drive and Input Trim.
Also here:
The Axe-Fx display shows the same incorrect values and the same
correct control wheel positions!

That's for now.
Section 1 and 2 describe Axe-Edit-Only bugs.
Section 3 and 4 describe bugs in Axe-Edit as well as in the Axe-Fx (display).
I don't have posted 3 and 4 in the bug-section of the Axe-Fx!

Kindly regards!
Michael

 

[Michael Pickens]

Gear:
Mac OS Mavericks
Axe-Fx II Mark II with Firmware 4.00
Axe-Edit 3.8.1

All bug-informations refer to the amp-block!

Thanks for the bug reports. Bugs 1 and 2 are now fixed and will be in the next Axe-Edit release.

Bugs 3 and 4 are not really bugs but are as-designed. When a modifier is attached to a parameter, the parameter itself becomes read-only and displays the last value set (either by the user or its default). The modifier will cause the knob position to update but the value always remains unchanged. This allows the hardware to focus it's processing power on the constantly changing modified parameter's audio (especially when attached to an expression pedal) and not waste CPU cycles on updating the value. Hope this helps.

 

[LPaulasBestFriend]

Thanks for the bug reports. Bugs 1 and 2 are now fixed and will be in the next Axe-Edit release.

Bugs 3 and 4 are not really bugs but are as-designed. When a modifier is attached to a parameter, the parameter itself becomes read-only and displays the last value set (either by the user or its default). The modifier will cause the knob position to update but the value always remains unchanged. This allows the hardware to focus it's processing power on the constantly changing modified parameter's audio (especially when attached to an expression pedal) and not waste CPU cycles on updating the value. Hope this helps.

Hello Michael;

Thank you for your answer! ;-)

About my remarks 3 and 4 I'm a bit confused ;-)
I could swear, that I have seen the (modifier)changed values in the edit field ;-)
But it's OK; I trust in your clarification ;-)

Considering your argument, could it be a solution, to make a difference between modifying
parameters by a scene controller and the rest?
I think, you understand what I mean?
For instance;
When I use modifiers for switching/changing 1 parameter, there is no big effort to change an edit field
or two and his value/s.
When I use an expression pedal for constantly changing values, it makes sense to save pains, changing
displayed values every 100th second ;-)

Particularly, changing the knob positions will also waiste system ressources.
Changing the values instead of changing the knob positions of a parameter could be also a solution ;-)

It's just an idea to make the use of this function a bit more comfortable ;-)

By the way, the new modeling version is fucking great ;-)
It's a big step forward to make the details of the signal-decay more natural.
Especially in the lower frequencies.
You can see it also good in SPL and Distortion-diagrams, using a measure sweep.
Especially lead- and crunch-sounds are affected, as I have seen.
I hope, I describe the effect in an intelligible way ;-)

Thanks and kindly regards!
Mike