[SOLVED] Library changes take two refreshes

[Nykkuno]

Quick question...

Is it common to need to run two library updates for the new additions to become visible?

I am seeing the below in the mpd logs... could this be the cause?

Sep 08 18:53 : ffmpeg/m4v: Format m4v detected only with low score of 5, misdetection possible!
Sep 08 18:53 : ffmpeg/mpeg4: time_increment_bits 0 is invalid in relation to the current bitstream, this is likely caused by a missing VOL header
Sep 08 18:53 : ffmpeg/mpeg4: time_increment_bits set to 5 bits, based on bitstream analysis
Sep 08 18:53 : ffmpeg/mpeg4: time_increment_bits 4 is invalid in relation to the current bitstream, this is likely caused by a missing VOL header
Sep 08 18:53 : ffmpeg/mpeg4: time_increment_bits set to 5 bits, based on bitstream analysis
Sep 08 18:53 : ffmpeg/mpeg4: looks like this file was encoded with (divx4/(old)xvid/opendivx) -> forcing low_delay flag
Sep 08 18:53 : ffmpeg/mpeg4: low_delay flag set incorrectly, clearing it
Sep 08 18:53 : ffmpeg/m4v: DTS discontinuity in stream 0: packet 21 with DTS 1008000, packet 22 with DTS 131561856000

The entries above were just prior to the track list of the new album that I add, so it is a distinct possibility.

[Tim Curtis]

No not common. Only one Library Update should be needed. Try clearing your Browser cache.

Are these files from iTunes?

[Nykkuno]

Hi Tim

I used CTRL-R and CTRL-F5 to refresh but that did not make it show the new album... until I did another scan.

The files in my library are from various sources... For the latest addition it was a rip from a CD using Freac (paranoid mode) to FLAC running on Linux Mint.

I have tried enabling "verbose" logging in mpd in an attempt to find out what file(s) is/are causing the ffmpeg issue but this did not give any useful indication of the file(s) that were responsible...

I am reasonably sure it must be a file in my library that is causing the issue.  The trick is, finding it...

[Tim Curtis]

Try the following:

1. Truncate the MPD log

Code:

sudo truncate /var/log/mpd/log --size 0

2. Regenerate the Music database (Library Config)

3. Examine the MPD log and look for permission or other errors

Code:

cat /var/log/mpd/log

[Nykkuno]

Try the following:

1. Truncate the MPD log

Code:

sudo truncate /var/log/mpd/log --size 0

2. Regenerate the Music database (Library Config)

3. Examine the MPD log and look for permission or other errors

Code:

cat /var/log/mpd/log

Thanks Tim

I should have thought of regenerating the MPD cache with that option earlier.

I have found the rouge FLAC file and, in addition, flac's with cue's that were being scanned but not added, and have shifted them into an ignore folder where there is a .mpdignore file with an asterix as it's content.  I'll can get around to sorting them out at another time.

It also helped me find some mkv files that possibly slowed down the scan and put an .mpdignore file in those folders to ignore the video files.

It has made the mpd scan quicker... once I have a new album to add I'll see if it still takes more than one library update to make it visible in Moode. 

In the meantime, thanks for your help.

[Tim Curtis]

There is also the "Audio formats" setting in the COVER ART section of Preferences. It controls which audio formats are scanned by the Thumbnail generator.

[Nykkuno]

There is also the "Audio formats" setting in the COVER ART section of Preferences. It controls which audio formats are scanned by the Thumbnail generator.

Thanks, but I prefer the granularity of the .mpdignore file.  

I have had a chance to add a new album and, this time, it was visible after only a single refresh.

So it looks like it was the rouge FLAC and/or one of the other issues that my cleanup activities resolved.

It would be nice if the MPD file scanner was more resilient but, we can consider this resolved as the MPD code base is not under your control.

Again, thanks for your help.

[TheOldPresbyope]

...so now it's time for you to edit your first post in this thread to mark it solved, yes?

Regards,
Kent

[Nykkuno]

...so now it's time for you to edit your first post in this thread to mark it solved, yes?

Regards,
Kent

True.

Figured out how to do that now...