-
Notifications
You must be signed in to change notification settings - Fork 333
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
Abort on GetUseExternalSubtitles() m_open assertion if the directory contains subtitle files #736
Comments
I get this error also when I use --subtitles no matter where the subtitles file is located. It seems there is no way to view subtitles from srt files. |
OSD is completely disabled at the moment, but omxplayer should simply ignore subtitles and not break. So this is really a nasty bug. |
I still have this problem in most updated Raspbian Buster on Raspberry Pi 4B. The options that are mentioned in vicwomg/pikaraoke#3 doesn't exist in the Raspbian version. |
Those aren't options for the omxplayer command-line. |
Getting the same error here: omxplayer.bin: OMXPlayerSubtitles.h:86: bool OMXPlayerSubtitles::GetUseExternalSubtitles(): Assertion `m_open' failed.
/usr/bin/omxplayer: line 67: 5948 Aborted (core dumped) LD_LIBRARY_PATH="$OMXPLAYER_LIBS${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}" $OMXPLAYER_BIN "$@" Running with fake-KMS Driver and with Is there any alternative to run video with subtitles with fake-KMS enabled(I really need this for a project)? Thank you guys! |
Is anyone still maintaining this repo, or shall I fork it and solve the issue myself? |
Could you rewrite the whole OSD part to use Dispmanx instead of OpenVG? This would make it possible to use OSD (including subtitles) on the RPi 4. |
Migrating to vlc after testing it. It supports subtitles with fake-KMS enabled. Thanks anyway! |
Environment
Issue
When I play a video from a folder that contains an
.srt
subtitles file omxplayer breaks on an assertion onGetUseExternalSubtitles
:If I move the srt file out of the folder everything works fine.
Note that this has started happening only after the latest
apt-get upgrade
.The text was updated successfully, but these errors were encountered: