+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: Official moOde 7.0.1 support thread (/showthread.php?tid=3290)
RE: Official moOde 7.0.1 support thread - Evil_Underlord - 12-29-2020
@TheOldPresbyope
It's a Pixel 4a, non-5G, via the Chrome browser. Everything up to date, but very very slow.
RE: Official moOde 7.0.1 support thread - jmarcusg - 12-29-2020
(12-29-2020, 03:05 AM)TheOldPresbyope Wrote: @oculto
I'm struggling to figure out what to suggest.
I don't have a HiFiBerry Digi+ Pro (nor a downstream audio system with an S/PDIF input) on hand so I can't exactly replicate your setup. To at least work with the I2S interface I installed a HiFi Berry DAC+ Pro on an RPi3B+. Flashed a uSD card with a fresh install of moOde 7.0.0 (which I immediately upgraded to 7.0.1 once I booted).
I can not reproduce any of your issues. This combo works fine communicating wirelessly. it plays the preloaded radio stations. It loads the entire contents of my NAS into its library. It plays through my downstream audio system whether the Auto-Shuffle feature is enabled or not.
Several times you mention behaviors which suggest the mpd process is getting killed (which shouldn't happen). These includeSorry, at this point I don't have any definitive answers. Be sure your power supply, power cable, and power connector are good enough for this application. Poor power can be a source of mysterious problems with any RPi-based audio streamer. I assume the software driver for the HiFiBerry Digi+ Pro is compatible with the kernel 5.4.77-v7+ in moOde 7.0.1 but I have no way of testing that.
- connecct to spotify but gui was unresponsive
- dashboard blank
- connection to mpd failed
You still need to post your logs but if the WebUI is unresponsive you'll have to log into the command line through SSH to be able to get them.
Regards,
Kent
Both Digi+ (RPi 3A+) and Digi+ Pro (RPi 3B+) work for me running 7.0.1
Marc
RE: Official moOde 7.0.1 support thread - TheOldPresbyope - 12-29-2020
(12-29-2020, 03:40 AM)Evil_Underlord Wrote: @TheOldPresbyope
It's a Pixel 4a, non-5G, via the Chrome browser. Everything up to date, but very very slow.
This reminds me that there have been ongoing differences in behavior between Chrome and Firefox browsers on Android phones. I expect it's down to their Javascript engines but no smoking guns have appeared using the browsers' dev tools. (Pure conjecture since I have nothing to do with frontend development.)
What happens if you try Firefox on your Pixel 4a?
In truth I rarely use my phone these days for anything but phone calls and texts now that I have my iPad. It's so much more comfortable to use for reading and for dealing with multimedia.
Also, out of curiosity, how many tracks are in your library? There's not hard and fast rule but big (multiples of 10K) libraries seem to bog down the interface, at least for some devices.
Regards,
Kent
RE: Official moOde 7.0.1 support thread - bitlab - 12-29-2020
(12-29-2020, 01:53 PM)jmarcusg Wrote:(12-29-2020, 03:05 AM)TheOldPresbyope Wrote: @oculto
I'm struggling to figure out what to suggest.
I don't have a HiFiBerry Digi+ Pro (nor a downstream audio system with an S/PDIF input) on hand so I can't exactly replicate your setup. To at least work with the I2S interface I installed a HiFi Berry DAC+ Pro on an RPi3B+. Flashed a uSD card with a fresh install of moOde 7.0.0 (which I immediately upgraded to 7.0.1 once I booted).
I can not reproduce any of your issues. This combo works fine communicating wirelessly. it plays the preloaded radio stations. It loads the entire contents of my NAS into its library. It plays through my downstream audio system whether the Auto-Shuffle feature is enabled or not.
Several times you mention behaviors which suggest the mpd process is getting killed (which shouldn't happen). These includeSorry, at this point I don't have any definitive answers. Be sure your power supply, power cable, and power connector are good enough for this application. Poor power can be a source of mysterious problems with any RPi-based audio streamer. I assume the software driver for the HiFiBerry Digi+ Pro is compatible with the kernel 5.4.77-v7+ in moOde 7.0.1 but I have no way of testing that.
- connecct to spotify but gui was unresponsive
- dashboard blank
- connection to mpd failed
You still need to post your logs but if the WebUI is unresponsive you'll have to log into the command line through SSH to be able to get them.
Regards,
Kent
Both Digi+ (RPi 3A+) and Digi+ Pro (RPi 3B+) work for me running 7.0.1
Marc
Here also no issues with a clean 7.0.1 on Pi2b with a Hifiberry Digi+ Pro.
You can check if the modules are loaded with the following command:
Code:
lsmod | grep wm8804Should return something like:
Code:
pi@moodedev:~ $ lsmod | grep wm8804
snd_soc_wm8804_i2c 16384 1
snd_soc_wm8804 16384 1 snd_soc_wm8804_i2c
regmap_i2c 16384 1 snd_soc_wm8804_i2c
snd_soc_rpi_wm8804_soundcard 16384 1
snd_soc_core 200704 3 snd_soc_rpi_wm8804_soundcard,snd_soc_wm8804,snd_soc_bcm2835_i2s
snd_pcm 94208 4 snd_soc_wm8804,snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_soc_coreNotice the wm8004 drivers; the driver for HB Digi+ Pro are loaded.
Else look in the output of the command dmesg for drivers issues.
RE: Official moOde 7.0.1 support thread - oculto - 12-29-2020
Guy’s, thank you for the attention with this case. I will try again son and post here more details.
BTW, the board i use is a generic chinese hat, with uses dtoverlay=hifiberrydigipro (i spell wrongly because i don’t have it with me now, but i will check the correct dtoverlay on raspbian)
And with this dtoverlay it works flawlessly. The last time i try, the problem occurred after i set the driver and reboot. But before that, i also set the mpd parameters. I will check it latter.
Please inform what logs have the information needed to be properly addressed here. I will post it.
RE: Official moOde 7.0.1 support thread - oculto - 12-29-2020
* * * update: i post a mistake here - the log bellow is using HIFI Digi+ but I already set the correct driver dtoverlay=hifiberry-digi-pro * * *
I few this i found on log...
Code:
20201228 132002 worker: -- Device
20201228 132002 worker: ALSA cards: (0:empty | 1:empty | 2:empty | 3:empty
20201228 132002 worker: Configured: (0:HIFI Digi+ | mixer:(Digital) | alsavol:Invalid card number.)
20201228 132002 worker: ALSA mixer actual (Digital)
20201228 132002 worker: ALSA Digital volume set to (Invalid card number.)
......
20201229 205337 worker: -- Audio
20201229 205338 worker: MPD conf updated
20201229 205338 worker: ALSA outputs unmuted
20201229 205338 worker: ALSA card number (0)
20201229 205338 worker: Audio output (HIFI Digi+)
20201229 205338 worker: Audio formats (cat: /proc/asound/card0/pcm0p/sub0/hw_params: No such file or directory)
20201229 205338 worker: ALSA mixer name (Digital)
20201229 205338 worker: MPD volume control (disabled)
20201229 205338 worker: Hdwr volume controller exists
20201229 205338 worker: Max ALSA volume (100%)
20201229 205338 worker: Reset renderer active flags
.....
20201229 205339 worker: ALSA Digital volume (Invalid card number.)complete log....
Code:
pi@moode:~ $ moodeutl -l
20201228 132001 worker: -- Start
20201228 132001 worker: Successfully daemonized
20201228 132002 worker: Integrity check (passed)
20201228 132002 worker: File check (OK)
20201228 132002 worker: Session loaded
20201228 132002 worker: Debug logging (OFF)
20201228 132002 worker: -- Device
20201228 132002 worker: ALSA cards: (0:empty | 1:empty | 2:empty | 3:empty
20201228 132002 worker: Configured: (0:HIFI Digi+ | mixer:(Digital) | alsavol:Invalid card number.)
20201228 132002 worker: ALSA mixer actual (Digital)
20201228 132002 worker: ALSA Digital volume set to (Invalid card number.)
20201228 132002 worker: -- System
20201228 132003 worker: Host (moode)
20201228 132003 worker: moOde (7.0.1 2020-12-23)
20201228 132003 worker: RaspiOS (10.7)
20201228 132003 worker: Kernel (5.4.77-v7+ #1371)
20201228 132003 worker: Platform (Pi-3B+ 1GB v1.3)
20201228 132003 worker: ARM arch (armv7l, 32-bit kernel)
20201228 132003 worker: MPD ver (0.22.3_p0x3)
20201228 132003 worker: CPU gov (ondemand)
20201228 132003 worker: USB boot enabled
20201228 132003 worker: File system expanded
20201228 132003 worker: HDMI port off
20201228 132003 worker: -- Network
20201228 132003 worker: eth0 exists
20201228 132004 worker: eth0 wait 0 for IP address
20201228 132007 worker: eth0 wait 1 for IP address
20201228 132010 worker: eth0 wait 2 for IP address
20201228 132013 worker: eth0 wait 3 for IP address
20201228 132016 worker: eth0 wait 4 for IP address
20201229 205337 worker: eth0 address not assigned
20201229 205337 worker: wlan0 exists
20201229 205337 worker: wifi country (BR)
20201229 205337 worker: wlan0 trying SSID (SouzaCastro)
20201229 205337 worker: IP addr (192.168.1.109)
20201229 205337 worker: Netmask (255.255.255.0)
20201229 205337 worker: Gateway (192.168.1.1)
20201229 205337 worker: Pri DNS (8.8.4.4)
20201229 205337 worker: Domain (8.8.8.8)
20201229 205337 worker: -- Audio
20201229 205338 worker: MPD conf updated
20201229 205338 worker: ALSA outputs unmuted
20201229 205338 worker: ALSA card number (0)
20201229 205338 worker: Audio output (HIFI Digi+)
20201229 205338 worker: Audio formats (cat: /proc/asound/card0/pcm0p/sub0/hw_params: No such file or directory)
20201229 205338 worker: ALSA mixer name (Digital)
20201229 205338 worker: MPD volume control (disabled)
20201229 205338 worker: Hdwr volume controller exists
20201229 205338 worker: Max ALSA volume (100%)
20201229 205338 worker: Reset renderer active flags
20201229 205338 worker: -- MPD
20201229 205338 worker: MPD started
20201229 205338 worker: MPD accepting connections
20201229 205338 worker: Configure MPD outputs
20201229 205338 worker: MPD output 1 ALSA default (on)
20201229 205338 worker: MPD output 2 ALSA crossfeed (off)
20201229 205338 worker: MPD output 3 ALSA parametric eq (off)
20201229 205338 worker: MPD output 4 ALSA graphic eq (off)
20201229 205338 worker: MPD output 5 ALSA polarity inversion (off)
20201229 205338 worker: MPD output 6 ALSA bluetooth (off)
20201229 205338 worker: MPD output 7 HTTP stream (off)
20201229 205338 worker: MPD crossfade (12 secs)
20201229 205338 worker: -- Feature availability
20201229 205338 worker: Source select (available)
20201229 205338 worker: Source select (source: MPD)
20201229 205338 worker: Source select (output: HIFI Digi+)
20201229 205338 worker: Bluetooth (available)
20201229 205338 worker: Airplay renderer (available)
20201229 205338 worker: Spotify renderer (available)
20201229 205339 worker: Spotify renderer (started)
20201229 205339 worker: Squeezelite renderer (available)
20201229 205339 worker: UPnP renderer (available)
20201229 205339 worker: DLNA server (available)
20201229 205339 worker: UPnP browser (available)
20201229 205339 worker: GPIO button handler (available)
20201229 205339 worker: Stream recorder (n/a)
20201229 205339 worker: -- Music sources
20201229 205339 worker: USB sources (none attached)
20201229 205339 worker: NAS and UPnP sources (none configured)
20201229 205339 worker: -- Miscellaneous
20201229 205339 worker: USB volume knob (Off)
20201229 205339 worker: USB auto-mounter (udisks-glue)
20201229 205339 worker: LED0 (On)
20201229 205339 worker: LED1 (On)
20201229 205339 worker: Saved MPD vol level (0)
20201229 205339 worker: Preamp volume level (0)
20201229 205339 worker: MPD volume level (0) restored
20201229 205339 worker: ALSA Digital volume (Invalid card number.)
20201229 205339 worker: Auto-play (Off)
20201229 205339 worker: Maintenance interval (3 hrs)
20201229 205339 worker: Screen saver activation (Never)
20201229 205339 worker: Session permissions (OK)
20201229 205339 worker: Watchdog started
20201229 205339 worker: ReadyRE: Official moOde 7.0.1 support thread - oculto - 12-30-2020
I think I found the problem.
pi@moode:~ $ aplay -l
aplay: device_list:272: no soundcards found...
for some reason, the card is not recognized, but it work with raspbian and dtoverlay=hifiberry-digi-pro (but not work on moode)
![[Image: HTB1Cu0ERVXXXXbLapXXq6xXFXXXP.jpg?size=2...8412a8485d]](https://ae01.alicdn.com/kf/HTB1Cu0ERVXXXXbLapXXq6xXFXXXP.jpg?size=219844&height=533&width=800&hash=fed4981a7971718c89d5e48412a8485d)
Code:
dmesg | grep wm8804
[ 8.562268] snd-rpi-wm8804 soc:sound: ASoC: failed to init link HiFiBerry Digi+ Pro: -517
[ 8.834480] snd-rpi-wm8804 soc:sound: ASoC: failed to init link HiFiBerry Digi+ Pro: -517
[ 8.858850] snd-rpi-wm8804 soc:sound: ASoC: failed to init link HiFiBerry Digi+ Pro: -517
[ 9.667237] wm8804 1-003b: Failed to read device ID: -121
[ 9.667572] wm8804: probe of 1-003b failed with error -121RE: Official moOde 7.0.1 support thread - oculto - 12-30-2020
no luck for me. Try to install the AOIDE driver, update moode sqllite db to offer AOIDE driver, it works fine but the card still not recognized. I tomorrow will try to rollback to 6.7.1 to see if it works
RE: Official moOde 7.0.1 support thread - vinnn - 12-30-2020
(12-24-2020, 05:39 PM)Tim Curtis Wrote: The code now handles multiple occurrences of Genre, Artist, Performer and Conductor tags and considers Artist, Performer and Conductor as all being "artists" which they are. This approach supports Classical collections which are often tagged with multiples, and it still supports Pop collections which normally only have a single Genre, Artist, AlbumArtist tag.
When there are multiple "artists" present it's not possible to determine which one is the AlbumArtist if no AlbumArtist tag exists.
In your test album The same value is assigned to Performer and Artist tags and thus we have multiple "artists", and there is no AlbumArtist tag. This is what results in "Unknown AlbumArtist".
I don't quite understand why the tagging utility creates both a Performer and an Artist tag with the same value. Is this a common practice?
-Tim
Hi Tim,
Took a while to get back to you having to find time after Christmas and work duties to look into this a bit further.
These albums will likely have been at some point EAC rips with cue sheets and I decided some years ago to split them all into tracks and ditch the cue sheets, the metadata in those cue sheets probably came from CDDB and the tools/scripts I used to split and tag the files en masse would have populated whatever was in the cue files, including the performer tags.
I've sorted the problem at my end, using metaflac I identified all the tracks with matching artist and performer tags (21195 of them!) and removed the performer tags without altering the file modification dates, turns out they were the only files I had that had performer tags so all is well.
Still I will put it out there that I don't think that's really the right way to handle album artists, I can see what you mean by looking in playerlib.php that the code is creating an array of artists tags if there are multiple artists under the same album and if the array contains more than one value then set album artist to Unknown AlbumArtist if there's no Album Artist tag and that's fine.
But as it's now adding the values of the performer and composer tags to the artist array, if a composer or performer tag exists at all (even if they're the same as artist) the artist tag is no longer used as the album artist in the absence of an album artist tag and I think that's having an effect that was not intended.
Code:
455 for ($i = 0; $i < $linecount; $i++) {
456 list($element, $value) = explode(': ', $lines[$i], 2);
457
458 if ($element == 'OK') {
459 // NOTE: Skip any ACK's
460 }
461 else if ($element == 'file') {
462 $item = count($flat);
463 $flat[$item][$element] = $value;
464 }
465 // @Atair: Gather possible multiple Genre, Artist, Performer and Conductor values as array
466 elseif ($element == 'Genre') {
467 if ($flat[$item]['Genre']) {
468 array_push($flat[$item]['Genre'], $value);
469 }
470 else {
471 $flat[$item]['Genre'] = array($value);
472 }
473 }
474 elseif ($element == 'Artist') {
475 if ($flat[$item]['Artist']) {
476 array_push($flat[$item]['Artist'], $value);
477 }
478 else {
479 $flat[$item]['Artist'] = array($value);
480 }
481 }
482 // @Atair: add performers to artists
483 elseif ($element == 'Performer') {
484 if ($flat[$item]['Artist']) {
485 array_push($flat[$item]['Artist'], $value);
486 }
487 else {
488 $flat[$item]['Artist'] = array($value);
489 }
490 }
491 // @Atair: add conductor to artists
492 elseif ($element == 'Conductor') {
493 if ($flat[$item]['Artist']) {
494 array_push($flat[$item]['Artist'], $value);
495 }
496 else {
497 $flat[$item]['Artist'] = array($value);
498 }
499 }
500 else {
501 $flat[$item][$element] = $value;
502 }
503 }The performer tag is a valid tag as is conductor, and in the context of classical music or audio books these are more likely to exist and be different to the artist tag and the same is likely to occur. Shouldn't have to add an Album Artist tag if the Artist string is the same on all tracks regardless of any other tags. In the case of audio books it's less likely to be an album at all, often a book or other spoken word audio file is a single file so overriding artist for Unknown AlbumArtist if performer exists doesn't make sense.
Whilst Album Artist is useful and required if an album contains tracks from multiple artists it isn't mentioned as one of the minimal proposed tags in the Vorbis specs, yet artist and perfomer is and the different contexts described.
https://www.xiph.org/vorbis/doc/Vorbis_I_spec.html#x1-860005.2.2
Anyway thought I'd put it out there in case this bites anyone else.
By removing the performer tags in my collection and regenerating the database I no longer have 1600+ albums showing up as artist unknown and they're again listed against their artist tags.
RE: Parametric EQ wirke different froh Version 6.7 - bitlab - 12-30-2020
(12-30-2020, 10:02 AM)Pjotr Wrote: Thank You the new version. The UI is very nice and I love the cover art in folderview.
But one: I run one system on a Acoustic Energy mono-center speaker as a mobile soundbar. Parametric equalisation in that system is necessary.
But it seems that the parametric eq works different from the 6.7.1. It tooks a very long time to find the right Sound and now I can't reproduce the Sound with the new Version.
My question: is there a way to copy or reproduce the eq settings from 6.7.1 to 7.1? Because when I Copy the bandwith and the order parameter It sounds completely different.
Thanks
With 7 we switch to the more common Q factor. Where Qneweqp = 0.5 / BWoldepq.