If you'd like to see this for yourself you can download episodes 10 and 11 from season 11 of NYPD Blue from Hulu. I was in the process of downloading this show when the DRM change happened. There were a handful of episodes that wouldn't originally download out of the series. Once StreamFab was updated to resolve the issues downloading from Hulu I was able to download the remaining episodes except that they took much longer during the Parsing stage and the frame rate on the resulting files was choppy and made the episodes unwatchable (a problem which still hasn't been fixed). If you download these two episodes now you'll see that episode 10 goes into Processing once the video and audio are downloaded and only takes about 30 seconds to finish. Episode 11 goes into Reencoding instead and takes about 5 minutes to finish. I added screenshots of both so you can see the difference in language used.
tdfrgsn
I can honestly say I have NOT see RE-ENCODING message before when downloading. And I've downloaded from Amazon (before it broke, as I'm not downloading anything there until its fixed and gives better than SD), Netflix, HBOMax, Disney+, Paramount+, as well as a few TV Series from Hulu.
THANK YOU for your response and the example. That is what I was looking for! My understanding from all the posts was that StreamFab is
ALWAYS Re-ENCODING for a particular service. Apparently it is not. Rather it is certain episodes/titles on certain services.
Let me get your thoughts on an experiment I just did....
I went into Hulu, queued up S11_E10 and S11_E11. Yes, S11_E10 did show Downloading -> Processing -> REmuxing. S11_E11 did show Downloading -> Reencoding (no processing or remuxing). Which appears to match what you see, is that correct?
Both took about the same amount of time from start to when StreamFab reported they were done. Sorry I didn't use a stop watch, if there was a difference in time it was negligible and not noticed. BUT that is not what you see, am I correct?
My CPU never went above 25% (and was often around 10-15% and my GPU never went over 80% ( was often around 50%). Are you seeing spikes in CPU or GPU? If so, how high do they go? Are you able to repeat it reliably with any particular video/service?
Here is where it gets odd... I pulled the VIDEO files for both episodes from the TEMP folder when download was done, but before StreamFab reported the episode was DONE. These are the raw videos as downloaded BEFORE any processing, re-encoding, or remixing was done. There is no audio in these files yet.
NEITHER file will play, no matter what video player I use.
From what MediaInfo shows, the video stats on both are identical, other than the bit rate, which is understandable for different videos.
AFTER both are done here are the stats of the final output MP4 file...

It looks the same as what you posted.
Its obvious on S11E10 the Video was NOT touched (all video parameters match),
it was NOT re-encoded. However S11E11 it was (bit rate is different, variable frame rate, and a few other added parameters now show).
Yes, S11E11 was re-encoded. And it is repeatable. Downloading those two episodes multiple times, results are the same. S11E10 always remuxes (video in Temp and final output are identical) and S11E11 always reports re-ecoding. (video in Temp and final output do have differences). And my CPU and GPU never spike.
So now I'm left with the following questions..
- Besides Hulu, which services (and titles) also see re-encoding like this? (I'm not going to count Amazon until they fix that mess).
- What makes it such that S11E11, with what APPEARS to be the same video characteristics before processing, needs to have video re-encoded, rather than re-muxed like S11E10.
- Why does this happen with only SOME videos and not others?
- IS everyone seeing the spikes in CPU/GPU? Or just some?
- IF I'm the only on not seeing spikes, is there something unique about my system that don't I see the spikes during encoding like others have reported? (my RTX3060 GPU isn't the beefiest, it doesn't perform any faster than my GTX1660ti for video encoding tasks with DVDFab stuff or other products)
I expect #2 and 3 can only be answered by the developers so I doubt we'll get an answer, but hopefully they are aware of it, and can find a fix.