Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 775126" data-attributes="member: 82144">Hi again srr037From what you've said and what I know about our code, the field obviously lists the complete set of video inputs in our code. We support up to 3 of each kind of input on a single device, hence the 1's, 2's and 3's. S-video would make more sense to me too, as would component instead of YRYBY or RGB etc., but these relate to the inputs on crossbar devices which are labelled in the same way (as per the Microsoft BDA standard). Device manufacturers choose how they associate those labels with physical inputs like s-video, and unfortunately I don't think they all use the same associations. I'm going to blame Microsoft for this one, but I will keep it in the back of my mind for the future... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />mm</blockquote>

[QUOTE="mm1352000, post: 775126, member: 82144"] Hi again srr037 From what you've said and what I know about our code, the field obviously lists the complete set of video inputs in our code. We support up to 3 of each kind of input on a single device, hence the 1's, 2's and 3's. S-video would make more sense to me too, as would component instead of YRYBY or RGB etc., but these relate to the inputs on crossbar devices which are labelled in the same way (as per the Microsoft BDA standard). Device manufacturers choose how they associate those labels with physical inputs like s-video, and unfortunately I don't think they all use the same associations. I'm going to blame Microsoft for this one, but I will keep it in the back of my mind for the future... :) mm [/QUOTE]

Verification