XySubFilterAutoLoader Input Pin is not Named

[GoogleCodeExporter]

What steps will reproduce the problem?
1. On the auto-loading version, the input has no name.
2.
3.

What is the expected output? What do you see instead?
It should be named 'Input'.

What version of the product are you using? On what operating system?
Beta 2, Windows 7 64bit.

Please provide related subtitle script (if any). And the less characters
the script is, the less effort I have to make to fix the issue, so if you
could make the script as simple as possible, that would be appreciated.

Please provide any additional information below.
Posting this on behalf of Blight. He is attempting to get xysubfilter working 
with Zoom Player, and has discovered that the input pin on the autoloading 
version is not actually named. I was unsure if I should put this issue into bug 
#152, or create a new report - so I erred on the side of caution and created 
this new report.

Original issue reported on code.google.com by forum.an...@gmail.com on 19 Jun 2014 at 8:45

[GoogleCodeExporter]

The XySubFilterAutoLoader dummy input pin is indeed unnamed, but you'll need to 
explain what he is trying to do which makes this an issue.

Original comment by cyber.sp...@gmail.com on 19 Jun 2014 at 10:29

• Changed title: XySubFilterAutoLoader Input Pin is not Named
• Added labels: Type-Other
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

I checked with bLight. Initially, he was not able to get xysubfilter to work, 
due to the missing pin name (I assume this is how Zoom connects to the older 
xyvsfilter). He has now used the manual version of xysubfilter, which now 
allows Zoom to load xysubfilter. He said that with regards to the pin name, he 
was trying to make sure  he connected to the right pin if in the future 
xysubfilter decides to add additional pins for other functionality.

Original comment by forum.an...@gmail.com on 19 Jun 2014 at 1:34

[GoogleCodeExporter]

Strictly speaking, XySubFilterAutoLoader should not be used for manual graph 
building. 

It is a helper filter only, with the sole purpose of deciding whether or not to 
load XySubFilter into the graph (and unload VSFilter). This unnamed 'dummy 
input pin' is a special pin which rejects all connections by design. When 'Load 
When Needed' is enabled, this dummy pin is also used to spy on the MEDIATYPE of 
connection attempts. Reference: 
https://code.google.com/p/xy-vsfilter/issues/detail?id=152#c151

Check with Blight, but I think it would make sense to leave things how they 
are, with only 'real' connectable pins given the standard names of 'Input' & 
'Output' now and in the future? Though if he disagrees and would still prefer 
it be named anyway, we could certainly make that change in the next release.

That said, for DirectShow itself the pin name is purely cosmetic. The real 
value which matters for determining type is PIN_DIRECTION ( 
http://msdn.microsoft.com/en-us/library/windows/desktop/dd377427 | 
http://msdn.microsoft.com/en-us/library/windows/desktop/dd368733 ).

Original comment by cyber.sp...@gmail.com on 19 Jun 2014 at 3:49

[GoogleCodeExporter]

Thanks, I pointed him to your post. I think he is satisfied where things stand 
at the moment, and he is happy for the report to be closed.

Original comment by forum.an...@gmail.com on 21 Jun 2014 at 8:22

[GoogleCodeExporter]

Original comment by cyber.sp...@gmail.com on 24 Jun 2014 at 2:20

• Changed state: Done