rooExtend – The easy start with Roon Extensions

Hi @Art_Set,
as rooExtend (which includes the Roon bridge supplied by Roon) is Bit-Perfect and any DSPs are out the only black box is the ASIO driver from the DACs manufacturer where we don’t know for sure if it is Bit-Perfect or not. Maybe Denafrips can offer a proof on this.

I’m an engineer and spend some time on the Audiosciencereview forum, which I also support. So I’m always skeptical when someone claims that something sounds different in certain configurations. In audio science, the only evidence will be a double-blind ABX test conducted with ABX software and a random selection of inputs. I recommend reading up on ABX and thinking about how to implement it in your setup.

If you carried out such a test with a reliable and documented setup and then get a statistically relevant result, I’ll be back in to find out the reason of sound difference with you.

The problem with human perception is that before the auditory impression is assessed, the brain goes through many stages from the eardrum to recognition. Just knowing from which source you are currently streaming can influence your perception, even if you don’t want to admit it.

That’s exactly what I experienced when I introduced the rooExtend-Box to an experienced hi-fi editor. In his listening session he switched between NAA for HQ Player and Roon Bridge for Roon in the rooExtend setup but forgot to press save. So nothing happened at all!

His conclusion was (and he was absolutely certain) that it sounded better with the NAA setting. In reality he was comparing the Roon Bridge to the Roon Bridge but since he knew what he had chosen it sounded different to him :crazy_face:

Best DrCWO

@DrCWO

Thanks for taking the time to reply.
Fully agree with you on the specifics of human perception.
But it is also not just 1s and 0s, otherwise it wouldn’t matter what we use and we can get the cheapest DACs and put the saved money towards better speakers and amps.
I do intend to also test with another DAC, which would put at least the theory if this is the Denafrips’ driver doing something or not to the test.

I am not an engineer, but I also subscribe to Asr and I like Amir’s reviews, but I also bought a Toping Dac based on one of these reviews and couldn’t stand it.
If I listen to music 4-5 hours a day on avarege and changing something in the chain makes me stop listening or drastically reduce this average, then maybe something is different. At this point either my brain gets used to it or I change back and life goes on.
Recently I got a Schiit Saga S to be able to change the volume without dsp. This is a transparent passive preamp. In the end I took it out of the chain and am now using the Roon Dsp as it sounds better.

Anyway, thanks again for your responses.

Guess you know that:

It makes me happy that things that measure good also sound good :blush:

Edit:
Maybe a more expensive DAC sounds better in someone‘s ears as he knows that it was expensive :thinking:

1 Like

Yes, I saw that, but at the same time people comment that only the Rme adi2 can actually do lossless volume attenuation up to 25db. In reality roon dsp sounds good, the only issue I have is that dsd is converted to pcm,but we already discussed this :slight_smile:

1 Like

There are glasses that are transparent. But we see people that wear brown, pink, blue or yellow glasses. There‘s nothing wrong with it. It‘s not a question of better or worse. It‘s a question of taste.
We can technically proof that a glass is transparent. But we can‘t say that this is the right way on how to look at the world. Anybody should decide which color to use and which fits best to his personal taste and lifestyle.

Same for audio. We can proof that audio gear is transparent by measurements. Some like it but others like colored tube sound. There is nothing wrong with it at all!

For me, the whole thing starts to become problematic when people think they have to convert others and make them believe their pink glasses are the only and BEST way on how to look at the word.

I can measure facts but I can never measure taste so I would therefore never presume that a transparent system has to suit everyone’s taste. Would be great to have this common understanding and stop acting like a missionary.

@art_set please don‘t get me wrong :pray: This was a general statement and I did not say you act like a missionary :wink:

Best DrCWO

3 Likes

Absolutely, I am not trying to say something is better or worse.
The fact that I have tubes in the chain makes it kind of obvious that I am listening to coloured sound, which to me sounds more realistic but for someone else may be an anathema.
I am just saying that a piece of tech can measure perfectly and still not sound great in someone’s system due to lack of synergy.

1 Like

Hi - Thanks for the quick response!
I’ve arranged to return the faulty MS Surface Dial - What do I need to make your software work with a spacemouse instead. I’m a bit frustrated with the bricked Surface Dail :slight_smile:

Just buy the Spacemouse Wireless and go.
Take care you get a package with the USB receiver included. Some reported issues buying the receiver and the SpaceMouse as separate devices.

But retry the Dial if it’s back, it’s nice :+1:

Best DrCWO

Great system DrCWO!
I thought i’d check in just to let others know it’s worth persevering with. I returned the faulty MS Surface Dial, got a replacement that is now working well on the latest version 3.3.2 of rooExtend.

