Axe-Fx III Firmware 27.00 Public Beta #8

Status
Not open for further replies.
Cortlan GK said:
I have a question: do the new amplifier modeling algorithms also include the USA MK IIC++ amplifier, which, as we know, was adapted for Metallica? Or maybe the new algorithm bypassed this amplifier so as not to change its current sound?
Click to expand...
I may be wrong but my ears say yes. My 2 Tallica live presets (one that blends dizzy v4 blue ch.3 and the mk2c++, and one that is identical but uses the dizzy v4 silver ch.3, have never sounded livelier and spot on as they do right now.
 
Possibly a bug:

1. Put a multitap delay block (all settings at default) after a bypassed block.
2. Set its envelope follower from OFF to -99.9 dB -> FX output is silenced completely, independent of block input level.
3. Unbypass the block in front -> multitap delay block might output some FX signal again, but I doubt it works truthfully to the -99.9 db setting.
4. Bypass the block in front again -> multitap delay may or may not keep on putting out an FX signal.
5. Switching the envelope follower to OFF restores the FX signal (of course), then setting it back to -99.9 dB again mutes it completely (see point 2).

I can't tell if this behaviour exists before the current beta (8).
I found this using the latest Axe-Edit, but I could reproduce it by operating the front panel with a pre-existing patch and as well with a newly created one. (see attached patch)

FWIW, in my pre-existing patch with lots of blocks, moving the multitap delay around the grid would "reactivate" the FX output at some places in the grid while leaving the envelope follower at the -99.9 dB setting. This is true even if the blocks in front would remain in bypassed state. At other places in the grid (i.e., after other blocks), the FX signal remains muted. Seems to me that the multidelay block's envelope follower reacts wrong after some blocks, after others it works as expected.
 

Attachments

kRixEL said:
Hi Folks.
really enjoying the axe3 so far! Thank you Fractal for this awesome piece of gear!!
i have been sitting on fw27b2 for a while and enjoyed using the virtual capo quite a lot..
i gave b8 a shot and compared to b2 its quite laggy still with the chords setting being the „worst“ so far. even when turning tracking completely off it seems not on par with the performance of the vc during fw27b2!? I‘m on -2 semitones. Am i doing something wrong here?
Regards!
Click to expand...
Are you certain you loaded b#8 and not b#7 which had many reports of lag/latency?
 
Budda said:
Seems good to me! New preset, EF86 with gain around 3 and an LP, YA IR.

Click to expand...

What pickups do you have in that Les Paul, and how close are the pickups to the strings? I'm surprised how jangly this amp model sounds, as I’m never able to get it to be like that with PAF style pickups. Which YA IR too?
 
Thenewexhibit said:
What pickups do you have in that Les Paul, and how close are the pickups to the strings? I'm surprised how jangly this amp model sounds, as I’m never able to get it to be like that with PAF style pickups. Which YA IR too?
Click to expand...
Canadian winder Mike Turk A2 PAF “59” and pretty cranked up. This guitar has the most everything of my les pauls lol.

YA: MV30 pack, blend mix #4 i believe
 
Thenewexhibit said:
What pickups do you have in that Les Paul, and how close are the pickups to the strings? I'm surprised how jangly this amp model sounds, as I’m never able to get it to be like that with PAF style pickups. Which YA IR too?
Click to expand...
And, detuned -5 at that! Great sounding LP he has.
 
I was reworking some presets from FW25 as I have been holding off due to recording. I was curious, so I did a little experiment. I don't know if it's just me, or if it's these updates, but I recorded a quick play through of one of the songs with the new firmware, and it sat in the mix quite easily with minor adjustments. hi pass, little cut at 580hz little boost at 1400-ish, and it was pretty usable for a quick adjustment. It makes me a little sad because these songs are already out of my hands and I really do like these improvements.

Other notes: Tuner is excellent, pitch block is sounding great!
 
unix-guy said:
Ok... Everyone else reporting that b#8 fixed pitch block latency introduced in b#7...

Haven't seen any complaints on this one.
Click to expand...
Played with the pitch block a bit tonight (dual chromatic and quad chromatic) and I didn't feel any latency. But I heard some warbling and tracking artifacts on the -2/+2 octave bands. I didn't mess with the notes/chords setting other than the default, so it may be something easy to dial out. Didn't really affect the overall effect I was going for, and still sounded good in the mix.
 
Budda said:
Canadian winder Mike Turk A2 PAF “59” and pretty cranked up. This guitar has the most everything of my les pauls lol.

YA: MV30 pack, blend mix #4 i believe
Click to expand...
Got ya! That’s cool to see you’re using it with the MV30 pack! I just assume it was the Matchless pack. I’m surprised how jangly it is with those pickups that high in a les paul!
 
Sebastian said:
Possibly a bug:

1. Put a multitap delay block (all settings at default) after a bypassed block.
2. Set its envelope follower from OFF to -99.9 dB -> FX output is silenced completely, independent of block input level.
3. Unbypass the block in front -> multitap delay block might output some FX signal again, but I doubt it works truthfully to the -99.9 db setting.
4. Bypass the block in front again -> multitap delay may or may not keep on putting out an FX signal.
5. Switching the envelope follower to OFF restores the FX signal (of course), then setting it back to -99.9 dB again mutes it completely (see point 2).

I can't tell if this behaviour exists before the current beta (8).
I found this using the latest Axe-Edit, but I could reproduce it by operating the front panel with a pre-existing patch and as well with a newly created one. (see attached patch)

FWIW, in my pre-existing patch with lots of blocks, moving the multitap delay around the grid would "reactivate" the FX output at some places in the grid while leaving the envelope follower at the -99.9 dB setting. This is true even if the blocks in front would remain in bypassed state. At other places in the grid (i.e., after other blocks), the FX signal remains muted. Seems to me that the multidelay block's envelope follower reacts wrong after some blocks, after others it works as expected.
Click to expand...
Fixed for next release.
 
unix-guy said:
Ok... Everyone else reporting that b#8 fixed pitch block latency introduced in b#7...

Haven't seen any complaints on this one.
Click to expand...
while the general latency of the vc seems very playable in this revision all in all i have a slight feeling that the actual latency slightly varies during playing... has the pitch block a static lookahead time or does it alter depending on the incoming signal?

asking for friend... who maybe had a look a little too close to the weed grinder last evening...:sweatsmile:
 
kRixEL said:
while the general latency of the vc seems very playable in this revision all in all i have a slight feeling that the actual latency slightly varies during playing... has the pitch block a static lookahead time or does it alter depending on the incoming signal?

asking for friend... who maybe had a look a little too close to the weed grinder last evening...:sweatsmile:
Click to expand...
Latency is variable because the best splice point is variable.
 
kRixEL said:
while the general latency of the vc seems very playable in this revision all in all i have a slight feeling that the actual latency slightly varies during playing... has the pitch block a static lookahead time or does it alter depending on the incoming signal?

asking for friend... who maybe had a look a little too close to the weed grinder last evening...:sweatsmile:
Click to expand...
If consistent latency is the top priority, you might try the Electro Harmonix Pitch Fork before the Axe. While I'm sure that the latency does vary, it seems to operate over a much smaller time window, giving the perception of static (and minimal) latency at any interval setting (even extreme shifting intervals). The apparent glitching and warble are also minimal. But there is a major cost...

The tradeoff is that the algorithm causes a consistent "blurring" of the attack. While the VC preserves a well-defined pick attack that is generally indistinguishable from the unprocessed signal, the Pitch Fork imparts what appears to be multiple cross-faded attacks extremely close together, causing both a softened character as well as a comb filter artifact most noticeable on the attack portion of the signal (but not so bad as to be percieved as a doubling). It may even be a "dumb" shifter without correlation that is well-executed. Overall, it's benificial for use cases that require consistent latency, and detrimental for transient preservation. The VC has higher fidelity. Different algorithms for different priorities. I suspect most players would opt for fidelity over latency, given reasonable extremes for both. I find the different approaches to realtime pitch shifting fascinating.

I haven't had an opportunity to try the new VC algorithm though. Looking forward to spending time at home with it. I curious as to how the new modes sound now, including Off.
 
To my ears since FW27, the majority of my pre sets (especially those with a pitch block) have been massively improved.

Tuner is way better

The dynamics on many of the gainy amps sound brutal.

In many pre sets, I have had to reduce the amp levels by 4-5db, but the new versions are so inspiring to play.

Overall this is the biggest sound upgrade to this magical box for ages.
 
Last edited:
Status
Not open for further replies.
Back
Top Bottom