Brad Hards

@shaundmorris What is the status on this PR? Are we moving forward with java 11 only?

If this is not a bug (i.e. it is expected behaviour), this behaviour should be documented.

Thanks for the report. Do you have time to contribute a test case that demonstrates the problem, and possibly a fix?

I don't believe we support Android on 1.11.0 (see https://github.com/WestRidgeSystems/jmisb/issues/253). Some of the work to split out dependencies that don't exist on Android (like BufferedImage) is on the 2.x branch....

Looks like a similar issue to https://github.com/bytedeco/javacv/issues/1514 Does that work for you?

OK - looks like we're back to #253. If you have a chance, try the 2.x branch. That would at least give you KLV decoding, then you could work out...

Yes, 2.x is in development, not released yet. Getting Android working is one of the goals for the 2.0.0 release. Any assistance (especially pull requests for code or documentation) would...

There are multiple issues here. I'll try to break it up with different responses, which might enable threading. The part about ``` [MetadataDecodeThread - klv_metadata_test_async.ts - 0] WARN org.jmisb.api.klv.st0102.ObjectCountryCodeString -...

The part about ``` org.jmisb.api.common.KlvParseException: Invalid classifying country coding method: 0 ``` looks like bogus data. You can't use 0 (see ST 0102 Table 2). Doing so invalidates the classification...

The offsets are likely driven by not providing good PTS info. Are you providing precision time stamps in the SEI and metadata? Can you possibly align off that instead? The...