• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

My Kingdom For A Remote Volume Knob! can this be made?

The Kii controller is much more than a remote, you can plug sources into it, so it's not a remote in the traditional sense, and being wired makes sense. It's a remote, but it can also be controlled by another remote control, it has an IR receiver.
Ah, thanks for the update. It's closer to a monitor controller + breakout box I guess.
 
I bought one and it was a mistake.

The KD-1 requires USB for power (no batteries) There isn't any firmware out yet.

Support sent me a link to get firmware for the Device Console. 1.23 beta.

No Bluetooth upgrade yet; to update the MiniDsp Flex's Bluetooth (when the upgrade comes out) you have to load the firmware files onto an android device and then (using MiniDSp Bluetooth) transfer the firmware to the DSP.

So I have a $260.,00 (175 + 60 tariffs + 25 shipping from China) paper weight.

The policy is absolutely no refunds or exchanges o_O

Read the fine print !!
 
Last edited:
I bought one and it was a mistake.

The KD-1 requires USB for power (no batteries)
That was mentioned a few posts back:

Can you run it off a USB power bank?
 
That was mentioned a few posts back:

Can you run it off a USB power bank?
Yes, is just needs 5V.

I was just being through with my experience.
 
We (me and Klaus) currently work on the firmware for this knob:

The firmware - we call it rooOrbital - will connect the knob to rooExtend and therefore will be able to control Roon.

The knob is full metal machined and very solid. It has a rechargeable battery and a display for cover art. It connects via WiFi. This means it works in your complete WiFi zone. Klaus runs a mesh in his house and can carry it around everywhere. I run two WiFi access points (same SSID and credentials) in my loft and also here I can operate it in the whole space. If the signal gets to weak it connects to the nearest access point.

We plan to release it end of this year. It already runs here in our lab but we are still testing, fixing issues and adding features.
 
We (me and Klaus) currently work on the firmware for this knob:

The firmware - we call it rooOrbital - will connect the knob to rooExtend and therefore will be able to control Roon.

The knob is full metal machined and very solid. It has a rechargeable battery and a display for cover art. It connects via WiFi. This means it works in your complete WiFi zone. Klaus runs a mesh in his house and can carry it around everywhere. I run two WiFi access points (same SSID and credentials) in my loft and also here I can operate it in the whole space. If the signal gets to weak it connects to the nearest access point.

We plan to release it end of this year. It already runs here in our lab but we are still testing, fixing issues and adding features.
Looks good
Esp32-s3 and WiFi... how long does the battery last?
 
Esp32-s3 and WiFi... how long does the battery last?
This needs a lot of power saving mechanisms like darken the display reduce CPU speed and set WiFi in power saving mode. We currently have two timers for diming the display the other for going to standby. We still experiment and optimize for power saving.

I can't tell a fix time as it depends on how often you turn the wheel as this wakes up the device either from power saving or from deep sleep. So if you don't touch it it lasts for a lot of days. But my guess is that with a normal load it lasts for two to three day. From seep sleep it take a second or so until the WiFi connection is re-established. From Power saving mode you get a sudden reaction turning the wheel.
 
We (me and Klaus) currently work on the firmware for this knob:

The firmware - we call it rooOrbital - will connect the knob to rooExtend and therefore will be able to control Roon.

The knob is full metal machined and very solid. It has a rechargeable battery and a display for cover art. It connects via WiFi. This means it works in your complete WiFi zone. Klaus runs a mesh in his house and can carry it around everywhere. I run two WiFi access points (same SSID and credentials) in my loft and also here I can operate it in the whole space. If the signal gets to weak it connects to the nearest access point.

We plan to release it end of this year. It already runs here in our lab but we are still testing, fixing issues and adding features.
Tried your Amazon link and got this: "This item cannot be dispatched to your selected delivery location. Please choose a different delivery location." -> (USA) ?

Would this be fully functional with the Minidsp 2x4 Flex ?
 
Would this be fully functional with the Minidsp 2x4 Flex ?
I don't know Minidsp 2x4 Flex. What I described is that it works with Roon using rooExtend and therefore with all Roon Ready devices.
But I have no idea if the Minidsp is Roon Ready.
 
Tried your Amazon link and got this: "This item cannot be dispatched to your selected delivery location. Please choose a different delivery location." -> (USA) ?

Would this be fully functional with the Minidsp 2x4 Flex ?
There are ways to communicate with a Minidsp Flex with devices similar to this using the minidsp-rs API, but not by way of Roon.
 
I've been trying to figure out how to control my MiniDSP SHD volume with my TVs IR remote. I have a Flirc IR receiver, but I would need some kind of control interface over the SHD. The integrated Volumio API is useless, it has volume adjustment of 1-100 with increments of 1 which is 2-3 dB for each increment. minidsp-rs popped up in Google and peoples posts, but I have hard time to make it work. The getting started and configuration parts of the documentation are non-existent. Can you provide assistance, please?