It was still a somewhat flaky in the pairing process but it worked after 4th time trying! I was half expecting the Dial to brick itself like the first one - but it didn’t.

I was getting a lot of core disconnect messages but changes the wireless from WPA2 to WPA and restarted the Roon server. One of these two changes restored stability.

It’s great and my wife also loves it! The dial sits between us on a coffee table and it’s great to adjust volume and mute as needed.

Thanks for a great system! One question: How much impact does having haptic feedback enabled have on battery life?

Cheers, Glen

1 Like

Hi @Glen_Wilson2,
great you made it now :+1:
Thanks’ for your positive feedback :smiley:

I have several hundred rooDial users now and general feedback was that connecting with WiFi is not the best solution. In the meantime I recommend a Pi4 with wired Ethernet. Roon itself did not recommend WiFi as the Roon API was not made for that. So receiving messages with transmission errors Roon Core disconnects rooExtend.
It all depends on where you live and how many WiFis are near by. Even worst is that BT uses the same frequency spectrum as WiFi so collisions happen as more WiFi is around. So if you get continuous trouble think about a wired Ethernet connection.

Best DrCWO

Thanks DrCWO,
Of course you are right, wired is always preferable to wireless. In my situation that’s a bit tricky as then the Pi would be some distance away from the seating area, stretching the limits of bluetooth coverage - always a compromise one way or the other!

I could always for the Pi to 5GHz to avoid contention between BT and Wifi at 2.4GHz but for the last 24 hours no core dicconects, so working well.

Log snip below - does it look healthy or flaky to you?
Also, does haptic feddback drain the battery quickly?

Thanks once again.

 Apr 17 20:22:11 rooExtend rooExtend[1054]: Request from: 10.1.1.110 image/jpg: /tmp/selfgz902/www/images/rooExtend_500.jpg
    Apr 17 20:22:11 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/javascript: /tmp/selfgz902/www/site.js
    Apr 17 20:28:30 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/html: /tmp/selfgz902/www/soundInterface.html
    Apr 17 20:28:30 rooExtend rooExtend[1054]: amixer---1
    Apr 17 20:28:30 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/css: /tmp/selfgz902/www/site.css
    Apr 17 20:28:30 rooExtend rooExtend[1054]: Request from: 10.1.1.110 image/jpg: /tmp/selfgz902/www/images/rooExtend_500.jpg
    Apr 17 20:28:30 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/javascript: /tmp/selfgz902/www/site.js
    Apr 17 20:35:16 rooExtend rooExtend[1054]: host 1.1.1.1 is dead
    Apr 17 20:44:36 rooExtend rooExtend[1054]: host 1.1.1.1 is dead
    Apr 17 20:45:16 rooExtend rooExtend[1054]: host 1.1.1.1 is dead
    Apr 17 21:17:39 rooExtend rooExtend[1333]: ***** startEventCapture
    Apr 17 21:23:10 rooExtend rooExtend[1333]: ***** events disconnected
    Apr 17 21:23:10 rooExtend rooExtend[1333]: ***** set LowSpeed
    Apr 17 21:29:27 rooExtend rooExtend[1333]: ***** startEventCapture
    Apr 17 21:31:26 rooExtend rooExtend[1054]: host 1.1.1.1 is dead
    Apr 17 21:34:35 rooExtend rooExtend[1333]: ***** events disconnected
    Apr 17 21:34:35 rooExtend rooExtend[1333]: ***** set LowSpeed
    Apr 17 21:36:42 rooExtend rooExtend[1333]: ***** startEventCapture
    Apr 17 21:41:40 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/html: /tmp/selfgz902/www/index.html
    Apr 17 21:41:44 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/css: /tmp/selfgz902/www/site.css
    Apr 17 21:41:44 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/javascript: /tmp/selfgz902/www/site.js
    Apr 17 21:41:44 rooExtend rooExtend[1054]: Request from: 10.1.1.110 image/jpg: /tmp/selfgz902/www/images/rooExtend_500.jpg
    Apr 17 21:41:48 rooExtend rooExtend[1333]: ***** events disconnected
    Apr 17 21:41:48 rooExtend rooExtend[1333]: ***** set LowSpeed
    Apr 17 21:48:05 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/html: /tmp/selfgz902/www/log.html
    Apr 17 21:48:05 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/css: /tmp/selfgz902/www/site.css
    Apr 17 21:48:05 rooExtend rooExtend[1054]: Request from: 10.1.1.110 image/jpg: /tmp/selfgz902/www/images/rooExtend_500.jpg
    Apr 17 21:48:05 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/javascript: /tmp/selfgz902/www/site.js
    Apr 18 00:15:08 rooExtend rooExtend[1054]: host 1.1.1.1 is dead
    Apr 18 00:45:28 rooExtend rooExtend[1054]: host 1.1.1.1 is dead
    Apr 18 06:22:30 rooExtend rooExtend[1333]: ***** startEventCapture
    Apr 18 06:27:36 rooExtend rooExtend[1333]: ***** events disconnected
    Apr 18 06:27:36 rooExtend rooExtend[1333]: ***** set LowSpeed
    Apr 18 06:27:58 rooExtend rooExtend[1333]: ***** startEventCapture
    Apr 18 06:29:04 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/html: /tmp/selfgz902/www/log.html
    Apr 18 06:29:04 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/css: /tmp/selfgz902/www/site.css
    Apr 18 06:29:04 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/javascript: /tmp/selfgz902/www/site.js
    Apr 18 06:29:04 rooExtend rooExtend[1054]: Request from: 10.1.1.110 image/jpg: /tmp/selfgz902/www/images/rooExtend_500.jpg
    Apr 18 06:30:30 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/html: /tmp/selfgz902/www/logUpdate.html
    Apr 18 06:30:30 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/css: /tmp/selfgz902/www/site.css
    Apr 18 06:30:30 rooExtend rooExtend[1054]: Request from: 10.1.1.110 image/jpg: /tmp/selfgz902/www/images/rooExtend_500.jpg
    Apr 18 06:30:30 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/javascript: /tmp/selfgz902/www/site.js
    Apr 18 06:32:59 rooExtend rooExtend[1333]: ***** events disconnected
    Apr 18 06:32:59 rooExtend rooExtend[1333]: ***** set LowSpeed
    Apr 18 06:35:24 rooExtend rooExtend[1054]: Request from: 10.1.1.110 text/html: /tmp/selfgz902/www/log.html

