Moode Audio Player for Raspberry Pi

TimCurtis · 2018-02-18 1:09 pm

klicker09 said:
Hello,
i have installed the newest version of moode.
When Ethernet is connected, everything works just fine.

But when i diconnect Ethernet, reboot the PI with the PI Display, i the chromium Browser starts up, but in the Playback Tab i could only see a white Scrren in the middle with light grey buttons.

If i connect a Tablet over Wifi, the Webside is normal to see, but not on the PI Display itself.

MPD seems to work, the music plays normal after the Reboot.

Nothing helps here, no reboot, nothing.
What could be the Problem.

I want to use it only with wifi, so no ethernet needed.

If i press on browse, sometimes the middle part of tghe display comes back, but from 10 tests, only 2 times.

Any Ideas what i can do?

Best regards, Mirko

Hi Mirko,

try iwconfig command and see what the WiFi signal looks like

Example from my Pi-Touch, Pi-3B, Edimax 7811Un

Code:

pi@rp5:~ $ iwconfig
Ethan      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"AirnetN2"  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 60:45:CB:B1:CB:78   
          Bit Rate:150 Mb/s   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          [COLOR="Red"]Link Quality=100/100  Signal level=95/100  Noise level=0/100[/COLOR]
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

pi@rp5:~ $

-Tim

TimCurtis · 2018-02-18 1:20 pm

stevefast said:
Hi,

I'm running moode4.0 on Pi2b+iqaudioDac+ and Pi3+IqaudioDac+

On both systems I have a "pop"-Noice on every skip to the next/previous" playlistentry (mpc play next etc.). (BTW: one of my amps is able to suppress the Nois; on Headphone i can hear it ever - even on my other amp). The noise ist independend of the volume (Volumecontrol set to hardware in mpd-settings).

Anyone with the same Problem?
Any idea for a solution?
Maybe Pulseaudio?

----------------------------------------
Audio information
INPUT PROCESSING
Source: http://ndr-ndr2-niedersachsen.cast.addradio.de/ndr/ndr2/niedersachsen/mp3/128/stream.mp3
Encoded at: VBR compression
Decoded to: 24 bit, 44.1 kHz, Stereo
Rate: 128 kbps
DSP OPERATIONS
Resampling: off
Crossfeed: off
Equalizer: Graphic EQ: (off), Parametric EQ: (off}
Crossfade: 0 seconds
Other: Volume normalize (no}, Replaygain (off)
Chip options: FIR interpolation with de-emphasis, gain=0 dB, boost=.8 dB
Volume ctl: Hardware (on-chip volume controller)
OUTPUT STREAM
Format: 24 bit, 44.1 kHz, Stereo
Rate: 2.117 mbps
AUDIO DEVICE
Device: IQaudIO Pi-DAC+
Chip: Burr Brown PCM5122
Architecture: Sigma/Delta Advanced Segment 24 bit 192 kHz
Interface: I2S
-------------------------------------

Any thoughts welcome.

no1spod said:
yeah it only works on one of mine, I still get the pop when it starts, but you can skip tracks etc with no pops.

it's a hardware/driver issue on those cards as it does it no matter what the os/player is.

I do notice it is worse on pi3.

I agree it certainly seems like a hardware/chip issue. All my PCM5xxx boards have the "bump" but my Mambo LS and BerryNOS (TDA1543) boards are totally glitch free. Don't know if there is any way to compensate for this in MPD but it might be a good question for MaxK.

It happens when manually changing tracks but not when not when tracks transition automatically within playlist.

The link below has some info on the issue.
Click/Pop/Crack when changing tracks : Raspberry Pi • RuneAudio Forum

-Tim

klicker09 · 2018-02-18 1:24 pm

Hi Tim,

here is the reault of iwconfig on my PI:

/var/log$ iwconfig
eth0 no wireless extensions.

lo no wireless extensions.

wlan0 IEEE 802.11 Mode:Master Tx-Power=31 dBm
Retry short limit:7 RTS thr

ff Fragment thr

ff
Power Management

n

But i Think, it is a booting Problem, when i look in the moode.log, i could see, that it took a long time to start the mpd. service.

