the reason why it's coming up now is because our algorithms to detect direct streaming and stream copying are much better than ever before from the client-side perspective. so prior builds (and other apps) would never even try to stream copy which is why the issue wasn't occurring.
but now with almost every app using the profile engine, we're getting really accurate client capabilities factored into the algorithm. this now leads to the issue of we know that the client can play it, but is the video suitable for what we're going to try to do (e.g. hls with stream copy). And the only way to answer that is to have the scan extract more information about the video's key frame intervals. So this is going to lead to longer scan times, but more of the "everything just works" streaming.