I love the Ad30 with update!
I have some bad news there. We're finding the new born + two other kids a little more challenging than we expected. My wife isn't ready to handle all three kids by herself for an entire day while I sneak off to Petaluma. The littlest is just 11 days old today.
If there's Skype or Google Hangout capabilities I can dial in and talk though.
Also note: the new noise gate algorithm uses just a hair bit more CPU, so if you were on the edge, it may have pushed you over. You can switch it back to classic if you want to try to gain that 1% back.
Would it be accurate to think of this new FW as (depending on how you set it of course) a return to some of the more idealized, opposed to purely accurate, amp tones of pre FW10 ?
FW9 for example, had a bunch of fans who liked the kind of studio ready ideal guitar tones, while it seemed like FW10 pushed things to a new level of realism, touch sensitivity etc. Responded more like a real amp and some folks missed the studio polish of earlier FW.
In 16.02, with things like the dynamics knob, it seems we have the option to take an amp past the limits of an accurate model, to a bit more of an idealized tone. Seems great to me, and naturally one doesn't have to use such settings if they want to. In my mind, this seems like a great direction to go, because while I appreciate 99.9% accurate models, I think its also pretty cool to use the freedom of the virtual amp to allow for tones and features simply not possible with a real amp.
Its like the Matrix if you will.... sure you can follow the rules of reality, OR, you can tell yourself there is no spoon, so to speak, and take your amp to new levels
What is everyone's opinion on this ?
I'm a HUGE fan of ideal amp tones so anything that allows for creation of the ideal is a HUGE plus for me. Even playing live with my band, many of the Ideal tones are greatly preferred by my bandmates.
My CPU actually lowered when I switched the input gate from classic to intelligent...?
I tested by doing the same thing to about half a dozen presets and they all reacted the same, either a displayed 1% reduction in Axe-Edit or no change.
Axe-Edit isn't the canonical source for CPU use -- look on the unit.
Very well. Maybe a bug in AE 3.1.1?
What would you like to call something that does not perform its intended function or does so errantly?
So when Variac is set to default at 100% is that comparable to 120V on the real deal?
OK, but I'm seeing actual CPU decreases... I get what you're saying about what the front panel reads vs axe edit. AE just happens to be taking a snapshot of the CPU use at a low point? Consistently?
Not really a huge deal either way, I just thought I was saving CPU.
Damn. There's a NOBLE PRIZE waiting for Cliff. Kudos.
110V I believe.