Code:

20180218 133915 worker: - Start
20180218 133916 worker: Successfully daemonized
20180218 133916 worker: - Init
20180218 133916 worker: Session loaded
20180218 133916 worker: Debug logging (off)
20180218 133922 worker: Host (SQPi)
20180218 133922 worker: Hdwr (Pi-3B 1GB v1.2)
20180218 133922 worker: Arch (armv7l)
20180218 133922 worker: Kver (4.9.79-v7+)
20180218 133922 worker: Ktyp (Standard)
20180218 133922 worker: Gov  (performance)
20180218 133922 worker: Rel  (Moode 4.0 2018-01-26)
20180218 133922 worker: Upd  (None)
20180218 133922 worker: MPD  (0.20.12)
20180218 133922 worker: USB boot not enabled yet
20180218 133922 worker: File system expanded
20180218 133922 worker: HDMI port off
20180218 133923 worker: File check ok
20180218 133923 worker: - Network
20180218 133923 worker: eth0 exists
20180218 133923 worker: eth0 address not assigned
20180218 133923 worker: wlan0 exists
20180218 133923 worker: wlan0 SSID is blank
20180218 133923 worker: wlan0 AP mode started
20180218 133940 command/moode: Connection to MPD failed
20180218 133942 command/moode: Connection to MPD failed
20180218 133955 worker: wlan0 wait 0 for IP address
20180218 133959 worker: wlan0 wait 1 for IP address
20180218 134002 worker: wlan0 (172.24.1.1)
20180218 134002 worker: - Audio
20180218 134002 worker: ALSA outputs unmuted
20180218 134002 worker: Audio out (I2S audio device)
20180218 134002 worker: Audio dev (HiFiBerry Digi+ Pro)
20180218 134002 worker: ALSA mixer name (Digital)
20180218 134002 worker: MPD volume control (disabled)
20180218 134002 worker: Hdwr volume controller not detected
20180218 134002 worker: - Services
20180218 134004 worker: MPD started
20180218 134004 worker: MPD scheduler policy (time-share)
20180218 134004 worker: MPD output 1 ALSA default (on)
20180218 134004 worker: MPD output 2 ALSA crossfeed (off)
20180218 134004 worker: MPD output 3 ALSA parametric eq (off)
20180218 134004 worker: MPD output 4 ALSA graphic eq (off)
20180218 134004 worker: MPD crossfade (off)
20180218 134004 worker: - Last
20180218 134004 worker: USB sources (THE-STICK)
20180218 134004 worker: NAS sources (mountall initiated)
20180218 134004 worker: Volume level (0) restored
20180218 134004 worker: Auto-playing id (11)
20180218 134004 worker: Maintenance interval (21600)
20180218 134004 worker: Watchdog started
20180218 134004 worker: Ready

I tested it in the last few hours and it looks like, right after the Wlan goes online, i could make a refresh on the PI screen and the Display is OK.

So the screen comes to early i would, is this possible?

Best Regards, Mirko

kekkosslovakia · 2018-02-18 1:58 pm

TimCurtis said:
I agree it certainly seems like a hardware/chip issue. All my PCM5xxx boards have the "bump" but my Mambo LS and BerryNOS (TDA1543) boards are totally glitch free. Don't know if there is any way to compensate for this in MPD but it might be a good question for MaxK.

It happens when manually changing tracks but not when not when tracks transition automatically within playlist.

The link below has some info on the issue.
Click/Pop/Crack when changing tracks : Raspberry Pi • RuneAudio Forum

-Tim

I only have this problem with the combination of IQaudIO Pi-DAC+ and Pi-AMP+.
All the other boards(Pi-DigiAMP+, Pi-DAC PRO, Pi-DAC+, Pi-DACZero and Pi-Digi+)I have are glitch free.

Below is the answer from Gordon when I asked about the problem.

"This has been seen with various files where the audio format changes.
Depending on the file being played you may find that altering the auto mute in alsamixer has an effect."

Regards
Janne

astropuppy · 2018-02-18 9:33 pm

