@CJacobsSA So it's not just the two test projects I mention above? Do you get the same error message?

I just tried another old test project, BruceUSA, same error message, this is serious.

Yes, I get the same error message when rendering any project with any settings. It always freezes during the initialization of rendering. No idea how to fix it unfortunately.

@CJacobsSA A workaround that I found is to first render in say QSV or CPU, then it throws no error and renders using Nvenc. Were you also attempting to render using Nvenc?

This is a VP17 issue, not with VP16.

I'm going to see if switching from Nvidia Studio driver back to "Gaming" driver does anything.

Update, while attempting to use the workaround on the "Benchmarking" SampleProject 4K it didn't work, render time just kept running up, no render started, had to kill with Task Manager.

So the workaround is hit and miss.

I was attempting to use NVENC, yes. CPU rendering also works fine for me but NVENC is just totally broken in VP17 on my end it appears. I'm interested to know if anyone else is having these issues.

@CJacobsSA Well swapping from Studio to gaming driver made no difference. Still can't render.

Seriously, does anyone test VP before it's released?

The program also seems to crash every OTHER time it's started. Very consistently, too- Crash, no crash, crash, no crash, et cetera. Guess this is why early adoption isn't a good idea these days!

@Former user No VP17 here, just VP16 on my new PC. I just Rendered an MP4 and MOV and both are silent in QT and VLC. Bring these to the VP16 Timeline and the audio plays fine. MediaInfo confirms Audio. Previous renders have Audio coming from speakers.

Has there been WUP in the last 24 hours?

I’m gonna Reboot PC.

@Grazie This IS a VP17 issue only. If you have or get VP17 then let us know if you have the issue, thanks. Unless I'm not following you, if that's a separate issue that you have then maybe start a new thread?

What's a WUP?

@Former user I was wanting to see if there was Windows Update that could have made a difference. And yes, your issue must’ve been BETA tested - surely?

I was attempting to use NVENC, yes. CPU rendering also works fine for me but NVENC is just totally broken in VP17 on my end it appears. I'm interested to know if anyone else is having these issues.

Same thing for me, CPU render works fine, NVENC doesnt

"A stream could not be read" error.

Happens on PC and Laptop. I used the Red Car test, 2k on PC, failed with above error and the "Benchmarking" J-V Sampleproject 4K on the laptop.

Same problem here 😞

I am now considering to skip the upgrade to version 17...😞​​​​​​​

Given Nvenc hardware rendering was working not too bad in VP16, this should really be addressed quickly.

@Former user I was wanting to see if there was Windows Update that could have made a difference. And yes, your issue must’ve been BETA tested - surely?

@Grazie We are the beta testers, for sure. I really don't think they can have any if this was missed, unless they only have AMD machines :D.

@Former user Whats an AMD machine? (😉) - WUP = Windows Update. You've almosy convinced me to DL the VP17 Demo. Oh yeah, my missing audio? - The 3FS cured it.

@Former user I was wanting to see if there was Windows Update that could have made a difference. And yes, your issue must’ve been BETA tested - surely?

@Grazie We are the beta testers, for sure. I really don't think they can have any if this was missed, unless they only have AMD machines :D.

I'm on a Threadripper! But with a 1080ti

Same problem here with VP17 and NVENC. Project can be rendered OK with VP16 and NVENC.

@Grazie Don't get me going on acronyms, when I can't even see the wood from the trees, 91s. LOL.

Many thanks for all the feedback guys, hopefully it'll accelerate a fix.

It's the same error message I found here

@Grazie Don't get me going on acronyms . . .

@Former user So, what does JN_ stand for? Getting you going? Moi? Should I post back that Muppets clip? It's getting quite pertinent now.

It's the same error message I found here

Ahh, thanks, the solution of making new render templates worked to fix the problem for me. VERY strange, hope they fix it because that seems like it'll trip up a lot of people.

Yes thats it. I had a own made template, simply used a default template that had same settings and rendered ok. Well found @set @peter-p.