@DrCWO

Just watched a review of pi2aes hat and sounds very interesting.
Interested to know if rooextend works with hats as output via roonbridge or I can only use usb?

Thanks

Currently USB only but I plan to introduce this in summer.
Best DrCWO

1 Like

Looks good so far. The “set Lowspeed” messages should disappear if you take out batteries and reinsert them. This is caused by a bug in the BT driver that I cannot fix.
Best DrCWO

:exclamation::exclamation: rooExtend v3.3.3 is out :exclamation::exclamation:

Release v3.3.3 comes with the following extensions/fixes:

  • Should work in Mainland China and Hong Kong.
    I had a lot of work regarding missing time servers and wrong certificates behind the great firewall :face_vomiting:

  • Used Memory is displayed in the License Manager now.

  • You will find a button to restart the Chromium Browser for HDMI on the rooExtend Service Page.

release v3.3.3 will install automatically at all Raspberry Pi instances running v3.x.x or above.

The release for the rooExtend-Box is not yet published!

Best DrCWO

3 Likes

Thanks DrCWO.
This seems to have fixed a repetitive restart issue I had on 3.3.2 with Core and Pi happening all the time.
So far so good!

Apr 24 23:29:06 rooExtend rooExtend[8742]: --------------------------------------------------
    Apr 24 23:29:06 rooExtend rooExtend[8742]: rooExtend 3.3.2 started...
    Apr 24 23:29:06 rooExtend rooExtend[8742]: Config Path:   /config.json
    Apr 24 23:29:06 rooExtend rooExtend[8742]: Hostname:      rooExtend
    Apr 24 23:29:06 rooExtend rooExtend[8742]: Restarted:     true
    Apr 24 23:29:06 rooExtend rooExtend[8742]: Timesync:      skipped, restated
    Apr 24 23:29:06 rooExtend rooExtend[8742]: Ethernet:      connected, stop WiFi
    Apr 24 23:29:07 rooExtend rooExtend[8742]: Got language:  NZ
    Apr 24 23:29:07 rooExtend rooExtend[8742]: Got timezone:  Pacific/Auckland
    Apr 24 23:29:07 rooExtend rooExtend[8742]: Set timezone:  Success
    Apr 24 23:29:08 rooExtend rooExtend[8742]: Has Bluetooth: true hci0 USB 8C:88:0B:69:BF:90
    Apr 24 23:29:08 rooExtend rfkill[8811]: unblock set for id 0
    Apr 24 23:29:08 rooExtend rooExtend[8742]: TV name:       --
    Apr 24 23:29:08 rooExtend rooExtend[8742]: Found:         Raspberry Pi 4 Model B Rev 1.5
    Apr 24 23:29:08 rooExtend rooExtend[8742]: Production:    true
    Apr 24 23:29:08 rooExtend rooExtend[8742]: Interface:     eth0
    Apr 24 23:29:08 rooExtend rooExtend[8742]: Has WiFi:      true
    Apr 24 23:29:08 rooExtend rooExtend[8742]: Is NanoPi:     false
    Apr 24 23:29:08 rooExtend rooExtend[8742]: Has Linux 64:  true
    Apr 24 23:29:08 rooExtend rooExtend[8742]: Has GPIO:      true
    Apr 24 23:29:08 rooExtend rooExtend[8742]: --------------------------------------------------
    Apr 24 23:29:08 rooExtend rooExtend[8742]: init LED
    Apr 24 23:29:09 rooExtend rooExtend[8742]: ##### Start: License Manager
    Apr 24 23:29:09 rooExtend rooExtend[8742]: ***** Started HTTP-Server at Port 10.1.1.55:80
    Apr 24 23:29:09 rooExtend rooExtend[8742]: ***** rooExtend got paired with CORE
    Apr 24 23:29:28 rooExtend rooExtend[8742]: ----- License Manager initialized...
    Apr 24 23:29:28 rooExtend rooExtend[8742]: ##### Stop: Network Audio
    Apr 24 23:29:28 rooExtend rooExtend[8742]: ##### Stop: Roon Bridge
    Apr 24 23:29:28 rooExtend rooExtend[8959]: ***** set HighSpeed 0
    Apr 24 23:29:28 rooExtend rooExtend[8959]: ##### Start: rooDial 1.5.7
    Apr 24 23:29:28 rooExtend rooExtend[8959]: ***** events disconnected
    Apr 24 23:29:28 rooExtend rooExtend[8959]: ***** rooDial got paired with CORE
    Apr 24 23:30:01 rooExtend rooExtend[8742]: ***** rooDial got unpaired by CORE
    Apr 24 23:30:01 rooExtend rooExtend[8959]: ***** Stop: bluetooth
    Apr 24 23:30:01 rooExtend rooExtend[8959]: ***** events disconnected
    Apr 24 23:30:01 rooExtend rooExtend[8742]: ***** rooExtend got unpaired by CORE
    Apr 24 23:30:01 rooExtend rooExtend[8742]: ===== Aborted by unpairing rooExtend =====
    Apr 24 23:30:01 rooExtend rooExtend[8742]: ***** Worker rooDial error: Error: write EPIPE
    Apr 24 23:30:01 rooExtend rooExtend[8742]: ##### Terminated: rooDial with code: 2
    Apr 24 23:30:04 rooExtend rooExtend[8742]: Terminated successfull
    Apr 24 23:30:05 rooExtend systemd[1]: rooExtend.service: Succeeded.
    Apr 24 23:30:05 rooExtend systemd[1]: rooExtend.service: Consumed 8.989s CPU time.
    Apr 24 23:30:15 rooExtend systemd[1]: rooExtend.service: Scheduled restart job, restart counter is at 6.
    Apr 24 23:30:15 rooExtend systemd[1]: Stopped rooExtend service.
    Apr 24 23:30:15 rooExtend systemd[1]: rooExtend.service: Consumed 8.989s CPU time.
    Apr 24 23:30:15 rooExtend systemd[1]: Started rooExtend service.
    Apr 24 23:30:15 rooExtend rooExtend[9039]: Verifying archive integrity...
    Apr 24 23:30:16 rooExtend rooExtend[9076]: [160B blob data]
    Apr 24 23:30:16 rooExtend rooExtend[9039]:  MD5 checksums are OK. All good.
    Apr 24 23:30:16 rooExtend rooExtend[9039]: Uncompressing rooExtend
    Apr 24 23:30:18 rooExtend rooExtend[9138]: [160B blob data]
    Apr 24 23:30:18 rooExtend rooExtend[9183]: --------------------------------------------------
2 Likes

Top! Thank you for that feature. Now I don’t have to restart my RasPi only because I want to see the artist-pictures. thumbs-up

1 Like

Thank you @DrCWO for adding this facility. Very handy to have an idea how few memory is allocated by rooExtend.
Kind regards, Frank.

1 Like

Thanks so much for implementing this so quickly. Works great and is quick to reload. Only wish I had asked sooner :wink:

1 Like

Quick update regarding the state of the new rooMax Roon Extension that interconnects the XenceLabs Quick Keys controller to Roon.

Today my first proof of concept had worked :grinning: :grinning: :grinning:

I can connect to the device plus change volume with the device. Also I can display the volume in real time on its display. I‘m very happy this works now. Very stable and I also tested with a distance of 10m without any issue :+1:

Hope I can finish a first release till end of May.

Best DrCWO

8 Likes