如何修复损坏的 *.ts 文件

如何修复损坏的 *.ts 文件

抱歉我的英语不好,但我希望你能理解我的问题。

我有一个 18GB 的​​传输流文件,似乎已损坏。因此无法将此文件上传到 Youtube。现在我希望你们中有人能帮助我。也许可以剪掉损坏的部分或恢复整个文件。为了更好地分析,这里是“ffprobe”命令的输出(Windows 10)

ffprobe.exe -i z:\mario\Video.ts

ffprobe version 2021-01-27-git-149bfc2445-full_build-www.gyan.dev Copyright (c) 2007-2021 the FFmpeg developers
  built with gcc 10.2.0 (Rev6, Built by MSYS2 project)
  configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-lzma --enable-libsnappy --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libdav1d --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libglslang --enable-vulkan --enable-opencl --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint
  libavutil      56. 64.100 / 56. 64.100
  libavcodec     58.119.100 / 58.119.100
  libavformat    58. 65.101 / 58. 65.101
  libavdevice    58. 11.103 / 58. 11.103
  libavfilter     7. 98.100 /  7. 98.100
  libswscale      5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc    55.  8.100 / 55.  8.100
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[h264 @ 00000197fa177a80] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 00000197fa177a80] decode_slice_header error
[h264 @ 00000197fa177a80] no frame!
[mpegts @ 00000197fa15ac00] PES packet size mismatch
[mpegts @ 00000197fa15ac00] Packet corrupt (stream = 1, dts = 7475501244).
Input #0, mpegts, from 'z:\mario\Video.ts':
  Duration: 04:50:35.30, start: 65626.756933, bitrate: 9617 kb/s
  Program 25114
  Program 25115
  Program 41104
  Program 44106
  Program 44107
    Stream #0:0[0x233]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(tv, bt709, top first), 1920x1080 [SAR 1:1 DAR 16:9], 25 fps, 25 tbr, 90k tbn, 50 tbc
    Stream #0:1[0x234](deu): Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, fltp, 192 kb/s
  Program 44108

error.log然后我使用以下命令创建了一个文件

ffmpeg.exe -v error -i z:\mario\Video.ts -f null - >error.log 2>&1

日志文件保存在以下 Google 驱动器上。

https://drive.google.com/file/d/1PCrvstWkZtisyCn-AWqgFjPjBOYEidK5/view?usp=sharing

感谢您的帮助!

答案1

解决这样的问题需要专门的软件。

以下是一些此类产品:

我没有使用过其中任何工具,因此无法对其中任何一个给出我个人的推荐。

相关内容