My file structure follows Plex guidelines and looks like this:
/Movies
/Awesome Movie (2017)
Awesome Movie (2017).mp4
/Behind The Scenes
Awesome Movie (2017) - Making Awesome Movie.m4v
/Deleted Scenes
Awesome Movie (2017) - Not Awesome Scene 1.m4v
Awesome Movie (2017) - Not Awesome Scene 2.m4v
/Interviews
Awesome Movie (2017) - Awesome Movie Star 1.m4v
Awesome Movie (2017) - Awesome Movie Star 2.m4v
/Scenes
Awesome Movie (2017) - Awesome Movie Scene 1.m4v
/Trailers
Awesome Movie (2017) - Awesome Movie Trailer 1.m4v
Awesome Movie (2017) - Awesome Movie Trailer 2.m4v
Awesome Movie (2017) - Awesome Movie Trailer 3.m4v
The problem I'm running into is that Radarr is attaching to the files in the subfolders instead of the main movie folder. This results in Radarr constantly trying to upgrade my files. The "Modify Movie Files" button doesn't seem to work.
Is there any way to get Radarr to ignore either subfolders or certain extensions? All of my "extras" files were given m4v and the main movie file given mp4 to make searches easier.
I have a similar request, how do you make radarr ignore Extras subfolder. Which per kodi structure is where all that stuff should live...

@thezoggy Extras subfolder should already be ignored by disk scan service as it’s part of the directory ignore regex. I’ll refactor the unit tests for it tonight and make sure they are passing.
Any chance Radarr could automatically ignore the folders in the original post - they're the reserved list of subfolders that Plex uses for movie extras. (Behind The Scenes, Deleted Scenes, Interviews, Trailers, Scenes)
Failing that, if there's a movie file in the root of the selected folder, assume that's the main movie file? (or files - some can be pt1, pt2, etc.).
Most of my titles have extras, and often Radarr picks one such file as the main movie and tries to upgrade it.
This issue has been automatically marked as stale because it has not had recent activity. Please verify that this is still an issue with the latest version of Radarr and report back. Otherwise this issue will be closed.
this bot is annoying
@thezoggy It is not when you have 274 issues open and some of them without either any information or already fixed. I agree for some issues it is annoying, but IMO collectively it makes a lot of sense.
The base idea is fine but it's just annoying it's closing valid issues.
Perhaps it can ignore closing stuff if you added a label/milestone or
something. That can tell the user yes I know about the issue and I plan to
get to it.. instead of having the user keep bumping.
On Sun, May 6, 2018, 3:25 AM Leonardo Galli notifications@github.com
wrote:
@thezoggy https://github.com/thezoggy It is not when you have 274
issues open and some of them without either any information or already
fixed. I agree for some issues it is annoying, but IMO collectively it
makes a lot of sense.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Radarr/Radarr/issues/1494#issuecomment-386862785, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAekkhmu4V1YX-WMrFCbdpuQtJTtfBNVks5tvrODgaJpZM4NS16L
.
Agreed, didn't have time yet to fiddle with the details of the bot. Added a confirmed label now.