Implement more ACB, USM, CPK releated features #17
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
ATTENTION: Massive API breaking changes ahead. Merge at discretion!
This PR introduces the following new features (excerpt from README)
NOTE: Most if not all features here are verified through offical toolings, however at limited capacity.
ACB Cue sheets (also AWB)
USM Sofdec2 (Encode & Decode)
Audio Stream
Video Stream
NOTE: Requires on FFMpeg for extracting stream packets.
.mp4container).h264raw container).ivfcontainer)CPK
API changes
Most of the extraction APIs that rely on OS-level file APIs have been refactored to either output
bytesor to singular files, respectively mapping to builder'sbuild() -> bytesfunctions, and sometimes (i.e. with CPK) asave(filename)functions.Moreover, higher level abstractions (e.g.
UTFViewer) are sparingly used to simplify some of the processes. Refer to examples in Tests from the fork for more details.Various other quality-of-life changes plus changes to internals (e.g. UTF tables) shall be omitted here for the sake of brevity.
Credits
This PR also incorporates two of @Mikewando's fixes, which effectively supercedes these two PRs
Addendum
The fork's development continues at https://github.com/mos9527/PyCriCodecsEx, which will also be available at PyPI for easier consumption.