Posts: 22
Threads: 4
Joined: Dec 2023
Reputation:
0
01-07-2024, 01:32 AM
(This post was last modified: 01-07-2024, 01:35 AM by SerbJ.)
(01-06-2024, 09:34 PM)TheOldPresbyope Wrote: @SerbJ
I owe you an apology. I had too many browser tabs open and thought I was posting my question to a different thread. Please disregard it.
Regards,
Kent
Don't feel bad, I missed your post on the end of the first page! Just saw it.
From ALSACAP got:
Sample Formats: S16_LE, S32_LE, SPECIAL, DSD_U32_BE
Audio Info Reported outputing PCM 32bit, 44.1KHz, stereo
Using the shell and alsamixer I might have found something. I don't understand all the pieces, but looks like the L/R volume is set as low as it can go. When I compare it to the Peachtree, it is set to 100/100 for L/R. I'd post the screen capture, but looks like I'd have to host the pic someplace.
Tomorrow, I am going to raise the L/R volume and see what happens.
Posts: 6,208
Threads: 184
Joined: Apr 2018
Reputation:
249
(01-07-2024, 01:32 AM)SerbJ Wrote: (01-06-2024, 09:34 PM)TheOldPresbyope Wrote: @SerbJ
I owe you an apology. I had too many browser tabs open and thought I was posting my question to a different thread. Please disregard it.
Regards,
Kent
Don't feel bad, I missed your post on the end of the first page! Just saw it.
From ALSACAP got:
Sample Formats: S16_LE, S32_LE, SPECIAL, DSD_U32_BE
Audio Info Reported outputing PCM 32bit, 44.1KHz, stereo
Using the shell and alsamixer I might have found something. I don't understand all the pieces, but looks like the L/R volume is set as low as it can go. When I compare it to the Peachtree, it is set to 100/100 for L/R. I'd post the screen capture, but looks like I'd have to host the pic someplace.
Tomorrow, I am going to raise the L/R volume and see what happens.
Actually, that was what I was headed toward but I conflated your thread with another which dealt with an HDMI issue.
You can add an image file by first adding it as a new attachment and then inserting the attachment into the post---check out the Attachments block below the post entry box.
Here's an example looking at my Khadas Tone 1 board (a USB DAC).
I've chosen the Hardware volume control setting under Output device in the Audio config panel, the Max volume setting under ALSA options is 100%, and the volume knob in the moOdeUI is set to 19.
Regards,
Kent
Posts: 22
Threads: 4
Joined: Dec 2023
Reputation:
0
01-07-2024, 09:35 AM
(This post was last modified: 01-07-2024, 09:44 AM by SerbJ.)
Thx, again.
If I set the Moode param to 0db it indeed goes to 100%.
I think that the listening test today, will go well.
If so, is there a way to configure so it is defaulted, and can still use S/W volume control?
Posts: 6,208
Threads: 184
Joined: Apr 2018
Reputation:
249
01-07-2024, 02:50 PM
(This post was last modified: 01-07-2024, 02:51 PM by TheOldPresbyope.)
@ SerbJ
There are two vertical columns in your (and my) alsamixer panel. The left-hand column is a graphical representation of the L/R (e.g., stereo) volume settings being passed to the driver for the DAC (which are related to the dB numbers in the text in the upper left-hand corner). The right-hand column is the Mono volume setting for...actually I don't know what the heck the "extra" mono mixer is. There can be even more mixers depending on the DAC, but I believe this left-hand column is the "main" mixer, so to speak. The "00" at the base of each column means neither is muted in ALSA.
If your moOde Audio config is set for Volume type: Hardware, then the L/R readings should track the moOde volume knob setting. If, however, the Volume type: is Software or Fixed or CamillaDSP, then the L/R readings will jump to 100/100 (0dB). This means that moOde/ALSA are controlling the amplitude of the PCM streamed to the DAC rather than telling the DAC to control the volume.
The alsamixer panel you posted suggests to me you have selected Volume type: Hardware and had the moOdeUI volume knob set to 0 at the moment of the image capture.
Like Wiley Coyote running off a cliff in a Road Runner cartoon and not being aware of it until he looks down, I may be running off the ALSA cliff in my meanderings and not know it yet. I'm sure someone more knowledgeble will correct me if I am.
Regards,
Kent
Posts: 22
Threads: 4
Joined: Dec 2023
Reputation:
0
(01-07-2024, 02:50 PM)TheOldPresbyope Wrote: @SerbJ
There are two vertical columns in your (and my) alsamixer panel. The left-hand column is a graphical representation of the L/R (e.g., stereo) volume settings being passed to the driver for the DAC (which are related to the dB numbers in the text in the upper left-hand corner). The right-hand column is the Mono volume setting for...actually I don't know what the heck the "extra" mono mixer is. There can be even more mixers depending on the DAC, but I believe this left-hand column is the "main" mixer, so to speak. The "00" at the base of each column means neither is muted in ALSA.
If your moOde Audio config is set for Volume type: Hardware, then the L/R readings should track the moOde volume knob setting. If, however, the Volume type: is Software or Fixed or CamillaDSP, then the L/R readings will jump to 100/100 (0dB). This means that moOde/ALSA are controlling the amplitude of the PCM streamed to the DAC rather than telling the DAC to control the volume.
The alsamixer panel you posted suggests to me you have selected Volume type: Hardware and had the moOdeUI volume knob set to 0 at the moment of the image capture.
Like Wiley Coyote running off a cliff in a Road Runner cartoon and not being aware of it until he looks down, I may be running off the ALSA cliff in my meanderings and not know it yet. I'm sure someone more knowledgeble will correct me if I am.
Regards,
Kent
The volume control was set to "Software". That is where it was for the above capture. I set it to "0db" and re-checked the graph, and the L/R was at 100%. BTW, most of this configuring is at my desk, where it is not connected to DAC. I did a quick test this AM, with it still set to "0db", and I have sound! :  I switched it back to "Software," and it still worked. I noticed that "Hardware" was now available for selection. It wasn't there before. What was odd, I did a shutdown, power off, and reboot, expecting it to be muted again, but it was not. ???
I hope to get more time and testing today, but looking positive.
Posts: 6,208
Threads: 184
Joined: Apr 2018
Reputation:
249
Glad to hear you're making progress. Let us know how it goes.
From my perspective, without the same device on my desk so I can repro your problem, I've run out of things to do.
Regards,
Kent
Posts: 22
Threads: 4
Joined: Dec 2023
Reputation:
0
(01-07-2024, 05:31 PM)TheOldPresbyope Wrote: Glad to hear you're making progress. Let us know how it goes.
From my perspective, without the same device on my desk so I can repro your problem, I've run out of things to do.
Regards,
Kent
You and Tim and the MoOde community have been a great help.
Douk did reply to me on 1/4. It was in my spam folder.
Hello，
We have not tested this system, but if the system can recognize it, it can generally be used normally.
Best Regards
Yours Douk Audio
Posts: 22
Threads: 4
Joined: Dec 2023
Reputation:
0
01-08-2024, 02:23 PM
(This post was last modified: 01-08-2024, 02:23 PM by SerbJ.)
I got to use it for about an hour. Everything seems to be working with the Douk now. I guess the R/L output was just "stuck". The Pi/MoOde combo is working better for me than the laptop/fubar2000/MonkeyMote combo. I will be getting more use to the Pi/MoOde over the next couple of months. At least one more will be built. I am intrigued by some of those chassis builds that include LPS, displays, and other modules. That might end up being a third one.
Thx again for all the help to this Linux illiterate!
|
