When I initially tested, the tuners were not pooled correctly. WMC definitely messed up the tuner in use inside MC. Not sure if it is still the case now.
We actually have 2 WMC PC's and the 1 JRiver PC sharing the pool of 12 Ceton tuners (2 x InfiniTV ETH 6) and there are definitely a lot of users posting on AVS Forum and The Green Button forum who make use of the pooling feature without any significant issues. While it's possible that's the culprit for the abbreviated recordings, I would be more inclined to think something else is going on. Of course without any indication as to why the recordings in question were truncated, it's kind of difficult to diagnose the problem. I did some searching and figured out how to turn on logging in MC and found where it's stored. Next time I get one of these truncated recordings, I'll try to see if there's any useful info in the logs.
No reason.
Oversight? Lack of time? Logistics?
All kidding aside, I consider this an extremely important DVR feature. Stuff is bound to happen that will cause a recording to fail once in a while. If the user isn't around at the time to notice what happened, they may lose out on the chance to manually reschedule, while the software ought to be able to do it automatically for the user. This is one of the things WMC does extremely well.
No. MC uses its own madVR settings. I am just trying to see if we did not set it appropriately.
Right, but as I said, the recordings from the other programs play fine when I have imported them into MC. I didn't say that I watched those recordings in BeyondTV or WMC (though they do play back fine in the other programs too) as that would obviously use all sorts of different settings.
Try changing that to Lanczos 3 taps, or Bicubic 75.
Those work out better than Laczos with 4 taps, but playback still isn't very good.
If your display max resolution is equal or less than 1080 lines, you may need down scaling, not up scaling.
My display is a HDTV with a resolution of 1920x1080P. Unless madVR uses really bizarre terminology, going from 1080i to 1080p wouldn't be down scaling. In any event, the only settings I've changed during this conversation were in the up scaling section and they have made very clear differences in the quality of playback in regards to reducing or eliminating the stuttering.
In case the scores might be useful, here are the results of running the Benchmark in the JRiver help menu:
Math Score: 2211
Image Score: 4345
Database Score: 4013
JRMark (version 19.0.163): 3523