EatPrilosec 22 Posted November 19, 2024 Posted November 19, 2024 im familiar with this issue, it used to happen on hvec 7.1 files a lot, but they seem to have been fixed from what ive noticed. but now the issue occurs with an av1 file. this is the only av1 movie i have my first question is: is this a browser issue, because its directplay, that i just need to wait for chrome/chromium(thorium specifically) devs to fix with AV1 or should i go grab the logs for you guys? ps i am not using the official web app, https://app.emby.media/, im using the self hosted web app. idk if this category is correct for that, if not sorry.
Solution Luke 42077 Posted November 19, 2024 Solution Posted November 19, 2024 Quote my first question is: is this a browser issue, because its directplay, that i just need to wait for chrome/chromium(thorium specifically) devs to fix with AV1 or should i go grab the logs for you guys? HI, it's a little tricky, because yes, that is correct. Obviously you'd like to have a solution sooner than that, and Emby could help by having the server transcode the content. The problem is we can't just go and transcode everything because many users will not be happy about that. Opus is the most problematic audio codec right now. There are a lot of devices that claim to support it, but then you run into problems when you try to actually play. Whose fault it is, it's hard to say. They are probably building their opus support based on specs, and I'm sure there are probably buggy authoring tools that might not always be creating the files correctly.
EatPrilosec 22 Posted November 19, 2024 Author Posted November 19, 2024 (edited) 2 hours ago, Luke said: HI, it's a little tricky, because yes, that is correct. Obviously you'd like to have a solution sooner than that, and Emby could help by having the server transcode the content. The problem is we can't just go and transcode everything because many users will not be happy about that. Opus is the most problematic audio codec right now. There are a lot of devices that claim to support it, but then you run into problems when you try to actually play. Whose fault it is, it's hard to say. They are probably building their opus support based on specs, and I'm sure there are probably buggy authoring tools that might not always be creating the files correctly. gotcha: avoid opus for now. suggestion: maybe a user-configurable "always transcode" option in the metadata for problematic direct-play media? ps: i also tested this on an android with directplay afterwards and it sounded terrible. like, it was playing in a cave. so it may be a combination of a badly made media file and bad player implementation. emby however seems to transcode it properly, so theres that. which also means theres nothing a log would help with id think Edited November 19, 2024 by EatPrilosec 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now