VP-17 A "stream could not be read" error when attempting rendering

Former user wrote on 8/5/2019, 11:49 AM

"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.

Back to post

Comments

joly-macfie wrote on 8/5/2019, 11:59 PM

#MeToo , any NVENC encode.

fr0sty wrote on 8/6/2019, 12:01 AM

Did you read the solution earlier in this thread? Saved render templates are causing the issue. Just use a stock render preset and modify it to your needs until the bug can be fixed.

michael-thompson wrote on 8/6/2019, 1:11 AM

I have installed VP17 and cannot even get it to start. It hangs up around "video plug in factory". I am running the latest beta version of Windows 10. VP16 works fine but does crash from time to time. So, if I can't get VP17 even to start, what hope? Tried in ordinary and administrator mode. I have also tried Windows 8 compatibility. And I have installed Nvidia Studio driver. None of these seem to help.

Former user wrote on 8/6/2019, 1:41 AM

@michael-thompson Same here, and others too, fixed by uninstalling Boris. https://www.vegascreativesoftware.info/us/forum/vegas-pro-won-t-start--116470/

michael-thompson wrote on 8/6/2019, 3:43 AM

Thanks, took out BCC, worked a treat. BCC now reinstalled. Also changed NVIDIA driver from gaming to studio.

Deva-Bida wrote on 8/22/2019, 2:40 AM

I also cannot render unless I make a new template.

NickHope wrote on 9/23/2019, 11:34 PM

The VEGAS Pro 17 Update 1 (build 321) release notes state:

"Custom NVENC templates from earlier version of VEGAS Pro can now properly be used for render"

RogerS wrote on 10/12/2019, 1:10 PM

I ended up getting the same error with a custom NVENC template in build 321. Starting over from a stock Magix one solved the "a stream could not be read" problem.

eightbit wrote on 11/1/2019, 11:22 AM

VP16 templates also caused this issue for me. Creating new templates solved the problem. Glad to have found this thread. Thanks.

animagic wrote on 1/27/2020, 12:30 AM

I ran into this today problem with a self-created template (1920x1080, 24fps, NVENC), so the problem has not been resolved in Build 387. I had to recreate the template to make it work

JN- wrote on 1/27/2020, 3:22 AM

This was fixed in build 321 ... see 4th. post up from here.

I ran into this issue again yesterday also, like the bad penny, it keeps coming back.