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

"FFProbe failed to look up audio tracks on the file you have submitted." for All Media #15

Open
GuyPaddock opened this issue Aug 18, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@GuyPaddock
Copy link

No matter whether I select WAV, MP3, or MP4 files, I get this message:

FFProbe failed to look up audio tracks on the file you have submitted. 1. You may have submitted a file that isn't a Video 2. The video file is not supported by FFProbe. If you believe this is an error, please submit an Issue report :)

However, I am running video2srt in WSL and the browser is in Windows. Does video2srt access the file by its path on the machine directly, or does the file get uploaded through the web browser?

Alternatively, is this an issue with my NodeJS setup? I'm using NodeJS 22.6.0.

@MatejMecka MatejMecka added the bug Something isn't working label Aug 18, 2024
@MatejMecka MatejMecka self-assigned this Aug 18, 2024
@MatejMecka
Copy link
Collaborator

Hey there!

Thank you for reporting this ^_^ This is the first time I hear about such an issue, do you mind also attaching the logs of what happens in the developer console?

So everytime you upload a file to video2srt, it takes the file and creates a blob of the file with the lifetime being the same with how long video2srt is open in the browser tab. You can find the code for this part of the project here:

console.log(files);
console.log(`${files[0].name}: ${files[0].size} bytes`);
video_url = URL.createObjectURL(files[0]);
video_type = files[0].type;
dragged_file = true;

The reason why that error pops up is related to the FFProbe component where it looks for audio tracks. One of my guesses, I don't have much information to confirm if this is it. If you have built it locally do you serve the following headers:

Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Embedder-Policy: require-corp

Would it be also okay to send a file I can also attempt to reproduce on my machine? If it's something of sensitive nature you can also send me an email with the attachment.

Have a good day,
Matej

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants