-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renamer: <baseFileName>
includes File Extension (.mkv)
#1846
Comments
Would also like to add that i've used linuxserver/docker-mediaelch as well to see if this particularly pertains to Windows 11, however it is replicable there as well under the same conditions.
The scanner for MediaElch correctly correlates the US and JP versions together, however shows the filepath for the US version. When saving, it saves the metadata for the JP release. For example: |
Hi, thanks for reporting! I can't reproduce it (yet). Could you tell me more about your file names and post them here? Do you separate your movies by folders? Your screenshot in your second post does not have the issue your described in your first one. Does your movie's filename have another extension such as The logic for the "baseFileName" relies on Qt, the UI framework we use. It uses Regards, Andre |
Sorry for the confusion, the files you see in my second comment were manually edited to remove the
As you can guess, yes, for this specific reason I have enabled it in Windows to ensure that this doesn't happen but also to make filetypes transparent without relying on Explorer itself to guess what it is (sometimes it applies, for example 'Adobe Acrobat PDF' if Acrobat is installed instead of just 'PDF') Here is a previously saved film, por example: And its files, from when they were added to ME: I'm not familiar with Qt, however it is strange the issue is replicable for me both on Windows and Linux (through linuxserver/docker-mediaelch). After some testing though, I introduce a strange problem that amends it: By isolating the film, on my Desktop in a folder named MediaElch successfully writes the new metadata without the file extension appended. So perhaps this is related to filepath length somehow? |
Oh, wow! Thank you very much for reproducing the issue! mkdir my-movie && cd $_
touch my-movie-us.mkv my-movie-jap.mkv
@hologarden In my opinion, this is a bug. Interestingly, there is a TODO note in the code about file extensions, where I've linked to #1175 That means I will have to double check the logic and will need to check that I don't introduce an old bug again. There is currently nothing you can do. |
Describe the bug
See title.
To Reproduce
Steps to reproduce the behavior:
映画 聲の形 (2016).mkv.nfo
instead of映画 聲の形 (2016).nfo
Expected behavior
See step 4 of reproduction.
Screenshots
If applicable, add screenshots to help explain your problem.
MediaElch Version:
Operating System:
Additional context
I have only recently updated to 2.12.0, though I don't know what previous version I had. This behavior is either newly intended or unintentional, but either way Jellyfin does not like it and it has messed with applying metadata to new entries.
The text was updated successfully, but these errors were encountered: