FrameServer Problem in V16--Please Confirm

wwaag wrote on 7/13/2019, 12:53 PM

I've discovered a problem with the new version 3.0 of the DebugMode FrameServer in V16 but would like someone to confirm the issue.

In V15 (also V13 and V14), when opening the RenderAs dialog, there is an option to select "Render loop region only" under Render Options as shown here.

However, in V16, the Render Options button is grayed out as shown here.

Could someone please confirm the issue? Thanks.

Comments

Marco. wrote on 7/13/2019, 1:33 PM

I confirm this option is missing in VP16, but even when using the old FrameServer version (I don't have the new version installed, yet).

Stivi wrote on 7/13/2019, 1:43 PM

Hello,

I confirm.

Edit : I haven't V3.0 but V2.15

wwaag wrote on 7/13/2019, 9:51 PM

Thanks for the confirmations. Sounds like something in V16 was changed. I'll post this issue on the FrameServer Github site. This problem doesn't affect HOS since all render start times and lengths are generated internally, but it could definitely be a problem for the non-HOS user.

j-v wrote on 7/14/2019, 2:41 AM

, but it could definitely be a problem for the non-HOS user.

How?
I'm a non-HOS user and I don't need that Frameserver anymore. I used it in versions 13 and 14 to send the outcome directly to handbrake but with all the new and much better rendertemplates of versions 15 and 16 I have not to used it.

wwaag wrote on 7/14/2019, 9:56 AM

@j-v

Sorry. I should have said "but it could definitely be a problem for the non-HOS user who wants to use the FrameServer in V16". For those with no use for frameserving, it's not an issue.