Owen Smith
1K Club - QQ Shooting Star
That's partly because a lot of people were trying to use the Receiver on wifi and it has crap wifi. Admittedly the Boom has the same crap wifi. I used the Receiver on wired ethernet. Also the DAC in the Receiver was pretty poor, I used it with an external DAC. Then people tried to configure the Receiver without using the Controller and it really wasn't designed for that. Finally people tried to use the Receiver as a wifi to ethernet bridge and that was disastrous as it uses the same MAC address on both interfaces (barking mad decision by someone) which caused no end of DHCP problems which varied depending on your broadband router. I didn't fall into any of the above traps and the Receiver worked fine for me, except I can't know if it was the cause of my sync problems.I wonder if the Receiver was actually the culprit. I've never owned a Duet/Receiver/Controller, but when I first got into that ecosystem long ago I read the forums religiously. It seemed to me that there were a LOT of complaints about the Duet. It's really too bad because it seemed like an excellent idea.
It was clear to me that the product line was a poor match for Logitech and they should never have bought it. As for still supporting it, Logitech haven't pulled the plug on any of the servers for the forums etc but they haven't paid any developers to work on it for nearly a decade I thought, it's all just public domain. Still, not pulling the plug on the servers is pretty good given how long its been.It was heartbreaking when Logitech dumped the product line, but all these years later they're still supporting it, which is nicer than I ever would have expected. And I'm really grateful that it all works so well on the Raspberry Pi. I used to worry that once the official Logitech hardware died I'd have no replacement.