I got a Raspberry Pi 4B which would be the host for the IR receiver, it's connected to the same WLAN as the SHD (static IP: 192.168.1.40). I downloaded the lastest minidsp rs (v0.1.12) armhf.deb package and installed. I've got no idea if the installation is in working order (there were errors initially, but after upgrading and --fix-broken it completed without errors) or if there's something wrong in the network. I added the following lines to /etc/minidsp/config.toml: [[static_device]] and url = "tcp://192.168.1.40:5333". I tried changing the bind_address parameters under http_server and tcp_server, but it's unclear if they are relevant for getting started. I restarted the service each time after making changes to config.toml.

Network check:
Code:
$ ping 192.168.1.40
PING 192.168.1.40 (192.168.1.40) 56(84) bytes of data.
64 bytes from 192.168.1.40: icmp_seq=1 ttl=64 time=3.14 ms
64 bytes from 192.168.1.40: icmp_seq=2 ttl=64 time=1.96 ms
64 bytes from 192.168.1.40: icmp_seq=3 ttl=64 time=2.47 ms
^C
--- 192.168.1.40 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.962/2.526/3.142/0.483 ms

When I do minidsp probe I get no output. minidsp --tcp 192.168.1.40:5333 probe no output. minidsp --url "tcp://192.168.1.40:5333" probe no output. I do get output from:
Code:
$ minidsp
Error: No devices found

$ minidsp probe --net
Probing for network devices...
Error: Address already in use (os error 98)

$ minidsp --tcp 192.168.1.40:5333 status
Error: No devices found

"Address already in use" I stopped the service and tried again:
Code:
$ minidsp probe --net
Probing for network devices...
No network devices detected

What do? Are there other alternatives? :D

PS. I do not have the WI-DG. Would that be mandatory?
 
Last edited:
I've been trying to figure out how to control my MiniDSP SHD volume with my TVs IR remote. I have a Flirc IR receiver, but I would need some kind of control interface over the SHD. The integrated Volumio API is useless, it has volume adjustment of 1-100 with increments of 1 which is 2-3 dB for each increment. minidsp-rs popped up in Google and peoples posts, but I have hard time to make it work. The getting started and configuration parts of the documentation are non-existent. Can you provide assistance, please?

I got a Raspberry Pi 4B which would be the host for the IR receiver, it's connected to the same WLAN as the SHD (static IP: 192.168.1.40). I downloaded the lastest minidsp rs (v0.1.12) armhf.deb package and installed. I've got no idea if the installation is in working order (there were errors initially, but after upgrading and --fix-broken it completed without errors) or if there's something wrong in the network. I added the following lines to /etc/minidsp/config.toml: [[static_device]] and url = "tcp://192.168.1.40:5333". I tried changing the bind_address parameters under http_server and tcp_server, but it's unclear if they are relevant for getting started. I restarted the service each time after making changes to config.toml.

Network check:
Code:
$ ping 192.168.1.40
PING 192.168.1.40 (192.168.1.40) 56(84) bytes of data.
64 bytes from 192.168.1.40: icmp_seq=1 ttl=64 time=3.14 ms
64 bytes from 192.168.1.40: icmp_seq=2 ttl=64 time=1.96 ms
64 bytes from 192.168.1.40: icmp_seq=3 ttl=64 time=2.47 ms
^C
--- 192.168.1.40 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.962/2.526/3.142/0.483 ms

When I do minidsp probe I get no output. minidsp --tcp 192.168.1.40:5333 probe no output. minidsp --url "tcp://192.168.1.40:5333" probe no output. I do get output from:
Code:
$ minidsp
Error: No devices found

$ minidsp probe --net
Probing for network devices...
Error: Address already in use (os error 98)

$ minidsp --tcp 192.168.1.40:5333 status
Error: No devices found

"Address already in use" I stopped the service and tried again:
Code:
$ minidsp probe --net
Probing for network devices...
No network devices detected

What do? Are there other alternatives? :D

PS. I do not have the WI-DG. Would that be mandatory?
I would suggest getting a SofaBaton programmable remote.

Get it from Amazon so you have 30 days to check it out. (Black Friday, maybe get a deal)

I'm using one and so far it has all my components and work fine.
 
this has everything i think we need for a modern controller. Bluetooth, wifi, battery. Now we just need someone to write the software
 
I would still prefer something like BLE with the lowest power consumption possible, like a regular remote, aiming at several months without having to worry about the batteries.
Anything esp32, let alone display and stuff, will have to be charged too often imo.
 

Attachments

  • IMG_1676.jpeg
    IMG_1676.jpeg
    184.5 KB · Views: 92
  • IMG_1677.jpeg
    IMG_1677.jpeg
    198.6 KB · Views: 82
  • IMG_1678.jpeg
    IMG_1678.jpeg
    213.7 KB · Views: 78
  • IMG_1679.jpeg
    IMG_1679.jpeg
    217.8 KB · Views: 92
  • IMG_1680.jpeg
    IMG_1680.jpeg
    213 KB · Views: 85
  • IMG_1681.jpeg
    IMG_1681.jpeg
    235.5 KB · Views: 88
Back
Top Bottom