I'm using Win 10 Pro 64-bit (fully patched) and the latest version of JRiver, with Red October HQ (madVR) playback (log & system info attached). The library is remote (Debian VM as library server on the NAS), files are *.iso however. Hence, they are downloaded and then played back (i.e. local files effectively).
Recently, I've noticed that I couldn't play back NTSC DVDs anymore (or I thought, the issue was with the NTSC DVDs). There was enormous stuttering (huge clock deviation, lots of dropped & repeated frames). After a while (like ca. 30s) everything would settle down somewhat, but still, playback wasn't smooth.
First, I thought: Driver issue? So, I went back to the "known good" driver for my system. No change in behaviour. After looking at other DVDs (PAL this time), I noticed comparable issues.
After a while I identified Videoclock as sort of being the culprit. After turning it off, everything works much better. However, I didn't turn on Videoclock by accident. It has always been on, since the initial install of JRiver. And it had worked great.
What has changed? Or, has something changed? I can't pinpoint it to a specific upgrade of MC27 because I'm using the system not often enough to actually evaluate each update with something like a test suite.
Today, I tested the setting again, after:
- Uninstalling JRiver
- Removing the nVidia driver with DDU
- Rebooting
- Installing the nVidia driver
- Installing JRiver
Then, I activated Videoclock and selected a DVD (PAL) via TheaterView. After the file was received from the library server, it was mounted by VirtualCloneDrive, and then played back via JRiver. No interaction with the system after the playback started. The DVD will bring up the menu, wait, and after some time will automatically start the main feature. After ca. 2 minutes, I did capture a screenshot of the madVR overlay and stopped the playback. Then, I "ejected" the *.iso and closed JRiver.
Now, I restarted JRiver, deactivated Videoclock and selected the same DVD as before. Again, download, playback, no interaction, screenshot at roughly the same time.
The difference is like night & day, with Videoclock being deactivated, there is only the slight initial stuttering that's always there, but then everything is smooth (however, not as smooth as it used to be-- the estimated time for frame drops/repeats used to be in the several hours or even higher range). With Videoclock enabled, the stuttering lasts much longer and there is massive frame drop/repeat. Also, the clock deviation is much higher (ironically, as Videoclock should do the opposite-- and it did, not too long ago).
Thanks already for looking into this...
PS: I'm aware that MC27 is kind of EOL, so maybe this topic belongs somewhere else now? If so, then I'm sorry and please feel free to move it respectively.