I find it hard to believe the user isn't expected to read any documentation, that's ignorance on the user's part. We have tooltips in the UI with warnings and help text and get questions about it, best case we point it out and they realize their mistake or worst case we point it out, they don't understand it and need more help, perhaps some of that is on use for being unclear or using domain specific terms, but largely it seems people don't read.
Remux vs x264 plus#
I find it hard to believe the user isn't expected to read any documentationĪ difference between none and having to read a lot though, plus if I've learned anything it's that people don't read.
Remux vs x264 how to#
Not to mention the people that had a friend set it up and then they tweak things, you shouldn't need to be a developer, be a rocket scientist or read a bunch of documentation to understand how to use Sonarr.
It's not really hard to double click an icon and setup basic settings, it becomes a lot more complicated when you suddenly see something way out of your realm and don't understand it. Like said, we're not going to customize everything to make FlexGet, if you want that, use FlexGet. The average joe shouldn't be ignored because a fraction of users would use a complicated feature. If the qualities are there that you want, what does a complicated custom quality setup give you? Re-ordering qualities within a profile trips people up enough already (not a lot, but enough) and this wouldn't help any. Most users aren't developers, we don't want to expose them to things they don't need to see.
Unless there is a skill testing question to unlock this mode I'm sure we'd get questioned on how to build the regex and test it and on and on, support hell. For a small group of users this may unlock some potential, but for everyone else it would be completely unnecessary and come with a 100% chance of being used wrong and having to be addressed via support. This would is exactly what we don't want to do, this is what FlexGet is/can be.
Remux vs x264 upgrade#
If this is difficult for somebody, i don't think they could get sonarr up and running by themselves, but it's just my 2 cents.Ĭorrect, right now they are in the same group, we want to split them out, but allow them to be in a profile with the same weight, so Sonarr could grab WEB-DL or WEB-Rip, but not both and also upgrade to a higher quality (this is covered by another issue you commented on, #1781 where I have added an example). If an avarage joe wants to go deeper, a 10 line forum guide can explain the system, and how can he edit it, if he chooses. instad of the current hdtv-1080p and webdl-1080p. a quality could be called amzn, or webdl, or internal or -myfavourite group. they can do everything with that system basicly, and can rank them in whatever order they want in the profiles they have created. You make and advanced only setting, where people can edit the tags (regex, string, whatever you wanna call it) which put releases into quality profiles. The current system is fine for the avarage user imho. I don't see how is it confusing or difficult to implement what i proposed earlier. do you want to seperate that? or not, cos it's difficult? right now webdl and webrip is in the same group (webdl). Thanks for the answer, but i'm still not clear what you mean by grouping.
0 kommentar(er)
