-
Notifications
You must be signed in to change notification settings - Fork 8
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
skiptosilence.lua causing black screens on videos permanantly #3
Comments
That's very odd but very interesting. Please provide me with this info:
I'll try to reproduce and see what could be the problem. I'm in a pretty busy period with finals atm, so it could take until the end of the month to get this resolved. I'll try to figure out the file cache location ASAP though so you get your files back though. |
I've tested with many videos, and it appears to only happen to specific episode of a show I have. Mpv folder below. |
I found two files that are possible candidates and I've (very quickly and briefly) tried both, neither give an issue with my setup. Could you verify which (if any) is the right file? You can check the file's file length in the Properties window.
or
This doesn't mean I can't reproduce, but it's worth making sure I'm working with the right file going forward. |
Oh my bad I completely forgot about that for some reason.
I'm definitely using the 1080p version, not the 480p or 720p. ([HorribleSubs] One Piece - 41 [1080p].mkv)
The file in question for assurance file Size: 572 MB (600,391,566 bytes)
https://pastebin.com/3JGggVng Here is a magnet where you can find this file. (paste bin because large)
…On 1/18/21, Arthur Jochems ***@***.***> wrote:
I found two files that are possible candidates and I've (very quickly and
briefly) tried both, neither give an issue with my setup. Could you verify
which (if any) is the right file? You can check the file's file length in
the Properties window.
- Filename: [HorribleSubs] One Piece - 41 [720p].mkv
- Size: 357251278 bytes
or
- Filename: [HorribleSubs] One Piece - 41 [480p].mkv
- Size: 162619832 bytes
This doesn't mean I can't reproduce, but it's worth making sure I'm working
with the right file going forward.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#3 (comment)
|
I haven't gotten around to this bug in a while because other priorities took over. Have you still experienced this issue since? |
I'm experiencing the same issue, where i press f3 and the black screen fast seeking doesn't stop, and whenever this happens, mpv produces this warning
For me it happens with any of the mkvs from It also happens, in general, with files with a pretty high bitrate. |
Seems to be a common issue. |
Disabling the video and subtitle while skipping instead of applying a blackout filter, fixes detuur#3. When there are too many packets in the demuxer packet, caused by exceeding the expected inside a packet then skipping will not stop and result in the action to never end. This is resulted from subtitles and video output from my testing. Also fixed the script-opts template in the same PR.
This issue is fixed in a PR I've received, so expect an update soon. |
From time to time when I use skiptosilence (f3), it will continue to speed through the video, and mess up the video (make the screen black). I assume this is because it doesn't find an area without sound for some reason so it continues to go without stopping, doing something to the video while its at it. After video is reloaded the video persists to be invisible due to some kind of settting applied by skiptofade script.
Opening a file affected by this issue will spread to other files you open in the same window and make them unwatchable too, and it is really messed up if the user doesn't know what to do, and it has honestly troubled me alot today. (I eventually found a work around by renaming my files to something else)
I currently have a few videos I can't watch anymore because the screen is black (subtitles show, and audio is working) each time I open them they continue to use whatever settings the script did to the video...
Could you resolve this problem? Or help me get my videos working again? I think I need to delete the cache containing details per-video about what settings to use.. and I have no idea where to find that.
The text was updated successfully, but these errors were encountered: