Reply to thread

Message

<blockquote data-quote="GregorV" data-source="post: 295135" data-attributes="member: 57522">would have been too niceyes, I can see on my systems meanwhile, that it does not always help. It is really strange - on my Intel machine with a&nbsp; NOVA-S PLUS I can scan high-band channels after each restart of TVService, but after reboot it still fails.On my AMD machine with a NOVA-HD-2S I can scan high-band channels after each reboot (when TVService is automatically started) but when I manually restart TVService it still needs several restarts before I can tune any high-bands.Before my change both machines behaved exactly the same way.But at least I am apparently at the right place in the code, because it changed behavior on my systems.I am pretty sure that it has to do with function calls to the DirectShow library:This is, what I changed in the Hauppauge.cs module:&nbsp; &nbsp; public Hauppauge(IBaseFilter tunerFilter, IBaseFilter analyzerFilter)&nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; //IPin pin = DsFindPin.ByDirection(tunerFilter, PinDirection.Input, 0);&nbsp; &nbsp; &nbsp; IPin pin = DsFindPin.ByName(tunerFilter, &quot;Input0&quot;);&nbsp; &nbsp;&nbsp; ...So it is just another method to find the Input pin for the Hauppauge tuner.I'll try to come closer to that in the next days.May be a developer could give some hints here, what could be tested.Thanks,Gregor</blockquote>

[QUOTE="GregorV, post: 295135, member: 57522"] [b]would have been too nice[/b] yes, I can see on my systems meanwhile, that it does not always help. It is really strange - on my Intel machine with a NOVA-S PLUS I can scan high-band channels after each restart of TVService, but after reboot it still fails. On my AMD machine with a NOVA-HD-2S I can scan high-band channels after each reboot (when TVService is automatically started) but when I manually restart TVService it still needs several restarts before I can tune any high-bands. Before my change both machines behaved exactly the same way. But at least I am apparently at the right place in the code, because it changed behavior on my systems. I am pretty sure that it has to do with function calls to the DirectShow library: This is, what I changed in the Hauppauge.cs module: public Hauppauge(IBaseFilter tunerFilter, IBaseFilter analyzerFilter) { //IPin pin = DsFindPin.ByDirection(tunerFilter, PinDirection.Input, 0); IPin pin = DsFindPin.ByName(tunerFilter, "Input0"); ... So it is just another method to find the Input pin for the Hauppauge tuner. I'll try to come closer to that in the next days. May be a developer could give some hints here, what could be tested. Thanks, Gregor [/QUOTE]

Verification