Finally got around to installing MoOde 4.0 on a PI3 with a HiFiberry DAC this afternoon. All I can say is "WOW" donation sent. GUI is vastly improved over 3.x.

Not sure whom is responsible for the 4.0 install/build script. Thank you, everything went without a hitch.

Great Work!

TimCurtis · 2018-02-18 10:45 pm

klicker09 said:

Hi Tim,

here is the reault of iwconfig on my PI:

/var/log$ iwconfig
eth0 no wireless extensions.

lo no wireless extensions.

wlan0 IEEE 802.11 Mode:Master Tx-Power=31 dBm
Retry short limit:7 RTS thr

ff Fragment thr

ff
Power Management

n

But i Think, it is a booting Problem, when i look in the moode.log, i could see, that it took a long time to start the mpd. service.

Code:

20180218 133915 worker: - Start
20180218 133916 worker: Successfully daemonized
20180218 133916 worker: - Init
20180218 133916 worker: Session loaded
20180218 133916 worker: Debug logging (off)
20180218 133922 worker: Host (SQPi)
20180218 133922 worker: Hdwr (Pi-3B 1GB v1.2)
20180218 133922 worker: Arch (armv7l)
20180218 133922 worker: Kver (4.9.79-v7+)
20180218 133922 worker: Ktyp (Standard)
20180218 133922 worker: Gov  (performance)
20180218 133922 worker: Rel  (Moode 4.0 2018-01-26)
20180218 133922 worker: Upd  (None)
20180218 133922 worker: MPD  (0.20.12)
20180218 133922 worker: USB boot not enabled yet
20180218 133922 worker: File system expanded
20180218 133922 worker: HDMI port off
20180218 133923 worker: File check ok
20180218 133923 worker: - Network
20180218 133923 worker: eth0 exists
20180218 133923 worker: eth0 address not assigned
20180218 133923 worker: wlan0 exists
20180218 133923 worker: wlan0 SSID is blank
20180218 133923 worker: wlan0 AP mode started
20180218 133940 command/moode: Connection to MPD failed
20180218 133942 command/moode: Connection to MPD failed
20180218 133955 worker: wlan0 wait 0 for IP address
20180218 133959 worker: wlan0 wait 1 for IP address
20180218 134002 worker: wlan0 (172.24.1.1)
20180218 134002 worker: - Audio
20180218 134002 worker: ALSA outputs unmuted
20180218 134002 worker: Audio out (I2S audio device)
20180218 134002 worker: Audio dev (HiFiBerry Digi+ Pro)
20180218 134002 worker: ALSA mixer name (Digital)
20180218 134002 worker: MPD volume control (disabled)
20180218 134002 worker: Hdwr volume controller not detected
20180218 134002 worker: - Services
20180218 134004 worker: MPD started
20180218 134004 worker: MPD scheduler policy (time-share)
20180218 134004 worker: MPD output 1 ALSA default (on)
20180218 134004 worker: MPD output 2 ALSA crossfeed (off)
20180218 134004 worker: MPD output 3 ALSA parametric eq (off)
20180218 134004 worker: MPD output 4 ALSA graphic eq (off)
20180218 134004 worker: MPD crossfade (off)
20180218 134004 worker: - Last
20180218 134004 worker: USB sources (THE-STICK)
20180218 134004 worker: NAS sources (mountall initiated)
20180218 134004 worker: Volume level (0) restored
20180218 134004 worker: Auto-playing id (11)
20180218 134004 worker: Maintenance interval (21600)
20180218 134004 worker: Watchdog started
20180218 134004 worker: Ready

I tested it in the last few hours and it looks like, right after the Wlan goes online, i could make a refresh on the PI screen and the Display is OK.

So the screen comes to early i would, is this possible?

Best Regards, Mirko

Hi Mirko,

Output from your ifconfig cmd does not look right. It should look like below showing SSID, access point MAC, Link qual, etc...

-Tim

Code:

pi@rp3:~ $ iwconfig
eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"AirnetN2"  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 60:45:CB:B1:CB:78   
          Bit Rate:150 Mb/s   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=100/100  Signal level=97/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

pi@rp3:~ $

