[SOLVED] MyMPD fixed database loading MPD

[Bromf]

MyMPD still unusable.
No matter what, I cannot select any track or album from the library but that every damn track is added to the queue.
I have reinstalled, uninstalled and tried using the Ubuntu PPA,  reimaged, tried different images...etc.

Always the same problem. Loads 16,000 + tracks.
Can't find any sensible documentation on the MyMPD site to enable the latest version so stuck with this unusable one.

Tried to live with LMS but its continual reset of the library at every boot is frustrating and I find I do not enjoy its sonic signature.
Neither the Classic nor the Material skin are easy to live with and so I find myself not spending time listening.

If there is some simple way to add the MyMPD repo and update I would be interested to try.

[cpcat]

I am using the same setup as you and it is flawless - whether accessing NAS, files on HD on SO machine,  or ram on SO machine.

I am using Ubuntu 22.04.1 desktop and SO firmware 1.2.10.

I am using CIFS to access NAS.

I’m attaching a pic of myMPD “about” screen.  I simply access myMPD via the remote icon on the player screen on SO machine.

One more thought:  when I was setting up CIFS share after upgrading to 1.2.10 SO fw,
it only PARTIALLY added it without a user/password/workgroup - ie would show the path/folders but would not allow access.  Then, when I added the  user/password/workgroup it was fully functional.  I could not get this to work at all with 1.2.9 ( I think because I had already added a nas mount via NFS but I’m not sure).  I ended up unmounting NFS and using only CIFS because NFS would not work for me with LMS.  CIFS seems to work for either LMS or MPD at least for me.

   

   

[Bromf]

AHA!!!
If, on the Browse tab in MyMpd, I change from Database to Filesystem then I can add albums to the queue with no problem at all :-)
This confirms the problem is in the database/cover view.
Further, if in Database view I select a genre then an album from it all the albums in that genre are added to the queue and not the whole database..

Need to find what database MyMPD uses and any reset command or alternatively if the problem lies with mpd as I see that MyMpd settings screen reports that the mpd version is out of date. If the way mpd administers its database is not aligned with MyMpd version then this might explain things.


And therein is found the fix!!

Seems that MyMPD and MPD versions have to be aligned. Changing to mpd 23.5 has removed the problem.
I had mpd 21.5 as I preferred that version but in the interests of use I suppose I will have to forgo that and accept the latest version.
Something to bear in mind for the future.

(Thanks @cpcat  for your screenshot...after much too much head-scratching I finally looked very closely at it and the answer became obvious. lol