Rendu Support Thread

[vortecjr]

10 hours ago, Dazed and Confused said:

I am no longer able to access Tidal through my MicroRendu using Linn Kazoo. After selecting Tidal in the Kazoo app there  is no option to enter my Tidal login & password. Instead it goes straight to a loading message with a spinning icon. I have uninstalled/installed Kazoo several times but the problem remains. Any ideas?

I have seen this once or twice, but I have I'm not been able to reproduce it. I'll report it to the developer and see if he has heard of it happening. Are on SO 2.7?

 

In the meantime use this method to restore Tidal play back:

https://audiophilestyle.com/forums/topic/27851-sonicorbiter-tidalqobuz-setup-with-openhome/?do=findComment&comment=880956

[gsquared]

44 minutes ago, vortecjr said:

This sounds like a power supply issue. Remove the LPS-1 and use it's charger to power the Rendu. See if this setup displays the same issue. 

 

I swapped out the charging PSU to the LPS-1 with an Uptone branded SMPS. Previously I was using an El Cheapo LPSU. I will see if that was the issue.

 

Thanks the suggestion.

[Dazed and Confused]

7 hours ago, vortecjr said:

I have seen this once or twice, but I have I'm not been able to reproduce it. I'll report it to the developer and see if he has heard of it happening. Are on SO 2.7?

 

In the meantime use this method to restore Tidal play back:

https://audiophilestyle.com/forums/topic/27851-sonicorbiter-tidalqobuz-setup-with-openhome/?do=findComment&comment=880956

 

Thanks very much  and yes the M/rendu is on 2.7.

 

I am about to leave on a six week trip, so apologies in advance if I respond late to any further replies or updates..

 

[Matias]

Hi I am also experiencing dropouts from the DAC. Music just stops playing, DAC shows no locked frequency. I enter my ultrarendu page (latest version) in DAC diagnostics and it is empty. I power cycle the DAC and it shows again. Play for some minutes and drops again...

This never happened a few months ago. Maybe after 2.7?

 

JRiver 24 + Gizmo - Asus router - Asus switch - ultraRendu + Uptone lps1.2 - Calyx Femto.

 

Any ideas?

[vortecjr]

3 hours ago, Matias said:

Hi I am also experiencing dropouts from the DAC. Music just stops playing, DAC shows no locked frequency. I enter my ultrarendu page (latest version) in DAC diagnostics and it is empty. I power cycle the DAC and it shows again. Play for some minutes and drops again...

This never happened a few months ago. Maybe after 2.7?

 

JRiver 24 + Gizmo - Asus router - Asus switch - ultraRendu + Uptone lps1.2 - Calyx Femto.

 

Any ideas?

Nothing in 2.7 would cause this. When the DAC locks up what sample rates are you playing? 

[Matias]

8 hours ago, vortecjr said:

Nothing in 2.7 would cause this. When the DAC locks up what sample rates are you playing? 

Happens with different ones. Today I was looping a 16/44 file upsampled to 24/176. But this has been happening with 24/192 as well. I always upsample to one of those 2.

 

Also what changed last months is that summer is quite warm lately, and I am not using AC all the time. Maybe heat has something to do with stability?

 

Or maybe should I set the DLNA options different?

 

DAC description: CALYX FEMTO Audio 2.0      20b1:0002

Diagnostic information for this DAC

CALYX CALYX FEMTO Audio 2.0 at usb-ci_hdrc.1-1.1, high speed : USB Audio

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

Capture:
  Status: Stop
  Interface 2
    Altset 1
    Format: S32_LE
    Channels: 2
    Endpoint: 2 IN (ASYNC)
    Rates: 44100, 48000, 88200, 96000, 176400, 192000
    Data packet interval: 125 us
Status: Unknown (status not available when device is not playing)
Simple mixer control 'Mic',0
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 127
  Front Left: Capture 127 [100%] [0.00dB] [on]
  Front Right: Capture 127 [100%] [0.00dB] [on]
Simple mixer control 'Mic',1
  Capabilities: cvolume cvolume-joined cswitch cswitch-joined
  Capture channels: Mono
  Limits: Capture 0 - 127
  Mono: Capture 127 [100%] [0.00dB] [on]
Simple mixer control 'CALYX Audio 2.0 Output',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 127
  Mono:
  Front Left: Playback 127 [100%] [0.00dB] [on]
  Front Right: Playback 127 [100%] [0.00dB] [on]
Simple mixer control 'CALYX Audio 2.0 Output',1
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 127
  Mono: Playback 127 [100%] [0.00dB] [on]
