1.10.1.4602 (and immediate previous beta) have broken transcode DVR

This version and the beta right before it broke the in-line transcoding on the DVR.
Situation - you have set each tuner’s gear options pulldown menu to “transcode” from the “off” setting.
You record a show, it uses constant ~50% cpu on an i5-3470 windows 10 plex server. This shows it isn’t using intel quicksync, previously the cpu usage would be nil and I mean nil, just hard drive activity and the recorded show would end up h264 with whatever native audio format the show was broadcast as.

This is if you have transcoder set to use hardware acceleration. I’ve turned this in-line to “off” and it doesn’t use CPU, but the written file stays as mpeg2. I also happen to use the commercial skipping but I don’t think that is related - that’s post processing.
Live TV and playback of recorded mpeg2 appear to use “(hw)” just fine in the h264 encoding.
This is with a Hauppauge QuadHD pci express card, but I don’t think its related to the card - I think the transcoder isn’t being told of the setting enabled anyore for the hardware acceleration when its launched by the DVR.

Really? nobody else runs these same settings and has seen this? When the beta came out I tried it then reverted to the previous release version and it was fine again, then now I’ll probably leave it writing as mpeg2 until they fix it again rather than downgrade again.

Not everyone uses transcode recordings for various reasons.

I understand it might be a minority used function but not just me by myself. I guess since I have quicksync for playback it doesn’t really hurt me since it never uses my cpu % whether its at time of record or playback its not really a big deal. What i’m hoping for is it comes back functional and with some space saving config options (adjust bitrate) since the files don’t shrink even with it, I would like my DVR shows to be stored on less space - I think that’s the main point of having the feature - other than allowing post-record direct play.