Red Car Stress Test: Render Interlace or Progressive?

Grazie wrote on 7/12/2019, 11:48 PM

Hello Red Car Enthusiasts'!

OK, I think I've not fully understood something fundamental.

In the RCST Render I get a Freeze of VP. One of the Render Templates is Interlace: XDCAM EX HQ 1920x1080-60i, 35 Mbps Render(s) : Why? Why have Progressive Media in a Progressive Veggie and then Render in Interlace? Have I misunderstood something rudimentary? OK, when I create my own a Progresive Template - XDCAM EX HQ 1920x1080-30p, 35 Mbps Render(s) - I get 14 seconds.

Why have an Interlace Template rendering on Progressive Media? Is this to truly Stress the Project & VP? Well, it's stressed-out this Editor! 😬

The other Template, MC AVC Internet HD 1080p Render(s) I get 54 secs.

Back to post

Comments

Grazie wrote on 7/14/2019, 7:50 AM

@Former user Ah, the Windows Updates going from 1803 to 1903 created the issue for you. Would that have been a System wide update?

Grazie wrote on 7/14/2019, 8:08 AM

I've just done some Googling .. I don't see how I can go back to the WINDOWS 10 1803 Version to knock out 1903.

Former user wrote on 7/14/2019, 8:10 AM

@Grazie If you go into system, updates, you’ll see an item over on the right OS version.

Click on that to confirm you are on 1903, if not then my theory is out the window, pun intended.

Dexcon wrote on 7/14/2019, 8:16 AM

don't see how I can go back to the WINDOWS 10 1803 Version to knock out 1903

Agreed. I noted that there was no backward capacity from 1903 in an unrelated post some time ago re 1903 killing audio functions unless new updated drivers were installed.

Former user wrote on 7/14/2019, 8:16 AM

@Grazie We were typing at the same time, so you are updated to 1903?

I never suggested going back to 1803 as a way to resolve the issue, a bit extreme I think, after all so far only a known issue with the Red Car project.

I merely mentioned 1803 because my old PC doesn’t have this issue using 1803.

Ive already suggested to you many times, to check if you are using the Studio version of the Nvidia driver and changing it to the Gaming driver, this worked out for me in resolving the issue on my laptop.

Grazie wrote on 7/14/2019, 8:19 AM

@Former user - Confirmed, 1903, which was installed in early July. There isn't an option to Roll-Back - is there?

Grazie wrote on 7/14/2019, 8:25 AM

I never suggested going back to 1803 as a way to resolve the issue,

@Former user - Oh, I thought you were? My mistake.

a bit extreme I think, after all so far only a known issue with the Red Car project.

@Former user And yes, it would be extreme!

I merely mentioned 1803 because my old PC doesn’t have this issue using 1803.

@Former user Ah, just a mention. Got you.

Ive already suggested to you many times, to check if you are using the Studio version of the Nvidia driver and changing it to the Gaming driver, this worked out for me in resolving the issue on my laptop.

@Former user Yes, and it's your considered feeedback that the Builders are dealing with. And again, I had the issue, and the Builders change it FROM the Gamer driver.

Grazie wrote on 7/14/2019, 8:27 AM

don't see how I can go back to the WINDOWS 10 1803 Version to knock out 1903

Agreed. I noted that there was no backward capacity from 1903 in an unrelated post some time ago re 1903 killing audio functions unless new updated drivers were installed.

@Dexcon - Ooo-er, that's some UPdate that 1903, and no mistake!

Former user wrote on 7/14/2019, 8:28 AM

@Grazie I don’t know if there is a way to go back to 1803. If there was I wouldn’t suggest it.

Heres what you need to do ...

1) Download and install the latest version of Geoforce experience, if you don’t already have it. Then log into it creating a new account.

2) Click on the “drivers” item in Geoforce experience app and see if you are using the “Studio” drivers.

3) If you are using the the Studio drivers switch to Gaming drivers, (click on the uppermost 3 vertical dots, to the right of “check for updates”), download the latest Gaming driver and update. This may or may not fix the issue.

If you elect to switch driver type be aware that it isn’t instant, the existing driver will be uninstalled and the new driver installed, it takes some time.

Dexcon wrote on 7/14/2019, 8:54 AM

@Grazie ... just to lighten up the mood a bit, though way off topic, you've got some great sporting events happening in the UK right now. NZ haven't done all that well in their innings in the World Cup Cricket final at Lords - England should win. And the 1st set at Wimbledon is very even right now (go The Fed!). And then there's the F1 at Silverstone being raced as I write.

Grazie wrote on 7/14/2019, 9:13 AM

@Dexcon - I’m Kool... England just come to the crease, and we’re off to the races!

And now a first ball LBW.... oops...

diverG wrote on 7/15/2019, 8:01 AM

@Grazie.
'vkmast' kindly supplied a link to older nVidia drivers. Have found that the latest driver recommended Gaming/Creative/Studio caused problems so reverted to the original supplied with card. Using link provided by vkmast I was able to move forward by about 12 months before hitting trouble within Vegas 14 & 16.

Using the same driver listing the drivers for the laptop 'gtx940mx' were tested. Latest drivers failed but I was able to advance the 'driver' date by some 12months before running into trouble within Vegas.

Once you find the 'sweet spot' it worth saving a copy of that driver in case Windows changes the driver whilst updating.

Going back to 1809 from 1903. You did take a system image before updating. In my case 1903 was OK on the desktops but the laptop network failed with 1903. Played with it for about a day before restoring the image and locking out auto updating. Takes 7 minutes.

Grazie wrote on 7/15/2019, 8:57 AM

Going back to 1809 from 1903. You did take a system image before updating.

@diverG - No.