FX Loop not working when MFC-101 connected

kavevester

kavevester

Inspired
Every time I put the MFC-101 to the AXE the FX loop stops working...

Uses Axe FX2/Quantum firmware 1.02
MFC-101 I will update later. Can't remember right here.

Anybody seen this? Something in the MFC that overrules settings for FX loop? (What should that be)
 
yes and no one was set to control the fx loop.. Do you know other hints in the MFC that could influence on this problem?
 
Chris@AxeFxTutorials said:
upload an axe preset where this happens, please.
Click to expand...
It's the same all over. When I put in a FX loop block on already created or if I create a new with only AMP/CAP/FX LOOP
Just updated the MFC and the AXE to the latest firmware. Also tried to reset (possible on MFC) IA's, Presets ect.¨Works fine without the MFC connected as already stated
 
kavevester said:
It's the same all over. When I put in a FX loop block on already created or if I create a new with only AMP/CAP/FX LOOP
Just updated the MFC and the AXE to the latest firmware. Also tried to reset (possible on MFC) IA's, Presets ect.¨Works fine without the MFC connected as already stated
Click to expand...

When you say the FX Loop "stops working", what do you mean exactly? Is the loop block being bypassed? Or is it still active but you can't hear anything through it?
-
Austin
 
When active in the block in Axe edit no sound. When disabled sound ok. Can hear the receiving (FX return) hums when I touch the disconnected cable so nothing gets send to FX send I guess. The output 2 is of cause set higher than zero (half way up).
So everything is good as long as MFC is disconnected to the AXE. Connected the send signal disappears
 
At the Axe-FX I/O: CTRL page, what is "Output 2 Volume" set to?

If you switch this to "none" then restart the Axe, does the problem still occur?
 
Bakerman said:
At the Axe-FX I/O: CTRL page, what is "Output 2 Volume" set to?

If you switch this to "none" then restart the Axe, does the problem still occur?
Click to expand...

The volume 2 is set half way up.. What do you mean by the re-starting procedure??? As long as the volume is turned up it should work right?
 
kavevester said:
The volume 2 is set half way up.. What do you mean by the re-starting procedure??? As long as the volume is turned up it should work right?
Click to expand...

No. For example: you may have your rig configured in some way to reduce the OUT 2 level. This can happen in several scenarios.
Setting the CC of OUT 2 to NONE and restarting is a method to prevent this.

Another approach would be to reset both your Axe-Fx and the MFC.
 
I looked into how to reset the MFC yesterday. It seems as if there is partial resets of "Preset", "Song" ect. Did'nt quit understand why. I wanted to restore to factory settings (total reset) and the same I want to do with the Axe today if I still have no solution to this problem.
Arghh.
 
AXe-Fx: Utility menu > Reset System Params.

MFC: power up while holding switch 11.
 
Thank U all for answers. Don't know what t.. f... is wrong but it worked when I got home today. Only touched in menu I/O - CTRL - OUT2 volume from 12 to something and back again. Actually no change ... Hmm guess this is not the last I have seen to this.. ¨For sure in a live job something like this will happend and I don't know the reason. Exciting ;-)
 
Reset the system settings on the Axe FX. I started having strange issues myself with the MFC and thought too it was the MFC.

It would be elasticy in preset switching and if I was on preset 1 and tried to go down to 383 it would jump to 103. If I used axe edit or the front panel to access a preset like 350, using the MFC to try to go to 351 or 349 would send me to preset 1 and also show the preset as edited...

I am on Q1.06, Not saying that's the cause though. Anyways, after checking my cat 5 with 2 others to the same results, and clearing preset banks to be sure it wasn't corruption, reseting the system settings fixed it for me.


And no I didn't have axe edit connected while trouble shooting the MFC
 
You must log in or register to reply here.
Back
Top Bottom