Official moOde 8 support thread

[Tim Curtis]

I have a Boss 2 but don't recall experiencing the issue you described. I can run some tests today.

When you mention "the sound stops sometimes, hanging." what does "hanging" mean? Do you have to reboot or power cycle the system?

it occurs again, open an SSH terminal and post the output from the commands below.

Code:

mpc status

amixer -c0

Its evident in the screen shot but unless I'm able to repro it with my Boss 2 which as I posted earlier doesn't exhibit this issue, a debug on my end won't be possible.

Maybe someone else with a Boss 2 thats doing this has some idea what might be going on.

[charlesky]

'Performer' and 'Conductor' tags appear to be interfering with retrieval of 'Artist' or 'Album Artist' data.

I see there have been a few issues with music tags in the past and heartily agree with @TheOldPresbyope that this whole thing is a dumpster fire with no standards. But right now (release 8.0.2) it appears that any files that have a 'Performer' or 'Conductor' tag defined end up being dumped in the 'Unknown Artist'/'Unknown AlbumArtist' category in tag view. This occurs with all of the choices in the 'Tag view artist' field. 

My music is stored on a USB drive connected directly to the Pi. If I edit the file tags (using MP3tag 3.14 on a PC), solely remove the 'Performer' or 'Conductor' tag and update the library then the album turns up correctly listed under the relevant artist in tag view.

I should note that this is happening on AAC files (with the .m4a extension) that have been tagged using MP3Tag.

[Tim Curtis]

Zip up some of the files that have performer/conductor tags and PM the download link to myself and @TheOldPresbyope so we can analyze the files and try to repro.

[Tim Curtis]

'Performer' and 'Conductor' tags appear to be interfering with retrieval of 'Artist' or 'Album Artist' data.

I see there have been a few issues with music tags in the past and heartily agree with @TheOldPresbyope that this whole thing is a dumpster fire with no standards. But right now (release 8.0.2) it appears that any files that have a 'Performer' or 'Conductor' tag defined end up being dumped in the 'Unknown Artist'/'Unknown AlbumArtist' category in tag view. This occurs with all of the choices in the 'Tag view artist' field. 

My music is stored on a USB drive connected directly to the Pi. If I edit the file tags (using MP3tag 3.14 on a PC), solely remove the 'Performer' or 'Conductor' tag and update the library then the album turns up correctly listed under the relevant artist in tag view.

I should note that this is happening on AAC files (with the .m4a extension) that have been tagged using MP3Tag.

The issue is being caused by having all the performers as a comma separated string stuffed into a single performer tag.

Code:

pi@sig:~ $ telnet localhost 6600
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
OK MPD 0.23.5
lsinfo "USB/VFAT128/Test_mixed/Performer tag/Ptag 01-08 Scn1. Air (A Phlistine) Loud as the thunders awful voice.m4a"
file: USB/VFAT128/Test_mixed/Performer tag/Ptag 01-08 Scn1. Air (A Phlistine) Loud as the thunders awful voice.m4a
Last-Modified: 2022-04-06T14:24:18Z
Format: 44100:f:2
Artist: Handel
Album: Samson
Title: Scn1. Air (A Phlistine): “Loud as the thunder’s awful voice”
Track: 8
Genre: Tag Test
Date: 2019
Composer: Handel
Performer: Tiffin Boys’ Choir, James Day (dir.), Dunedin Consort (Choir & Orchestra), John Butt (dir.) / Joshua Ellicott (Samson -tenor), Jess Dandy (Micah, Friend to Samson -alto-), Matthew Brook (Manoah, Father to Samson -bass-), Vitali Rozynko (Harapha, Gigant -bass-), Sophie Bevan (Dalila, Wife of Samson -soprano-), Hugo Hymas (An Israelite, A Philistine, Messenger -tenor-), Mary Bevan (A Virgin, An Israelite Woman, A Philistine Woman -soprano-), Fflur Wyn (Virgin, A Philistine Woman -soprano-)
Comment: Dunedin Consort, John Butt & Hugo Hymas
Disc: 1
Time: 173
duration: 172.965
OK
Connection closed by foreign host.
pi@sig:~ $

MPD requires individual tags for each artist, performer, genre, etc
https://github.com/MusicPlayerDaemon/MPD...sions/1385

[charlesky]

'Performer' and 'Conductor' tags appear to be interfering with retrieval of 'Artist' or 'Album Artist' data.

I see there have been a few issues with music tags in the past and heartily agree with @TheOldPresbyope that this whole thing is a dumpster fire with no standards. But right now (release 8.0.2) it appears that any files that have a 'Performer' or 'Conductor' tag defined end up being dumped in the 'Unknown Artist'/'Unknown AlbumArtist' category in tag view. This occurs with all of the choices in the 'Tag view artist' field. 

My music is stored on a USB drive connected directly to the Pi. If I edit the file tags (using MP3tag 3.14 on a PC), solely remove the 'Performer' or 'Conductor' tag and update the library then the album turns up correctly listed under the relevant artist in tag view.

I should note that this is happening on AAC files (with the .m4a extension) that have been tagged using MP3Tag.

Ok, I found the place in the code that is causing this and fixed it. 

