-
-
Notifications
You must be signed in to change notification settings - Fork 971
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
MovieFileController doesn't return Video Dynamic Range in CustomFormats when querying by movieId #9811
Comments
👋 @scalerow, In order to help you further we'll need to see logs. You'll need to enable trace logging and replicate the problem that you encountered. Guidance on how to enable trace logging can be found in our troubleshooting guide. |
Never mind, you're using the wrong arguments for /movie and most likely you're looking at different movies. And we're not even calculating custom formats for files in /movie. |
Are you referring to this: "/api/v3/movieFile?movieId=123"? If so, I might a phrased myself wrong - the id 123 was just meant as an example. I'm not sure exactly where you're formatting the score, all I have noticed is that if you select a movie using Interactive search, and you select a "download" that is measured to lets say score +6500, which includes a HDR-tag. Then wait for it to download, and check it out again in the "Files" -tab, the HDR-tag is gone, and the score will be +5000. To verify that I've selecteded a movie with score +6500 I clicked on history, which confirms that I in fact did select a movie with HDR and +6500 score. If I enable the column "Video Dynamic Range" in the Files-tab, it also confirms that the file indeed should've had a HDR tag. The first screenshot applied is the responses to requests radarr has sent when radarr loads the movie I've selected in my library. The second image is the request radarr sent when I clicked "History". I did attach radarr.trace.txt to the original issue , which was downloaded after a reproduction - are they missing something? EDIT: the second picture and the text added to it was missleading, sorry. The actual URL that picture stems from is: |
You attached the HTML output for something else. Attach the correct trace logs and we'll see after if the report is correct since history doesn't reflect the current state of the movie files. |
Sorry, I messed up the log file - this one should be correct. |
What's the release title/filename with this issue? |
Filname before renaming/organizing: Poor.Things.2023.2160p.WEB-DL.DDP5.1.Atmos.DV.HDR.H.265-FLUX |
Easy fix, add the |
Feeling stupid, I'm sorry for taking up your time. Thanks alot! |
Is there an existing issue for this?
Current Behavior
The endpoint at /api/v3/movieFile?movieId=123 does not return Video Dynamic Range, which in turn seems to cause the wrong custom format score when looking at a movies files. See example:
However the movie endpoint seems to be returning the correct custom formats and thus also the correct custom format score:
Expected Behavior
Should return the same custom fomats and the same custom format score
Steps To Reproduce
Environment
What branch are you running?
Develop
Trace Logs? Not Optional
radarr.trace.txt
Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.
trace
- that are relevant and show this issue.The text was updated successfully, but these errors were encountered: