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.

Comments

CJacobsSA wrote on 8/5/2019, 11:50 AM

Same here. At first I figured it was because of proxy files or the specific media I was using, but it's anything. I just cannot render anything at all, in any format, with any settings.

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

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

CJacobsSA wrote on 8/5/2019, 11:53 AM

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.

Former user wrote on 8/5/2019, 12:07 PM

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

CJacobsSA wrote on 8/5/2019, 12:15 PM

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.

Former user wrote on 8/5/2019, 12:18 PM

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

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

CJacobsSA wrote on 8/5/2019, 12:27 PM

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!

Grazie wrote on 8/5/2019, 12:38 PM

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

Former user wrote on 8/5/2019, 12:41 PM

@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?

Grazie wrote on 8/5/2019, 12:45 PM

@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?

iggy097 wrote on 8/5/2019, 12:53 PM

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

aboammar wrote on 8/5/2019, 1:07 PM

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

HP Z1 AIO Workstation G3

OS: Windows 10 Pro 64bit

Display: 23.6" UHD 4K

CPU: Xeon E3-1270 v5  quad-core @ 3.60GHz, 8MB cache, up to 4GHz with Intel Turbo Boost Technology

GPU: nVidia Quadro M2000M 4GB

RAM: 32GB DDR4 2133MHz ECC memory

System Drive: 1TB M.2 (2500MB/s)

Working Drive: 1TB M.2 (2500MB/s)

Storage Drive: 3GB SSD (500MB/s)

Video: Vegas Pro 16 Suite / DaVinci Resolve 16 Studio

Audio: PreSonus Studio One Pro 4

Graphics: CorelDraw Technical Suite 2018 / Xara Designer Pro X

Image Editing: Corel PhotoPaint 2018 / Corel PaintShop Pro X9 Ultimate / PHASEONE Capture One Pro 11

3D Graphics: Maxon Cinema 4D Studio 10

Website: www.innoviahouse.com

Vimeo: vimeo.com/innoviahouse

Former user wrote on 8/5/2019, 1:09 PM

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

Former user wrote on 8/5/2019, 1:12 PM

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

Grazie wrote on 8/5/2019, 1:20 PM

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

iggy097 wrote on 8/5/2019, 1:24 PM

@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

jxb wrote on 8/5/2019, 1:24 PM

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

Former user wrote on 8/5/2019, 1:27 PM

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

Former user wrote on 8/5/2019, 1:29 PM

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

j-v wrote on 8/5/2019, 1:33 PM

It's the same error message I found here

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 1909 build 18363.720, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 1909 build 18363.720, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 442.92 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

Grazie wrote on 8/5/2019, 1:34 PM

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

 

CJacobsSA wrote on 8/5/2019, 2:17 PM

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.

Former user wrote on 8/5/2019, 2:20 PM

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.

Former user wrote on 8/5/2019, 2:38 PM

@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 beginning to feel like muppet land all right, and this is just day one😫.

1) To summarise my own experience... Installed VP17 on my laptop, crashed when attempting any renders.

2) Installed VP17 on my PC, never even loaded.

3) Couldn’t any longer load my 5D MK. IV .mov files.

The 2) PC issue was obviously more serious, but thanks to other users I fixed it by eradicating Boris. Didn’t happen on laptop because Boris was previously banished.

The other issue 1) has temporarily been fixed by avoiding using own made templates.

3) was fixed by enabling quicktime in a new option called deprecated.

Managed to get Prodad Mercalli to reappear again by copying folders around again. Did the same for Pluraleyes by copying the file around.

Can't wait for what tomorrow will bring.