[VladSoldier]

I don't see any feedback from them

 

[captblaze]

I don't see any feedback from them

The comments have to get really harsh and then someone from Chord will come on and try and explain things away. Usually by then a mod steps in and does damage control

 

[vo_obgyn]

Chord Electronics for 2000$

This is the same message I have been getting for some time now,

 

[earnmyturns]

This is the same message I have been getting for some time now,

I had left the Hugo2+2go unused for a while as my wired speaker and headphone systems were doing their jobs. When I got to it again, it got stuck in some weird state and I had to do a factory reset, which is a PITA as the little control switch does not register properly sometimes, and returns to the main audio menu. Finally got it reset, and then tried to update firmware. Tried both GoFigure and ethernet, stuck on 1.5.7. Hugo2+2go has been the least reliable, hardest to configure audio device I've owned in over a decade, and I've owned lots from different brands, big and small.

 

[Currawong]

I can't say for sure, but as the software (and hardware) for the 2go are not made by Chord, it's possible that the issue is not actually with Chord, but a third party. I can't at all imagine that Chord are ignoring this, even if they aren't saying anything. Of course, if it is a contractural issue, they wont be saying anything publicly at all.

 

[captblaze]

I can't say for sure, but as the software (and hardware) for the 2go are not made by Chord, it's possible that the issue is not actually with Chord, but a third party. I can't at all imagine that Chord are ignoring this, even if they aren't saying anything. Of course, if it is a contractural issue, they wont be saying anything publicly at all.

It’s still a Chord issue. Whether a 3rd party compiles the software or not

 

[Currawong]

It’s still a Chord issue. Whether a 3rd party compiles the software or not

I didn't say it wasn't, just that they may not be able to offer an explanation publicly.

 

[captblaze]

I didn't say it wasn't, just that they may not be able to offer an explanation publicly.

"it's possible that the issue is not actually with Chord, but a third party" I'll leave this here and then say goodnight

 

[AussieMick]

"it's possible that the issue is not actually with Chord, but a third party" I'll leave this here and then say goodnight

Pedantic much? Infer from context, that’s clearly not what @Currawong was meaning.

 

[Currawong]

Indeed, what I said is pretty clear. I didn't at all suggest that it isn't Chord's responsibility.

It's no different with Chord's DACs, which are designed by Rob Watts, who is under contract. If there's a problem with the design of one of Chord DACs, Chord has to have a third party, in this case Rob, address it. We are just lucky in the case of Chord DACs, that third party is very active on the forums and you can ask them questions directly. With the 2go and Poly, you can't.

 

[Guffers]

It’s a shame that the situation is what it is. These products are not cheap and deserve better support and software. I’ve just tried updating my 2Go again and the server is still unavailable.