Hi Res Qobuz sounds like white noise

Hi

K50G4 running Squeeze/Squeeze. Connection to DAC via USB.

When I play hi-res files from Qobuz it sounds like white noise but get close the speaker and you can hear some level of music way down in the noise.

Standard res files play OK, and hi-res files from the SSD play OK.

The Qobuz forum suggests an issue between the two USB interfaces. So the first question is, does the K50 process streaming hi-res files differently from locally stored hi-res files? If not, do they appear at the outbound USB interface differently?

This started about 6 weeks ago.

I have tried using the AES interface to see if it is in fact the USB interface, but for some reason that doesn’t play at all. It has worked in the past so not sure what’s going on.

Any thoughts?

Cheers

The K50 runs software that processes the files. Thus it would come down to how Squeeze as configured on your K50 is processing the files.

It’s my understanding that Squeeze plays files the same regardless of where they come from. It will make a call to Qobuz, retrieve the files from their servers, and then just plays them. When playing from the local drive, it makes a call to the operating system on your K50, retrieves the files, then plays them.

I just confirmed that high res from Qoboz plays just fine. What I would suggest: confirm that your USB cable is well seated. Power down both your DAC and K50, them power on your DAC and after it is fully on, start your K50. Next go to Squeeze… server settings… have it clear library and rescan everything.

I think you need to check the K50’s configuration under Squeeze; perhaps a screenshot would help. I’d try setting playback to Native if you haven’t already.

Book a support session with the team muzza:

Alternatively pop on up to factory with the unit

Thanks folks, will try the recommendations before logging a call. I’ll post back here with the results.

Cheers

Hi folks

Tried everything on the list. Even logged into Tidal and tries to play a hi-res files. Defaulted to 16/44, but at least they played.

I’ve got Antipodes looking into it. Hopefully they’ll identify the issue with the K50 or elsewhere and we can move forwards.

I’ll report back.

Cheers

Kia ora team

Prince connected to my K50 and found some server plug-ins I had enabled that were probably causing the issue. One being a DSP plug-in but wasn’t using, and there was CPO something also?

Those plug-ins had been enabled for some time with no issues and then the system went rogue. Had those plug-ins caused immediate issues on selection I would have de-selected them at the time, but at that point nothing was amiss.

The local hi-res files always played, I guess they’re routed straight to the player rather than passing through the server.

Prince looked at the Squeeze forums which pointed to one of the plug-ins as a potential issue. I did the same some time ago but didn’t find anything.

Perhaps there could be a repository on the Antipodes forum / support site that catalogues known plug-ins that might be causing issues?

Anyhow, the probelm seems to be fixed.

Thanks Prince!

4 Likes

Good to hear Prince traced it to the enabled plug-ins rather than the K50 hardware itself. The detail about local hi-res files bypassing the server path is a useful clue, since it narrows where the routing issue sat. A catalogue of known-problematic plug-ins on the support site would save a lot of guesswork, especially when something runs fine for months before going rogue. Please do post back if Antipodes confirms anything further about that CPO plug-in.

See this:

The C-3PO detail is the part worth pinning down: disabling the transcoding helper after v4.4 seems to be the standard first step, so it may not be your K50 routing at all. What still puzzles me is why it ran quietly for months before misbehaving, which suggests a version change rather than a setting you touched. If Antipodes confirms the plugin interaction, a short note in the support docs on which Squeeze plugins to disable by default would help everyone.

Squeeze is in two parts, Squeeze server and Squeezelite (player)

Squeeze Server with Qobuz:

  • Handles authentication, metadata browsing, library integration, and search queries against the Qobuz API
  • Resolves the streaming stream using pseudo-protocols (such as qobuz://) and fetches the audio stream data or URL
  • Transcodes or packetizes the audio stream if required by the target player

Squeezelite (player):

  • Receives the audio stream pushed or pulled from the Lyrion server
  • Decodes the audio format (FLAC, MP3, etc.) and outputs the sound to your DAC/speakers
  • Reports playback status, position, and volume back to the server interface

Streaming does not bypass server side.

Thanks Mark

Does playing local files bypass the server side? I had no problems playing local hi-res files.

Would Prince have changed the menu access? I can no longer see Advanced options, and can’t add Qobuz Connect as a streaming option.

Thanks.

When using an Antipodes all files, streamed or stored locally use both server and player, nothing by-passes the server.
C3P0 code handles streamed and local files differently, hence can play local without issue.

Antipodes do not use Connect, with Qobuz Connect the server is in the Cloud, with Squeeze/Qobuz integration the server in is the Antipodes device.

The Menu would not have been changed by Support.
The message Squeeze gives is sadly not accurate.

The path for Qobuz is:

3 Dot Menu - Server

Manage Plug-ins

Click Settings on Qobuz plugin

Add user credentials

Remember to use the drop-down for Hi-Res

CLICK SAVE