OK, so it's working, but badly.
I can tell you that MPD is very fussy about directory names, and tag information. If these don't match exactly, I have read that MPD's database will list the item multiple times.
But did you have the problem of multiple listings before you enabled Album Art, or did it only happen after you enabled Album Art?
I can tell you that MPD is very fussy about directory names, and tag information. If these don't match exactly, I have read that MPD's database will list the item multiple times.
Okay, maybe I've been misunderstood.
Step #1:
Made basic config, saved it.
...nothing happened
After restart the app, at last option "Complete" I could realize a short flickering for a second as it seemed queue was handled. After that, nothing more and fields are cleared, no covers.
Step #2:
Then I switched to port 80, saved settings, rebooted app and this is the result at bottom line:
Okay, there're quite some german and international umlauts in directory names. In combination with nginx it's fine at this point.
Step #1:
Made basic config, saved it.
...nothing happened
After restart the app, at last option "Complete" I could realize a short flickering for a second as it seemed queue was handled. After that, nothing more and fields are cleared, no covers.
Step #2:
Then I switched to port 80, saved settings, rebooted app and this is the result at bottom line:
linuxfan said:
Okay, there're quite some german and international umlauts in directory names. In combination with nginx it's fine at this point.
Last edited:
Ah, so now I understand that you are referring to what is displayed in the Album Art menu.
It's hard to know why this menu is showing such a high number of items in the queue, but we should be mindful that there are 3 separate applications interacting with each other - MPD, lighttpd, and MaximumMPD. And I suspect the developer of MaximumMPD has written the Album Art component to interact with nginx, not lighttpd.
Maybe in the next day or two I will have a look at the nginx documentation so it can be set up for MaximumMPD (independent of the Rune app).
Until then, you could maybe try a different MPD client to see if it has different behaviour.
It's hard to know why this menu is showing such a high number of items in the queue, but we should be mindful that there are 3 separate applications interacting with each other - MPD, lighttpd, and MaximumMPD. And I suspect the developer of MaximumMPD has written the Album Art component to interact with nginx, not lighttpd.
Maybe in the next day or two I will have a look at the nginx documentation so it can be set up for MaximumMPD (independent of the Rune app).
Until then, you could maybe try a different MPD client to see if it has different behaviour.
linuxfan said:
I did it...and I got it!
Dear linuxfan,
I raise my glass on you and thank you so much, even if we are back at the beginning, called nginx.
But, time is money and €5.49 is not worth the time we would have continued to invest.The solution: I bought Soundirok app, followed it's user guidance and enabled nginx again.
(replaced default to my IP).
Soundirok said:
May I introduce:
In the end, this not what I'm starting for but it is a solution. Perhaps better than the original expectations.
Best regards,
Oliver
That's great you now have a solution with Soundirok.
Out of this adventure I think you can see that MPD can be good/ordinary/bad, depending on the client app!
There are clearly differences in how different MPD clients interact with different cover-art web servers:
Soundirok appears to work well with nginx - when nginx is managed/configured by the Rune app.
But this same Rune/nginx setup does not work well with MaximumMPD, as revealed by your results in post #62.
I see that MaximumMPD suggests to use nginx, and they recommend a specific nginx configuration here -
Maximum MPD
I was about to suggest how to enable this configuration for you ... but no matter, you have Soundirok working instead.
Out of this adventure I think you can see that MPD can be good/ordinary/bad, depending on the client app!
There are clearly differences in how different MPD clients interact with different cover-art web servers:
Soundirok appears to work well with nginx - when nginx is managed/configured by the Rune app.
But this same Rune/nginx setup does not work well with MaximumMPD, as revealed by your results in post #62.
I see that MaximumMPD suggests to use nginx, and they recommend a specific nginx configuration here -
Maximum MPD
I was about to suggest how to enable this configuration for you ... but no matter, you have Soundirok working instead.
A last question in my mind (I‘m an „emotional pefectionist“ ):
Broken down to the essential features I need, do you think it‘s „worth“ to test Moode Audio for sound comparison at this point? I do not use I2S, but only transport data from A to B, operated with Soundirok (now). And, I have to buy a Raspberry SBP (or familiy) therefore.
): Broken down to the essential features I need, do you think it‘s „worth“ to test Moode Audio for sound comparison at this point? I do not use I2S, but only transport data from A to B, operated with Soundirok (now). And, I have to buy a Raspberry SBP (or familiy) therefore.
For a sound comparison, no. I believe the sound quality of your particular digital playback system is ultimately determined by the USB digital interface contained in your M-ONE DAC/amp. It's highly unlikely you will get any better result from a Raspberry Pi than your Odroid, especially so if you use a rPi 3x, since this model shares USB and ethernet data across the same bus.
But hey, this is a hobby, so if you want to compare a Moode setup for operability, then sure. You might prefer the Moode client interface.
Just make sure to use a rPi 4B.
But hey, this is a hobby, so if you want to compare a Moode setup for operability, then sure. You might prefer the Moode client interface.
Just make sure to use a rPi 4B.
Maybe I'm a bit old-schooled in this respect. I had a look at Moode v7 preview and it has a huge functionality, but I need the least of it (this is not meant to be disencitive). My focus was on GUI's usability.
1:0 Odroid C1+, it's separated here.
Okay, now I'm really fine and clear!
Have a nice weekend!
linuxfan said:
1:0 Odroid C1+, it's separated here.
Okay, now I'm really fine and clear!
Have a nice weekend!
@linuxfan:
Our little "Linux adventure" left me no peace to do my „own thing“ and so I took out my old Asus eePC.
Within a few days I’ve managed to install both Mojano on my netbook and with it an ArchLinixARM mSD card for a headless system my Odroid.
With this I can listen to my music controled by Soundirok...but no covers.
The lighttpd server is reachable (wget http://<local-ip>:8081 successfully, call browser URL shows the server‘s directory listing).
Can I reach the goal in a short term? Where is the sticking point? Could you please look over it again. It would be great.
Regards,
Oliver
Our little "Linux adventure" left me no peace to do my „own thing“ and so I took out my old Asus eePC.
Within a few days I’ve managed to install both Mojano on my netbook and with it an ArchLinixARM mSD card for a headless system my Odroid.
With this I can listen to my music controled by Soundirok...but no covers.
The lighttpd server is reachable (wget http://<local-ip>:8081 successfully, call browser URL shows the server‘s directory listing).
Code:
server.port = 8081
server.username = "http"
server.groupname = "http"
server.document-root = "/mnt/music"
#server.errorlog = "/var/log/lighttpd/error.log"
dir-listing.activate = "enable"
dir-listing.enconding = "utf-8"
index-file.names = ( "index.html" )
mimetype.assign = (
".html" => "text/html",
".txt" => "text/plain",
".css" => "text/css",
".jpg" => "image/jpeg",
".jpeg" => "image/jpeg",
".png" => "image/png",
)Can I reach the goal in a short term? Where is the sticking point? Could you please look over it again. It would be great.
Regards,
Oliver
Last edited:
Okay, at least I have these two little messages at mod start:
As far as I understand, this has something to do with asynchronous input/output but no idea where to start.
The ArchLinux system is quite "basic". I've only installed ALSA-utils, MPD and MPC and made the necessary adjustments that we have discussed here (I don't use wildmidi as far as I can judge).
Code:
alarm mpd[200]: Oct 04 12:23 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
alarm mpd[200]: Failed to initialize io_uring: io_uring_queue_init() failed: Function not implementedAs far as I understand, this has something to do with asynchronous input/output but no idea where to start.
The ArchLinux system is quite "basic". I've only installed ALSA-utils, MPD and MPC and made the necessary adjustments that we have discussed here (I don't use wildmidi as far as I can judge).
Last edited:
Sorry, I need your help again. This alarm message is still present:
What do I have install or to do?
This is what I found for "liburing":
Any logs, etc. I can show you?
Code:
alarm mpd[200]: Failed to initialize io_uring: io_uring_queue_init() failed: Function not implementedWhat do I have install or to do?
This is what I found for "liburing":
Code:
liburing: /usr/lib/liburing.so /usr/include/liburing /usr/include/liburing.hAny logs, etc. I can show you?
- Status
- This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.