11-30-2020, 08:56 AM
Yea, I realized this also. Normally (if autoplay works correctly) this is done quicker:
Probably I could go ahead and increment the loop condition in function openMpdSock() from 6 to let's say 30, but I prefer to solve the problem if any possible then having a workaround. Do you have any idea what prolongs MPD's startup time under certain conditions? It seems to be kind of deterministic condition, see test results above...
In the release notes for moOde 6.5.2 is mentioned:
- FIX: Start up logic for auto play and auto-shuffle
Do you see any context between this fix and my actual issue?
Code:
20201126 014300 worker: MPD started
20201126 014301 worker: MPD accepting connectionsProbably I could go ahead and increment the loop condition in function openMpdSock() from 6 to let's say 30, but I prefer to solve the problem if any possible then having a workaround. Do you have any idea what prolongs MPD's startup time under certain conditions? It seems to be kind of deterministic condition, see test results above...
In the release notes for moOde 6.5.2 is mentioned:
- FIX: Start up logic for auto play and auto-shuffle
Do you see any context between this fix and my actual issue?
