fatg3erman / RompR

Web client for Mopidy and MPD
https://fatg3erman.github.io/RompR/
Other
192 stars 21 forks source link

Track "Panel" empty if tracklist too long #102

Closed count00zero closed 4 years ago

count00zero commented 4 years ago

HI there and THANK YOU for your great RompR :)

I have an issue, since my "playlist" (playing my whole music library with mpd; visualizing with rompr) has grown a bit. If I select a small playlist in the playlist panel and let mpd play it; all the tracks are visible in the playlist panel also the currently played track (see screen 1) including all the playing file info which is available (spotify, wikipedia, etc.)

When I load my whole music library (whole playlist) ~39800 playable songs, the playlist panel empties out and I get no currently played song info nor can I select wikipedia, spotify, etc.). <- screen 2.

Could you think of any reason for that behaviour?

THANKS a lot and BR, count

Screen 1 Screen 2

fatg3erman commented 4 years ago

The playlist is too big and the web server is timing out before RompR has a chance to retrieve all of it.

The one thing I never, ever, expected people to do was have enormous playlists. I wrote RompR because I hate playlists :-D

RompR has plenty of better ways to play your entire collection on shuffle if that is what you want to do. Loading a playlist that large will never work.

count00zero commented 4 years ago

Hi and thanks for your reply. I did the "playlist part" just to be able to reproduce it. I have the same effect when I just fire up my mpd-daemon with my configured music_directory and then browse to my rompr installation. I also tried to find something with the full debug log, but was unable to find the problem.

Using latest rompr.git source (but also tried earlier releases) mpd: 0.22~git (v0.21.25-1114-ge8380cf2a) mpc: version: 0.34

fatg3erman commented 4 years ago

OK I'm sorry but your explanation is not making any sense.

The first image above shows it all working correctly.

Please describe EXACTLY what you did to produce the second image. Do not assume anything, describe in detail every single thing you did. Because your two posts, currently, are contradicting each other.

count00zero commented 4 years ago

OK, I'll try to do that (start from scratch) Let's assume I restart my mpd daemon service (with my configured music_directory) and the music starts playing. mpc output:

music/Kidneythieves/Zerospace (2002)/12 - Placebo.mp3 [playing] #25823/38196 0:08/6:40 (2%) volume:100% repeat: off random: on single: off consume: off

Then I surf to my rompr installation and what I see (doesn't change over time) is this: Screen 2

THEN I try to see if rompr works, load a small playlist and voila: Screen 1

That's the whole story :)

fatg3erman commented 4 years ago

OK thanks, that makes sense now, though I still don't understand why the title of this Issue is 'if playlist too long'?

I've just tried what you described and could not reproduce the problem, so what I need is a debug log, at level 7, of the case where you start RompR and it doesn't display any information.

https://fatg3erman.github.io/RompR/Troubleshooting#debug-logging

The Debug Information would also be useful:

https://fatg3erman.github.io/RompR/Troubleshooting#reporting-bugs

count00zero commented 4 years ago

Thank you again for your help!

Debug Info: `

fatg3erman commented 4 years ago

It's a little difficult to be certain but what I can tell from the log is that you have a very large number of saved playlists and the processing of them simply stops. This could be due to the webserver timing out, or it could be running out of memory. What I really need to see is the web server error logs and the php (or php-fpm depending on your setup) error logs to find out what's causing it to stop, but I suspect it's not going to be something fixable.

Also you are still contradicting yourself. You say this is not to do with the tracklist but then you change the title to "If tracklist too long". How many tracks are in your tracklist when this happens?

count00zero commented 4 years ago

Thank's for the Info, I will look into that! The only thing in nginx error file which jumps out is: [error] 541620#541620: *1 open() "/opt/www404" failed (2: No such file or directory),

I think it stopped working, when I changed to the most recent version of mpd and then tried out myMPD (which started to build smart playlists) -> I will get rid of those ... Maybe that's the reason.

Regarding the "tracklist" I am simply out of words to describe it the right way ;-) I mean the list of tracks, which are defined within mpd.conf (music_directory) and which are in my playqueue and randomly sorted.

But maybe that's just a side effect. Because I even can't see the currently played song, which bugs me a bit more ...

Edit: played around a bit with nginx config: [error] 580335#580335: 1 open() /opt/www/rompr/themes/SunsetLoch.css.js" failed (2: No such file or directory) [error] 594413#594413: 1970 open() "/opt/www/rompr/newimages/thisdoesntexist.png" failed (2: No such file or directory)

count00zero commented 4 years ago

Just out of curiosity, i created the missing "/opt/www/rompr/newimages/thisdoesntexist.png" And now I see this (see screen 3): Screen 3

fatg3erman commented 4 years ago

OK I'll try to rephrase the question one more time. How many tracks are in your play queue?

Or in other words, if the panel on the right was working, how many tracks would it contain?

count00zero commented 4 years ago

Based on mpc there would be 37484 tracks in my play queue

fatg3erman commented 4 years ago

Then I refer you back to the very first answer I gave you.

Rompr will not work with a play queue that long.

count00zero commented 4 years ago

OK, got it. Thanks a lot for your time and patience!