[PROBLEM] Volume issue on moode 8.0.2

[sand87ch]

The volume on moode v8.0.2 is different from what i saw on v7.6.1.

In v761 the volume when connected from airplay will always be set at 0.0db.

So the best thing was in airplay i just  needed to increase the volume on airplay using my phone which was easier.

However since 8.0.2 release the volume after each song will go back to -127db and then we have to manually change the sound on the allo boss 2 since now the control from the phone wont work.I m at a loss here.Have tried various changes to the UI configuration without much result.

Hence i have now reverted to v7.6.1.Any idea how can i make 8.0.2 behave like v7.6.1 volume wise when connected from airplay.

Regards,
Sandeep

[Tim Curtis]

I ran a quick 10 minute test playing tracks from Amazon Music HD and am not able to repro. The volume of the receiver stays at 0dB from track to track.

The Airplay renderer (shairport-sync) is session based which means the following:

- Just prior to starting play it executes an "pre" event script that sets the volume to 0dB
- When play stops it waits for up to "active_state_timeout" number of seconds before ending the session and executing the "post" event script which resets volume to its original value.
- The default value for "active_state_timeout" is 10 s
- There is another timeout named "Session timeout" which is configurable via Audio Config, EDIT Airplay config. It defaults to 120 seconds and handles the condition where the music source disappears (network issue, phone turned off). The 10 sec "active_state_timeout" will still occur but this setting is supposed to maintain the session in case the music source comes back online.

[sand87ch]

I ran a quick 10 minute test playing tracks from Amazon Music HD and am not able to repro. The volume of the receiver stays at 0dB from track to track.

The Airplay renderer (shairport-sync) is session based which means the following:

- Just prior to starting play it executes an "pre" event script that sets the volume to 0dB
- When play stops it waits for up to "active_state_timeout" number of seconds before ending the session and executing the "post" event script which resets volume to its original value.
- The default value for "active_state_timeout" is 10 s
- There is another timeout named "Session timeout" which is configurable via Audio Config, EDIT Airplay config. It defaults to 120 seconds and handles the condition where the music source disappears (network issue, phone turned off). The 10 sec "active_state_timeout" will still occur but this setting is supposed to maintain the session in case the music source comes back online.

Hey Tim,

Really sorry for not being quick to reply.I will reinstall the 8.0.2 and let me get back to you. I will do the following:-

Install the latest version and try again. If this occurs, then I will create a video of this along with a screenshots of the settings I have. Are there any logs i can gather from somewhere which could also be helpful for you to reproduce this if this happens?

Regards,
Sandeep

[sand87ch]

I ran a quick 10 minute test playing tracks from Amazon Music HD and am not able to repro. The volume of the receiver stays at 0dB from track to track.

The Airplay renderer (shairport-sync) is session based which means the following:

- Just prior to starting play it executes an "pre" event script that sets the volume to 0dB
- When play stops it waits for up to "active_state_timeout" number of seconds before ending the session and executing the "post" event script which resets volume to its original value.
- The default value for "active_state_timeout" is 10 s
- There is another timeout named "Session timeout" which is configurable via Audio Config, EDIT Airplay config. It defaults to 120 seconds and handles the condition where the music source disappears (network issue, phone turned off). The 10 sec "active_state_timeout" will still occur but this setting is supposed to maintain the session in case the music source comes back online.

Hey Tim,

I can now confirm this that the volume is at 0.0db while playing tracks via airplay on 8.1.2 64bit version.

However i have noticed one thing(which i dont know if its an issue with my Allo Boss 2 or not)the boot times i.e to start up the moode audio takes a lot of time.sometimes it doesnt even boot and i need to either restart or push the hardware button for it to start.

To speed up boot i did disconnect the integrated BT and WiFi adapter as i am using an external TP Link T2U dual band wifi adapter.The boot speeds were real quick in case of version 7.I saw this low boot speed on 8.0.2 as well as now on 8.1.2.By Slow i mean its pretty much slow like sometimes even after 10 mins you cant connect to the device and its screen doesnt show anything.

[Tim Curtis]

Very odd.

