Initially the Duet had well documented wireless issues. And with spotty
connectivity its main purpose was compromised. I couldn't hardwire it
with Ethernet, so relegated it to secondary duty. Then they fixed the
wireless issues, but every 6 months or so mine would disappear from the
device list, a
cliveb wrote:
> I never did get why so many people had problems with the Duet. I've got
> one of the original beta-test units and it's never really missed a beat.
> (Maybe the fact I have it connected via Ethernet rather than wireless
> helps?) For sure, the early firmware releases on the Control
garym wrote:
> I purchased a new duet shortly after they were released. Set it up
> initially and ran it for a few years and never had a single issue with
> receiver or controller (other than sometimes fuzzy artwork). Never so
> much as a reset. But like you, it was always connected via ethernet
Archimago wrote:
> Personally, I don't think the "emotional engagement" argument makes any
> sense either. Personally, the more emotionally engaged with the music I
> become, the more I enjoy and like to listen -irrespective -of the
> quality.
Spot on :) I always feel that people that claim they
cliveb wrote:
> I never did get why so many people had problems with the Duet. I've got
> one of the original beta-test units and it's never really missed a beat.
> (Maybe the fact I have it connected via Ethernet rather than wireless
> helps?) For sure, the early firmware releases on the Control
pablolie wrote:
> And when I got *one* Duet, OMG, now there was one buggy product. It
> actually never entirely stopped acting up in my environment, but at
> least it became usable over time.
I never did get why so many people had problems with the Duet. I've got
one of the original beta-test uni
