[PR #1319] Fix 708 timing issue

**Original Pull Request:** https://github.com/CCExtractor/ccextractor/pull/1319 **State:** closed **Merged:** Yes --- Process packet as soon as the packet len is equal to the specified len  **In raising this pull request, I confirm the following (please check boxes):** - [x] I have read and understood the [contributors guide](https://github.com/CCExtractor/ccextractor/blob/master/.github/CONTRIBUTING.md). - [x] I have checked that another pull request for this purpose does not exist. - [x] I have considered, and confirmed that this submission will be valuable to others. - [x] I accept that this submission may not be used, and the pull request closed at the will of the maintainer. - [x] I give this submission freely, and claim no ownership to its content. - [ ] **I have mentioned this change in the [changelog](https://github.com/CCExtractor/ccextractor/blob/master/docs/CHANGES.TXT).** **My familiarity with the project is as follows (check one):** - [ ] I absolutely love CCExtractor, but have not contributed previously. - [ ] I have never used CCExtractor. - [x] I have used CCExtractor just a couple of times. - [ ] I am an active contributor to CCExtractor. --- Process current packet as soon as the packet length is equal to the specified length. This leads to the packet being processed in the current FTS, instead of being processed in the next FTS, like before. Fixes #641 Also ends up fixing #646, as the last packet is now processed instead of waiting for a next packet which never comes This is causing the issue #677 again. Working on a fix for that

claunia commented

2026-01-29 17:20:15 +00:00

Owner

Original Pull Request: https://github.com/CCExtractor/ccextractor/pull/1319

State: closed
Merged: Yes

Process packet as soon as the packet len is equal to the specified len

In raising this pull request, I confirm the following (please check boxes):

I have read and understood the contributors guide.
I have checked that another pull request for this purpose does not exist.
I have considered, and confirmed that this submission will be valuable to others.
I accept that this submission may not be used, and the pull request closed at the will of the maintainer.
I give this submission freely, and claim no ownership to its content.
I have mentioned this change in the changelog.

My familiarity with the project is as follows (check one):

I absolutely love CCExtractor, but have not contributed previously.
I have never used CCExtractor.
I have used CCExtractor just a couple of times.
I am an active contributor to CCExtractor.

Process current packet as soon as the packet length is equal to the specified length. This leads to the packet being processed in the current FTS, instead of being processed in the next FTS, like before. Fixes #641

Also ends up fixing #646, as the last packet is now processed instead of waiting for a next packet which never comes

This is causing the issue #677 again. Working on a fix for that

claunia added the pull-request label 2026-01-29 17:20:15 +00:00

claunia closed this issue

2026-01-29 17:20:16 +00:00

[PR #1319] Fix 708 timing issue #2096