2010-08-16, 03:52 PM
I am trying to troubleshoot recording problems that I am having, and something in the logs is making me suspect that multirecord could be causing the problem. Is there a way to disable the feature in config.xml?
2010-08-16, 03:52 PM
I am trying to troubleshoot recording problems that I am having, and something in the logs is making me suspect that multirecord could be causing the problem. Is there a way to disable the feature in config.xml?
2010-08-16, 03:58 PM
tjb Wrote:I am trying to troubleshoot recording problems that I am having, and something in the logs is making me suspect that multirecord could be causing the problem. Is there a way to disable the feature in config.xml? In Decives->Device setup you can set Common Interface to None, or if you need decryption, you can set Instances to 1. Then it will not attempt multirecord on that device. "I'd rather have a bottle in front of me than a frontal lobotomy"
2010-08-16, 04:06 PM
Reddwarf Wrote:In Decives->Device setup you can set Common Interface to None, or if you need decryption, you can set Instances to 1. Then it will not attempt multirecord on that device. Common Interface is already set to None, instances is set to 0. Both are greyed out and cannot be modified. However I know it will still attempt to use miltirecord. Am I missing something?
2010-08-16, 04:23 PM
No, you cannot disable multi-record. It's always enabled.
Sub,
I know it's asking a lot, but is there any chance to get a special build that allows me to disable multirecord (for testing purposes)? I have seen a couple things in the logs that lead me to believe that my problems with recording and LiveTV are related to multirecord. Pretty please?
2010-08-16, 06:32 PM
sub Wrote:No, you cannot disable multi-record. It's always enabled. Am I missing something? I thought that with only one instancs it was no way of multirecording? And analog definitly can't multirecord. "I'd rather have a bottle in front of me than a frontal lobotomy"
2010-08-16, 07:00 PM
I think sub is saying that for a device that can multirecord, then it always will; there is no possible configuration for an ATSC or QAM tuner that would prevent it from multi-recording. Analog devices of course can't, and a device with a CI module like what you have may or may not depending on how it's configured.
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
2010-08-16, 07:02 PM
@tjb: you seem to have identified in your other thread that recording using multi-record actually does work; it's when the second tuner is used that your problem occurs... so why would disabling multi-record help?
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
2010-08-16, 07:07 PM
Yes, that is true. But when it is supposed to use the second tuner it appears that the tuning info never shows up in the log as shown in the thread http://forums.gbpvr.com//showthread.php?...ion-1.5.28
I have also seen the last thing in the nrecord log saying something to the effect about checking to see if it can multirecord. Those are the reasons I think it may be related to multirecord. I have tried this on two Windows 7 systems and also on an XP system, all of them fail in one way or another.
2010-08-16, 07:21 PM
tjb Wrote:Sub,Unfortunately I cant make a small change a small change to disable it. I'd have to change heaps of things, so not practical for a small test version. |
|