I was using Render Loop...

I was using Render Loop...

@skeeter123 - Let's have a go!

BRB

@skeeter123 - I threw in a NewBlue Film FX, onto a 10 sec Event, did a Render As Loop to a NEW TRACK, took 5 secs and it finished.

@skeeter123 - I threw in a NewBlue Film FX, onto a 10 sec Event, did a Render As Loop to a NEW TRACK, took 5 secs and it finished.

I'm stumped. It just won't render video. The audio renders just peachy. Preview video is there. During the render, the frames processed never counts up.... I have include video ticked in the preferences....odd, no? What did I miss? I would think that the System Restore would have taken it back to the pre-update state that was working just fine...

I'm stumped. It just won't render video.

@skeeter123 - Me too. Post your Render Setup here and I’ll gladly have a squint at it.

I don't have the machine in front of me, so I'm having to go from memory here. It's a brand new 2019 model LG gram laptop. i7 processor. Win 10 home. 16gb RAM, 512gb and 1tb SSDs.

I'm just wondering what in the update script that was released yesterday didn't jive with the setup. Before the update it was working wonderfully. I had installed the patch for the frame server crashing after Vegas pro starts rendering glitch. The patch did the trick, BTW.

I did a system restore to the point right before the update. Which is where it was working fine.

Is there a way to uninstall HOS ?.

Squint away. My eyes are hurting from all the squinting.

I appreciate the assistance!

@skeeter123

I've had one other user report the same problem of black frames. For that user the "patch" for the previous version did not work for him as well. Others have reported similar problems when attempting to use the FrameServer with Premiere. Others have reported no issues.

"Is there a way to uninstall HOS ?."

You can unisntall HOS just like any other app. In Win10, just select Settings and then Apps and scroll down till you find HOS.

Try re-installing 1.0.2.59 and then the "patch" to see if it works once again.

@wwaag

Would it be possible to expose QSV MPEG-2 encoder in Render+, Render Events, and Proxy Assist?

I must think such a thing would make blazingly fast dailies, proxies, and prerenders!

@Musicvid

Yes. If you run the GPU check and have an Intel processor, it shows up as a QSV option. I actually tested it quite awhile ago, but deleted it since the render quality was so poor--but you're right, it might be useful for pre-renders or proxies. I'll take another look.

I was able to get a few renders to stick but the file icon kept disappearing. I just tried modifying an existing line:

qsvencc64 -i <inAVS>  --codec mpeg2  --cqp 23 --quality balanced -o <outFile>.mp4

You would probably have better luck if you started with a vbr command line and then modify that. My suspicion is that the cqp and quality settings don't have any impact on Mpeg2 renders. To find out exactly what is supported, open the command prompt and enter "qsvencc64 -h" or you can save it to a text file with "qsvencc64 -h > "your text file location".

I tried modifying with a CBR switch but it didn't work.

Just ran a short test on 1080 60P video renders with qsv using vbr at 15K for both avc and mpeg. No difference in render speed. AVC was 95.498 fps while mpeg2 was 95.99 fps. I'd call that a wash.

@skeeter123

I've had one other user report the same problem of black frames. For that user the "patch" for the previous version did not work for him as well. Others have reported similar problems when attempting to use the FrameServer with Premiere. Others have reported no issues.

"Is there a way to uninstall HOS ?."

You can unisntall HOS just like any other app. In Win10, just select Settings and then Apps and scroll down till you find HOS.

Try re-installing 1.0.2.59 and then the "patch" to see if it works once again.

 

 

All good now! Uninstall/reinstall was the ticket! THANKS!!

Alert! For those using the new HOS Build 1.0.2.60 in Vegas versions V13-V16 wishing to use AviDub, you must change the AVI internal preferences in VirtualDub. Otherwise, only black video will be produced. Unlike previous builds, the "Prefer internal decoders..." line must be "unticked" as shown.

For V12 users that still use an earlier FrameServer version, the box should remain "ticked".

Just ran a short test on 1080 60P video renders with qsv using vbr at 15K for both avc and mpeg. No difference in render speed. AVC was 95.498 fps while mpeg2 was 95.99 fps. I'd call that a wash.

I was just investigating this after noticing that Vegas XDCAM-EX35 still renders faster than qsv. I keep coming back to it for those short proofs and dailies, now that I'm doing more testing again.

My machine is a little more modest, running 78-80 fps through frameserver. I think that frameserver/cpu is the throttle here. Any way to throw more Priority at the Frameserver?

@Musicvid

On my machine, an i8700K (I really need to post my specs) QSV avc (1080 60P) is still faster than XDCam (1080 30P). Nvenc renders are even a bit faster. Even straight CPU renders with x264 are faster, in fact a little faster than QSV. All renders set to abr 25Mbps, which is roughly the same as the XDCAM bitrate. Just a few FHD clips with no Fx--straight rendering. There is an option in R+ to increase processing priority in which you can set the priority of all apps in the render chain including Vegas. When set to High, I've found very little effect, but it might be worth a try.

Where I'm really seeing a speed difference is XDCAM-EX35 720 p60.

It's faster on my modest four-banger than a proxy, QSV mpeg2, or HDV 720p, which I had been using, mostly to throw quick proofs and tesrs on the Chromecast or media server.

@wwaag

Can we have an option to avoid the unsaved template nag screen every time I want make a change?

I don't want to save them until I've got one working, which for me can mean many attempts (and "warnings").

@wwaag

Can we have an option to avoid the unsaved template nag screen every time I want make a change?

I don't want to save them until I've got one working, which for me can mean many attempts (and "warnings").

+1

@Musicvid

+1

I've been annoyed many more times than you. LOL. Will delete altogether on next build. Once the dialog opens, the template reads <unsaved> so the warning is pretty superfluous anyway.

It also sticks if you don't save it, so yeah, no vigilance required.