Drive1 - bypass mode changed + hidden in Axe Edit +

1

1vl

Member
My current problem is that the bypass mode of Drive 1 changed automatically in some presets + it is not displayed in Axe Edit in these presets. The mode can be changed at the Device display or in Axe Edit by clicking blind... The space is simply empty, no "through" or "mute" is displayed. It remained that way even after deleting the Drive block and deleting and re-importing the preset and reinstalling and refreshing everything Axe-Edit + RANF.

Fw. is 28.02, Axe Edit 1.14.12., a preset with Drive 1 with missing bypass mode info is attached.

The problem has a history, and I have more information about it:

It started with a strange behavior after updating to fw 28.02 - "System hangs + shifted Drive Types memory locations"
https://forum.fractalaudio.com/threads/axe-fx-iii-firmware-28-02-release.211806/post-2653949:

But not only firmware changed:
The Axe iii is connected via AES to an RME Fireface, which also provided the clock. For unknown reasons, it set itself to 44.1 kHz around the time the first problems occurred. The immediate effects, that I noticed were the Axe Tuner and Pitch effects working slightly out of tune. But these were resolved immediately after resetting to 48 kHz.

Now I'm totally unshure, what exactly happened here. My first step was to have Axe generate the clock. However, I'd like to understand, what happened, how maybe I contributed to that and of course make sure that settings, presets, and functions work as set.

Is this firmware-related, or could an incorrect clock sample rate cause all these problems with blocks, loss of system setting,...? And how can this be resolved?
Please excuse the confusion, there were just to much things going on at once...
And thanky you for looking into this
 

Attachments

Thank you for classifying the problem!
I've since discovered that the error doesn't occur if I reinstall an older backup of the preset I created under 27.03 and the previous version of Axe Edit. Maybe this will help narrow down the problem.
 
  • Like
Reactions: Rex
1vl said:
Thank you for classifying the problem!
I've since discovered that the error doesn't occur if I reinstall an older backup of the preset I created under 27.03 and the previous version of Axe Edit. Maybe this will help narrow down the problem.
Click to expand...
The attached preset appears to have corrupted data in the Drive 1 block that is preventing valid communication with the editor.

You stated that the error does not occur when reinstalling the backup of the preset. The problem should not return using this restored version of the preset in firmware 28.02 and the latest editor.
 
Michael Pickens said:
The attached preset appears to have corrupted data in the Drive 1 block that is preventing valid communication with the editor.

You stated that the error does not occur when reinstalling the backup of the preset. The problem should not return using this restored version of the preset in firmware 28.02 and the latest editor.
Click to expand...
Thanks for the insight + your work, Michael!
If I understand you correctly, the error appears in the editor, but the problem lies in the preset. And you are right: The preset backup form fw27 worked in fw28.2, but there are to many presets affected, I restored the whole backup.

Now I'm wondering how that happend.

After installing fw28.02, my drive modes list was faulty:
https://forum.fractalaudio.com/attachments/drives_fw28_02-png.152551/
My layman's guess is that the presets couldn't find a suitable drive block when called up and "got confused".

But how do the drives get mixed up in the first place?
No one has reported this problem yet. Could it be that it's not the firmware, could it even be that my audio interface caused this?
It served as a clock, is connected via AES and switched out of the blue to 44.1 kHz.
The Axe worked, I became aware of the problem through the following signs:
The tuner and pitch effects reacted differently (shifted); could this also affect more processes inside the axe (like maybe memory usage or the "clock speed"?) so it "gets confused"?

I know this may be a bit of a layman's idea, but I wanted to give you all the information and I would really apprechiate to hear what you think about the causes. (If I and others can avoid a potentially self-inflicted error, that would be a win.)
 
You must log in or register to reply here.
Back
Top Bottom