by windcrest77 » Sat Aug 20, 2011 10:15 pm
Lowlander wrote:Yes, I'm currently running one PC with read-only access to the music files and there are no issues.
Yes it does work, but its not apparent unless you run a test and check the last modified time on the files. Because the property changes still get saved to MM DB but dont get captured in the media tags. Which is fine, this is the good behavior. As a test I copied a bunch of stuff to a second hard drive, scanned it in, then added a special permission to the root folder that denies all forms of write access, set it to inherit to all the contents. Then I updated some ratings and yes my files dont get changed.
Its nice that MM is ignoring permissions access errors it encounters when it goes to update the tags. But in a future release of MM it would be nice if songs that have write access denied errors maybe show up with a little icon on the grid row indicating that your last attempted update to that song wont be replicated in the media file just the DB. This way people that want their files read only would have the confidence in knowing that they are indeed read only, and people that dont want them read only would see immediately what files are not able to have their tags updated.
Now I can just log on with two accounts one for full control and another that wont change my files. I did my test with the everyone account, but the effect should be the same if I create a read only account, I'm the only one on this machine.
Better than the icon above or having to set permissions at all would be to have a checkbox in the MM options that simply let someone turn on/off all media file modification updating globally (or even a tree to set this property by folder). Then MM can be instructed to not allow any file/folder write IO to occur in that level, this includes tags, moving files, renaming, everything. Then you could run MM in read only mode whenever you plug in a certain hard drive that you dont want written to just by checkmarking the root to be read only. Inheritance would be assumed. And people would not have to mess with permissions and accounts.
[quote="Lowlander"]Yes, I'm currently running one PC with read-only access to the music files and there are no issues.[/quote]
Yes it does work, but its not apparent unless you run a test and check the last modified time on the files. Because the property changes still get saved to MM DB but dont get captured in the media tags. Which is fine, this is the good behavior. As a test I copied a bunch of stuff to a second hard drive, scanned it in, then added a special permission to the root folder that denies all forms of write access, set it to inherit to all the contents. Then I updated some ratings and yes my files dont get changed.
Its nice that MM is ignoring permissions access errors it encounters when it goes to update the tags. But in a future release of MM it would be nice if songs that have write access denied errors maybe show up with a little icon on the grid row indicating that your last attempted update to that song wont be replicated in the media file just the DB. This way people that want their files read only would have the confidence in knowing that they are indeed read only, and people that dont want them read only would see immediately what files are not able to have their tags updated.
Now I can just log on with two accounts one for full control and another that wont change my files. I did my test with the everyone account, but the effect should be the same if I create a read only account, I'm the only one on this machine.
Better than the icon above or having to set permissions at all would be to have a checkbox in the MM options that simply let someone turn on/off all media file modification updating globally (or even a tree to set this property by folder). Then MM can be instructed to not allow any file/folder write IO to occur in that level, this includes tags, moving files, renaming, everything. Then you could run MM in read only mode whenever you plug in a certain hard drive that you dont want written to just by checkmarking the root to be read only. Inheritance would be assumed. And people would not have to mess with permissions and accounts.