JE

Thanks for your pull request. But putting this in a new function i think it is the wrong way. Could you integrate this feature in the current search method? You...

which function are you talking about?

Same issue here. I debugged it a bit and it is related to where the MatroskaExtractor is getting its dolbyvision config from: https://github.com/google/ExoPlayer/blob/release-v2/library/extractor/src/main/java/com/google/android/exoplayer2/extractor/mkv/MatroskaExtractor.java#L2223 My TV does not support dolby vision...

fyi @christosts

@christosts , needed now to switch back to a previous version of exoplayer... the workaround was not working anymore for some videos since **getDecoderInfos** only returns **one** entry and that...

`#define X_DIAG_PIN PC1 // X-STOP #define Y_DIAG_PIN PC3 // Y-STOP #define Z_DIAG_PIN PC0 // Z-STOP #define E0_DIAG_PIN PC2 // E0DET #define E1_DIAG_PIN PA0 // E1DET`

This would be nice!