Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


9.0.8 UI slow when running Camilla
#21
That of course is a good question (* especially for troubleshooting).
UI responsiveness is very livable in both cases but definitely a bit more snappy without camilla. Enjoyable even. So UI is a non issue.
Volume control is actually equally as sluggish without camilla running.

Didnt think of trying that out because without equalization I would forgo any volume control and instead walk to the amp/speakers for "purity" reasons. I havent actually ever critically compared moode's SW Vol. cont. to Vol. off, thats just what I preferred for the brief time when dsp wasnt yet a thing for me. so this is not a critisim of the SW Volume.

I really only care about SQ but with my less 'tech-savvy' friend's setup usability is important to me too. How the volume control behaves bothers me. Dunno why really. I guess because 'it feels kind of broken'.

it goes like so:


64 - 6.76 sec
65 - 2.53 sec
66 - 5.40 sec
67 - 3.80 sec
68 - 7.21 sec  and so on...

dont worry I didnt measure it...nah, I actually did
Reply
#22
Thats very abnormal. What client are you using?
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#23
sorry I dont know what you mean by client in this context . Am I using a client?
1 windows laptop, 2 google pixel phones and a samsung tablet - is that it?
Reply
#24
Yes, the device you are using to display the WebUI.

Generally speaking WebUI performance depends on end-to-end throughput between client and server (Pi), and diagnosing a performance issue involves isolating the bottleneck for example slow or poor quality network connection, slow boot media, slow client, slow software component, etc

Given good end-to-end throuput, typical volume control responsiveness should be < .5sec with or without CamillaDSP volume.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#25
oh.
I just tried a desktop pc that's wired to router - same result.
Reply
#26
(09-17-2024, 03:34 PM)Tim Curtis Wrote: Generally speaking WebUI performance depends on end-to-end throughput between client and server (Pi), and diagnosing a performance issue involves isolating the bottleneck for example slow or poor quality network connection, slow boot media, slow client, slow software component, etc

I sure get that and gratefully follow any advise I'm given.

Can I change volume through a terminal "omitting" the UI or sth.? would that make sense in order to see if it's UI related?
Reply
#27
Try the vol.sh command

Code:
pi@trx:~ $ /var/www/util/vol.sh --help
Usage: vol.sh [OPTION] [VOLUME]
Change the volume and update the knob.

With no OPTION or VOLUME, print the current volume.
With just VOLUME, set current volume to VOLUME.

-up            VOLUME  value between 1 and 100
-dn            VOLUME  value between 1 and 100
-mute          mute or unmute the volume
-restore       set volume to current knob level
--version      print the program version
--help         print this help text
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#28
Good morning,
changing the volume via vol.sh takes several seconds as well.

are there any other settings (mdp, alsa, audio output, volume options) that could cause this?

It couldn't be because the dac board is externally powered, could it?
Reply
#29
Hello,

when I use the Volume slider inside Camilla's GUI Volume changes instantly. The Volume Knob (moode gui) won't be Updated accordingly at all in this Case. 

What does the Volume Knob (with Volume Type Camilla) inside the moode GUI do differenty? How are they "connected"?
Reply
#30
The volume is proxied to CamillaDSP via the mpd2cdspvolume daemon.

Code:
pi@moode:~ $ systemctl status mpd2cdspvolume
● mpd2cdspvolume.service - Synchronize MPD volume to CamillaDSP
    Loaded: loaded (/lib/systemd/system/mpd2cdspvolume.service; disabled; preset: enabled)
    Active: active (running) since Wed 2024-09-18 23:03:57 EDT; 12h ago
  Main PID: 1418 (python)
     Tasks: 1 (limit: 4464)
       CPU: 117ms
    CGroup: /system.slice/mpd2cdspvolume.service
            └─1418 python /usr/local/bin/mpd2cdspvolume --pid_file /var/run/mpd2cdspvol/mpd2cdspvol.pid --volume_state_file /var/lib/cdsp/statefile.yml --config /etc/mpd2cdspvolume.co>

Sep 18 23:03:57 moode systemd[1]: Started mpd2cdspvolume.service - Synchronize MPD volume to CamillaDSP.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply


Forum Jump: