Posts: 1,538
Threads: 106
Joined: Mar 2018
Reputation:
73
04-05-2022, 10:57 PM
(This post was last modified: 04-05-2022, 11:03 PM by DRONE7.)
(04-05-2022, 09:34 PM)arczar Wrote: (04-05-2022, 06:38 PM)Tim Curtis Wrote: I did a few tests unplugging my Revolution DAC which has a small display that shows the volume in dB and no issues with moOde or the DAC volume being reset to 100%.
What model DAC are u using?
If another user has the same model perhaps they can try and repro your issue. DIY DAC on ak4490, but the most important part responsible for the volume is the USB converter - XMOS DIYINHK.
I forgot important information. After starting the DAC moode shows the previous level of the dash in steps 1-100. Eg 11 which correspond to -58dB. The problem is that instead of showing -58dB then it is 0dB. I enter the ALSAMIXER, and it really is 0dB. I click +, step 12 appears and the volume is -56dB. Magic...
IIRC there are/were 2 versions of the DIYinHK XMOS XU208. One had some firmware that interfaced volume control on Windows based systems and the other didn't.
The second version worked with linux the first version was flakey with Linux.
Is yours an XU208?
Later versions XMOS XCORE-200 XU216 didn't have that problem.
I will see if I can find some info.
----------
bob
Posts: 48
Threads: 7
Joined: Jan 2021
Reputation:
0
(04-05-2022, 12:46 PM)Hello,i use the build in volume control in moode... schliden Wrote: (04-05-2022, 07:51 AM)dad33 Wrote: (04-05-2022, 02:41 AM)schliden Wrote: Hello,
same probleme as i described in the moode 8 thread.
@dad33, is your problem using the built in moOde volume control or with a UPNP control app like Kazoo ?
@Tim Curtis I had previously been using Volumio for well over a year in the same fashion, ie. using Volumio as a UPNP/OpenHome renderer controlled from Kazzo.
Although I had some other issues with Volumio, I never had an issue with volume control.
I note that upmpdcli.conf under Volumio employed Audio Control Hooks:
Code: ## AUDIO CONTROL HOOKS
externalvolumecontrol = 1
getexternalvolume = /tmp/getvolume
onvolumechange = /tmp/setvolume
The audio control hooks in moOde: /etc/upmpdcli.conf are commented out, so not sure how UPNP volume control is actually handled in moOde..
Posts: 13,443
Threads: 305
Joined: Mar 2018
Reputation:
545
(04-05-2022, 09:34 PM)arczar Wrote: (04-05-2022, 06:38 PM)Tim Curtis Wrote: I did a few tests unplugging my Revolution DAC which has a small display that shows the volume in dB and no issues with moOde or the DAC volume being reset to 100%.
What model DAC are u using?
If another user has the same model perhaps they can try and repro your issue. DIY DAC on ak4490, but the most important part responsible for the volume is the USB converter - XMOS DIYINHK.
I forgot important information. After starting the DAC moode shows the previous level of the dash in steps 1-100. Eg 11 which correspond to -58dB. The problem is that instead of showing -58dB then it is 0dB. I enter the ALSAMIXER, and it really is 0dB. I click +, step 12 appears and the volume is -56dB. Magic...
I don't know if this will help troubleshooting but the dmesg output below shows the messages that are logged when power cycling my Rev DAC. Try it on your end and see of there are any errors. First reboot so the dmesg log is cleared.
Code: # Command
dmesg
# Powered off
[ 192.933170] usb 1-1.2: USB disconnect, device number 3
# Powered back on
[ 216.211707] usb 1-1.2: new high-speed USB device number 7 using dwc_otg
[ 216.343088] usb 1-1.2: New USB device found, idVendor=20b1, idProduct=0008, bcdDevice= 1.01
[ 216.343123] usb 1-1.2: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[ 216.343144] usb 1-1.2: Product: Revolution
[ 216.343161] usb 1-1.2: Manufacturer: Allo.com
[ 217.540391] usb 1-1.2: 1:3 : unsupported format bits 0x100000000
[ 217.834052] input: Allo.com Revolution as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.3/0003:20B1:0008.0002/input/input1
[ 217.901994] hid-generic 0003:20B1:0008.0002: input,hidraw0: USB HID v1.10 Device [Allo.com Revolution] on usb-3f980000.usb-1.2/input3
Posts: 159
Threads: 19
Joined: Mar 2020
Reputation:
3
Hello,
since I've been using moOde 8.0.2, I have the same problem of volume adjustment as in the initial post of this thread with the MAFA android app (MPD client): volume jumps to 0 if I try to change it. This didn't occur with moOde 7.6.1.
I use Allo BOSS2 and MiniBOSS DACs.
I will do more tests and let you know.
Thanks,
Romain
Posts: 18
Threads: 2
Joined: Oct 2021
Reputation:
0
Code: [ 5752.031887] usb 1-1.2: new high-speed USB device number 3 using xhci_hcd
[ 5752.163002] usb 1-1.2: New USB device found, idVendor=20b1, idProduct=2009, bcdDevice=24.04
[ 5752.163030] usb 1-1.2: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[ 5752.163051] usb 1-1.2: Product: DIYINHK USB Audio 2.0
[ 5752.163069] usb 1-1.2: Manufacturer: DIYINHK
[ 5752.182464] input: DIYINHK DIYINHK USB Audio 2.0 as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.3/0003:20B1:2009.0001/input/input0
[ 5752.252354] hid-generic 0003:20B1:2009.0001: input,hidraw0: USB HID v1.10 Device [DIYINHK DIYINHK USB Audio 2.0] on usb-0000:01:00.0-1.2/input3
[ 5752.399134] usb 1-1.2: 1:3 : unsupported format bits 0x100000000
[ 5752.412076] usbcore: registered new interface driver snd-usb-audio
This didn't occur with moOde 7.6.1. The problem occurs regardless of whether I use BubbleUPNP on Android or use the original moOde interface in the browser
Posts: 13,443
Threads: 305
Joined: Mar 2018
Reputation:
545
04-07-2022, 06:29 PM
(This post was last modified: 04-07-2022, 06:29 PM by Tim Curtis.)
Looks quite normal. The only difference I see is that in my case the USB port is type 2 using dwc_otg interface and in your case its a USB 3 port which uses the xhci_hcd interface.
It's not obvious to me what might be going on that would cause ALSA volume to be reset to 0 when connecting.
Posts: 48
Threads: 7
Joined: Jan 2021
Reputation:
0
I tested the problem on my second raspberry pi 4b with moode 8.
No volumegoes to zero problems with pi headphone jack and hardware volume control.
It must be a problem with I2S devices.
Posts: 18
Threads: 2
Joined: Oct 2021
Reputation:
0
but the problem doesn't exist at all in version 7.6.1 and earlier ...
Posts: 13,443
Threads: 305
Joined: Mar 2018
Reputation:
545
It could be that changes in the newer OS and Linux kernel that moOde 8 runs on is causing an issue with your particular USB audio device.
The challenge is how to troubleshoot. One approach is to start with plain RaspiOS Bullseye Lite and see what happens in alsamixer and the dmesg log when you power cycle the audio device, but since I don't have the specific hardware that you are using it won't be possible for me to attempt a repro.
If the issue occurs on plain RaspiOS Bullseye Lite you could try posting to the Raspberry Pi Linux repo.
Posts: 159
Threads: 19
Joined: Mar 2020
Reputation:
3
(04-07-2022, 09:28 AM)romain Wrote: Hello,
since I've been using moOde 8.0.2, I have the same problem of volume adjustment as in the initial post of this thread with the MAFA android app (MPD client): volume jumps to 0 if I try to change it. This didn't occur with moOde 7.6.1.
I use Allo BOSS2 and MiniBOSS DACs.
I will do more tests and let you know.
Thanks,
Romain
Problem only occurs with my BOSS2 DAC whereas it works fine with the MINIBOSS. Same install, same moOde version (8.0.2), same mpd settings on both players, the only difference is the I2S device. Changing volume type from hardware to software has no effect.
|