Post the moOde startup log. It will contain time stamps that show how long various moOde startup processes take.

Code:

moodeutl -l

Also post a product link for the particular WiFi adapter you are using.

[sand87ch]

Very odd.

Post the moOde startup log. It will contain time stamps that show how long various moOde startup processes take.

Code:

moodeutl -l

Also post a product link for the particular WiFi adapter you are using.

This is the product page

https://www.tp-link.com/in/home-networki...rcher-t2u/

I have the log.However i am unable to attach .txt or .pdf of the log as when i submit the error pop up says "this type of attachment is not allowed.Please change the file type" and doesnt give any indication as to what type it accepts.

[Tim Curtis]

Just paste the text directly into the post.

[TheOldPresbyope]

Threads on the Raspberry Pi Forum stretching back to 2016 suggest this T2U adapter requires “non-free firmware” that isn’t pre-installed in the Raspberry Pi OS image. Apparently the driver itself now is, although up until a couple of years ago it had to be built by the user or installed ala MrEngMan offerings.

Regards,
Kent

[sand87ch]

Just paste the text directly into the post.

This is the log:-

Code:

pi@moode:~ $ moodeutl -l
20220802 031041 worker: --
20220802 031041 worker: -- Start moOde 8 series
20220802 031041 worker: --
20220802 031041 worker: Successfully daemonized
20220802 031242 worker: File check (OK)
20220802 031242 worker: Session vacuumed
20220802 031242 worker: Session loaded
20220802 031242 worker: Debug logging (OFF)
20220802 031242 worker: --
20220802 031242 worker: -- Audio debug
20220802 031242 worker: --
20220802 031242 worker: ALSA cards: (0:Boss2 | 1:empty | 2:empty | 3:empty
20220802 031242 worker: MPD config: (0:Allo Boss 2 DAC | mixer:(Master) | card:0)
20220802 031242 worker: ALSA mixer actual (Master)
20220802 031242 worker: ALSA Master volume set to (0%)
20220802 031242 worker: --
20220802 031242 worker: -- System
20220802 031242 worker: --
20220802 031244 worker: Host (moode)
20220802 031244 worker: moOde (8.1.2 2022-07-08)
20220802 031244 worker: RaspiOS (11.3)
20220802 031244 worker: Kernel (5.15.32-v8+ #1538)
20220802 031244 worker: Platform (Pi-4B 1.4 4GB)
20220802 031244 worker: ARM arch (aarch64, 64-bit)
20220802 031244 worker: MPD ver (0.23.5)
20220802 031244 worker: CPU gov (ondemand)
20220802 031244 worker: USB boot (enabled)
20220802 031244 worker: File sys (expanded)
20220802 031244 worker: HDMI port (Off)
20220802 031245 worker: Sys LED0 (On)
20220802 031245 worker: Sys LED1 (On)
20220802 031245 worker: --
20220802 031245 worker: -- Network
20220802 031245 worker: --
20220802 031245 worker: eth0 adapter exists
20220802 031245 worker: eth0 check for address (No)
20220802 031245 worker: eth0 address not assigned
20220802 031245 worker: wlan0 adapter exists
20220802 031245 worker: wlan0 country (IN)
20220802 031245 worker: wlan0 connected SSID is (Home-WiFi)
20220802 031245 worker: IP addr (10.0.0.8)
20220802 031245 worker: Netmask (255.255.255.0)
20220802 031245 worker: Gateway (10.0.0.1)
20220802 031245 worker: Pri DNS (10.0.0.1)
20220802 031245 worker: Domain ()
20220802 031246 worker: wlan0 power save disabled
20220802 031246 worker: --
20220802 031246 worker: -- Audio config
20220802 031246 worker: --
20220802 031341 worker: MPD conf updated
20220802 031341 worker: ALSA card number (0)
20220802 031341 worker: MPD audio output (Allo Boss 2 DAC)
20220802 031344 worker: Audio formats (S16_LE, S24_LE, S32_LE)
20220802 031344 worker: ALSA mixer name (Master)
20220802 031344 worker: MPD mixer type (software)
20220802 031344 worker: Hdwr volume controller exists
20220802 031344 worker: Max ALSA volume (100%)
20220802 031344 worker: ALSA output mode (Default: plughw)
20220802 031344 worker: ALSA loopback (Off)
20220802 031344 worker: Boss 2 OLED started
20220802 031344 worker: Reset renderer active flags
20220802 031344 worker: CamillaDSP (off)
20220802 031344 worker: --
20220802 031344 worker: -- MPD startup
20220802 031344 worker: --
20220802 031344 worker: MPD started
20220802 031344 worker: MPD accepting connections
20220802 031344 worker: MPD output 1 ALSA Default (On)
20220802 031344 worker: MPD output 2 ALSA Bluetooth (Off)
20220802 031344 worker: MPD output 3 HTTP Server (Off)
20220802 031344 worker: MPD crossfade (off)
20220802 031344 worker: MPD ignore CUE files (yes)
20220802 031344 worker: Default playlist loaded for first boot
20220802 031344 worker: --
20220802 031344 worker: -- Music sources
20220802 031344 worker: --
20220802 031344 worker: USB sources (none attached)
20220802 031344 worker: NAS sources (none configured)
20220802 031344 worker: --
20220802 031344 worker: -- Feature availability
20220802 031344 worker: --
20220802 031344 worker: Source select (available)
20220802 031344 worker: Source select (source: MPD)
20220802 031344 worker: Source select (output: Allo Boss 2 DAC)
20220802 031344 worker: Bluetooth (available)
20220802 031344 worker: Airplay renderer (available: started)
20220802 031344 worker: Spotify renderer (available)
20220802 031344 worker: Squeezelite (available)
20220802 031344 worker: RoonBridge renderer (not installed)
20220802 031344 worker: Multiroom sender (available)
20220802 031344 worker: Multiroom receiver (available)
20220802 031344 worker: UPnP renderer (available)
20220802 031344 worker: DLNA server (available)
20220802 031344 worker: GPIO button handler (available)
20220802 031344 worker: Stream recorder (n/a)
20220802 031344 worker: --
20220802 031344 worker: -- Other
20220802 031344 worker: --
20220802 031344 worker: USB volume knob (Off)
20220802 031344 worker: Shellinabox SSH started
20220802 031344 worker: USB auto-mounter (udisks-glue)
20220802 031344 worker: Saved MPD vol level (0)
20220802 031344 worker: Preamp volume level (0)
20220802 031344 worker: MPD volume level (0) restored
20220802 031344 worker: ALSA Master volume (100%)
20220802 031344 worker: Auto-play (Off)
20220802 031344 worker: CoverView toggle (-off)
20220802 031344 worker: Maintenance interval (120 minutes)
20220802 031344 worker: Screen saver activation (Never)
20220802 031344 worker: Session permissions (OK)
20220802 031438 worker: Watchdog started
20220802 031503 worker: Read

[TheOldPresbyope]

There are three mysterious time gaps in your log which total about 3-1/2 minutes. I compare this to an Pi4B on my desk running moOde 8.1.2 which just now took about 20 seconds to complete the file check and no time (in recorded seconds) to complete the other two steps. This makes me wonder if your system memory card (uSD? USB?) is up to snuff.

Code:

20220802 031041 worker: Successfully daemonized
20220802 031242 worker: File check (OK)
...
20220802 031246 worker: -- Audio config
20220802 031246 worker: --
20220802 031341 worker: MPD conf updated
...
20220802 031438 worker: Watchdog started
20220802 031503 worker: Read

Regards,
Kent

PS - have to add the usual caveat that the Pi's power supply and power cable have to be of good quality or all sorts of odd behavior can occur.

PPS - I have a 32GB uSD card on my PI4B. I suppose if one had a vastly bigger card, 256GB say, stuffed full of music tracks it might take two minutes to complete the file-system check even if the card were up to snuff but that wouldn't account for the large variability in boot times you reported (up to 10 minutes and waiting). --- I don't recommend putting moOde on a large memory card for various reasons. This possible time delay is one I hadn't thought of.