PJ Aitken

For me, the low bit of VCP e6 does indicate the PBP mode: With PBP mode enabled (ie, two inputs / split screen): ``` $ ddcutil -b 1 getvcp e6...

Thanks @rockowitz. I've emailed you some "ddcutil interrogate" outputs. The hardware configuration is debian connected to the displayPort + HDMI-1 inputs, and macOS connected to HDMI-2. No windows machines. I...

FWIW, ``ddcutil getvcp SCAN`` gives different output for some VCPs compared with discrete queries: SCAN: ``` VCP code 0x20 (Horizontal Position (Phase) ): current value = 0, max value =...

I see the same: different data returned by "scan" versus "getvcp". Here's the output of ``ddcutil getvcp SCAN --verbose --trcfunc=get_raw_value_for_feature_metadata --trcfunc=i2c_fileio_reader --trcfunc=i2c_fileio_writer``: ``` Getting data for non-table VCP code 0x20...

The earlier read of 0x02 returned 2. Writing 1 to 0x02 resets 0x02 - but 0x52 continues to report 0x02: ``` $DDC getvcp -b 1 x02 VCP code 0x02 (New...

@bugrasan I found how to set/swap the PBP inputs: setvcp 0x60 controls the input source: ``` 0f: DisplayPort-1 10: DisplayPort-2 11: HDMI-1 12: HDMI-2 ``` PBP mode has to be...

Internally to nDPI, it might not matter much that application IDs are reused. However nDPI nolonger stands alone: in the SDN world it is now used as part of larger...

I've added some example code [here](https://github.com/ntop/nDPI/pull/1090) for discussion. What do you think?

This is an example of how [issue 1072](https://github.com/ntop/nDPI/issues/1072) might be addressed.

@lnslbrty: > How do we want to handle custom protocol ids? As @IvanNardi mentioned in #1072 it is necessary that public ids and custom ids stay distinct. First, I think...