INTERACT FORUM

More => Old Versions => JRiver Media Center 19 for Windows => Topic started by: jacobacci on June 13, 2014, 03:48:23 am

Title: Dealing with read-only files
Post by: jacobacci on June 13, 2014, 03:48:23 am
I do a lot of tagging in JRiver (especially SACD ISOs as I can only tag them in MC). Every now and then when I save the tags, I get an error message that the file cannot be written to. I then need to open Windows Explorer, go into Properties and remove the read-only attribute. Then the tags can be saved just fine.

MP3tag has a nifty feature. In the case of a read only file, it offers to remove the read only attribute before saving the tags. Saves the detour via Windows Explorer. Could this be implemented in JRiver as well?
Thanks
Title: Re: Dealing with read-only files
Post by: fitbrit on June 13, 2014, 01:50:29 pm
+1
Title: Re: Dealing with read-only files
Post by: astromo on June 13, 2014, 04:07:20 pm
MP3tag has a nifty feature. In the case of a read only file, it offers to remove the read only attribute before saving the tags. Saves the detour via Windows Explorer. Could this be implemented in JRiver as well?
Thanks

Very sensible suggestion .. yes please.

I'd add to this that if this functionality is implemented to give the user the option to remove (provide means to reinstate if required) the read only attribute automatically. That's how I'd roll if I had the option.
Title: Re: Dealing with read-only files
Post by: 6233638 on June 13, 2014, 04:28:25 pm
That seems dangerous to me - after all, won't files that are marked as read-only be like that for a specific reason?
I'd say that rather than having Media Center remove the read-only status, an option to hide the error and only write changes to the library instead would be a better choice.
Title: Re: Dealing with read-only files
Post by: glynor on June 13, 2014, 08:29:56 pm
That seems dangerous to me - after all, won't files that are marked as read-only be like that for a specific reason?
I'd say that rather than having Media Center remove the read-only status, an option to hide the error and only write changes to the library instead would be a better choice.

If it asks first, I see no harm.

But otherwise I agree completely.
Title: Re: Dealing with read-only files
Post by: jacobacci on June 14, 2014, 06:44:16 am
Sounds good. Is there any way to know whether this makes it into the to-be-added-features list?
Would be great.