FW9Beta Testing update:
Trying the firmware since last night. So far i experienced Communication Time-out after about 30 minutes of playing for the 3rd time now.
Here is a screen shot.
I use Axe Fx II mark II with MFC 101 mark II connected.
My setup:
Windows 10 64bit, USB connected. Using headphone monitoring from AFX. Windows playback device set to AFX. MFC connected with Cat5e.
Throw an ADA MP-1 crunch and lead channel in there while you have the hood open, too. Kthxbai.Cliff please add the EF86 channel from the DC30!!!!!!!!!! it's the best channel on the amp!!!!!!! Thanx, jlynnb1
speaker compression hugely improved string control . anyone notice this? and my strings feel so balanced now.
you can actually change how (in or out) of control your strings are . lovin it
Again, forgive my ignorance for the following inquiry:
I use Motor Drive (MD) in the cab block for every preset I use and loooooove it. Since MD in the amp block is now replaced, are we being encouraged to use the new Speaker Compression (SC) in the amp block along with the cab's MD?
I ask because, IIRC, it was originally suggested to use MD either in the cab or amp block, but not both.
If you are recording or using an FRFR system then SC in the amp block is preferred (MD in the cab block off).
could each position be mapped to a range on say the treble control? i know zero about programming so it may well be impossible, just throwing an idea out there.It wouldn't be hard except we'd need six models, one for each position of the rotary switch.
I'm using Reaper with Axe Edit sometimes as well. The only error I have had was in the process of copying/pasting more than 10 presets within AxeManage. Otherwise I haven't had any issues with Axe Edit, and any of the DAWs I've used with it (Reaper, FL Studio & Bitwig). Which leads me to think it may not be Reaper. Maybe is it more particular to the O/S and its driver integration behaviors? That, or maybe something to do with static electricity in the room, or were you watching pretty girls on the tube out of the corner of your eyes?Working with support, we thought that my DAW (Reaper) audio driver was competing with the Axe-FX driver since I'm going direct to DAW via USB.
I had thought I confirmed this by running Axe-Edit without my DAW launched as it seemed to not have communication errors unless the DAW was running. That didn't last long and the errors starting happening even without my DAW running.
What's even more strange is how random it is. Sometimes it will work for a long time (1+ hours) and sometimes it starts acting up right away.
We'll see how it acts after upgrading to the Q9 beta.
Same here all my presets with just a touch of output compression are rendered silent.Help.
Set some great sounds last night but today the 'Output Comp' has changed how it acts. Today edited presets were silent until I turned 'Output Comp' down( the first 5% turn clockwise on the output comp dial takes it from 0 to -30db i.e. is acting like a reverse volume). I am using front panel only. What gives? 0 to -30db with no guitar signal and not reacting to guitar input. The strange thing is, it was working last night.
I'm not seeing this after updating my firmware. If I create a new preset, I clear out the preset and add in say the JTM45 amp. I for one do not see Speaker Compression or Spkr Comp in any block or setting. I do see speaker drive but it is always 0. Is something off in my setup? I have a Mk2. thanks
I'm not seeing this after updating my firmware. If I create a new preset, I clear out the preset and add in say the JTM45 amp. I for one do not see Speaker Compression or Spkr Comp in any block or setting. I do see speaker drive but it is always 0. Is something off in my setup? I have a Mk2. thanks
It's been (and still is?) a 'Mark I/II' issue. PC and Mac.I have an XL+ with Q9.0 beta connected to a Mac and haven't had any time outs...Might be just affecting the WIN users.