Video problem

[lmh]

Thanks for your support on this thread. I have a GTX 1080 Ti and experience this issue, too.

[marksdoran]

I think we have essentially come to the end of the road here, it seems there is some codec/driver/legacy code that is causing this problem with specific cards and for whatever reason no matter what I do I just can't replicate it.

Our best option at this point is to re-write the video component in i2 from scratch so that it works properly moving forward and sort out any sync/playback issues at the same time. I have already added this to our system, however I haven't been given a time frame on when it will be completed yet.

When I have more information I will update you.

Ok, I can understand that...lack of reproducibility makes it really hard to narrow things like this down. Thanks for trying!

Total long shot: something like Windows Quick Assist or Team Viewer might allow you to take a look at the problem on a system that does have the problem. Might be easier to "borrow" a system that has the problem that way rather than trying to create one or literally borrow one via Fedex or whatever. If you wanted to try that -- run a debug version of the code with extra debug output or something -- I'd be willing to take a run at that with you. Happy to do NDAs or whatever if that would be needed. Heck, I've even got Visual Studio 2013 and 2017 installs on one of the systems here that does have the issue. I have used Team viewer to latch on to systems in Europe to run VS debug sessions from remote on machines with pesky problems that I couldn't replicate locally.

Might be more work than you want to get into; especially given that it seems there is a viable workaround but I figured I'd throw it out there.

One extra thing I'd toss in to the mix if you are gathering requirements for a revised video component. With the one we have now, it is almost always possible to reverse the video step by step (by which I mean using the left arrow key to step) but it is only sometimes possible to advance it with the arrow keys. I haven't figured out the pattern of why that works sometimes and not others. Obviously it would be nice in a replacement video component if there was a reliable way to go forward and backward frame by frame while keeping the data in sync.

[adrian]

I sent you a PM the other day regarding this, let me know if you are still up for a Team Viewer session.

[z0mgchris]

I've just tested on my laptop which has an intel i7 and a 1660Ti GPU (plus integrated gpu). cant replicate because it's just defaulting to the iGPU (even with it disabled in device manager). However I am going to test on my home desktop which is a ryzen cpu with no gpu integrated and a 1080Ti. I'll try my current drivers (somewhat old from memory - will check) and then update to the latest while using the sample file provided.

Happy to do teamviewer etc sometime once i've tested.

[marksdoran]

I sent you a PM the other day regarding this, let me know if you are still up for a Team Viewer session.

Oy, sorry -- didn't think to watch for a PM -- email sent!

[Kododon]

I think we have essentially come to the end of the road here, it seems there is some codec/driver/legacy code that is causing this problem with specific cards and for whatever reason no matter what I do I just can't replicate it.

Our best option at this point is to re-write the video component in i2 from scratch so that it works properly moving forward and sort out any sync/playback issues at the same time. I have already added this to our system, however I haven't been given a time frame on when it will be completed yet.

When I have more information I will update you.

Just wanted to chime in that I've been having the problem everyone here is describing.

I actually download the mainconcept player off the motec website and interestingly the video shows a black screen but the audio does, just like in i2 pro. I assume it might have to do with older encoders unable to process more modern h.264 type encoded files. I am using an mp4 file that I recorded myself. I will download that video file off the motec website to see if that works or at least look at the encoding to see any differences. I am going to try running i2 pro in legacy mode and the like to see if that helps at all. Will also try the workaround posted earlier.