Live TV Random Stutter

[softworkz 5066]

11 minutes ago, Lyfesaver said:

the only thing I did was update the driver between those two attempts but I guess that is what did it.

 

Then definitely =>

1 hour ago, softworkz said:

If you want to take another chance, you may try to install an OLDER driver version, like this one from May 2024: https://www.intel.com/content/www/us/en/download/785597/823163/intel-arc-iris-xe-graphics-windows.html

Or if you still have the download on disk from the previous driver, then I would try to install that one instead.

[Lyfesaver 133]

Ya know what, I think I know what the ultimate culprit is. On Nov 5th the server's z390 (with an F model 9th gen i5) crapped out and to get back up and running ASAP I just swapped it out with a new z790 with a K model 12th gen i9. So not only did the chipset changed but so did the designation of the external GPU as the new CPU had an iGPU. While Win 10/11 does handle overall base system changes like that better than it predecessors, it is still far from perfect/acceptable.

Edited December 4, 2024 by Lyfesaver
typo and clarification added

[Lyfesaver 133]

Ya, now that I think about it more I bet that is what created the duplicates and things were fine with just the old driver installed and as soon as I updated, boom... something about the new ones or maybe a conflict that never really got eliminated with the clean installs or the hard removals I did in Safe Mode.

[softworkz 5066]

It's a little late that you "suddenly remember" that there has been a fundamental system change in-between.

It's not about graphics drivers then, but other drivers which haven't been switched properly.

Install Win11 - it will keep your settings, but it's like a fresh install -  probably the best in yure case now.

[Carlo 4560]

Yes I have to agree and fresh re-install of the OS is the best bet.

I do have a question for you @Lyfesaver. How many monitors do you have plugged into the computer? Have you ever plugged a monitor into the A380?
If so how many?

I asked this because I see the 2 adapters each having a different AdapterLuidLow address. Some adapters (in general) depending on BIOS settings will report all interfaces/addresses vs the first. This normally only reports this way if the port/address was ever in use, hence me asking about plugged in monitors.
This info in no way helps to fix the issue, it's just another information point to understanding the overall issue.

Thanks

[softworkz 5066]

19 minutes ago, Carlo said:

I do have a question for you @Lyfesaver. How many monitors do you have plugged into the computer?

I asked this because I see the 2 adapters each having a different AdapterLuidLow address. Some adapters (in general) depending on BIOS settings will report all interfaces/addresses vs the first. This normally only reports this way if the port/address was ever in use, hence me asking about plugged in monitors.
This info in no way helps to fix the issue, it's just another information point to understanding the overall issue.

I can answer that.

He has one monitor connected to the A380. This can be seen form the HW Detection log in section "QuickSyncCodecProvider". This is D3D9, where each device corresponds to a plugged in monitor and you can only see devices with a plugged-in monitor and a gpu with two monitors appears twice.  It's different in case of QuickSyncDx11CodecProvider, where there's always one entry for each gpu (no matter how many monitors). The device enumeration here comes from the DXGI API and when it lists 2 adapters even though he has just one, then there's something wrong.

This is also the reason why in case of D3D9, you always had to have a monitor plugged in which isn't required with D3D11. The same relation exists between DXVA2 (D3D9) and DX11VA btw.

Edited December 5, 2024 by softworkz

[Carlo 4560]

Nice, thanks for that info.  I actually don't have an ARC card yet as I was waiting for the new Battleimage ARC cards (B). The but since Intel has already said they are canceling the PCIe ARC cards, going forward as an ARC iGPU (Ultra Core CPUs), I'm having second thoughts. 

Seems kind of stupid to make that public before they even release the Battleimage cards but that's Intel for you.

[softworkz 5066]

They are cancelling discrete GPUs? (haven't followed news recently)

[Lyfesaver 133]

4 hours ago, softworkz said:

They are cancelling discrete GPUs? (haven't followed news recently)

I believe this is what Carlo is referring to

[Lyfesaver 133]

On 12/4/2024 at 8:30 PM, softworkz said:

It's a little late that you "suddenly remember" that there has been a fundamental system change in-between.

It's not about graphics drivers then, but other drivers which haven't been switched properly.

Install Win11 - it will keep your settings, but it's like a fresh install -  probably the best in yure case now.

I am trying to do that, but even it is not going as plannned

My current roadblock. I know y'all cant help on that one, but just wanted to show you where I was at in the upgrade process.

No worries tho, I will get to the mountain top, even if its the last thing I do

[softworkz 5066]

There's surely a log which tells the exact reason, then you can uninstall that driver or service.

Or: Download an ISO image for installation from a USB stick on bootup, yet I don't remember whether this will retain your data, so don't go without backup into this.

[Lyfesaver 133]

1 minute ago, softworkz said:

There's surely a log which tells the exact reason, then you can uninstall that driver or service.

Or: Download an ISO image for installation from a USB stick on bootup, yet I don't remember whether this will retain your data, so don't go without backup into this.

Turns out it was my EasyAntiCheat. Renamed the folder and poof:

[Lyfesaver 133]

 

EUREKA!!!!

[softworkz 5066]

It seems to be a hardware issue. The duplication is still there.

But probably it's working at least. Just uncheck the entries with [1]

Also, disable trhe "Show D3D9 Codecs" settings in the diagnostics plugin that we had enabled.

[Lyfesaver 133]

3 minutes ago, softworkz said:

It seems to be a hardware issue. The duplication is still there.

But probably it's working at least. Just uncheck the entries with [1]

Also, disable trhe "Show D3D9 Codecs" settings in the diagnostics plugin that we had enabled.

Done!

 

Thank you so much softworks and Carlo, seriously. I know it can be very frustrating to offer support on projects and extremely frustrating when dealing with me in particular. So from the core of my being... thank you very, very much

[Lyfesaver 133]

34 minutes ago, softworkz said:

... Just uncheck the entries with [1] ...

Seems if I check one and Save then the other [1] also gets checked but you are right that it is most likely working fine

[softworkz 5066]

33 minutes ago, Lyfesaver said:

Seems if I check one and Save then the other [1] also gets checked

That's probably due to identical IDs. We have never had any case like that - which illustrates how quirked the situation is. Just leave it checked then, it probably won't matter if it's the same Id.

I would still consider contacting Intel about it, evenmore when something doesn't work as expected - that will be the first step.

[Lyfesaver 133]

1 hour ago, softworkz said:

I would still consider contacting Intel about it, evenmore when something doesn't work as expected - that will be the first step.

Good idea, will do

[Carlo 4560]

On 12/6/2024 at 9:57 AM, Lyfesaver said:

Good idea, will do

Meanwhile

Have you had a chance to try transcoding now that you have the hardware encoders loading?

[Lyfesaver 133]

10 hours ago, Carlo said:

Meanwhile

Have you had a chance to try transcoding now that you have the hardware encoders loading?

I have, it seems to be working well