-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
[BUG] SMP decoder crashing #243
Comments
Is there any solution for that? I'd like to use H265 but it is only possible with SMP decoder |
This is a bit off-topic, but will NDL for both audio and video work with H264? |
Yes NDL + ALSA works fine. |
Got it. Thanks for the error log, but according to that it doesn't look good. Because the crash happens inside the system decoder so SMP may not function correctly on your TV. |
SMP is not working on my TV also. I've described the issue before in another post that wasn't specifically about the SMP crash, so I'll get into more details here. First, here are my specs: Basic information
As you can see, we have the same webOS version. SMP was working just fine with it and i could stream at 4K with no issues. Someone in my house accidentally updated my firmware to version 05.20.15. Before that, SMP worked just fine. I tried downgrading my TV, but after reading some forums I found out that version 05.20.15 specifically disabled the ability to downgrade the software, somehow. I really have little experience in coding, and no experience in working with webOS. Could it be that the changes made by LG in this version also messed up with the ability to use SMP somehow? And if that's the case, could there be any workaround? Here's my log file, just in case: Thanks! |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Game should open normally
Basic information
Additional context
NDL + ALSA works fine.
SMP + ALSA + h264 = crashes crash.txt
SMP + ALSA + h265 = connecting forever
Crash log
The text was updated successfully, but these errors were encountered: