1080p DASH stream conjoined to (4x64) video

[Chox]

Okay this one might be a bit hard to explain.

Was recording an MPD DASH stream using N_m3u8DL-RE and was not aware that in the first hour of the stream being live it was outputting a garbage 4x64 video stream before sending out 1080p30 video an hour later.

Everytime I try to remux the recorded mp4 and m4a file it keeps reporting itself to be 1 hour and 36 minutes long and at a bitrate of 76mbps when in actuality it is 12 hours long at a bitrate of 9mbps.

The M4A file also reports itself as being "H264" even though it's within an .m4a container.

I believe this might be caused by a corrupted header (if not the header from the different video coming in the first hour) but I'm not sure.

Here is the ffprobe for the video file.

D:\youtubedl>ffprobe "D:\OUTSIDE_LANDS_2025--CHOXUWU\DAY_1\AMAZON_PRIME_STREAM\c
enc_2025-08-08_11-35-17.mp4"
ffprobe version N-114833-g5e380bcdb1-20240415 Copyright (c) 2007-2024 the FFmpeg
 developers
  built with gcc 13.2.0 (crosstool-NG 1.26.0.65_ecc5e41)
  configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-conf
ig=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64 --target-os=mingw
32 --enable-gpl --enable-version3 --disable-debug --disable-w32threads --enable-
pthreads --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype --en
able-libfribidi --enable-gmp --enable-fontconfig --enable-libharfbuzz --enable-l
ibvorbis --enable-opencl --disable-libpulse --enable-libvmaf --disable-libxcb --
disable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth
--enable-chromaprint --enable-libdav1d --enable-libdavs2 --enable-libdvdread --e
nable-libdvdnav --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --ena
ble-frei0r --enable-libgme --enable-libkvazaar --enable-libaribcaption --enable-
libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus -
-enable-librist --enable-libssh --enable-libtheora --enable-libvpx --enable-libw
ebp --enable-lv2 --enable-libvpl --enable-openal --enable-libopencore-amrnb --en
able-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libope
nmpt --enable-librav1e --enable-librubberband --enable-schannel --enable-sdl2 --
enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-l
ibuavs3d --disable-libdrm --enable-vaapi --enable-libvidstab --enable-vulkan --e
nable-libshaderc --enable-libplacebo --enable-libx264 --enable-libx265 --enable-
libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIB
TWOLAME_STATIC --extra-cxxflags= --extra-libs=-lgomp --extra-ldflags=-pthread --
extra-ldexeflags= --cc=x86_64-w64-mingw32-gcc --cxx=x86_64-w64-mingw32-g++ --ar=
x86_64-w64-mingw32-gcc-ar --ranlib=x86_64-w64-mingw32-gcc-ranlib --nm=x86_64-w64
-mingw32-gcc-nm --extra-version=20240415
  libavutil      59. 15.100 / 59. 15.100
  libavcodec     61.  5.103 / 61.  5.103
  libavformat    61.  3.100 / 61.  3.100
  libavdevice    61.  2.100 / 61.  2.100
  libavfilter    10.  2.101 / 10.  2.101
  libswscale      8.  2.100 /  8.  2.100
  libswresample   5.  2.100 /  5.  2.100
  libpostproc    58.  2.100 / 58.  2.100
[mov,mp4,m4a,3gp,3g2,mj2 @ 00000000004daf40] could not find corresponding trex (
id 1)
[mov,mp4,m4a,3gp,3g2,mj2 @ 00000000004daf40] could not find corresponding track
id 0
[mov,mp4,m4a,3gp,3g2,mj2 @ 00000000004daf40] trun track id unknown, no tfhd was
found
[mov,mp4,m4a,3gp,3g2,mj2 @ 00000000004daf40] error reading header
D:\OUTSIDE_LANDS_2025--CHOXUWU\DAY_1\AMAZON_PRIME_STREAM\cenc_2025-08-08_11-35-1
7.mp4: Invalid data found when processing input

