Just tested it here and it works fine. I can confirm the laggy menu behavior though.Mic DI IR capture is not working in 2.05 for me. I shot an IR in 2.04, worked, upgraded, nope, downgraded and yep.
Note, changing the IR number in the setup menu was very laggy also. Not so with 2.04.
Just tested it here and it works fine. I can confirm the laggy menu behavior though.
XFormer match doesn't work well for me...
It was a very powerful setting before but now it s really subtle...
Is that normal?
it's an axedit graphic bug, the parameters are taken into consideration on the afxAmp block/ input eq the line for the graph is missing. Noticed this when I went to adjust the low cut
it's an axedit graphic bug, the parameters are taken into consideration on the afx
The meters on the front panel are the post-fader meters. The meters in the block are pre-fader. The red line on the meters in the block indicate -12 dBFS.
Again, sorry for not letting this die, but I'm not seeing what you describe. When the DAW levels for Out1 and Out4 read the same, the hardware meters are not the same. It's as if the +4/-10 reference levels are not being taken into account. I've created a short video - I hope this helps.
Again, sorry for not letting this die, but I'm not seeing what you describe. When the DAW levels for Out1 and Out4 read the same, the hardware meters are not the same. It's as if the +4/-10 reference levels are not being taken into account. I've created a short video - I hope this helps.
It's all analog. My projects aren't all at 48kHz so I don't use USB mode.Out of curiosity, is your III acting as the audio interface via USB in that example, or are you connected to the Apollo with the analog outs?
Like maybe the Apollo is expecting a +4 dBV signal at its inputs or something? Also I think you're probably seeing proper level from Out4 into the Apollo because Output 4 (and 3) is designed for unity gain when it's front panel Level knob is turned all the way up, unlike Output 1
maybe I'm wrong, but I believe that the discrepancy in levels between out 1 and 4 is the volume knob on output 1. It looks to me like you have your patch way too loud on output 1 and then are probably running the output volume hardware knob low on affx to achieve "same gain" on apollo
That sounds like your Delay Compensation was set too high.I shouldn't have said it doesn't work. It does work but the result is not usable. All high end content.
The meters on the front of the Axe-Fx are relative to full-scale. They are not calibrated in dBu. They are to assist you so that you don't clip the converters.Here's a crappy picture of the front panels of the Apollo and Axe III. The purple circles (on the left) are Out 1 and the blue (on the right) are Out 4. Note that the Apollo sees the same level on both outputs, but the Axe III front panel shows different levels (three lights for Out 1, two lights for Out 4).
Out 1 is set to -10dBV reference as are both inputs on the Apollo.
View attachment 51835
Works correctly here.Hi,
I use the tap tempo switch on the mfc since the launch of afxiii.
i send a midi CC#14 message
everything has always worked well on this side before this new fw version.
the message is well received by the afxiii but the calculation of the tempo no longer seems based on an average calculations of the number of taps.
my global tempo setting is set on average.
did you have the same issue on your side?
That sounds like your Delay Compensation was set too high.
I don't understand the question. Can you describe exactly what you are trying to do? Are you using the editor?Maybe I am wrong but, on the Control Switch scenes configuration, it is only possible to select the first slot and the options are: input 1-2-3-4, Other slots are not configurable.
How does work the CS configuration now?