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.

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 !!!

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.

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 !!!

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.

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

This issue has been reported to the dev team.