Axe-Fx III Firmware Release Version 13.02

[DLC86]

I installed 13.02 with no problem, however, my presets suddenly have more gain than before...

Twin Vib is not supposed to break up with drive=5, right?

Check the global input gain if you're coming from FW13.00

 

[FractalAudio]

I found the problem.

 

[MrGuitarabuse]

I found the problem.

We never doubted this for one second

 

[Rock Chalk]

Will be interesting to see what it was, since only some were having issues.

 

[FractalAudio]

Will be interesting to see what it was, since only some were having issues.

The linker didn't zeroinit an array on the slave core. So in some cases there would be a NaN in there that was causing a NaN in the amp block. The linker does some strange things sometimes. I had to specifically initialize the array to zero (which you shouldn't need to do according to the C standard).

 

[Rock Chalk]

The linker didn't zeroinit an array on the slave core. So in some cases there would be a NaN in there that was causing a NaN in the amp block. The linker does some strange things sometimes. I had to specifically initialize the array to zero (which you shouldn't need to do according to the C standard).

Heh heh.....I’ll take your word for it!

 

[henryrobinett]

So far I' a lucky one. I haven't been running it hard, but I did reamp and track and have been lightly using the FC-12 with noproblems

 

[200man]

The linker didn't zeroinit an array on the slave core. So in some cases there would be a NaN in there that was causing a NaN in the amp block. The linker does some strange things sometimes. I had to specifically initialize the array to zero (which you shouldn't need to do according to the C standard).

So the linker command file had allocated the ram for the slave core.
And the slave core is accessible at the time the C init function is called.
If that’s true...that is a linker bug...
Initializing yourself is never a bad idea...

 

[aens]

Never seen a company CEO discuss code or bugs with their customers. One more reason to love Fractal Audio.

 

[andyp13]

The linker didn't zeroinit an array on the slave core. So in some cases there would be a NaN in there that was causing a NaN in the amp block. The linker does some strange things sometimes. I had to specifically initialize the array to zero (which you shouldn't need to do according to the C standard).

you’re just stating the obvious............

 

[Rock Chalk]

The linker didn't zeroinit an array on the slave core. So in some cases there would be a NaN in there that was causing a NaN in the amp block. The linker does some strange things sometimes. I had to specifically initialize the array to zero (which you shouldn't need to do according to the C standard).

And just for the record, that wasn’t near as interesting as I thought is was going to be!

 

[Piing]

Our Zero Hero deserves a break

 

[randyman]

Frankly, I would have thought it more likely to find a NIN in the amp block, but what do I know …

 

[rickster71]

Is a new version of 13.02 going to be posted soon? want to make sure there are no bugs before I up to 13.02

 

[FractalAudio]

So the linker command file had allocated the ram for the slave core.
And the slave core is accessible at the time the C init function is called.
If that’s true...that is a linker bug...
Initializing yourself is never a bad idea...

It is indeed a linker bug. It happened because the array overflowed from the declared section. The linker should initialize data regardless of whether it has overflowed or not.

I spent the morning making sure there were no other cases of this. Nasty little linker bug.

 

[kit dunborg]

Nasty little linker bug

Great band name!

 

[DaAxeMan]

It is indeed a linker bug. It happened because the array overflowed from the declared section. The linker should initialize data regardless of whether it has overflowed or not.

I spent the morning making sure there were no other cases of this. Nasty little linker bug.

Do we hold off installing?

 

[yek]

Do we hold off installing?

Currently there's nothing to install.

 

[Johnkenn]

The linker didn't zeroinit an array on the slave core. So in some cases there would be a NaN in there that was causing a NaN in the amp block. The linker does some strange things sometimes. I had to specifically initialize the array to zero (which you shouldn't need to do according to the C standard).

That was my first thought, too.

 

[Joe Bfstplk]

The linker didn't zeroinit an array on the slave core. So in some cases there would be a NaN in there that was causing a NaN in the amp block. The linker does some strange things sometimes. I had to specifically initialize the array to zero (which you shouldn't need to do according to the C standard).