Strange behaviour in VPro 17 with self made rendertemplates

j-v wrote on 8/5/2019, 6:05 AM

Has someone an idea what is happening when I use a few of my self made Magix AVC rendertemplates? In this example a FHD template out of a 2,7 K GOPro project.
In Vegas Pro 16 they render very good.

Comments

fr0sty wrote on 8/5/2019, 6:08 AM

I can replicate this issue.

Peter_P wrote on 8/5/2019, 6:19 AM

@j-v

Did you try to set up these render parameters new in Vp17 instead of using the old existing template ?

j-v wrote on 8/5/2019, 6:49 AM

@j-v

Did you try to set up these render parameters new in Vp17 instead of using the old existing template ?

Yess that helps, but renaming helps not.

And so it is strange behaviour, I did not see in former updates.

set wrote on 8/5/2019, 10:57 AM

had the same issue too on my nvidia card machine... but didn't happened on my Radeon GPU machine.

and the temporary solution to this is to create new render template.

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

Same issue, both threads ... https://www.vegascreativesoftware.info/us/forum/vp-17-a-stream-could-not-be-read-error-when-attempting-rendering--116475/

fr0sty wrote on 8/5/2019, 2:30 PM

This issue has been reported to the dev team.