2) Disable auto-import work during Display View playback
Thoughts?
Yes. On both really, if #1 is possible, but mostly #2. And Thumbnailing too.
In my case, I don't think it really is so much the Auto-Import that is slowing things down as the Thumbnailing. I suspect the problem is that the Filters used to decode the videos don't always respect the thread priority of JRWorker.exe, or at least don't play nicely with multiple instances of each other running, particularly in "startup" (or perhaps it is simple disk throughput or something).
One easy to replicate example I can think of is this:
1. Set Media Player Classic to allow multiple instances started from file.
View --> Options. Then Choose
Player in the tree on the left, and change
Open options to "Open a new player for each media file played".
2. Open a high-quality file in MPC. Preferably one that uses Haali and FFDSHOW to decode. Something like a x264 MKV would be perfect. Let it play for a few seconds.
3. Then open a few more other (similar) files in second, third, and fourth copies of MPC.
If you do this, at least on all of my systems, the video playback in the first copy of MPC will "pause" for a second or two while the new instance is loading. Once they are loaded, then everything "springs" back to life and they can play concurrently. This happens to me even if I'm loading the multiple files off of different physical disks, though it does seem to be slightly worse if they are all on the same disk (which makes some sense as the drive head seeks to find the new spot).
I think this is a bit of a microcosm of what we are seeing in MC when it is launching multiple thumbnail worker threads. Once they are launched, they could "play" fine. The problem is that they don't really "play" they just render a frame and then quit and launch a new thread, and I think it is sending the Windows scheduler into a tizzy. Even if they all have low priority, this constant loading and unloading of filter resources (not to mention disk head seeking) is bound to draw some substantial resources.
That's all fine, so long as you aren't doing something that has zero tolerance for latency, like full-screen video playback does.