USB HID Volume, microRendu and Roon (case closed)

[rrm]

Mytek just released a firmware update (2.34) for the Brooklyn enabling it to support USB HID volume control.  Mytek's release notes: https://mytekdigital.com/download_library/firmware/BrooklynDAC_firmware_readme.txt

 

Plugging my Brooklyn directly into my mac via USB worked just as expected: I could use the volume slider in the Roon software to adjust the Brooklyn's hardware volume settings.  Unfortunately, I can't seem to get this to work through microRendu.  

 

I set the Volume Control setting in the microRendu > Settings > RoonReady > Volume Control to Hardware:

 

But in Roon when I try change the volume, it says "Volume control is Fixed"

 

And the Roon > Device Setup > External Volume Control drop down is disabled and fixed at None:

 

Interestingly, after updating the Brooklyn's firmware to 2.34 the microRendu > Apps > DAC Diagnostics > "Set DAC to MAX volume" button works now (it didn't before).  Has anyone been able to get their microRendu to work with the latest Brooklyn firmware, or another DAC supporting USB HID Volume control?       

 

 

 

[vortecjr]

Yes, it's working fine here. Did you press Save in Settings / DAC Diagnostics? 

[rrm]

Yes, I did save the settings, and I've tried rebooting and power cycling everything in the chain (sonictransporter > microrendu > Brooklyn) several times.  Roon still says "Volume control is fixed."

 

One thing I noticed is in the DAC diagnostics, it shows "amixer: Mixer hw:0 load error: Broken pipe" at the bottom:

 

I'm wondering if that could be related to volume control.  Does yours show that error too?

 

Many thanks.

[vortecjr]

Mine says: 

Status: Unknown (status not available when device is not playing)

Simple mixer control 'PCM',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 99
  Mono: Playback 99 [100%] [0.00dB] [on]
Simple mixer control 'PCM Clock Source',0
  Capabilities: enum
  Items: 'Unit 6' 'Unit 7'
  Item0: 'Unit 6'
Simple mixer control 'Clock Source 7 Validity',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [on]

 

[rrm]

Interesting.  Were your diagnostics also for a Brooklyn with firmware v2.34?

[vortecjr]

Yes. I updated my unit yesterday to try it. 

[rrm]

Thanks for testing.  I just tried updating the microRendu software and it did update a few packages.  Unfortunately I'm volume control still isn't working.  Oddly after updating the microRendu, the DAC diagnostics now shows much less info than before:

 

Clicking "Set DAC to MAX volume" still works as does Roon generally, except expect it still indicates the volume level fixed.  Do you have any other suggestions I might try?  Can I completely reset it to factory defaults somehow?  I'm guessing the issue is with the microRendu rather than the Brooklyn because the Brooklyn's volume control via USB works just fine when I use it as a sound output device on my mac.   Thanks again for your help.

[vortecjr]

Right now the unit is not seeing your DAC. It has to list your DAC on that page. Power cycle your DAC and then the unit.

 

DAC description: Brooklyn DAC      25ce:001f

Diagnostic information for this DAC

Mytek Digital Brooklyn DAC at usb-ci_hdrc.1-1.1.2, high speed : USB Audio

Playback:
  Status: Stop
  Interface 2
    Altset 1
    Format: S32_LE
    Channels: 2
    Endpoint: 1 OUT (ASYNC)
    Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
    Data packet interval: 125 us
  Interface 2
    Altset 2
    Format: SPECIAL DSD_U32_BE
    Channels: 2
    Endpoint: 1 OUT (ASYNC)
    Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
    Data packet interval: 125 us

[rrm]

I thought the same thing and did power cycled the DAC and microRendu several times, with no change.  Despite not showing up in the diagnostics page, it actually is working: I can stream music Roon --> UR --> Brooklyn fine even while the diagnostics page is in this state.  I also noticed the DAC does show up in the Settings > System Settings > Custom DAC:

 

     

 

I also tried downgrading the Brooklyn firmware back my previous verison, 2.22, and it still does not show up in the microRendu DAC diagnostics.  Any other suggestions most appreciated.

[vortecjr]

Are you on Sonicorbiter 2.3 or 2.5?

[rrm]

I'm on 2.3.  I tried clicking Update in the Software Manager which outputs this:

Upgrade in progress...

05/28/2017 10:58:33 - Starting upgrade. (This can take a long time...)

05/28/2017 10:58:33 - Updating sonicorbiter packages...
Last metadata expiration check performed 0:00:00 ago on Sun May 28 10:58:36 2017.
Dependencies resolved.
Nothing to do.
Complete!
05/28/2017 10:58:38 - Updating process 1 of 3 complete...
05/28/2017 10:58:44 - Updating process 2 of 3 complete...
05/28/2017 10:58:44 - Updating OS packages...
Last metadata expiration check performed 0:00:04 ago on Sun May 28 10:58:41 2017.
Dependencies resolved.
Nothing to do.
Complete!
05/28/2017 10:58:47 - Updating process 3 of 3 complete. Please reboot

The Software Manager still shows 2.3:

 

 

Is there another way to update it to 2.5?

[vortecjr]

3 hours ago, rrm said:

I'm on 2.3.  I tried clicking Update in the Software Manager which outputs this:

Upgrade in progress...

05/28/2017 10:58:33 - Starting upgrade. (This can take a long time...)

05/28/2017 10:58:33 - Updating sonicorbiter packages...
Last metadata expiration check performed 0:00:00 ago on Sun May 28 10:58:36 2017.
Dependencies resolved.
Nothing to do.
Complete!
05/28/2017 10:58:38 - Updating process 1 of 3 complete...
05/28/2017 10:58:44 - Updating process 2 of 3 complete...
05/28/2017 10:58:44 - Updating OS packages...
Last metadata expiration check performed 0:00:04 ago on Sun May 28 10:58:41 2017.
Dependencies resolved.
Nothing to do.
Complete!
05/28/2017 10:58:47 - Updating process 3 of 3 complete. Please reboot

The Software Manager still shows 2.3:

 

 

Is there another way to update it to 2.5?

No. The only way to get Sonicorbiter 2.5 is to purchase it. Here is a link: https://www.smallgreencomputer.com/pages/sonicorbiter-2-5 

[rrm]

I can confirm that after upgrading to Sonicorbiter 2.5, it's working as expected now.  Many thanks for your help.