moOde audio player for Raspberry Pi

[dadim]

Can you elaborate? I have almost 2K albums. ALL ripped to single CD image + CUE file. No problem at all.
CUEs cannot contain illegal characters... they may contain characters that you cannot read properly... thing is: CUEs MUST BE UTF8 at least; then, there is no illegal character.

What is this that you call "integrity problems"? A CUE cannot have such a thing, as it just indexes "addresses" / frames within a file. If it is messed up (that is: one track starts before the one preceding it) then you better re-rip, so the CUE may get properly regenerated...

ETA
Please note, that CUE files go together with ONE AUDIO FILE ONLY. Using CUEs as if they were M3U playlists is an abomination. Use M3Us.

Please look at the Tim's post #290 above where he quotes from the sample I sent him, both the metadata problems of the ape file itself and the undetermined (that's the 'illegal' I mentioned) characters in the audio filename and the album title. Moreover, the CUE file is not encoded in UTF-8, but rather in ISO-8859-15.

And just to clarify a thing: when I split the single audio file, using the CUE track indexes to separate flac files, I don't keep the CUE any more, I delete it.

 

[phofman]

If the code reading the cue file expects UTF-8, ISO-8859-15 may produce wrong results.

It should be trivial to convert to any encoding supporting the used characters, IIUC it's just a text file. E.g. https://askubuntu.com/a/1051426

 

[dadim]

The challenge is that on my end 0.24 MPD had no issues indexing the broken cue/ape you provided which would suggest something else in moode is causing the issue on your end or something external to moode.

I searched the 0.24 MPD issue list and can't find any "cue" or "cue+database update" issues so maybe the AI is hallucinating again.

MusicPlayerDaemon/MPD

Music Player Daemon. Contribute to MusicPlayerDaemon/MPD development by creating an account on GitHub.

github.com

Indeed, I find no apparent explanation why the indexing on my side fails (and gets stuck) while at your side succeeds. I don't know if it is related with the system Locale of my mooode or with the filenames' character encoding moode 'sees' from the Zyxel NAS sharing. It is worth mentioning also, that the mpd 0.23 fails also (the indexes are not playable), but it is more forgiving and continues the library scanning and update. As far as the AI response, I think that it is one more result of hallucination.

 

[dadim]

And does mpd output any log on an error like that?

No log entries are created because the task never ends, gets stuck.

 

[dadim]

If the code reading the cue file expects UTF-8, ISO-8859-15 may produce wrong results.

It should be trivial to convert to any encoding supporting the used characters, IIUC it's just a text file. E.g. https://askubuntu.com/a/1051426

Yes, I suppose.

 

[phofman]

I don't know if it is related with the system Locale of my mooode or with the filenames' character encoding moode 'sees' from the Zyxel NAS sharing.

My 2 cents it's the combination of moode local locales and NAS network sharing locales. We used to fight with SMB sharing user-created files stored on linux servers to windows clients. Then the linux servers changed locale to UTF-8 and samba had to be reconfigured again (long time ago, UTF8 has been used everywhere since).

 

[dadim]

Indeed, I find no apparent explanation why the indexing on my side fails (and gets stuck) while at your side succeeds.