Simple mixer control 'CALYX Internal Clock Validity',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [on]

 

[vortecjr]

1 hour ago, Matias said:

Happens with different ones. Today I was looping a 16/44 file upsampled to 24/176. But this has been happening with 24/192 as well. I always upsample to one of those 2.

 

Also what changed last months is that summer is quite warm lately, and I am not using AC all the time. Maybe heat has something to do with stability?

 

Or maybe should I set the DLNA options different?

 

DAC description: CALYX FEMTO Audio 2.0      20b1:0002

Diagnostic information for this DAC

CALYX CALYX FEMTO Audio 2.0 at usb-ci_hdrc.1-1.1, high speed : USB Audio

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

Capture:
  Status: Stop
  Interface 2
    Altset 1
    Format: S32_LE
    Channels: 2
    Endpoint: 2 IN (ASYNC)
    Rates: 44100, 48000, 88200, 96000, 176400, 192000
    Data packet interval: 125 us
Status: Unknown (status not available when device is not playing)
Simple mixer control 'Mic',0
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 127
  Front Left: Capture 127 [100%] [0.00dB] [on]
  Front Right: Capture 127 [100%] [0.00dB] [on]
Simple mixer control 'Mic',1
  Capabilities: cvolume cvolume-joined cswitch cswitch-joined
  Capture channels: Mono
  Limits: Capture 0 - 127
  Mono: Capture 127 [100%] [0.00dB] [on]
Simple mixer control 'CALYX Audio 2.0 Output',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 127
  Mono:
  Front Left: Playback 127 [100%] [0.00dB] [on]
  Front Right: Playback 127 [100%] [0.00dB] [on]
Simple mixer control 'CALYX Audio 2.0 Output',1
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 127
  Mono: Playback 127 [100%] [0.00dB] [on]
Simple mixer control 'CALYX Internal Clock Validity',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [on]

 

Everything there looks fine to me. Not sure what can cause this symptom. I don’t upsample with DLNA so maybe try straight playback. We can’t rule out anything right now including the DAC. 

[Matias]

47 minutes ago, vortecjr said:

Everything there looks fine to me. Not sure what can cause this symptom. I don’t upsample with DLNA so maybe try straight playback. We can’t rule out anything right now including the DAC. 

 

I will also try a different USB cable and see if it improves stability.

[jaaptina]

Hi Jesus,

 

I keep the ultraRendu always "on". The dac/amplifier I turn off every night. Every 4 or 5 days my ultraRendu fails to start after I've turned the dac/amp on. I have to reboot the ultraRendu to be able to start a track.

 

I'm using LPS-1 to power the ultraRendu. 

 

I'v made a screenshot before and after the reboot.

[vortecjr]

On 2/8/2019 at 2:52 PM, jaaptina said:

Hi Jesus,

 

I keep the ultraRendu always "on". The dac/amplifier I turn off every night. Every 4 or 5 days my ultraRendu fails to start after I've turned the dac/amp on. I have to reboot the ultraRendu to be able to start a track.

 

I'm using LPS-1 to power the ultraRendu. 

 

I'v made a screenshot before and after the reboot.

When was the last time you pressed update? Try going to the Settings page and pressing Save in the output you use. You can also try removing the USB and reinserting it.

[Axiom05]

Any MPD update planned for the near future?

[vortecjr]

9 hours ago, Axiom05 said:

Any MPD update planned for the near future?

Yes and we have some interesting things we want to do with it:) Did you have something in mind? 

[sockpit]

Help please!  I cleared the DNLA cache of my microRendu (don’t ask), and now the Kazoo can’t find the mR.  The wheel in Kazoo just spins in the Qobuz “tile”.  

 

As the OP of this long thread, please help me out.  I’m not particularly knowledgeable about his this all works, but can follow instructions

[rickca]

2 minutes ago, sockpit said:

I cleared the DNLA cache of my microRendu (don’t ask), and now the Kazoo can’t find the mR.

I don't even know how you did that ... but did you restart MPD/DLNA?  I don't have a microRendu anymore, but I think it's under

Settings --> MPD-DLNA.  At least click on Save.  Then exit and restart Kazoo.

[sockpit]

I’ve restarted and even rebooted the mR.  And closed and opened the Kazoo app.

 

Have put in a request to Jesus in the sonicorbiter DNLA output thread. Thanks.

[jaaptina]

After deleting DLNA cache you need to renew your Qobuz login. 

[vortecjr]

