Fix hypothetical issue with encrypted CEA608
This will never happen in practice, since CEA608 shouldn't be encrypted (and we can't handle it if it is), but in theory appendSampleEncryptionData can be called, then skipFully can throw when applying the CEA608 transformation, then when retrying appendSampleEncryptionData will be called again for the same sample. appendSampleEncryptionData consumes from trackFragment.sampleEncryptionData, and so the second time around data is being consumed one sample ahead. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=189931631
Showing
with
4 additions
and
4 deletions
Please
register
or
sign in
to comment