GitHub
Moderator
[pvrparse] author @the bandit @Ev0 sets wrong return code
processPacket() was changed to return -2 for a "broken startcode" (was return 0 in 5.6.002). The new parseData() propagates this via early exit, and
asyncWrite() treats -2 as stream corruption and calls return len before the actual disk write — meaning recording data is silently discarded. This
affects channels where a PUSI packet's PES payload doesn't begin with 0x000001 (CI-decrypted channels, MPEG-1 audio, subtitle streams, etc.).
Continue reading...
processPacket() was changed to return -2 for a "broken startcode" (was return 0 in 5.6.002). The new parseData() propagates this via early exit, and
asyncWrite() treats -2 as stream corruption and calls return len before the actual disk write — meaning recording data is silently discarded. This
affects channels where a PUSI packet's PES payload doesn't begin with 0x000001 (CI-decrypted channels, MPEG-1 audio, subtitle streams, etc.).
Continue reading...