[PROBLEM] ashuffle not running

[hindumagic]

Hi, I've seen some trouble with ashuffle in the past, but I can't find a proper resolution yet.

I'm running a HiFiBerryDAC compatible hat (I2S) on a Pi2B with a wifi adapter plugged into USB and my library is on a NAS via SMB.

I figure that ashuffle hasn't worked from the start.  Trying to debug it with this and here is the direct result:

ian@boombox:~ $ ashuffle
MPD error: Response line too large

This is what I get after setting mpd logging to verbose in the mpd log:

Feb 09 16:33 : client: [11] opened from 127.0.0.1:44122
Feb 09 16:33 : client: [11] process command "notcommands"
Feb 09 16:33 : client: [11] command returned 0
Feb 09 16:33 : client: [11] process command "listallinfo"
Feb 09 16:33 : client: [11] command returned 0
Feb 09 16:33 : client: [11] closed

Anyone bump into this, have any ideas, or give me further guidance?  It doesn't seem that ashuffle has its own log.  Thanks!
Ian.

[hindumagic]

Note: opened an issue for ashuffle in GihHub: https://github.com/joshkunz/ashuffle/issues/89

[Herman]

Looks like I 'm having the same issue: http://moodeaudio.org/forum/showthread.p...930&page=5

[CallMeMike]

@Herman

That was over TWO years ago... Have you 'resisted' to Tim's advise to raise a ticket on ashuffle Git repo?

It looks like @hindumagic went straight to the proverbial tree without much ado... :-)

[TheOldPresbyope]

So others know the game is afoot...

@hindumagic posted his issue to the ashuffle repo. After some more sleuthing, he and the ashuffle maintainer identified the triggering condition. The metadata for at least one music track in the library contained a ginormous (ca 5kb text) comment field. This caused an upstream library to kick out an error. The upstream library maintainer has been notified.

No remedy has been devised yet, so the current work-around is to find and edit such big text fields.

Regards,
Kent

[Herman]

@Herman

That was over TWO years ago... Have you 'resisted' to Tim's advise to raise a ticket on ashuffle Git repo?

It looks like @hindumagic went straight to the proverbial tree without much ado... :-)

https://github.com/joshkunz/ashuffle/issues/44

It did not lead to a solution.
In the meantime the "recently added" filter was added and improved and an attractive alternative to fill the playlist.
Ideally you should be able to combine this feature with ashuffle.