mirror of
https://github.com/Radarr/Radarr
synced 2024-12-22 16:02:43 +00:00
Updated Common Problems (markdown)
parent
bf6678aea0
commit
e67be96003
1 changed files with 3 additions and 2 deletions
|
@ -25,8 +25,9 @@
|
||||||
* Radarr will need to move files away from where the downloader puts them into the final location, so this means that Radarr will need to read/write to both the source and the destination directory and files.
|
* Radarr will need to move files away from where the downloader puts them into the final location, so this means that Radarr will need to read/write to both the source and the destination directory and files.
|
||||||
* On Linux, where best practices have services running as their own user, this will probably mean using a shared group and setting folder permissions to `775` and files to `664` both in your downloader and Radarr. In umask notation, that would be `002`.
|
* On Linux, where best practices have services running as their own user, this will probably mean using a shared group and setting folder permissions to `775` and files to `664` both in your downloader and Radarr. In umask notation, that would be `002`.
|
||||||
|
|
||||||
## Movie Files Not in Folders
|
## Movie File and Folder Naming
|
||||||
* Currently, Radarr requires that each movie be in a folder. The format should be something like `./Movie Title (Year)/` to facilitate correct identification during import. Further, having the quality in the filename is also useful like `Movie Title (Year) [Quality-Resolution].ext` so that during import the correct quality will be matched. A useful tool for making these changes to your collection is [filebot](http://www.filebot.net/#download) which has paid version in both the Apple and Windows stores, but can be found for free on their [SourceForge](https://sourceforge.net/projects/filebot/files/latest/download) site. It has both a GUI and CLI, so you can use whatever you're comfortable with.
|
* Currently, Radarr requires that each movie be in a folder with the format `Movie Title (Year)/`, optionally `_` or `.` are valid separators. To facilitate correct quality and resolution identification during import, a file name like `Movie Title (Year) [Quality-Resolution].ext` is best, again `_` or `.` are valid separators too.
|
||||||
|
* A useful tool for making these changes to your collection is [filebot](http://www.filebot.net/#download) which has paid version in both the Apple and Windows stores, but can be found for free on their [SourceForge](https://sourceforge.net/projects/filebot/files/latest/download) site. It has both a GUI and CLI, so you can use whatever you're comfortable with. For the above example, `{ny}` expands to `Name (Year)` and `{vf}` gives the resolution like `1080p`. There is nothing to infer quality, so you can hard code that using something like `{ny} [Bluray-{vf}]` assuming you want to make your entire collection Bluray in quality.
|
||||||
* This limitation is a known source of concern, a [feature request](http://feathub.com/Radarr/Radarr/+29) exists to enable the option to *not* use a folder for each movie and the developers have this in mind for the future.
|
* This limitation is a known source of concern, a [feature request](http://feathub.com/Radarr/Radarr/+29) exists to enable the option to *not* use a folder for each movie and the developers have this in mind for the future.
|
||||||
* The [[Create a Folder for Each Movie]] is a great source for making sure your file and folder structure will work great.
|
* The [[Create a Folder for Each Movie]] is a great source for making sure your file and folder structure will work great.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue