Avidemux Forum

Avidemux => Windows => Topic started by: michaelosh on July 17, 2021, 08:52:06 PM

Title: failed
Post by: michaelosh on July 17, 2021, 08:52:06 PM
i try to open dvb-c ts record and it write me attempt to open name.ts failed!
in my old computer it was open files like this
how can i find solution to this?
Title: Re: failed
Post by: eumagga0x2a on July 17, 2021, 10:21:07 PM
1. Please make sure you have write permissions to the directory where the MPEG-TS file is located.

2. Please make sure you use the latest 64-bit nightly build (https://avidemux.org/nightly/) of Avidemux for Windows (builds cross-compiled for Windows on Linux are in the "win64" folder, native builds are in "vsWin64", pick the most recent one).

3. If an .idx2 index file for the MPEG-TS video has been created, delete it.

4. Start Avidemux and try to load this MPEG-TS file. If it still cannot be loaded, please close Avidemux and attach the log file %localappdata%\avidemux\admlog.txt to your reply.

Further steps depend on the content of the log file.
Title: Re: failed
Post by: michaelosh on July 18, 2021, 01:40:28 PM

Simple loading:
 file: D:/‏‏תיקיה חדשה (2) הקלטות/ D:/20210318 0113 - STARS HD - instant record.ts, size: 67294788
 found 1 files
Done
[TsPacket] Detecting TS/TS2...
[TsPacket] Score : 188:20, 192:1 out of 20
[TsPacket] Probably TS1 (188)...
[TsIndexer] Audio probed, 0 found, doing video
Starting H264 indexer

Simple loading:
 file: D:/‏‏תיקיה חדשה (2) הקלטות/20210318 0113 - STARS HD - instant record.ts, size: 67294788
 found 1 files
Done
[TsPacket] Detecting TS/TS2...
[TsPacket] Score : 188:20, 192:1 out of 20
[TsPacket] Probably TS1 (188)...
[qtRegisterDialog] 13:37:40-856 reparenting widget DialogProcessing
[tsPacketLinear] Refill failed for pid : 0xb21 (2849)
[tsPacketLinear] Refill failed for pid : 0xb21 (2849)

[tsHeader::open] 13:37:40-866 Indexing of D:/movie/20210318 0113 - STARS HD - instant record.ts failed, aborting
Close event!
[HandleAction] 13:37:57-001 ************ EXIT **************
[HandleAction] 13:37:57-001 Closing ui
[renderDestroy] 13:37:57-019 Cleaning up Render
[Qvideo]Destroying QVideo
[ADM_clearQtShellHistory] 13:37:57-020 Clearing script shell history (0 entries)
[myQApplication::~myQApplication] 13:37:57-020 Cleaning render...
[renderDestroy] 13:37:57-020 Cleaning up Render
[myQApplication::~myQApplication] 13:37:57-020 Cleaning preview...
[admPreview::destroy] 13:37:57-020 Destroying preview
Cleaning up
[admPreview::destroy] 13:37:57-020 Destroying preview
[ADM_vf_clearFilters] 13:37:57-020 clear filters
[ADM_EditorSegment::deleteAll] 13:37:57-020 [Editor] Deleting all videos
[ADM_EditorSegment::deleteAll] 13:37:57-020 [Editor] Deleting all videos
[Script] Tinypy INFO - Closing Python
[admDxva2_exitCleanup] 13:37:57-020 Dxva2 cleanup begin
[admDxva2_exitCleanup] 13:37:57-020 Dxva2 cleanup end
[ADM_ad_cleanup] 13:37:57-020 Purging audio decoder
[ADM_vf_cleanup] 13:37:57-021 Destroying video filter list
--End of cleanup--

Images stat:
___________
Max memory consumed (MB)     : 0
Current memory consumed (MB) : 0
Max image used               : 0
Cur image used               : 0
[ADM_ExitCleanup] 13:37:57-023
Goodbye...

[myQApplication::~myQApplication] 13:37:57-023 Exiting app
[preferences::save] 13:37:57-027 Saving prefs to C:\Users\micha\AppData\Roaming\avidemux\config3.tmp
[admPreview::destroy] 13:37:57-040 Destroying preview
Normal exit
[abortExitHandler] 13:37:57-040 already done, nothing to do
Title: Re: failed
Post by: eumagga0x2a on July 18, 2021, 01:58:45 PM
Was it with the latest nightly? (I would not need to ask this question if you had provided the entire admlog.txt file)

If yes and if the content of the file is innocuous enough, please provide the problematic file (it is just ~64 MiB small) as a sample via WeTransfer (no email address required!), Mega, Dropbox or Google Drive so that I can investigate why indexing fails.
Title: Re: failed
Post by: michaelosh on July 18, 2021, 03:52:17 PM
Quote from: eumagga0x2a on July 18, 2021, 01:58:45 PMWas it with the latest nightly? (I would not need to ask this question if you had provided the entire admlog.txt file)

If yes and if the content of the file is innocuous enough, please provide the problematic file (it is just ~64 MiB small) as a sample via WeTransfer (no email address required!), Mega, Dropbox or Google Drive so that I can investigate why indexing fails.
y
yeah it was lightly
later today i will send you private wetransfer
Title: Re: failed
Post by: eumagga0x2a on July 18, 2021, 04:37:39 PM
Thank you, got the sample (which seems to be heavily damaged as mpv fails to play it), looking into it.
Title: Re: failed
Post by: michaelosh on July 18, 2021, 05:13:03 PM
Check you pm
Title: Re: failed
Post by: eumagga0x2a on July 18, 2021, 05:45:09 PM
The failure to index the file is caused by either misparsed or incorrect PMT in the file (we end up with program IDs, specified by the PMT, which don't exist). Forcing brute-force reading allows indexing to succeed. Will try to investigate deeper later.
Title: Re: failed
Post by: michaelosh on July 18, 2021, 07:38:10 PM
Quote from: eumagga0x2a on July 18, 2021, 05:45:09 PMThe failure to index the file is caused by either misparsed or incorrect PMT in the file (we end up with program IDs, specified by the PMT, which don't exist). Forcing brute-force reading allows indexing to succeed. Will try to investigate deeper later.
thx
Title: Re: failed
Post by: michaelosh on July 19, 2021, 09:17:27 PM
Quote from: eumagga0x2a on July 18, 2021, 05:45:09 PMThe failure to index the file is caused by either misparsed or incorrect PMT in the file (we end up with program IDs, specified by the PMT, which don't exist). Forcing brute-force reading allows indexing to succeed. Will try to investigate deeper later.

Found sloution?need maybe other file?
Title: Re: failed
Post by: eumagga0x2a on July 20, 2021, 12:09:03 AM
Didn't have time yet (actually, not even time to turn on the PC until late at night). No other sample needed, at least for now, thank you.
Title: Re: failed
Post by: eumagga0x2a on July 24, 2021, 01:33:58 PM
Should be fixed by [demuxers/MpegTS] Verify that video track advertised by PMT is present, fix handling of multiple PMTs sharing the same PID, skip decoding PSI if section syntax indicator is not set (https://github.com/mean00/avidemux2/commit/6e3f289a1653d16946364ffe158fdbe3ab6ffb9a). Please try a future nightly or build Avidemux from source yourself.

The main issue was that we gladly accepted – no questions asked – the first video track a PMT had to offer and were seeking back to where we started after each cycle of seeking and decoding the next PMT in the list specified by PAT, thus getting the same data when multiple PMTs were broadcast with the same PID.
Title: Re: failed
Post by: michaelosh on July 25, 2021, 03:48:47 PM
Quote from: eumagga0x2a on July 24, 2021, 01:33:58 PMShould be fixed by [demuxers/MpegTS] Verify that video track advertised by PMT is present, fix handling of multiple PMTs sharing the same PID, skip decoding PSI if section syntax indicator is not set (https://github.com/mean00/avidemux2/commit/6e3f289a1653d16946364ffe158fdbe3ab6ffb9a). Please try a future nightly or build Avidemux from source yourself.

The main issue was that we gladly accepted – no questions asked – the first video track a PMT had to offer and were seeking back to where we started after each cycle of seeking and decoding the next PMT in the list specified by PAT, thus getting the same data when multiple PMTs were broadcast with the same PID.
So download tomorrow the nightly build and check if it working?
Title: Re: failed
Post by: eumagga0x2a on July 25, 2021, 06:08:34 PM
"Nightly" is a general term for a non-release build / a build from the current state of development. I don't know when the next set of official nightly builds will be generated and uploaded, but it is likely that there will be some in course of the week.

If you have a Linux system, you can build Avidemux for Windows from source yourself (https://github.com/mean00/avidemux2/blob/master/cross-compiling.txt) and become independent from the supply of official builds.
Title: Re: failed
Post by: eumagga0x2a on August 01, 2021, 09:19:28 AM
I am openly curious how (presumably) fixed versions cope with real-world MPEG-TS files in your case. Have you already tried the latest nightly from https://avidemux.org/nightly/win64/ (https://avidemux.org/nightly/win64/)?