-
Notifications
You must be signed in to change notification settings - Fork 396
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
0% processed, no scenes detected - Bluray MKV #186
Comments
Adding a mediainfo dump as well, in case it helps. |
Hey @adworacz; Unfortunately PySceneDetect cannot handle files with multiple audio tracks correctly. Updated error information has been added in the latest version with the following workaround (on the FAQ): The best I can do for now is to suggest removing the audio tracks if possible via:
Sorry about the inconvenience. Will close this as a dupe of #179 if that's okay with you? I just don't want to create a huge temporary file on users systems when this occurs, so hoping the updated error messaging makes sense. |
Edit: I do seem to be two versions behind, so I'll try updating as well. I'm not sure if that's the same issue - I'm not receiving that error, and if I use it on the same version of a movie that's passed through Handbrake encoding, which has multiple audio tracks, it works just fine. I admit, the underlying codecs for the audio and video are completely different, but both utilize the same number of frames and multiple audio tracks. Here's proof:
With that video's media info: |
Okay, I updated to the latest version from git, and I AM receiving that error now. As you say, extracting the video out does allow for pyscenedetect to run. It is interesting that some videos with multiple audio tracks work, and others don't... So yes, feel free to close this as a duplicate. |
Hello @adworacz; Thanks for getting back to me on that. I thought that it affected every video with multiple audio tracks, so that is new information to me. Are you able to share a small sample that triggers the issue out of curiosity? I would like to store it for future reference when I'm able to revisit this issue... If not though, no worries! Eventually I would like to see if it's possible to rewrite PySceneDetect using a lower-level ffmpeg library for doing the video I/O, or perhaps doing it in C++ via the SceneStats project. These are far in the future unfortunately, so for now PySceneDetect is kind of stuck using the OpenCV VideoCapture API, which doesn't really help much with debugging these kinds of issues. Sorry for the inconvenience, and thanks for the report. |
I'm now wondering if this was actually related to something similar to Breakthrough/DVR-Scan#62 where the first frame actually can't be decoded for some reason. Reaching out to folks to see if anyone can share a minimal working example (as short of a clip as possible exhibiting this issue). Thank you! |
Bug/Issue Description:
Unable to detect/process Bluray MKV at all, scenedetect just exits instantly with no obvious logs.
Required Information:
Provide the following information to assist with reporting the bug:
scenedetect -i The\ Martian\ -\ Extended\ Edition_t02.mkv -v debug detect-content
-v debug -l BUG_REPORT.txt
to the beginning of the command, then re-run PySceneDetect and attach the generatedBUG_REPORT.txt
file.I was unable to, and it produced the following error:
Removing the
-l BUG_REPORT.txt
produce the following:Expected Behavior:
I expected scenedetect to scan the file in question and produce a timecode list of scenes, just like it does on the DVD below.
Computing Environment:
Additional Information:
I tried in on a DVD MKV (both produced using MakeMKV on this same machine) and it worked just fine.
Sample output below from successful run. Same machine, same day, same software install.
The text was updated successfully, but these errors were encountered: