TS Transport Stream validation

[maudit]

hi, is there a free software that given a ts video file, it check it and tells me if all is ok, or maybe for example due to a lack of signal power for a second or more.. some frames and/or audio parts are missing or corrupted?

[netmask56]

As long as it is mpeg2 ProjectX was once the program to use but that was decades ago. Now TSDoctor, a paid program but it does have a fully operational free period. Possibly VideoRedo has a free period?

[maudit]

ok, well, all ts are h264 encoded nowadays, and those trial sw u indicated, are trial... anyway thankyou for the info.

[lollo]

I highly recommend TSDoctor.

It is not free, but is a wonderful piece of software. I am using it since more than 10 years to check my dvb-s/dvb-t hd/sd transport stream recordings with high satisfaction!

[johnnyquid]

You could use a ffmpeg command such as:
ffmpeg -f_err_detect +bitstream+buffer+careful+compliant+aggressive -i "myfile.ts" -f null NUL

See https://ffmpeg.org/ffmpeg-formats.html for more information.

[maudit]

You could use a ffmpeg command such as:
ffmpeg -f_err_detect +bitstream+buffer+careful+compliant+aggressive -i "myfile.ts" -f null NUL

See https://ffmpeg.org/ffmpeg-formats.html for more information.

I see.. interesting... thanks but can you help me understand a couple of things?

what these two commands do? I mean -i and -f null NUL
-i "myfile.ts" -f null NUL

anyway where is the ffmpeg install folder?
I'm trying to locate the folder where to write that command in the command prompt.

also

1 - err_detect, f_err_detect flags (input)
Set error detection flags. f_err_detect is deprecated and should be used only via the ffmpeg tool.

it says "is deprecated and should be used only via the ffmpeg tool."
what that means? what is ffmpeg tool? what I have do to?
Have I to use err_detect and not f_err_detect? I can't get it.


other commands are clear..

2 - ‘bitstream’
Detect bitstream specification deviations.

3 - ‘buffer’
Detect improper bitstream length.

4 - ‘careful’
Consider things that violate the spec and have not been seen in the wild as errors.

5 - ‘compliant’
Consider all spec non compliancies as errors.

6 - ‘aggressive’
Consider things that a sane encoder should not do as an error.

[maudit]

sry double message, (I replied instead of edit) ignore this..

edit: I also wanted to thank netmask56 and lollo for their suggestions.
ciao grazie.

[johnnyquid]

-i is used before the name of the input file that you want to check.
-f null specifies that no output file is to be created. Usually ffmpeg converts the input file(s) to an output file (usually to a different format).
Replace "myfile.ts" with whatever file you want checked.
NULL is used as dummy output file (which is not actually created). ffmpeg usually always wants an output filename specified.

I usually get the ffmpeg binaries (programs) from this website at https://www.videohelp.com/software/ffmpeg. It does not come with an installer so the program ffmpeg.exe will be wherever you unzip the files. The -f_err_detect flag works when using ffmpeg.exe. It may not work with the ffmpeg related programs.

[maudit]

thx a lot johnnyquid, is all clear and perfectly explained.
just a couple of questions:

- that archive you mentioned: https://www.videohelp.com/software/ffmpeg
is it the same I can find here?:
https://ffmpeg.org/download.html#build-windows
https://www.gyan.dev/ffmpeg/builds/
ffmpeg-git-full.7z

- about the ffmpeg.exe I already have in the \MeGUI-2913-64\tools\ffmpeg folder,
I have to not care about it? is it another ffmpeg build specifically made for MeGUI?

be patient, i'm sorry if they are naive questions, I never did it before, I cannot get why many softwares,
like audacity or subtitle edit or others must download their own version of ffmpeg, instead of using just one.

[johnnyquid]

New versions of ffmpeg get released pretty often. The ones you mention are likely just different versions. ffmpeg can be built to support many different video/audio formats and each build could have support for a different set video/audio formats. Peoply also build them with different compilers and compiler options so some builds might be a bit faster or slower than others. The so called "full" builds usually support the most formats but even the ones that are not "full" builds likely support the video/audio format that you will have to deal with. I would recommend just getting the non-beta version from this site.