Thanks for pointing this out!
The reason for the assert is that the y4m read function did not have support for 422. We have just checked in a fix to that. (There was no such support in version 1 either, but that binary might have been compiled without the asserts)
Here is a new binary:
https://drive.google.com/open?id=1iJ...yQmWu6EwPwOQ10
Now it should be able to understand both 422 and 444 directly from the y4m file so there is no need to indicate "-input-chroma-format 2 -input-bitdepth 10". I hope it works fine now!