DVB-C on MVP - forcibly disconnected

[psycik]

Hi sub 1 little issue

Small issue with the new dvb card. When stopping live tv from a dvb channel it reboots the mvp. It seems to happen pretty consistanly.

Have bundled up the logs. This happens regardless of mux, only seems to be live tv, and doesn't do it when stopping a pvr500 based channel.

I think I left the machine with the cyberlink mux but a newer version than 1307.

[sub]

It probably wont make any difference, but can you confirm it behaves the same with the default blue skin?

If that doesnt help, it might be worth trying the mvpmc dongle. At least then we'll be able to get some info on why the MVP disconnected if it still happens.

[sub]

It probably wont make any difference, but can you confirm it behaves the same with the default blue skin?

If that doesnt help, it might be worth trying the mvpmc dongle. At least then we'll be able to get some info on why the MVP disconnected if it still happens. Those logs just say "the MVP disconnected for some unknown reason"...not very helpful.

[psycik]

Ive tried that, but I can't even get it to start a channel now.

I seem to have a very long delay before the mpg file actually has something in it, so the mvp just gives up.

I've tried increasing the MVP Live TV Pre-play delay to 10000 and it still doesn't start.

Here are the logs anyway, but they don't show the error that you want.

[sub]

I seem to have a very long delay before the mpg file actually has something in it

Yeah, this certainly is one hassle with using digital capture devices for live tv with the MVP. It takes a long time before the device and mux start producing any data (about 5 seconds). Unfortunately there isnt much I can do about this aspect. I'm not sure if this is your problem or not though.

[psycik]

I just tried on the pc to start a recording, it creates the file instantly, but it was a good 30 seconds before the file started showing any size. About 5 seconds or so for live tv (in live preview mode).

[sub]

Thirty seconds is a bit extreme - and would certainly be enough to cause a problem for the MVP. On my machine it takes about 5 seconds to start growing, regardless of whether you're recording or watching live tv timeshift (both are effectively the same code).

I cant see any delays in the recording service logs, but thats not to say it hasnt taken some time for the device to start producing data. I'll have a think about it to see if there is any way we could see this time.

[mvallevand]

I seem to have a very long delay before the mpg file actually has something in it, so the mvp just gives up.

lf you mean mvpmc there are no timers that would drop any connections with the client, from that aspect it is totally server driven.

Martin

[psycik]

Sub requested I use mvpmc to get some more logging on a disconnection problem I'm having, but it's turned into a bigger issue thats unrelated to your dongle..

[psycik]

Even the recording service is figureing out something is wrong.

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

Look for the recording of bones.