Or, do you think the Librarian would say “What books are they? We need to see what happened to them before we remove them from the catalog.” Do you think the Librarian would say “Sure, go ahead and do that”. What you are defending is analogous to you, in a physical Library and acting like Roon, going to the Librarian and saying “I can’t find 5 books on the shelves, so I want to delete them from the catalog”. It already has code and a UI to create and display a list of files it’s having a problem with - that’s what it does with the Skipped Files item already available under Libraries. Roon alreay monitors my library - that’s how it can identify this situation and suggest deleting the entries. If you don’t want or need such a feature, fair enough, just move on. Why on earth should Roon not make it easy and automatic to get a list of deletions to enable User investigation/remediation? If you have a workaround, fair enough, post the helpful response, it there is a feature that does what the OP is requesting but he has not discovered it and you know how to do it, fair enough - post the helpful response. How easy or difficult to implement the feature is technically is irrelevant, and is up to Roon Devs to resolve, not Roon users to challenge other Roon Users on. It is up to Roon staff to determine if a Feature Request is worthy of consideration and implementation, not other Users, and it is puzzling why you would take it upon yourself to effectively attack what to me and others, seems a perfectly reasonable function. I do not understand why you would go into battle to put down a reasonable request and to argue against it, unless the request fundamentally changes the way Roon works in other aspects such that Roon is degraded. The only appropriate responses from other Roon Users are to say “Yes, that would be good, I also vote for this”, or to post a method of doing what is requested or a workaround. How can that not be so?įeature Requests is a stream where Roon Users can post requests for changes or additional features that they would like to see made available. If the Roon Library Cleanup is proposing to delete database entries or pointers, it is perfectly reasonable for a User to want to easily and quickly know what source or target objects are involved. Roon is fundamentally a Music Library Management, Integration and Delivery tool. It seems what you want is for Roon to monitor your library and be able to report back when any files are removed or made unavailable for any reason and you want a detailed list of said files. It will also increase the UI complexity and take away from coding resources that could be utilized to make Roon better for everyone, not just those that want to see what files may have gone missing…or not. Like I said, what you want will increase support enquires. I would love to hear how this could be implemented with an appropriate UI for all customers to understand and use. Source for the third checkbox: files unavailable because the storage location or account they are associate with are disabled. Source for the second check box: files unavailable from a storage location that no longer exists. Source for the first check box: files that have been deleted via Roon, deleted from the file system, or removed from a streaming service. No, Roon tells you the source and the reason but not the individual file names. If the entries (files) had been listed they would have had much better information to start with and find out if it was an easily correctable local problem, rather than having to immediately contact Support. They had to contact Support to try and figure out what was going on and get advice on how to correct it. There are existing, fairly recent entries in this Support section by people who had hundreds or thousands of entries Roon wanted to delete. I want Roon to explcitly tell me which entries, corresponding to which missing files, it proposes to delete. If, for whatever reason, hardware, software, or user error, some files can’t be found by Roon any more, I don’t want to go off examining all my monitored locations to see if anything (based on my perfect knowledge and exact memory of every file they should contain) is missing (or had its security or filename accidentally changed). They spell out the reason that Roon wants to clean up some entries, without providing any information from the entries themselves which could be used to identify which particular files went missing. The 3 sections do NOT spell out the source of the files. I’m afraid we’re not writing English using the same meanings for all the words.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |