Option to prevent m2ts files from being imported/renamed #3722

New issue

Closed

opened 2026-02-19 22:37:09 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-19 22:37:09 -05:00

Owner

Originally created by @23833716 on GitHub (Oct 27, 2019).

The largest m2ts of a full UHD disc backup is being imported/moved by Radarr, it's also being renamed. I would like to be able to prevent this behavior somehow as I need the entire backup unmodified. When the m2ts file is moved and renamed it takes some legwork to figure out exactly what I need to rename it back to.

My only option appears to be stopping Radarr from handling completed downloads, which would not ideal as I would still like Radarr to handle completed downloads of containers (ie mkv). Basically, I would like the best of both worlds. ;)

Just hoping there could be an option added in the future. Maybe under 'Completed Download Handling' a toggle to select yes or no to 'Apply to m2ts files?'.

Originally created by @23833716 on GitHub (Oct 27, 2019). The largest m2ts of a full UHD disc backup is being imported/moved by Radarr, it's also being renamed. I would like to be able to prevent this behavior somehow as I need the entire backup unmodified. When the m2ts file is moved and renamed it takes some legwork to figure out exactly what I need to rename it back to. My only option appears to be stopping Radarr from handling completed downloads, which would not ideal as I would still like Radarr to handle completed downloads of containers (ie mkv). Basically, I would like the best of both worlds. ;) Just hoping there could be an option added in the future. Maybe under 'Completed Download Handling' a toggle to select yes or no to 'Apply to m2ts files?'.

deekerman

2026-02-19 22:37:09 -05:00

closed this issue
added the
Type: Feature Request
label

deekerman commented

2026-02-19 22:37:10 -05:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Oct 27, 2019):

Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.90. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot[bot] commented on GitHub (Oct 27, 2019): Issue-Label Bot is automatically applying the label `feature_request` to this issue, with a confidence of 0.90. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/Radarr/Radarr) and [code](https://github.com/hamelsmu/MLapp) for this bot.

deekerman commented

2026-02-19 22:37:10 -05:00

Author

Owner

@stale[bot] commented on GitHub (Dec 26, 2019):

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.

@stale[bot] commented on GitHub (Dec 26, 2019): 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.

deekerman commented

2026-02-19 22:37:10 -05:00

Author

Owner

@pinn73 commented on GitHub (Jul 8, 2020):

This is still an issue. I don't have rename option on but radarr only moves the large m2ts file correctly and the other files are left in the original folder meaning there are 2 entries for the movie in Kodi.

@pinn73 commented on GitHub (Jul 8, 2020): This is still an issue. I don't have rename option on but radarr only moves the large m2ts file correctly and the other files are left in the original folder meaning there are 2 entries for the movie in Kodi.

deekerman commented

2026-02-19 22:37:10 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Nov 14, 2020):

multi file support to fix this will be covered in a future version...

Duplicate of #145

@bakerboy448 commented on GitHub (Nov 14, 2020): multi file support to fix this will be covered in a future version... Duplicate of #145