captblaze
Headphoneus Supremus
It a fact no matter how many days since.That's a different issue and one that clouds the conversation 10 years later.
It a fact no matter how many days since.That's a different issue and one that clouds the conversation 10 years later.
It a fact no matter how many days since.
Don’t hold your breath. They haven’t fixed the ability to connect to the update servers.So has any one heard anything regarding Chord and Qobuz Connect? Would really appreciate a software/firmware update for my Oku that lets me bypasss all these buggy renderers out there
Given that Qobuz Connect was only launched a week ago, it is probably much too soon for Chord to have fully analyzed what firmware code changes will be required, before starting to implement any code updates.So has any one heard anything regarding Chord and Qobuz Connect? Would really appreciate a software/firmware update for my Oku that lets me bypasss all these buggy renderers out there
I was alsGiven that Qobuz Connect was only launched a week ago, it is probably much too soon for Chord to have fully analyzed what firmware code changes will be required, before starting to implement any code updates.
Plus as has been pointed out, there are no update servers online.
Just my opinion, but I wouldn't be surprised if owners have to wait until Canjam London in a few weeks, for major update news about Poly, 2Go and the upcoming TT streamer.
it would require Poly to have a functioning Qobuz playback system. and the Poly can only really make use of MPD, which is opensource software running on linux, and miniDLNA. most likely also raop for airplay. all of these are opensource. I don't see a full custom qobuz frontend being developed.Given that Qobuz Connect was only launched a week ago, it is probably much too soon for Chord to have fully analyzed what firmware code changes will be required, before starting to implement any code updates.
Plus as has been pointed out, there are no update servers online.
Just my opinion, but I wouldn't be surprised if owners have to wait until Canjam London in a few weeks, for major update news about Poly, 2Go and the upcoming TT streamer.
Given that Qobuz Connect was only launched a week ago, it is probably much too soon for Chord to have fully analyzed what firmware code changes will be required, before starting to implement any code updates.
Plus as has been pointed out, there are no update servers online.
Just my opinion, but I wouldn't be surprised if owners have to wait until Canjam London in a few weeks, for major update news about Poly, 2Go and the upcoming TT streamer.
we all do, but we need to be pragmatic about our estimates of the possible timescales, or we risk suffering self-generated frustrations if there is a delay.I want to have hope that there are good surprises in store for the Poly.
Never purchasing products from this company is the only way to guarantee that doesn't happen.we all do, but we need to be pragmatic about our estimates of the possible timescales, or we risk suffering self-generated frustrations if there is a delay.
That's not going to happen but how about a collaboration with a DAP company that makes a DAP with removable DAC modules a Chord module for a AK, Cayin or iBasso DAP would be awesome, again, not happening.I hope CHORD turns Mojo 3 into a streaming DAC, reduces size and weight and comes up with a decent software stack particularly for DLNA, that resembles the likes of MinimServer for local playback.
Based on what I read on this pageit would require Poly to have a functioning Qobuz playback system. and the Poly can only really make use of MPD, which is opensource software running on linux, and miniDLNA. most likely also raop for airplay. all of these are opensource. I don't see a full custom qobuz frontend being developed.
Also apart from the "Apps & UX Guidelines for 3rd party integration" PDF, I have no clue how these companies get to create applications to interface with Qobuz.
Based on what I read on this page
https://www.qobuz.com/us-en/magazine/story/2025/05/14/qobuz-connect-how-it-works/
The Qobuz Connect app:
Of course this would also apply to Hugo 2Go.
- Would want to control the volume of the Mojo2 connected to the Poly:
- Option 1 would be for two way communication - Mojo2 transmits its volume setting to Connect app. Connect app transmits the desired volume setting to Mojo2, which then adjusts its volume. I can't imagine this rewrite of the Mojo FPGA happening before Mojo3
- Option 2 would be for two way communication - Mojo2 volume set to 100% by the user. Connect app transmits the desired volume setting to Poly, which then adjusts the volume data sent to Mojo2. I can imagine this being possible, but it may not be what Qobuz envisioned as a compatible amplifier
- The concept of two way communication is uncontroversial in itself, because this had to be enabled for the Poly firmware to become Roon compatible
I think companies have to join the Qobuz Society, before they get told the full details.
Does anyone have a different interpretation?