High bitdepth (> 8): Could not find a strategy for crc32c_8x8!

[L4cache]

Sorry for being so late, I encountered this problem several months ago.
Build is successful but when actually running the built binary the error occurs.
(mingw-w64 is used for building)
I've made a simple workaround, which appears to bypass the problem.
L4cache@484f5aa

[Jovasa]

Yes, we are aware of this and will fix it eventually. We haven't had the time to put too much effort on 10 bit encoding, thus there might be some problems with it.

[L4cache]

Thanks, but before the real fix happens, is my workaround safe to use though? At least it can make the encoder produce bitstream rather than exits immediately, but I see Windows logs error in event log whenever the high bitdepth encoder "finishes" encode, I'm not sure if it's gonna break my encoding result.
By the way, the 8-bit encoder outputs bitstream with Main10 profile... I know it's in spec, but is it intentional?

[Jovasa]

Thanks, but before the real fix happens, is my workaround safe to use though?

As long as you don't use IBC, it should be OK.

At least it can make the encoder produce bitstream rather

Have you verified with VTM that the encoded bistream is valid?

I see Windows logs error in event log whenever the high bitdepth encoder "finishes" encode, I'm not sure if it's gonna break my encoding result.

Sound like the encoder might crash on when closing itself. This should not affect the produced bitstream. If I have time next week I'll try to investigate.

By the way, the 8-bit encoder outputs bitstream with Main10 profile... I know it's in spec, but is it intentional?

Currently the profile is hard coded so it defaults to the one that allows widest range of outputs.

[fador]

By the way, the 8-bit encoder outputs bitstream with Main10 profile... I know it's in spec, but is it intentional?

I can add to this that I believe the Main profile used in previous standards was removed and Main10 is the new basic profile to be used also for 8-bit coding.