Axe-Fx III Firmware 31.02 Release

Status
Not open for further replies.
Possum said:
Just tried your preset @kit dunborg and it sounds fine on my end. I can clearly hear the distortion happening on the posted samples here, though. Just to confirm so I didn't get anything wrong: You guys roll down the tone knob on the guitar? Tried it with disabled cab and poweramp sim, tone know down, multiple reboots - can't make that little gremlin show up. :D

I'm in a mood for a christmas bug hunt now...
Click to expand...
Hi,
yeah, that's how the distorted down was best audible - tone know rolled all the way down. Apparently, according to Cliff, sometimes the bug shows up, sometimes it doesn't so I figure you are one of the lucky ones :)

Enjoy the holidays everybody!

EDIT: Cliff beat me to it! :)
 
Last edited:
Possum said:
Just tried your preset @kit dunborg and it sounds fine on my end. I can clearly hear the distortion happening on the posted samples here, though. Just to confirm so I didn't get anything wrong: You guys roll down the tone knob on the guitar? Tried it with disabled cab and poweramp sim, tone know down, multiple reboots - can't make that little gremlin show up. :D

I'm in a mood for a christmas bug hunt now...
Click to expand...
I could only hear it, (even with guitar tone roll off), by placing a PEQ block before output and isolating / soloing a band around 7K, which makes it very audible for me. If not pointed out, my old faulty ears would not have noticed.
 
FractalAudio said:
It's random. It's been fixed for the next release.
Click to expand...

If you’re able to explain to a coding philistine without divulging too much, I’d love to know how or why it’s random.

Is the code dynamic (is that even a thing?) or something?

Just curious and want to learn more is all.
 
FractalAudio said:
It's random. It's been fixed for the next release.
Click to expand...
Tube amp perfection achieved!!! Sometimes tube amps sound amazing and are inspiring to play but other times with the exact same equipment it's a struggle and fight to get the same sound. My ears? temperature? humidity? phase of the moon? but there's definitely some randomness in there also
:)
 
biggness said:
If you’re able to explain to a coding philistine without divulging too much, I’d love to know how or why it’s random.

Is the code dynamic (is that even a thing?) or something?

Just curious and want to learn more is all.
Click to expand...
Could be almost anything causing a behavior like this - I’ve been developing control software for computed tomography for over a decade and spent more time hunting weird bugs than writing code :rolleyes: but would be interesting as well. I’m not familiar with spice and I have no clue how the axe modeling is done/how similar its engine is to spice, but my guess is it’s related to some some objects state variables not being initialized properly when booting the axe and thus randomly causing the distortion. Impossible to tell…
 
unix-guy said:
Given that he was responding to someone else saying the couldn't reproduce, I don't think that's what he was saying...
Click to expand...

fair enough.. but the question I have and I'm confident you'll know the answer:

were clean amp distortion issues happening with Beta FW 31.01 v2? I'm thinking it was not..

so that thought led me to think the "random" reference Cliff made sounded less to do with code and more to with some goofy error during the transition to a new official FW release.. and he's got the fix already done.
 
  • Like
Reactions: hmj
Possum said:
Could be almost anything causing a behavior like this - I’ve been developing control software for computed tomography for over a decade and spent more time hunting weird bugs than writing code :rolleyes: but would be interesting as well. I’m not familiar with spice and I have no clue how the axe modeling is done/how similar its engine is to spice, but my guess is it’s related to some some objects state variables not being initialized properly when booting the axe and thus randomly causing the distortion. Impossible to tell…
Click to expand...
Yeah, I can literally only imagine (incorrectly) to what it would be lol
 
My name is mud said:
Congratulations, you match the clean tone of the Marshall MS2 ! (Reminds me this immediately)

Yeah you have that sort of permanent « vinyl simulator « in your sample. I clearly hear it here even in my phone . The type of tone you have when the signal is too hot, or when you play direct through a mixer . Or In a Marshall ms2 with humbuckers 🙉
Click to expand...
I could hear it clearly on my
Phone, too


Personally, I’m a few firmwares back because when the pitch block was reworked the virtual capo gives me artifacts that I don’t get on the version before that. Since my set leans heavily on the virtual capo I had to stay back.
 
Been trying out 31.02 on the axe. Anyone else run into a issue with the USB audio in stopping after 5 to 10 min's? The only way I have been able to get it going again is to reboot the Axe. I first noticed it when recording using Studio One with Axe as the interface. The output seems to work fine as I still get signal to studio one after the input stops working. With studio one and all other USB devices removed it does the same thing when playing a .mp3 as a test (stops after 5 to 10 mins). Just to be clear, this is the USB audio coming from the PC into the AxeFX.

  • Windows 10
  • AxeFX - FW-31.02
  • AxeEdit- 1.14.25
  • AxeFXUSB - 1.17
  • Device Driver: 5.74.0.20373
 
Last edited:
Status
Not open for further replies.
Back
Top Bottom