capture card signal status receives 1080p instead of 720p

[TNyer]

Description

Provide a detailed description of the issue

I would like to record 720p footage from my Skylake computer. I am using a separate computer for recording with a capture card. In VirtualDub, looking at the custom properties the SIGNAL STATUS does not reflect the resolution on the Skylake system. It always shows 1920x1080P. I have tested the issue on non-Intel system and the SIGNAL STATUS was correct (1280x720P). So I assume some kind of signal protocol is missing from the Skylake driver.

Does it fail every single time, or only sometimes?

If you can offer a % rate please do.

YES

100%

Hardware (HW)

Brand and Model of the system.

Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (4 CPUs), ~3.7GHz

Hybrid or switchable graphics system?

ie Does it have AMD or NV graphics too?

NO

Make and model of any Displays that are used to see the issue (see note2 below). 

LFP = Local Flat Panel (Laptop panel)EFP = External Flat Panel (Monitor you plug in)

SyncMaster S24A350H (Digital)

How much memory [RAM] in the system (see note2 below).

8192MB RAM

Provide any other hardware needed to replicate the issue.

ie: Cables&brand, cable type [vga, hdmi, DP, etc], dock, dongles/adapters, etc

HDMI to DVI cable with SA7160 PCI capture card

<sp...

[TNyer]

Hi Amy:

Sorry for the late reply!

I have an Intel Skull Canyon NUC as well, and it produces the same issue - no 720p signal on Win10, Ubuntu is fine. Interlacing problem is gone with the new driver / custom resolution option.

I have updated the other thread, hopefully, Esteban will have a look at the issue!

[TNyer]

Hi Amy!

Back here, EstebanC_Intel is right, it's not a good idea to derail that thread.

To sum things up:

- We didn't get a reply from YUAN, it's a dead-end, I guess, will try one more time.

I have three strong points that support my case, that Intel is at fault:

- I have two Intel Skylake systems (one very expensive one) that both encounters the same issue. Bad signal in Win10, good signal on Ubuntu.

- Other GPU vendors do not have this kind of issue, tried several computers.

- One user in the other thread provided /message/399422# 399422 feedback very similar to my complaint.

You have only one:

- Tested a different capture card, and it receives the correct 720p signal.

If you assess all the information that I have provided so far, you can only arrive to one educated guess: it's more likely that something is broken with the Intel drivers on Windows.

I have spent way too much time with this issue and the support I get is very annoying, a bit undignified. It would be great to have a chat with a member of the driver developer team, maybe an engineer of some sort.

I hope that I can test this issue with a Haswell / Broadwell system soon!

[idata]

Hi, Toorop:

I understand your points, so let me review your case one more time and see what I can do.

FYI, no answer from http://www.yuan.com.tw/en/contact/Contact.htm Contact Us | YUAN.

Regards,

Amy.

[TNyer]

Hi,

I managed to have a word with Wendy from YUAN, so I am hopeful that we will have a response on the issue. It would be nice if someone from the YUAN team would join us here. I will keep you posted, if they resort to email communication with me.

[idata]

Oh really? That is really good, please keep me posted on that.

Regards,

Amy.

[idata]

Hello, Toorop:

I am following up your thread.

How is everything going with YUAN support? Were they able to take a look at the case?

Regards,

Amy.

[TNyer]

Hello, Amy_Intel:

After the initial quick exchange of emails with YUAN (10th of August) I didn't get any update. I wrote a heads-up email at the end of August. No reply, yet.

Should there be any progress, I will definitely keep you posted.

[TNyer]

No update from YUAN, but some interesting thing.

I tried the https://www.battlefield.com/beta Battlefield 1 beta on the i3-6100 and the signal status was okay (720p). Nonetheless, the recorded footage was off, the sound was right, but got black screen initially. Strange. Unfortunately, the beta period is over so I cannot investigate the case further.

I guess, http://www.dice.se/ DICE - the studio behind the Battlefield series - is doing some low level coding and gets behind the driver.

Do you have someone in the driver team that looks into game specific optimizations, problems? I don't have high hopes since Intel seems to have dropped the ball when it comes to game ready drivers.

[idata]

Let me know if they say anything.

In regard to Battlefield 1, we have been testing the game, and we continue to do so. As soon as we have more information we will keep you posted

Regards,

Amy.

[TNyer]

Thanks for the info!

It's a huge letdown that I didn't get any update from YUAN, I thought we might get to the bottom of what is going wrong. Will ping them again next week, though.

I contacted someone who has nearly the same capture card as I do - different branding, virtually the same card. Although he can't test the issue with a Skylake iGP, he experienced all sorts of trouble when upgraded his OS to Win10 - and not limited to VirtualDub, different recording sw had issues as well. He recommended that I should try with Win7. If I have some free time I will definitely give it a go.

[idata]

Toorop, please keep me posted, and if you try to install Windows 7 let me know your findings.

Regards,

[TNyer]

Hi,

I managed to get support from YUAN a few weeks ago. They were able to identify that the problem is real, so that's a start. I hope to get some news from them this week. I am hopeful that I will have the time to try Windows 7 on the recording side this weekend. Sorry for the late reply!

[idata]

Those are really good news!

Don't forget to keep me posted.

Regards,

Amy.

[TNyer]

Hi,

I had some spare time to try Win7 on the recording PC. Unfortunately, the problems didn't go away. So I don't think the problem is caused by the recording PC.

Can you suggest me a method to record footage - for example on Linux with an open source program.

Back to Win10-Win10 setup:

Interestingly, if the skylake has native 720p on Windows, I can see the correct signal status, but cannot capture anything, just the sound.

Sometimes it reports back 1080p signal status and I can capture the up-sampled footage.

I came across the first bug on non-Intel system. I was running an application on 720p but got 1080p signal. If I jumped back to Win10 and set the resolution to 720p and restarted the app I got the correct 720p and the correct footage. Interesting ...

I believe something goes wrong between the gfx drivers and Windows UWP. Maybe MS is at fault, just like with my /message/336221# 336221 interlacing issue.

I hope to have a skylake system beside the i3-6100 and skull canyon to investigate the issue further.

Can you recommend a 1440p 60Hz lossless capture card? What do you use at Intel labs?

Thanks.

[idata]

The one that we use is https://www.startech.com/AV/Converters/Video/usb-3-0-video-capture-device-hdmi-dvi-vga~USB3HDCAP USB 3.0 Video Capture Device - HDMI, DVI, VGA | Video Adapters | StarTech.com, maybe you could try some other model from this brand. I used this one to replicate the issue you were reporting, but it worked flawlessly in an Intel® HD Graphics 530 platform.

Regards,

Amy.

[TNyer]

I managed to get 720p signal from Intel NUC Kit NUC6i7KYK (CPU i7-6770HQ). Yeah, shocking news!

All games tested worked flawlessly, except for Codemasters' DiRT Rally.

Naturally, I use 1920x1080p in Win10, then start a game for testing. In the case of DiRT Rally I had to set the Win10 resolution to 720p and then start the application to get 720p signal. Otherwise, it was 1080p.

I had to set the aspect ratio from AUTO to 16:9 in F1 2016 (another Codemasters title) to get 720p signal.

The driver was a bit older on this system, but not ancient by any means.

If I insert the HDMI splitter, I am not able to get 720p signal, just the upscaled 1080p.

Unfortunately, I had no luck with i3-6100.

I tried with the latest drivers - this is the PC that we test regularly, so this is updated often. I was not able to get 720p (no splitter between the card and source). I don't know if the driver is making a difference, but I regularly checked the signal after every new Intel driver release. Will check driver versions and stuff, but as you can imagine, testing is a bit time consuming.

I had other problems with DiRT Rally, I got 1080I signal by default. I had to create custom resolution in the Intel driver application to get proper 1080p signal on the capture card. If you recall, I reported this issue as well. An Intel developer said that Microsoft is at fault, they do not adhere to the specification and game developers do funky thinks as well. I strongly believe my 720p issue is buried somewhere between the OS and gfx driver. As I said earlier, I was able to get 720p from a skylake running Ubuntu.

I don't know whether these custom resolution settings affected my testing, maybe solved the 720p issue on the NUC.

YUAN was kind enough to send me another capture card for testing. Will see what happens with that one.

In the last resort, I will consider another brand, as you suggested.

[idata]

Let me know how that goes, I definitely understand what you are saying about testing.

I will keep an eye on your thread.

Regards,

Amy.

[TNyer]

The new capture card did not solve my issue, waiting for YUAN to say something about that.

I tested the signal status without a capture card, here are my findings:

I used the latest Beta Battlefield 1 drivers on both of my systems - i3-6100 and Skull Canyon NUC.

I connected the systems to an HDTV via an HDMI cable. The TV shows a pop-up message if the signal has changed.

If I change the resolution in Windows, everything is fine, the TV displays the correct resolution - i3-6100 and Skull Canyon both OK. Resolutions: 720p and 1080p.

If I start a gaming application on Skull Canyon, the TV shows the correct signal. If I insert a splitter, unfortunately, I can only see 1080p. Strange.

But it works fine if it is connected directly to the TV.

The i3-6100 can't send proper 720p resolution from gaming applications to the TV, TV reports back 1080p. Even when I have 720p resolution in Win10 and start a game in 720p, the TV displays the message that it is on 1080p.

This coincides with my experiments if I connect the systems to the YUAN capture card (without a splitter). YUAN can record 720p from Skull Canyon. It's clear that the splitter is introducing some kind of error to the system. Order a new splitter, hope that helps.

I have to reiterate that I don't have any issues with AMD and NVIDIA graphics solutions, with and without a splitter.

Any thoughts? Are you in connection with someone in the driver team or should I stop reporting this issue as no one cares?

[idata]

During my test with the card I did not use HDMI splitter, it was just the HDMI straight connection and the card.

Let me check if I can test this one more time, this time I will use an http://ark.intel.com/products/89187/Intel-NUC-Kit-NUC6i7KYK Intel® NUC Kit NUC6i7KYK Specifications.

Regards,

Amy.

[TNyer]

As it stands, the NUC Kit NUC6i7KYK functions properly without an HDMI splitter.

The i3-6100 is the one that can't send proper signal status - this is the biggest concern right now.

Why test the Skull Canyon when it has no issues except for the HDMI splitter?

Can you comment on how is it possible that the resolution change in Win10 is working properly, but a gaming application can't send 720p signal?

And of course I will repeat myself, because this should ring an alarm bell that something is wrong on Intel's side:

Everything is fine with AMD and NVIDIA and Intel with Linux. You seem to take no notice of this fact ... Any official comment on this? Maybe from a driver developer?

Thanks!

[idata]

I understand, I just want to test several platforms to see the outcome. To be honest, we have only tried recording on the desktop and playing some 4k videos; however, I will like to try this on a gaming environment. So, I will follow your steps one more time and shared my result. BTW, this time I will be using the drivers base line 15.45.

Regards,

Amy.