Skip to content
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: BestSource never works #27

Closed
ipid opened this issue Feb 10, 2023 · 9 comments
Closed

BUG: BestSource never works #27

ipid opened this issue Feb 10, 2023 · 9 comments

Comments

@ipid
Copy link

ipid commented Feb 10, 2023

Thanks for your Aegisub fork! Your fork has fixed a lot of bugs in Aegisub, and also integrated a lot of useful features that greatly improved my efficiency in creating subtitles.

Recently I found that Aegisub always crashes after I set the audio or video source to BestSource. I've tried every video on my computer, and no matter what kind of video I open, BestSource doesn't seem to work. FIX: I've tried many videos and it seems that video generated by Adobe Premiere makes BestSource crash.

Screenshot: Change video source to BestSource

Is this a known issue, or is it just not working on my machine?

@arch1t3cht
Copy link
Owner

It depends on what you mean. The BestSource video source is indeed extremely slow (it's only there as a safe fallback for videos where everything else fails) so it's normal for Aegisub to "freeze" for multiple minutes when loading it.
Regarding the audio source, I've had one or two crashes happening after fully caching audio loaded with BestSource, but it never happened reliably. If you only set the audio source, does it always crash, and if so, when exactly?

@seproDev
Copy link

seproDev commented Feb 10, 2023

I just attempted to use the BestSource video source on my machine and with every video I tried so far I first get the error message Timecodes are out of order in the scanning log window. While the first frame loads successfully on scrubbing Aegisub crashes.

Using Windows 10 with the Feature Release 09.

Here the crashlog.txt, though it's not really meaningful.

Attaching WinDbg, on crash I get: (390c.3af0): Integer divide-by-zero - code c0000094 (first chance)
Though, the real problem is likely with the scanning before. Occasionally and only on some files, I also get Couldn't read frame!

@ipid
Copy link
Author

ipid commented Feb 10, 2023

As for the video source

I had exactly the same bug as @seproDev's.

First I want to amend my statement: not all videos cause BestSource to crash, but videos generated by Adobe Premiere do.

Here I got 2 videos. One is Video-downloaded-from-Twitter.mp4 and another is Video-generated-by-Adobe-Premiere.mp4.

image

I've set both Video provider and Audio provider to BestSource:

screenshot

It opens the video from Twitter successfully but it outputs the length of each frame to be 1h20min:

image

And after opening the video from Premiere Pro, it reports Timecodes are out of order:

image

When I try to seek a frame other than the first frame, Aegisub crashes:

image

Let me provide the video sample here:

test-videos.zip

> sha256sum test-videos.zip
100e5e15855dd2073c51b30f2dc2b8521b878ec14d17b694c383586ccd98c800 *test-videos.zip

I'm using Win10 21H2 and the latest release (the portable one).

For Audio Source

Seems working fine.

@arch1t3cht
Copy link
Owner

Thanks for the detailed report, this was a very dumb mistake. I'm surprised the previous state even worked for the videos I tested.
I pushed a fix that makes the two videos above work for me, you can try it on this build.
Github autoclosed the issue after I pushed, but feel free to reopen it if there's still more issues.

@seproDev
Copy link

seproDev commented Feb 13, 2023

Tested out the build and most videos work now.
I still have this one video which crashes similarly, but only if it is the first video loaded.
To replicate. Delete the bsindex folder and load this video. The error message is Couldn't read frame!

arch1t3cht added a commit that referenced this issue Feb 13, 2023
@arch1t3cht
Copy link
Owner

Hopefully fixed with this build.

@seproDev
Copy link

Could you, re-run the windows build? It randomly failed.

@arch1t3cht
Copy link
Owner

Yup, done.

@ipid
Copy link
Author

ipid commented Feb 14, 2023

The Windows build works fine on my machine! Thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants