I do see 5 cuts identified
2024-09-06T18:58:56 MCEBuddy.CommercialScan.Remover → ParseEDL: Cut Segment Start:0.000 End:61.301 Action:0
2024-09-06T18:58:56 MCEBuddy.CommercialScan.Remover → ParseEDL: Cut Segment Start:1212.502 End:1753.003 Action:0
2024-09-06T18:58:56 MCEBuddy.CommercialScan.Remover → ParseEDL: Cut Segment Start:2920.505 End:3536.006 Action:0
2024-09-06T18:58:56 MCEBuddy.CommercialScan.Remover → ParseEDL: Cut Segment Start:4776.211 End:5307.011 Action:0
2024-09-06T18:58:56 MCEBuddy.CommercialScan.Remover → ParseEDL: Cut Segment Start:5414.414 End:6543.000 Action:0
Then I see a failure when trying to cut the 3rd segment
2024-09-06T18:59:26 MCEBuddy.AppWrapper.FFmpeg → Conversion failed!
→ Process exited with code -1094995529
→ FFMpeg output file size [KB] → 34.00
Thereafter it stops and doesn’t cut the remaining segments (it shouldn’t so it may be a bug there) but it appears the original file may be corrupted.
2024-09-06T18:59:26 MCEBuddy.AppWrapper.FFmpeg → [mpegts @ 0000019b322f5e00] Invalid timestamps stream=0, pts=9216112, dts=9216113, size=14338
2024-09-06T18:59:26 MCEBuddy.AppWrapper.FFmpeg → [mpegts @ 0000019b322f5e00] Invalid timestamps stream=0, pts=9492388, dts=9492389, size=38037
2024-09-06T18:59:26 MCEBuddy.AppWrapper.FFmpeg → [mpegts @ 0000019b322f5e00] PES packet size mismatch
2024-09-06T18:59:26 MCEBuddy.AppWrapper.FFmpeg → [mpegts @ 0000019b322f5e00] Packet corrupt (stream = 0, dts = 594041354).
2024-09-06T18:59:26 MCEBuddy.AppWrapper.FFmpeg → [mpegts @ 0000019b322f5e00] PES packet size mismatch
2024-09-06T18:59:26 MCEBuddy.AppWrapper.FFmpeg → [mpegts @ 0000019b322f5e00] Packet corrupt (stream = 0, dts = 594041354).
Can you upload the original TS file and your .EDL file so we can replicate the issue and see what’s going on.