Open Kazoo and click on the menu bars at the top left. Click on any of the tabs except Tidal and Qobuz. Go to Apps / MPD DLNA and clear the cache...wait for the page to refresh automatically and a wait a few seconds before proceeding. In Kazoo now click on the Tidal or Qobuz tab and you should prompted to enter the login ID and password.  

[Axiom05]

12 hours ago, vortecjr said:

Yes and we have some interesting things we want to do with it:) Did you have something in mind? 

Nothing specific, just like to keep things reasonably up to date. However, I am curious about how the new mpd support of Qobuz can be used.

[sockpit]

13 hours ago, vortecjr said:

Open Kazoo and click on the menu bars at the top left. Click on any of the tabs except Tidal and Qobuz. Go to Apps / MPD DLNA and clear the cache...wait for the page to refresh automatically and a wait a few seconds before proceeding. In Kazoo now click on the Tidal or Qobuz tab and you should prompted to enter the login ID and password.  

Thank you so much @vortecjr  That did the trick!

[pwhinson]

Sorry to bring up something that has probably been covered in the 200+(!) pages of issues related to the MR.  What does it mean when I can access the interface of the MR via its IP address but NOT through sonicorbiter.com?  Generally when this happens, the rest of my system "loses" the MR, Roon fails to see it, and despite many reboots, unplugs, etc. I don't seem to be able to get the MR back.  That is until the next day when it magically appears back in Roon and seems to work OK.  

[pwhinson]

OK, so I rebooted my cable modem and router and now sonicorbiter.com finds the microrendu.  Previously I could only get into the interface by entering the MR's IP address into my browser.  STILL though, MR is not playing music (ROON, Directstream DAC).  It just cycles through whatever playlist is load giving each track about 3 seconds before moving onto the next.  When I run the RAAT diagnostics from the microrendu interface I get the following (below).  Error messages include  ERROR error in snd_pcm_hw_params: Input/output error (-5)  and WARNING [lua@0x1a1cef4] [192.168.7.134:52001] setup failed: RAAT__OUTPUT_PLUGIN_STATUS_FORMAT_NOT_SUPPORTED 
[0000238] 44.584 TRACE [lua@0x1a1cef4] [192.168.7.134:52001] SENT [16] {"message":"RAAT__OUTPUT_PLUGIN_STATUS_FORMAT_NOT_SUPPORTED","status":"UnexpectedError"} and Any help would be greatly appreciated.  Jesus?

[vortecjr]

When was the last time you pressed update? Update the unit and wait for the Back to Main Menu link. Then go to the Settings page and pressing Save in the output you use. You can also try removing the USB and reinserting it and power cycling the DAC.

[pwhinson]

vortecjr actually I updated the unit once last night when I was having these problems.  It didn't seem to need the update as I recall (the version number was current?)...but when I pressed update it did go its usual long sequence of reporting back to me and the update completed normally.  Its morning here in Atlanta (I was encountering the issue late last night) and I haven't yet gone back to see if its still persisting.  I was really curious as to what the error messages meant.  After I posted all this, I went to the trouble of rebooting my cable modem and router.  The wireless system in the house is a EERO Pro system but my house also has Ethernet so there's a switch up on the fourth floor fed by the primary switch at my cable modem.  After doing that I was able to get into the interface BOTH via sonicorberter.com and by going to the devices IP address.  Before I gave up last night the MR WAS showing up again in Roon, but instead of playing tracks either local or streamed from qobuz, Roon would just cycle through the playlists, appearing to "try" to play each track, each time giving up after about 3 seconds, then moving to the next track and continuing in that fashion until it reached the end of the playlist.

[pwhinson]

I just tried playing something through the MR and its continuing to behave consistently as it did late last night before I finally gave up.  Cycles through playlists without playing anything.  Ran diagnostics again and (as above) the primary error messages seems to be:

 

0000127] 32.519 WARNING [lua@0x1a1cef4] [192.168.7.134:52001] setup failed: RAAT__OUTPUT_PLUGIN_STATUS_FORMAT_NOT_SUPPORTED 

[Axiom05]

@pwhinson This is a long shot but I once had a hard drive crash while Roon was playing music (Roon Core was on the HDD). This really caused unexpected issues with my ultraRendu when I switched back to using MPD. Music would only play for 10 minutes at a time and then stop. Try disconnecting everything from the Rendu, power, USB, Ethernet, and let it sit for a while. I left mine disconnected overnight and when I reconnected everything, it worked fine again. No explanation why but it worked.