Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Library files could not be written. Bug? (Read 2241 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Library files could not be written. Bug?

Hello there,

I am new here. I'm using foobar2000p since 2011. From this time forward I have the portable installation on my Windows-Share (small home-server) in my music-folder. Mostly I run foobar from this remote directory on my desktop pc. Until version 1.1 I had no problems using a big music library (around 500 GB Music).

My problem cames slowly in version 1.3. On closing foobar sometimes I'm getting the error 'Library files could not be written (Directory not empty). If you choose 'cancel', your recent library changes will be lost.'. After a few clicks on 'repeat' foobar quits successfully. Since the update to version 1.4.1 I'm getting the same error nearly everytime. Clicking 'repeat' doesn't work anymore. It seems that the error occours on (bigger) changes in library. If I run foobar without making major changes in the library the program closes successfully.

Console shows:

Code: [Select]
Shutting down...
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\filter", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0001", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0002", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0003", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0004", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0005", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0006", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0007", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0008", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0009", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0010", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0011", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0012", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0013", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\meta-0014", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\tree", reason: Object not found
Location not parsable: "X:\Musica\Foorbar_untouched\library\17CC571178B47388.old\filter", reason: Object not found

Running this portable foobar on the local machine (home server, Win 7 x64) there are no problems.

I've tried to run this portable installation from network share under Windows 10 x64:
  • with administrator privileges
  • in windows 7 compatible mode
  • with full access rights for 'everyone'
  • after deletion of the library-folder
  • with clean portable installation of version 1.4.1

no chance! Old version 1.1 is running perfectly.

Do you have any ideas? It would be wonderful if you can help me.

Thank you a lot and greetings!
Jan

Re: Library files could not be written. Bug?

Reply #1 –
Are you sure you tested with a clean portable install? I could simulate your issue by having the portable foobar2000 directory be included in the monitored library and having enabled the transacted filesystem operations.

I suggest you move the foobar2000 outside the monitored Musica directory, and make sure "Use transacted filesystem for saving configuration" setting is disabled under Preferences -> Advanced -> Tools.

Re: Library files could not be written. Bug?

Reply #2 –
Addressed for the next foobar2000 update, thanks for reporting.
For now, it might be a better idea not to include foobar2000's portable installation folder in your Media Library to avoid this.
Microsoft Windows: We can't script here, this is bat country.

Re: Library files could not be written. Bug?

Reply #3 –
Quote from: Case on
Are you sure you tested with a clean portable install?

Yes, I tested with a clean foobar2000 portable installation.

Quote from: Case on
I suggest you move the foobar2000 outside the monitored Musica directory, and make sure "Use transacted filesystem for saving configuration" setting is disabled under Preferences -> Advanced -> Tools.

Thank you very much. That works! Unfortunately now in my playlists the file paths to the audio files are wrong.

Quote from: Peter on
Addressed for the next foobar2000 update, thanks for reporting.
For now, it might be a better idea not to include foobar2000's portable installation folder in your Media Library to avoid this.

Thank you very much. I'm looking forward to it. So I make no changes in my playlists :)

Re: Library files could not be written. Bug?

Reply #4 –
Should be fixed in 1.4.2 beta 1.
Microsoft Windows: We can't script here, this is bat country.