And here is a sample of both the corrupted video/audio files and a healthy recording from the same exact DASH stream.

https://gofile.io/d/ozJatt

Any help would be appreciated!

[Chox]

Bump!

[Chox]

Bump

[videoAI]

The error messages you're encountering with `ffprobe` indicate that there
are issues with the MP4 file. This suggest that the file may be corrupted or
improperly formatted. Here’s an error breakdown and potential solutions:

Error Breakdown:

1. Could Not Find Corresponding TREX: This indicates that the track reference
extension (TREX) for the specified track ID is missing. This can happen if the
file is not properly encoded.

2. Could Not Find Corresponding Track ID: This suggests that the specified
track ID does not exist in the file, which may be due to corruption.

3. TRUN Track ID Unknown: The track run (TRUN) box is referencing a track
ID that cannot be found, indicating a problem with the file structure.

4. Error Reading Header: This is a general error indicating that `ffprobe`
cannot read the file's header, which is essential for understanding the file's
format and contents.

Potential Solutions

- Try using `ffmpeg` to convert the file to another format or re-encode it.
This can sometimes fix structural issues:

ffmpeg -i "D:\OUTSIDE_LANDS_2025--CHOXUWU\DAY_1\AMAZON_PRIME_STREAM\cenc_2025-08-08_11-35-17.mp4" -c copy output.mp4

or use a good program like clever FFmpeg-GUI

Tip:
In the future, use TVDownloader, update youtube-dl.exe. It gives you a GUI,
resolution [select / best], metadata, FFmpeg / youtube-dl, and password
handling [protected sites] options for your downloads.

[Chox]

The error messages you're encountering with `ffprobe` indicate that there
are issues with the MP4 file. This suggest that the file may be corrupted or
improperly formatted. Here’s an error breakdown and potential solutions:

Error Breakdown:

1. Could Not Find Corresponding TREX: This indicates that the track reference
extension (TREX) for the specified track ID is missing. This can happen if the
file is not properly encoded.

2. Could Not Find Corresponding Track ID: This suggests that the specified
track ID does not exist in the file, which may be due to corruption.

3. TRUN Track ID Unknown: The track run (TRUN) box is referencing a track
ID that cannot be found, indicating a problem with the file structure.

4. Error Reading Header: This is a general error indicating that `ffprobe`
cannot read the file's header, which is essential for understanding the file's
format and contents.

Potential Solutions

- Try using `ffmpeg` to convert the file to another format or re-encode it.
This can sometimes fix structural issues:

ffmpeg -i "D:\OUTSIDE_LANDS_2025--CHOXUWU\DAY_1\AMAZON_PRIME_STREAM\cenc_2025-08-08_11-35-17.mp4" -c copy output.mp4

or use a good program like clever FFmpeg-GUI

Tip:
In the future, use TVDownloader, update youtube-dl.exe. It gives you a GUI,
resolution [select / best], metadata, FFmpeg / youtube-dl, and password
handling [protected sites] options for your downloads.

I came to the VideoHelp forum to speak with real people. I am not in need of a glorified ChatGPT, if I did I would have just gone to ChatGPT (which I already have).

FFMPEG throws the same error as FFPROBE. From what I can gather FFMPEG cannot handle the file in it's current state. This is not a YouTube video, this is a DASH livestream capture. I can't just "redownload it".

And no mkvtoolnix doesn't make a difference when muxing. Still reports a garbage video and audio track (that reports itself as AVC and not audio), same time code and a 4x64 video resolution.

Please anyone that is a real person I would very much value your input.

Using Untrunc-GUI with a healthy stream sample just puts out an error.
I can only assume that at this point the video file requires some sort of manual header repair/transplant through some sort of hex editor.
If anyone can show a guide, recommend free programs or some directions for that I would very much be grateful for that. The best thing I have been able to find that fits this criteria is an old version of "AtomBox Studio" and even that application crashes when ingesting the file.

EDIT: I should add that the file size is practically the same as a healthy capture. 50~gb video track and 800~mb for audio track.

[videoAI]

You could have fooled me ..
BTW, I am a real person ..

Any help would be appreciated!

[Chox]

You could have fooled me ..
BTW, I am a real person ..

Any help would be appreciated!

Apologies if I came off harsh. Been trying to get someone to look at this thread. Would have assumed so from the syntax of your response and the general advice in your response giving off LLM generic response vibes. Also your name is literally "videoAI".

[videoAI]

Apologies accepted.

Lets start over ..

The name was selected in an attempt to move the forum into 2025.
it is astonishing how many users are still asking about VCRs and video tapes.

Your replies would be easier to read if you place them above, not below, the
quoted text.

I did use AI to analyze the log file which is faster than sifting through it myself
but my tips were all me (human that is ..). I still stand by my recommendations
for the two tools I proposed.

However I do understand your preference for N_m3u8DL-RE. I prefer GUIs to
command line tools.

clever FFmpeg-GUI has a scan video section. worth a try ...
Also it is one of the best FFmpeg based multiplexers by far

My Knowledge of streaming is fairly good .. but my atom hex editing skills
may not be up to par.

so why did I attempt to help out?
- you bump'd twice ..
- and no one was responding ..

I guess everyone is asleep, being middle of the night and all, at least in North America.

Apologies if I came off harsh. Also your name is literally "videoAI".

[Chox]

Apologies accepted.

Lets start over ..

The name was selected in an attempt to move the forum into 2025.
it is astonishing how many users are still asking about VCRs and video tapes.

Your replies would be easier to read if you place them above, not below, the
quoted text.

I did use AI to analyze the log file which is faster than sifting through it myself
but my tips were all me (human that is ..). I still stand by my recommendations
for the two tools I proposed.

However I do understand your preference for N_m3u8DL-RE. I prefer GUIs to
command line tools.

clever FFmpeg-GUI has a scan video section. worth a try ...
Also it is one of the best FFmpeg based multiplexers by far

My Knowledge of streaming is fairly good .. but my atom hex editing skills
may not be up to par.

so why did I attempt to help out?
- you bump'd twice ..
- and no one was responding ..

I guess everyone is asleep, being middle of the night and all, at least in North America.

Apologies if I came off harsh. Also your name is literally "videoAI".

[Attachment 88344 - Click to enlarge]

I appreciate your input. But I think I'm gonna need someone with atom hex editing skills for this case.

[videoAI]

Now that we're sure the file is severely damaged, and assuming you still do not want a paid option,
you are left with ..

1- try recover-mp4-to-h264, if you have not tried it already.
2- can you open/play the file in VLC? I doubt it, but if yes ... you have options
3- a third option is to use a software trial version to create a working sample from which you can copy the header info to your 50gb file using a hex editor or a header copy program. try 'Video Repair Tool'.

I appreciate your input. But I think I'm gonna need someone with atom hex editing skills for this case.

[Chox]

Now that we're sure the file is severely damaged, and assuming you still do not want a paid option,
you are left with ..

1- try recover-mp4-to-h264, if you have not tried it already.
2- can you open/play the file in VLC? I doubt it, but if yes ... you have options
3- a third option is to use a software trial version to create a working sample from which you can copy the header info to your 50gb file using a hex editor or a header copy program. try 'Video Repair Tool'.

I appreciate your input. But I think I'm gonna need someone with atom hex editing skills for this case.

recover-mp4-to-h264 results in a 2.4 kb file size. Recommend and custom arguments in the syntax?

Edit: It appears "--start read from position" is producing a file size congruent to the actual video file and not mere kilobytes. Will update if this leads to resolution.

Edit 2: The outputed file is only 43 percent of the actual file size.

Is Video Repair Tool just a glorified Untrunc-GUI with a pay wall?

[videoAI]

which tool gave you "43 percent of the actual file size"?

"The free trial version of Video Repair Tool will repair half of your movie."

Edit 2: The output file is only 43 percent of the actual file size.