Opus files with a bitrate below 130 kbps are detected as "Unknown" #4362

New issue

Open

opened 2026-02-20 03:04:15 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-20 03:04:15 -05:00

Owner

Originally created by @sn0skier on GitHub (Feb 10, 2026).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

I have some .opus files with a bitrate below 130 kbps. They are detected as unknown when imported into Lidarr.

There is a related closed item, but they never provided the logs so it was closed without being resolved: https://github.com/Lidarr/Lidarr/issues/2784
Notice that they also had a file below 130 kbps.

Expected Behavior

.opus files below 130 kbps should be recognized as "OGG Vorbis Q5" quality or possibly some other "OGG Vorbis" quality.

Steps To Reproduce

Import a low quality .opus file of <130 kbps into lidarr.
Examine the status of the file inside Lidarr and see that it is "Unknown"

Environment

- OS: Windows 11
- Lidarr: 3.1.2.4913 (plugins branch)
- Docker Install: No
- Using Reverse Proxy: No
- Browser: Chrome Version 144.0.7559.133 (Official Build) (64-bit)
- Database: Sqlite 3.50.4

What branch are you running?

Plugins (experimental)

Trace Logs?

https://gist.github.com/sn0skier/88382deba605e94c3722286ae25012d8

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @sn0skier on GitHub (Feb 10, 2026). ### Is there an existing issue for this? - [x] I have searched the existing open and closed issues ### Current Behavior I have some `.opus` files with a bitrate below 130 kbps. They are detected as unknown when imported into Lidarr. There is a related closed item, but they never provided the logs so it was closed without being resolved: https://github.com/Lidarr/Lidarr/issues/2784 Notice that they also had a file below 130 kbps. <img width="397" height="351" alt="Image" src="https://github.com/user-attachments/assets/03642e4a-5d0b-4997-a46d-5d4eb2ffee06" /> ### Expected Behavior `.opus` files below 130 kbps should be recognized as "OGG Vorbis Q5" quality or possibly some other "OGG Vorbis" quality. ### Steps To Reproduce 1. Import a low quality .opus file of <130 kbps into lidarr. 2. Examine the status of the file inside Lidarr and see that it is "Unknown" ### Environment ```markdown - OS: Windows 11 - Lidarr: 3.1.2.4913 (plugins branch) - Docker Install: No - Using Reverse Proxy: No - Browser: Chrome Version 144.0.7559.133 (Official Build) (64-bit) - Database: Sqlite 3.50.4 ``` ### What branch are you running? Plugins (experimental) ### Trace Logs? https://gist.github.com/sn0skier/88382deba605e94c3722286ae25012d8 ### Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. - [x] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman added the

Type: Bug

Status: Needs Triage

labels

2026-02-20 03:04:15 -05:00

deekerman commented

2026-02-20 03:04:16 -05:00

Author

Owner

@sn0skier commented on GitHub (Feb 10, 2026):

I contacted the discord with this issue and they provided this screenshot of the code

As I mentioned there, I think a lot of people will run into this issue as downloads from YouTube hover around the 130 kbps mark and regularly dip below it. Decreasing the cutoff to 120 kbps should significantly reduce the incidence of this issue, though it may not eliminate it entirely. Maybe other "OGG Vorbis" qualities should be added?

@sn0skier commented on GitHub (Feb 10, 2026): I contacted the discord with this issue and they provided this screenshot of the code <img width="297" height="120" alt="Image" src="https://github.com/user-attachments/assets/37fd0c85-28f9-45aa-a3f0-fcfc05def6b0" /> As I mentioned there, I think a lot of people will run into this issue as downloads from YouTube hover around the 130 kbps mark and regularly dip below it. Decreasing the cutoff to 120 kbps should significantly reduce the incidence of this issue, though it may not eliminate it entirely. Maybe other "OGG Vorbis" qualities should be added?