TimCurtis · 2018-02-18 11:04 pm

kekkosslovakia said:
I only have this problem with the combination of IQaudIO Pi-DAC+ and Pi-AMP+.
All the other boards(Pi-DigiAMP+, Pi-DAC PRO, Pi-DAC+, Pi-DACZero and Pi-Digi+)I have are glitch free.

Below is the answer from Gordon when I asked about the problem.

"This has been seen with various files where the audio format changes.
Depending on the file being played you may find that altering the auto mute in alsamixer has an effect."

Regards
Janne

Hi Janne,

Audio format or that odd alsa setting have never been attributed to this particular PCM5xxx glitch in my experience.

Its easy enough to reproduce but debugging would require expertise in the low-level functions of the audio device, ALSA API and MPD.

-Tim

TimCurtis · 2018-02-18 11:07 pm

astropuppy said:
Finally got around to installing MoOde 4.0 on a PI3 with a HiFiberry DAC this afternoon. All I can say is "WOW" donation sent. GUI is vastly improved over 3.x.

Not sure whom is responsible for the 4.0 install/build script. Thank you, everything went without a hitch.

Great Work!

Thanks go to @koda59 and @HeeBoo for the nice Builder, and to @swizzle for the new, modern UI with its extra nice Adaptive-ness

-Tim

TheOldPresbyope · 2018-02-18 11:44 pm

TimCurtis said:

Hi Mirko,

Output from your ifconfig cmd does not look right. It should look like below showing SSID, access point MAC, Link qual, etc...

-Tim

Code:

pi@rp3:~ $ iwconfig
eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"AirnetN2"  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 60:45:CB:B1:CB:78   
          Bit Rate:150 Mb/s   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=100/100  Signal level=97/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

pi@rp3:~ $

Ummm, Tim, looks like @klicker09 is running an RPi3B in AP mode. Here's my output for same:

Code:

pi@moode-001:~ $ iwconfig
eth0      no wireless extensions.

wlan0     IEEE 802.11  Mode:Master  Tx-Power=31 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          
lo        no wireless extensions.

Same.

Regards,
Kent

TimCurtis · 2018-02-18 11:52 pm

Hi Kent,

For sure I missed that in his moode log output :-0

20180218 133923 worker: wlan0 AP mode started

I'll try and repro

-Tim

TimCurtis · 2018-02-19 12:08 am

Hi Kent,

I changed to AP mode on my Pi Touch and initially got the odd white panel but when I selected Refresh from the moOde menu all was good.

Could be a Chrome Browser cache thing --or-- maybe my results were successful due to the new nohook param in dhcpcd.conf thats part of moOde 41, hard to say.

-Tim

keithg · 2018-02-19 12:23 am

koda59 said:
About not mounting NAS, look via SSH if /mnt/NAS exists ?
If /mnt/NAS is not here, just type :
sudo mkdir /mnt/NAS
... and try again to mount it via UI

Very weird ... same problem on two different SD Cards

So I hoped that whatever glitch was keeping me from finishing a build was gone this morning. So, I tried again from scratch. I was patient and after a couple power cycle reboots, it finished without error and came up. I then logged in and enabled the iqaudio dac+ driver and rebooted. That came up fine. THen I tried to add my NAS shares (smb from freenas 11.0) and now it is locked up. I can SSH in, I can get the default web page, I select configuration, I select sources, but nothing happens. I can close the configuration window and go back to the default interface but cannot add my music files nor delete it. 'df' shows nothing mounted, dmesg shows no errors. /var/log/moodeaudio.log shows

Code:

...
20180218 212809 wrk_sourcemount(): Mount error: (username specified with no parameter)

I do not need a password to mount them in Rune nor from any of my Linux machines. What do I need to do to reset this?

TimCurtis · 2018-02-19 1:33 am

keithg said:
So I hoped that whatever glitch was keeping me from finishing a build was gone this morning. So, I tried again from scratch. I was patient and after a couple power cycle reboots, it finished without error and came up. I then logged in and enabled the iqaudio dac+ driver and rebooted. That came up fine. THen I tried to add my NAS shares (smb from freenas 11.0) and now it is locked up. I can SSH in, I can get the default web page, I select configuration, I select sources, but nothing happens. I can close the configuration window and go back to the default interface but cannot add my music files nor delete it. 'df' shows nothing mounted, dmesg shows no errors. /var/log/moodeaudio.log shows

Code:

... 20180218 212809 wrk_sourcemount(): Mount error: (username specified with no parameter)

I do not need a password to mount them in Rune nor from any of my Linux machines. What do I need to do to reset this?

Hi,

Just enter a bogus userid and password for now, for example guest, guest.

Upcoming moOde 4.1 includes a Samba share scanner and much better input validation for example userid cannot be blank, friendly name cannot already exist, no leading slashes in server etc..

-Tim

keithg · 2018-02-19 3:58 am

Tim,

I cannot remove the mount point. I click confirm and It just hangs there. I can play internet radio, but cannot mount and play anything off my nas. I even tried to put in the runeaudio options "cache=none,noserverino,ro", and it does not stick. Is there a way to reset the database from the command line. The UI does not seem to respond. This is on a Pi3.

Keith

klicker09 · 2018-02-19 6:26 am

Hello Tim,

thanks for the Test.

This is the same thing i see.
When connected to ETH0 this dosnt happend, only when its in Wlan Only mode.

Normaly no refresh is needed.

When i look in the moode.log, i see that there is a Point where ETH0 is enabled.
But in the Settings, i have ETH0 disabled, this settings seems to take place a little bit later.
So the Chromium Browser is already running before ETH0 is disabled.

This could be the cause for this display Problem?

Best Regards, Mirko

TimCurtis said:
Hi Kent,

I changed to AP mode on my Pi Touch and initially got the odd white panel but when I selected Refresh from the moOde menu all was good.

Could be a Chrome Browser cache thing --or-- maybe my results were successful due to the new nohook param in dhcpcd.conf thats part of moOde 41, hard to say.

-Tim

moshel · 2018-02-19 7:11 am

Hi,

I have recently upgraded my 0.38 to 0.40. I have one really nice dsd file i used to play easily on the 0.38 but now it plays with small pauses every 2 seconds or so.

Anything i forgot? Anything changed? Any ideas?
Best regards
Moshe

thanhvo31 · 2018-02-19 7:35 am

For guys who suffer from samba issue with Moode 4.0 Newest kernel Linux moode 4.14.18-v7+ #1093 SMP Fri Feb 9 15:33:07 GMT 2018 armv7l GNU/Linux
Add to vers =2.0 to Mount flags = ro,dir_mode=0777,file_mode=0777,vers=2.0.

philrandal · 2018-02-19 7:54 am

thanhvo31 said:
For guys who suffer from samba issue with Moode 4.0 Newest kernel Linux moode 4.14.18-v7+ #1093 SMP Fri Feb 9 15:33:07 GMT 2018 armv7l GNU/Linux
Add to vers =2.0 to Mount flags = ro,dir_mode=0777,file_mode=0777,vers=2.0.

It depends on what is presenting the CIFS share.

In my case I needed both sec=ntlm and vers=1.0

No one size fits all.

Cheers.

Phil

streamerguy · 2018-02-19 10:31 am

streamerguy said:
Hi Kent,

Thanks for your answer!
I will build a fresh install tomorrow (to make sure everything is standard Moode 4.0) and will only use the internal audio output.
I'll keep you posted.

Regards

Hi Kent,

I installed a fresh Moode 4.0 without any modifications build and let it run for more then 24 hours using the internal audio output, no freezes.
After connecting the DAC, the Pi froze within an hour. Because I had a ssh session running I was able to capture the following messages:

pi@raspberrypi4:~ $
Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.173769] skbuff: skb_over_panic: text:8054f268 len:1526 put:1526 head:ac270440 data:ac270482 tail:0x705f6 end:0x222 dev:eth0

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.178144] Internal error: Oops - BUG: 0 [#1] SMP ARM

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.199867] Process swapper/0 (pid: 0, stack limit = 0x80c00210)

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.201170] Stack: (0x80c01d48 to 0x80c02000)

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.202462] 1d40: 000005f6 ac270440 ac270482 000705f6 00000222 b9558800

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.205107] 1d60: 80c01d84 00000222 80c01d94 80c01d78 80618498 806167cc b9558d00 b9171f00

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.207779] 1d80: adc286c0 00000000 80c01dbc 80c01d98 8054f268 80618444 60000113 00000000

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.210447] 1da0: b9171f00 60000113 00000000 00000000 80c01ddc 80c01dc0 80559254 8054f240

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.213143] 1dc0: b6414e80 b9171f00 b9171f00 00000000 80c01dfc 80c01de0 80559380 805591e0

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.215975] 1de0: bab422d0 b6414e80 b9568000 b9171f00 80c01e24 80c01e00 80583408 80559340

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.218935] 1e00: 80c01e44 20000113 804eda0c b94eb940 b94eb944 00000000 80c01e34 80c01e28

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.222020] 1e20: 805924b8 805833a8 80c01e5c 80c01e38 80123138 805924a4 801230c4 80c02080

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.225273] 1e40: 00000000 80c00020 00000100 b9c05180 80c01ec4 80c01e60 8010169c 801230d0

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.228600] 1e60: 8017440c 8071bb84 00000001 00200100 80c02d00 00010b41 0000000a 80c7b980

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.232008] 1e80: 80c72798 80c0312c 80b793b8 80c02080 80c01e60 00000001 801732e0 80b7cec4

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.235475] 1ea0: 00000000 00000000 00000001 b9c05180 80c00000 babffa40 80c01ed4 80c01ec8

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.238963] 1ec0: 80122ccc 8010151c 80c01efc 80c01ed8 80173910 80122bcc 80c01f18 80c04670

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.242453] 1ee0: 60000013 ffffffff 80c01f4c 80c723fd 80c01f14 80c01f00 8010150c 801738ac

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.245946] 1f00: 80c040a4 80108a58 80c01f74 80c01f18 8071c3bc 80101470 00000000 ba35c470

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.249442] 1f20: 00000000 00000000 80c00000 80c0312c 00000001 80c03198 80c723fd 80c723fd

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.252936] 1f40: babffa40 80c01f74 80c040a4 80c01f68 80108a54 80108a58 60000013 ffffffff

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.256432] 1f60: 80108a54 00000000 80c01f84 80c01f78 8071bb14 80108a30 80c01f9c 80c01f88

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.259928] 1f80: 80162020 8071baec 808023f0 ffffffff 80c01fac 80c01fa0 80716324 80161f48

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.263424] 1fa0: 80c01ff4 80c01fb0 80b00d28 807162ac ffffffff ffffffff 00000000 80b006f8

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.266921] 1fc0: 00000000 80b56a30 00000000 80c7b294 80c0311c 80b56a2c 80c089a8 0000406a

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.270417] 1fe0: 410fd034 00000000 00000000 80c01ff8 0000807c 80b00980 00000000 00000000

Message from syslogd@raspberrypi4 at Feb 17 18:16:08 ...
kernel:[ 984.340488] Code: e58dc014 e58d500c e58d4010 ebefcea0 (e7f001f2)

-----------------------------------------------------------------------------------------------------------------------------------------

Session stopped

These issues never happened on Moode 3.7, so at this moment I'm stuck on 3.7.
Is there anything left I can try regarding settings in the cmdline.txt /config.txt / kernel /drivers etc.?

Thanks and regards.

kaspersone · 2018-02-19 11:34 am

Spotify

TimCurtis said:
Well sure, if u install something thats not included in moOde then of course altering the configs is usually necessary. I was referring to the configs that are managed by moOde.

Btw, moOde doesn't include Spotify Connect due to the 100% initial volume issue, but it looks like some devs have begun to work on librespot again so hopefully this will be fixed.

-Tim

Hi Tim,

They have fixed the initial volume - you can set the initial volume in the config now. Its 50% for standard (instead of the previously 100%)
Options * librespot-org/librespot Wiki * GitHub

Option
initial-volume
Initial volume in %, once connected [0-100]
VOLUME

Moode Audio Player for Raspberry Pi

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member