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

converting problem #189

Open
birizui opened this issue Dec 30, 2024 · 6 comments
Open

converting problem #189

birizui opened this issue Dec 30, 2024 · 6 comments

Comments

@birizui
Copy link

birizui commented Dec 30, 2024

Hey, after a couple days using v5.8, i found these problems:

  1. For idk reason, many conversions got corrupted in a way that the output doesn't render the real duration and get jumpy when i play them. Picture below is one of the example. The real recording is only 6 minutes, but the file produced/showed almost 2 hours duration. However, when i play it, it'll play minute 1, then skip-jumped to minute 15, then minute 45, and so on. In total, the recorded duration was less than 3 minutes, the other 3 minutes gone because of that skip-jumps.

1735539922400-01

  1. I tried to fix that problem by setting the command automatic duration for only 100 seconds, but unfortunately the app (often) wouldn't do the command. It'd record longer duration than what i asked unless i type ctrl+c manually (eventho i already use mode automatic) and the output most likely would end up corrupted.

Please help fix this. Thank you.

@Michele0303
Copy link
Owner

Try running the command:

ffmpeg -i corrupted_video.mp4 -c copy fixed.mp4

@birizui
Copy link
Author

birizui commented Dec 30, 2024

Try running the command:

ffmpeg -i corrupted_video.mp4 -c copy fixed.mp4

How to use this? Do i have to rename the corrupted_video.mp4? Because i got this result:

Trailing option(s) found in the command: may be ignored.
[in#0 @ 0xb40000776e89c900] Error opening input: No such file or directory
Error opening input file corrupted_video.mp4.
Error opening input files: No such file or directory

@Michele0303
Copy link
Owner

Instead of corrupted_video.mp4 put the name of the corrupted video, or rename it

@birizui
Copy link
Author

birizui commented Dec 30, 2024

Instead of corrupted_video.mp4 put the name of the corrupted video, or rename it

Thank you. Turns out in termux i have to add /sdcard/Documents/ in front of the video name. Unfortunately, this doesn't fix the problem because the corrupted video already in mp4 format. The output still jumpy with unmatched duration like my original post.

@birizui
Copy link
Author

birizui commented Dec 30, 2024

Instead of corrupted_video.mp4 put the name of the corrupted video, or rename it

Thank you. Turns out in termux i have to add /sdcard/Documents/ in front of the video name. Unfortunately, this doesn't fix the problem because the corrupted video already in mp4 format. The output still jumpy with unmatched duration like my original post.

Follow up: the command above only works for file with flv still in it, for example TK_name_2024.12.30_07-46-16_flv.mp4

Meanwhile my corrupted video already in format like this: TK_name_2024.12.30_07-46-16.mp4

This problem didn't happen in v5.4

@roberto-sartori-gl
Copy link

I can confirm I see problem 1) too, I had a video which is expected to be ~17 minutes long but is reported as 1h long whenever I play with any player. The video is fine up to the ~17 minutes mark, and then a static image is present.

The command:
ffmpeg -i recorded_file.mp4 fixed_file.mp4

does not fixes the issue, even if the encoding shows as encoded only 17 minutes the final file is still reported as 1h long (in the example of the 17 minutes file above).

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