The thing that the internet has to do with windows update. Might be worth looking into update history and roll back Windows if you haven't checked that yet. I have had more trouble with windows updates screwing with drivers than I can count.
Paul
I have noticed the issue for me happens what i have both the axe fx AND the focusrite scarlett interface connected through usb at the same time.
Disconnecting the scarlett makes the axe edit working fine.
So there's probably a conflict going on between the two devices.
Dude.......defining AxefxII USB sources/destination within an aggregate device definition. When I took the AxeFxII out of this definition, the problem subsided - .....
Awesome! Happy to helpDude.
You are being showered in rose petals.
Thousands, and thousands, of rose petals.
Can you feel them?
Fragrant and plump, carelessly spinning as they fall, gently brushing your cheek, (some stay in your hair)... creating a delicate carpet where I bow, grovel forth and kiss your feet, clutch at your pants in a beseeching manor, and fervently proclaim you as my saviour...
For you are THE ONE!
The one who has solved the riddle of the Time Out error!!
I will be forever in your debt.
I offer you my first born.
.
.
.
(Did i just type all that out aloud?)
.
.
.
SO for those following along at home, yes it worked, had the Axe Fx II as part of an aggregate device with an RME Fireface 400, ( firewire device).
Using Logic X and was getting time out, lost communication, and unrecognised device errors, regardless of whether the aggregate device was being used by Logic or not.
Deleted the aggregate device and all good now.
Thanks again !
Carl
Tried a similar thing on PC- worked like a charm.Just an fyi for others that may run into this on MAC, I started having this problem recently and discovered that it's onset coincided with my defining AxefxII USB sources/destination within an aggregate device definition. When I took the AxeFxII out of this definition, the problem subsided - so far so good after a few hours. The aggregate device contained both AxeII and III usb sources/destination but I did not test to see if it was this co-location that causes the issue or if AxefxII AxeEdit simply does not like having an aggregate device running with the same components.