DVB-C on MVP - forcibly disconnected

[sub]

In this example, hit record from tv guide, then watched the file system and stopped the recording when it finally changed off 0 bytes.

Are you sure? ie, if you view the properties of the file it may report some non-zero value. Windows Explorer often wont show that the file has changed in size unless you view the properties of the file.

[psycik]

Just tried again and did a dir \\pvr\recordings\dancelife

Using a dir command on the file system, started the record (from tv guide with the record button) at 11:42:30. Started hitting dir comand, after about a second the file was created with zero bytes.

At 11:44:02 the file size finally showed 106,490 bytes.

[sub]

Thats odd. I cant explain that one.

[psycik]

no other options, solutions? Things to look at??

Doesn't seem to matter which mux or dvr-ms or mux version.

Any other way of capturing something with that card to see if it does the same thing??

[sub]

I'm not really sure what to suggest.

When you say 106490 bytes, did you mean kilobytes?

[sub]

Does this problem vary between channels?

You could try creating the following registry setting:

HKEY_LOCAL_MACHINE\software\devnz\LogPSIProcessing.log=2 (DWORD)

The try again. This should produce a c:\psi.log file. I'd be interested to know if this log indicates its getting data from almost immediately, or whether it only gets data about when the file starts growing.

[psycik]

Sorry I had to go out.

No that was bytes rather than kilobytes. I stopped it as soon as I saw it change from 0.

I've tried adding those keys.

If that a key called HKEY_LOCAL_MACHINE\software\devnz\LogPSIProcessing with a dword value called .log ?


Or is that a dword value called HKEY_LOCAL_MACHINE\software\devnz\LogPSIProcessing.log ??

I tried both and neither worked I'm affraid. And just restart the recording service after creation?

[psycik]

Tried all combinations, and no log, but started up the plugin log monitor window, and that is empty until after than 1 min time period then it suddenly kicks in to gear, and the file starts updating... So I would conclude that it's not actually tuned and doing anything until after that 1 minute.

[sub]

That was supposed to be:

HKEY_LOCAL_MACHINE\software\devnz\LogPSIProcessing=2 (DWORD)

[psycik]

ok, creating log now, started recording, but it seems the same, 0 byte log for 60 to 90 secs then all go.

It like the tuner doesn't get told to start. Do you want all the logs?