Problem with LMS on Raspberry Pi 3B

[bencat]

I have been having a quite frustrating day with LMS after a very long period of it just working in the back ground and doing what I ask it has now after playing random mix/ song mix which is how I use it songs stop in the middle say they are buffering and then never restart. 

I have looked at the log and it appeared to be an issue with Dynamic Mix plug in as the log kept saying could not find dynamic mix link . So removed the plug in but then still kept happening and the following line kept appearing 

[18-05-28 10:56:47.0167] Slim::Schema::forceCommit (2147) Warning: Trying to commit transactions before DB is initialized!

After looking on the basic settings page and after a number of reviews I just noticed that the Media Folder and the Playlist folder were different one was usb but the other was usb0 so have now changed both to usb0 which is the one that is showing on the file mounting page on Max2play . 

Doing a rescan of the Library under Media Folder which I am keeping my fingers crossed will solve this issue and let me get back to listening again without that horrible feeling the tune is going to cut off.

Has anyone come across this sort of issue before ? Will what I have done solve the problem ?

 

[bencat]

I am not completely sure but I think the above has solved my issues and streaming is now without any stops or buffering . Never seen this before so a little puzzled as to how tw different paths were open .

 

[bencat]

Spoke too soon and had a very frustrating time last night with constant buffering and drop outs . Looked at the log and could not really see a cause for all the failures to connect.

Took the decision to remove all the plug ins that I really do not use (but thought they would be useful) did a Stretch update , max2play reboot and a full LMS stop and then restart .

Listened for about an hour after all this on my second system and no issues or drop outs. Will have to see if things are still working right tonight. Looking at the log it is certainly much less busy with almost no additions after the LMS was restarted .

So again fingers crossed this will now settle down but I am a little puzzled as to what has caused all this disruption when it has worked so well for so long .