TIDAL HI FI Playback via Mac Google Chrome

Works fine with other USB devices - have you tried alternatives? Which version of OS X?

Does your MBP play OK into the DAC using sources other than Tidal? If not, you probably need to go to System Preferences > Sound and select the correct output. (Then select 'Sound Effects' and choose 'play through internal speakers' to avoid annoying beeps playing through your HiFi.)

David, the 2Qute is the only USB DAC I have. OSX 10.11.1 El Capitan.

Chrissu, iTunes plays back just fine. Before playing music I performed set up In Sound Preferences selected the 2Qute for output and set Sound Effects set to internal speakers. TIDAL indicates the song is playing but cannot hear anything.

Safari works in 320 and my Windows PC works 44.1/16 but nothing in Chrome for Mac.

Regards,

M

Sometimes you just have to go with what works, Use safari!

mackb3 posted:

TIDAL HI FI from my MacBook Pro USB to 2Qute will not produce sound. Output is selected 2Qute. When 2Qute is unplugged default is internal speaker or if I plug in my GRADO SR60's all works. Chrome is version is the latest. Version 47 64 bit.

I've searched TIDAL for answeres with no luck. Any ideas?

M

 

I had a similar experience with a MacBook Pro, Chrome and a Hugo. The Chord dealer couldn’t offer a solution so I did the research myself. The notes below are an edited and expanded version of the explanation I sent to the dealer.

Chrome not playing through Hugo:

(current MacBook Pro, Mac OS X 10.11, current Chrome release)

The Chrome browser wouldn’t play sound via the Chord Hugo. There were no problems with the Qobuz Desktop player application or with the Apple Music player but Qobuz wouldn’t work through the browser, nor would iPlayer Radio or other browser-based audio sources. Chrome is the recommended browser for Qobuz.

The solution:

• Chrome doesn’t support anything above 192K. The MacBook Pro and Hugo had aligned themselves at 384K.

• The relevant settings are changed in the Audio Midi utility rather than in System Preferences. I configured the Hugo for 192K; I now had audio via Chrome and the Hugo but it was accompanied by clicking sounds. Changing to settings below 192K changed the clicking but didn’t eliminate it.

• I did a little more research and then configured the Built-in Microphone input and Built-in Output to match the Hugo output. This meant limiting the Hugo output to 96K because the input and built-in speaker output don’t support anything above 96K.

• Problem solved.

Summary:

• Connect your 2Qute to the MacBook.

• Open Audio MIDI Setup (Launchpad/“Other” folder).

• Select the 2Qute in the devices list.

• Configure 96000.0 Hz. It will probably configure itself to “2ch-32bit integer” and you can’t change that setting.

• Set “Built-in Output” output to 96000.0 Hz and “2ch-32bit Float”.

• Set “Built-in Microphone” input to 96000.0 Hz and “2ch-32bit Float”.

I chose “2ch-32bit Float” because it is closest to “2ch-32bit integer”. I have no idea what either setting means but the configuration process described eliminated the problem.

X Bratsche Scratche posted:

mackb3 posted:

TIDAL HI FI from my MacBook Pro USB to 2Qute will not produce sound. Output is selected 2Qute. When 2Qute is unplugged default is internal speaker or if I plug in my GRADO SR60's all works. Chrome is version is the latest. Version 47 64 bit.

I've searched TIDAL for answeres with no luck. Any ideas?

M

 

I had a similar experience with a MacBook Pro, Chrome and a Hugo. The Chord dealer couldn’t offer a solution so I did the research myself. The notes below are an edited and expanded version of the explanation I sent to the dealer.

Chrome not playing through Hugo:

(current MacBook Pro, Mac OS X 10.11, current Chrome release)

The Chrome browser wouldn’t play sound via the Chord Hugo. There were no problems with the Qobuz Desktop player application or with the Apple Music player but Qobuz wouldn’t work through the browser, nor would iPlayer Radio or other browser-based audio sources. Chrome is the recommended browser for Qobuz.

The solution:

• Chrome doesn’t support anything above 192K. The MacBook Pro and Hugo had aligned themselves at 384K.

• The relevant settings are changed in the Audio Midi utility rather than in System Preferences. I configured the Hugo for 192K; I now had audio via Chrome and the Hugo but it was accompanied by clicking sounds. Changing to settings below 192K changed the clicking but didn’t eliminate it.

• I did a little more research and then configured the Built-in Microphone input and Built-in Output to match the Hugo output. This meant limiting the Hugo output to 96K because the input and built-in speaker output don’t support anything above 96K.

• Problem solved.

Summary:

• Connect your 2Qute to the MacBook.

• Open Audio MIDI Setup (Launchpad/“Other” folder).

• Select the 2Qute in the devices list.

• Configure 96000.0 Hz. It will probably configure itself to “2ch-32bit integer” and you can’t change that setting.

• Set “Built-in Output” output to 96000.0 Hz and “2ch-32bit Float”.

• Set “Built-in Microphone” input to 96000.0 Hz and “2ch-32bit Float”.

I chose “2ch-32bit Float” because it is closest to “2ch-32bit integer”. I have no idea what either setting means but the configuration process described eliminated the problem.

XBS,

You are a lifesaver. That did the trick, thank you very much.

M