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: Is there an option to treat the library as read-only? (Read 1432 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Is there an option to treat the library as read-only?

I've used foobar2000 very little, but I'm playing with it a little right now. Is there any way to tell it to never alter any tagging info within the library? I don't need to use it for tagging and am afraid that with a slip of the mouse, I may inadvertently change something.

Is there an option to treat the library as read-only?

Reply #1
This question came up again in something I'm working on. Let's say you wanted to use foobar2000 as an audio player for a party. Is there any way in foobar2000 to be sure that someone allowed to use the program to control playback can't alter any metadata? Can the tagging capability be disabled?

Is there an option to treat the library as read-only?

Reply #2
Suggestion:
Create a separate "party" user account on your machine that has only read-only access to your music.
Microsoft Windows: We can't script here, this is bat country.

Is there an option to treat the library as read-only?

Reply #3
Yes, if foobar2000 offers no ability to be configured as only a player, I thought of doing that. I just wondered if it might be more customizable. Sometimes you just don't want a Swiss Army knife.

Is there an option to treat the library as read-only?

Reply #4
If such option existed, your "party users" could find it and turn it off.

You can also remove any components that have tag altering capability and hide "properties" etc from the context menu.

I could potentially add such switch and make all my components obey it, but I cannot guarantee that third party components would obey it as well so it would be somewhat pointless. Component authors should instead make sure that it's hard to make irreversible tag changes unintentionally rather than rely on app-wide "tag writing enabled/disabled" options.
Microsoft Windows: We can't script here, this is bat country.

 

Is there an option to treat the library as read-only?

Reply #5
I have a folder located at E:\music . . . size is 480+ GB . . . contains 13,934 files and 1,575 folders.

To set the read-only attribute on everything inside E:\music, I opened the Command Prompt window and typed:   ATTRIB +R E:\music\*.* /S /D

In less than a second everything inside E:\music was read-only.

To clear the read-only attribute on everything inside E:\music, I opened the Command Prompt window and typed:   ATTRIB -R E:\music\*.* /S /D

In less than a second everything inside E:\music was back to normal.