/var/www/inc/playerlib.php controls the way the library handles tags. If a file doesn't have the 'AlbumArtist' tag defined then it tries to construct this by building an array containing the contents of the 'Artist', 'Performer' and 'Conductor' tags (if they are present). This works fine. Unfortunately, it looks like a trap was built in at some point to catch cases in which a file has multiple 'Artist' tags defined - this is certainly undesirable, though not really fatal - and spit them out as 'Unknown AlbumArtist'. This gets tripped when it encounters the Artist/Performer/Conductor array that was accumulated earlier, which certainly looks like an unintended behaviour. 

The easiest way to fix this is simply to remove the trap. While multiple 'Artist' tags are a bad practice, music tags are such a wild west that it's not unknown, and probably not a good reason to disrupt the way the library is displayed. 

The problem occurs at line 577 in playerlib.php:

Code:

'album_artist' => ($flatData['AlbumArtist'] ? $flatData['AlbumArtist'] : (count($flatData['Artist']) == 1 ? $flatData['Artist'][0] : 'Unknown AlbumArtist')),

I changed this to:

Code:

'album_artist' => ($flatData['AlbumArtist'] ? $flatData['AlbumArtist'] : ($flatData['Artist'][0] ? $flatData['Artist'][0] : 'Unknown AlbumArtist')),

in a freshly-flashed copy of moode and rebuilt the library. Everything now works fine, with no aberrant 'Unknown AlbumArtist' categories. A file will now only get assigned to this if none of 'Album Artist', 'Artist', 'Performer' or 'Conductor' are defined. Since there are no real standards when it comes to music tagging this allows the tag view display to be more flexible to handle different approaches.

If anyone else is bothered by this behaviour and wants to make such a change feel free to PM me, though it's a slightly tricky process doing it from a Windows PC and needs special tools.

[Edit] The same change needs to be made to line 772 since there's a separate function to handle UTF8 encoding.

[Tim Curtis]

Hello community, hello Tim,
2 days ago i update to the new V8.
My Hardware: raspberry pi4B with ALLO Boss DAC2

I always select Mixter Type: Hardware cause it sound better than software.

When i rotate the volume controller the sound stops sometimes, hanging.

In Moode 7 it always works fine.

Is that a bug that might be fixed?

Thank you.

I was able to catch a repro of this on an Audiophonics 9038 DAC. It looks like after starting up  the Hardware mixer which for this particular device s named "Digital" is reporting that it is in the "off" state.

Code:

pi@kef:~ $ amixer sget Digital
Simple mixer control 'Digital',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined
 Playback channels: Mono
 Limits: Playback 0 - 100
 Mono: Playback 66 [66%] [-34.00dB] [off]

Ensuring that it's set to "on" during startup seems to fix the intermittent problem where sound cuts out after changing the volume.

Code:

amixer sset "Digital" on

[Wheel_nut]

Hi Tim, I don't know whether my experience is related to the post above but when I installed moOde 8.0, I could not get any sound output until I toggled the Volume Control setting from Hardware to Software and back again.

This was consistent on the two installations that I updated. I am using a HiFiBerry DAC+ I2S Hat on a RPi 3B.

Robin

[Marrahm]

CamillaDSP freezing?

I’m using the same filters I ran for the last version of Moode. Works fine for a few minutes, usually less than 10 and then sound abruptly stops. Although play counter on Moode continues. Pipeline says everything still “running” although the L and R sound bars no longer move.

I’m reasonably confident it has something to do with Camilla and my filters are not issue b/c it seems to do it even when switched to “flat” in Camilla and it does not happen if I turn Camilla off.

Any suggestions for troubleshooting? This did not happen under last version of Moode.
Thanks,
Mike

[Jedrek]

After upgrading from 7.6.1 to 8.0.2, I now have a lightning bolt in the top right corner on the LCD screen. In addition, the Power LED does not light up at all.
Nothing was changed except updating the system. I know that it applies to the power manager, but is it possible to somehow restore the LED operation and make the yellow lightning disappear on the LCD?
I know that the solution is to change the power supply, but I am asking for a software solution.

This solution: https://pimylifeup.com/raspberry-pi-low-...e-warning/ only clear a yellow lightning and red led light up.
System info noticed:
Throttled bitmask = 0x50005
Throttled text = Under-voltage detected, Currently throttled, Under-voltage has occurred, Throttling has occurred

After going back to version 7.6.1, everything is back to normal. I do not have a lightning bolt icon, the supply voltage is the same as with version 8.0.2. I have no speed throttle.
System info noticed:
Throttled bitmask = 0x0

[Busybox]

I backed up everything on my 7.6.1 system, did an image update to 8.0.2, and restored everything from my backup. Everything seemed to work fine except:

1. Nothing happens when I click on the "Audio Info" entry under the "M" menu. (I rarely look at this, except after upgrades/updates to make sure things look sane.) If I click on the bit rate displayed under a radio station's artwork, the "Audio Info" display does come up on the "Station" tab, but when I click on the "Playback" tab, nothing happens.

Update: This appears to be a problem with Chrome (v100.0.4896.127). Edge and Safari work fine.

2. The default playlist is blank. I know the playlist wasn't backed up in previous backup versions, but I thought this had been implemented as of 7.6.1?


Cheers,

- Steve