I have a clearer picture on this. When I copy a couple of suspicious albums (where at the NAS' side the library indexing gets stuck) to a USB stick and use only this stick as library source (unmount NASes), the indexing succeeds. It is something related to the interaction of moode with the old NAS when the albums are in the form of a single audio file and a CUE sheet. I selected the "Ignore CUE files" setting in the Music Library settings of moode, but the frozen indexing remains.

 

[Nutul]

A sample couple of files could help. Looks to me some path-related thing that confuses the system.
Get two sample albums that DO cause the issue somewhere on the internet, and provide us with a downloading link, so we can test them on our system and see if we can reproduce - and then analyse - the problem. Only explaining several times the same thing, doesn't change the behavior of the device...

 

[dadim]

A sample couple of files could help. Looks to me some path-related thing that confuses the system.
Get two sample albums that DO cause the issue somewhere on the internet, and provide us with a downloading link, so we can test them on our system and see if we can reproduce - and then analyse - the problem. Only explaining several times the same thing, doesn't change the behavior of the device...

Thanks. Actually I don't explain the same thing again and again. What I tried to said in my previous message is that the same albums in which the indexing freezes on the NAS filesystem, when they are copied to a USB stick, from there the indexing succeeds. Please check your pm.

 

[Nutul]

(...) when they are copied to a USB stick, from there the indexing succeeds (...)

This is exactly the point I am at. Different filesystems / charsets / and the like.
Hence, posting something we can work on is the best, and quickest, form of help.
I'll check my PM, thanks.

P.S.
Nope... none yet. will wait.

 

[Tim Curtis]

Hi,

moOde 9.4.1 is available in the Media Player OS section of the Raspberry Pi Imager or as a direct download at https://moodeaudio.org. Visit the Forum for more information https://moodeaudio.org/forum/showthread.php?tid=8048&pid=66583#pid66583

 

[dadim]

@Tim Curtis in moode 8.3.9 is it possible to set spotify connect to accept lossless formats (bitrate higher than 320k)? As far as I see from the Spotify Connect settings page, the drop-down menu of Bitrate has values up to 320 .

 

[Tim Curtis]

@Tim Curtis in moode 8.3.9 is it possible to set spotify connect to accept lossless formats (bitrate higher than 320k)? As far as I see from the Spotify Connect settings page, the drop-down menu of Bitrate has values up to 320 .

It will show up in moode 9 after the librespot (Spotify Connect) project finishes implementing it and publishes a new release. You can see in their commit history https://github.com/librespot-org/librespot/commits/dev/ that there was an initial feature add for "lossless"
feat(playback): add inital flac decoding support via the symphonia crate (#1589) a couple weeks ago.

It won't show up in older moode 8 because our project doesn't maintain the 32-bit 8 series code base anymore or any 32-bit component builds. This officially happened when we released the 9 series back in mid-2024 and were unable to recruit a volunteer dev willing to take on the 32-bit work and commit to it long term. It's a very substantial effort but the offer is still open

 

[roderickvd]

We haven’t cracked the code for lossless support in librespot yet.

 

[dadim]

It's a very substantial effort but the offer is still open

What's the profile of the volunteer developer you are looking for?

 

[dadim]

We haven’t cracked the code for lossless support in librespot yet.

This means that Spotify demands royalty fees to provide the API for lossless support in Spotify Connect?

 

[Nutul]

This means that Spotify demands royalty fees to provide the API for lossless support in Spotify Connect?

No.
1. lossless is available ONLY to premium accounts - that is: not the free ones. If this is what you mean with royalty fees, then yes: you got it right.
2. There are changes in the WEB API addressed at requesting the lossless version of a track, and this has not yet been figured out by the developers of SpotifyConnect for moOde.

 

[Tim Curtis]

What's the profile of the volunteer developer you are looking for?

Expertise:

- Debian packaging
- Building and packaging apps written in C, C++, Rust, Python, BASH, PHP, Javascript
- Resolving dependency issues, compile errors and library incompatibilities
- Creating source patch files
- PiOS structure
- Building kernel drivers
- Building OS images using pi-gen
- Maintaining packages in Cloudsmith

One of our devs @bitlab created highly automated package and image builder tooling.
There is more info on this via the Developer link at moodeaudio.org but here are some quick links for convenience.

Master Guide

docs/master_development guide.md at main · moode-player/docs

Project documentation. Contribute to moode-player/docs development by creating an account on GitHub.

github.com

Package Builder

GitHub - moode-player/pkgbuild: Scripts to build third-party packages for moOde

Scripts to build third-party packages for moOde. Contribute to moode-player/pkgbuild development by creating an account on GitHub.

github.com

Image Builder

GitHub - moode-player/imgbuild: Scripts to generate a custom OS image for moOde

Scripts to generate a custom OS image for moOde. Contribute to moode-player/imgbuild development by creating an account on GitHub.

github.com

Cloudsmith package repo

Cloudsmith - Repositories - moodeaudio (moodeaudio) - moOde package repository (m8y) - Packages

Get better DevOps with secure software delivery for: Alpine, Cargo, CocoaPods, Composer, Conan, Conda, CRAN, Dart, Debian, Docker, Go, Helm, Hex, HuggingFace, LuaRocks, Maven, npm, NuGet, P2, Python, RedHat, Ruby, Swift, Terraform, Vagrant, Raw & More!

cloudsmith.io

 

[Tim Curtis]

Hi,

moOde 9.4.2 is available in the Media Player OS section of the Raspberry Pi Imager or as a direct download at https://moodeaudio.org. Visit the Forum for more information https://moodeaudio.org/forum/showthread.php?tid=8107&pid=67052#pid67052

 

[Ixtlan62]

Hi,

moOde 9.4.2 is available in the Media Player OS section of the Raspberry Pi Imager or as a direct download at https://moodeaudio.org. Visit the Forum for more information https://moodeaudio.org/forum/showthread.php?tid=8107&pid=67052#pid67052

View attachment 488061

Hi,
I'm a moOde user (RPI4 - D50s DAC - 7" HDMI 1024x600 display e Nas storage). I updated moOde to version 9.4.2. I'd like to customize peppymeter by adding information about what I'm listening to to the skins (title, cover, duration, etc.). I saw that the "opt" folder also contains the skin folders and the meter.txt file, but it can't be edited. Do you think this will be possible via WEBUI in the future?

Thanks