It would truly be awesome if audirvana-studio (core) would include Qobuz Connect! It would make it so any client app that includes that connection type could connect to core, even those on the same Linux computer as the core service.
Please, please, please! 
??? What exactly do you think AudirvÄna will bring to the table, beyond DSP? If the employment of DSP is the rationale, this obviates the premise for Qobuz Connectā¦
@Agoldnear - Thatās exactly the point I was making. Since core (on Linux) acts as a āhardwareā device, getting instructions from the mobile app as to the account and what to play, then the Qobuz Connect receiver inclusion could make it possible to just stream from any app that has the client protocol included.
While it might not be a priority, it could be a nice feature so that any Linux computer could act as a hardware network device for Qobuz using the core engine.
Does AudirvÄna Core not support streaming from Qobuz?
It doesnāt support streaming Qobuz from ANY client that has Qobuz Connect ability. Maybe Iām not being clear enough in my description, and thatās on me.
So, I apologize for my ignorance about AudirvÄna Coreā¦ Are you not able to stream content from Qobuz as a client?
Let me paint an example for clarity:
Audirvana core on Linux + the Audirvana app on the phone works flawlessly and sounds amazing (of course).
Audirvana core on Linux + any other client app that has Qobuz Connect as an option does not work.
For example: On Linux, thereās an app named QBZ, which is a great app, but the sound engine isnāt as polished as Audirvana. However, it does support Qobuz Connect to dedicated devices that support that protocol / connection types. If Core had the option to connect using Qobuz connect, that client app (or any that support the connect option), it could open up the Linux client app (and phone apps) to control Audirvana Core as they adopt the connection.
Does that make more sense? Core is the server, apps that support could be the client, with some limitations.
What makes sense to me, is the premise of Qobuz Connect as the audio-engine and GUIā¦ Otherwise it is superfluous in the context of the AudirvÄna audio-engine playback of streamed content from Qobuz, which I presume it does.
You may be correct, Iām not sure. But my assumption is that since Qobuz Connect is a connection protocol, it doesnāt do any of the audio processing, which is then left to the device that receives the client request and connects to the Qobuz service. At least, thatās my understanding of how the technology works, but I may be wrong.
Basically, I would like this:
Present: Audirvana Studio app āā Core (proprietary connect protocol)
Request: Any app with Qobuz Connect āā Core (Qobuz protocol)
This describes the premise and nature of Qobuz Connectā¦ it is the audio-engine that drives the audio deviceā¦
Listen in Hi-Res with Qobuz Connect
With Qobuz Connect, the control of your paired audio devices remains entirely within the Qobuz app, so listening through your connected amplifier or wireless speakers no longer requires the use of the manufacturerās app. Whatās more, Qobuz Connect ensures Hi-Res music playback at up to 192 kHz/24-bit on your connected equipment.
So, itās more like a Bluetooth / network streaming protocol vs. one like casting to a device (that uses the device hardware for processing).
If thatās the case, then maybe my request doesnāt work.
It is a playerā¦ using proprietary protocol that is supported by some devicesā¦
the supported hardwareā¦
https://www.qobuz.com/us-en/discover/apps-partners#audio-qobuz-connect
Still, I think it might be possible, but there may be licensing concerns. From Google AI summary when I asked if Qobuz Connect was like casting:
Yes, Qobuz Connect functions similarly to casting technologies like Spotify Connect or Google Cast, where your phone or laptop acts as a remote control while the streaming device pulls music directly from the cloud. It allows for seamless playback transfer between devices and ensures high-resolution audio streaming without draining your phoneās battery.
OK, Iām done.
@Antoine - Please consider this request and let me know if itās totally out of the question. Thanks!
It is superfluous in the context of AudirvÄnaā¦ The salient question comes from the perceived value and sound-quality in any given playback scenarioā¦ Qobuz Connect is a barebones approach to streamed Qobuz digital-audio content playback on a supported deviceā¦
A.f.a.i.k. Qobuz connect is the same as Tidal connect and Spotify connect. It is a āall in oneā software package that is embedded by a manufacturer. It does the signal process as well, not just connectivity, search and control of the playback. Thatās why Qobuz connect sounds different than Qobuz embedded if you use a streamer that features both.
Iām also wondering where this would leave the application AudirvÄna where it comes to the processing. In my belief the processing by the PC is what makes the sound quality of AudirvÄna stand out.
If AudirvÄna would use Qobuz Connect then the renderer (in my case my Naim streamer) would be asked to get the stream directly from the sourceā¦ So doesnāt that mean then that the benefits of using AudirvÄna are being diminished?
Maybe this is exactly what other participants in the thread are saying, but as English isnāt my native language Iām not sure if this is indeed what they try to say.
No, not necessarily. Instead of the Naim it would be Audirvana acting as the Qobuz connect end-point and pass it on to the Naim. But I think that is currently not possible with Qobuz Connect.
Tidal connect works a bit different. That is a library of components that together make Tidal connect. Grimm Audio has implemented Tidal connect by only using the parts that are needed to interact with Tidal, but they have written the sound processing part themselves.
In theory, Audirvana could do the same.
I see. So Qobuz Connect would use AudirvÄna as the renderer and AudirvÄna the Naimā¦