2013-01-25, 03:22 AM
Now I realize why I haven't run into this bug before, though I did encounter something similar (http://forums.nextpvr.com/showthread.php...vice-versa!). I don't use padding, so this re-allocation of tuners rarely happens on my setup. NPVR schedules shows without considering padding, then attempts to accomodate padding at recording time if it can. It's only when a recording is moved to another tuner that this bug occurs. Without padding, the only time this happens is when someone is watching Live TV using a tuner scheduled for a recording.
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV