Nathan,
It does not seem to be caused by any recent changes in MC. The huge delay was in DirectShow graph-building and definitely had to do with your device.
Have there been any changes on your computer, or the driver for this device?
Let me explain what I found from the log file:
Normally, for most digital TV devices, there is a tuner filter and there is a separate capture filter. The tuner filter connects to the capture filter.
There are some devices that do not follow this pattern. For those there is only one filter. Your device happens to belong to this group. We have not prior knowledge of how a device is configured, so we always try making connections of filters assuming there are two filters, and only to fall back to the second scenario after the initial attempt fails.
Now with your device, only one filter, the tuner filter, is needed, but the same filter is also put in the capture filter category. I do not know if this is the practice of all such devices. When MC tries to load a capture filter, it actually finds one, although it is actually a tuner/capture combo device, and attempts to connect. That connection would fail, but it does not fail immediately - it took 4 full seconds to fail. Compounded by the fact that there are two similar devices on the same machine, we attempt such connection twice. That was 8 seconds! Adding time for other things, the entire graph building took more than 10 seconds (more than the 8 seconds that you thought it took
).
If you did not see that same behavior before, then it must be something new on your computer, as the graph-building part of MC has not changed at all. That is why I ask whether your computer has changed. In particular, could the no-capture-filter thing be the result of an updated driver from the device manufacture?
