MediaPortal Forum - View Single Post

marmite · 2007-04-26, 18:22

I tried reproducing this a couple of days, by scheduling back to back recordings with 'every day on this channel' and 'Mon-Fri' (I'm not sure which I did the first time I saw this problem) but I was unable to reproduce it.

But it had occured multiple times before I reported.. so I was still on the look out for it. Then I thought of something which might explain ( I mentioned at end of previous post)

>"I have my DVB-T card in settings 'This card can decode' set to 3."

It occured to me, that this was probably not supposed to be set like this. I had thought that you needed to set this to tell TVEngine that it could record multiple shows of the same MUX. But.. I'd revereted it back to 1 now and I see that it quite happily record of the same MUX anyway....

I also hoped this was at the root of the problem here, but alas I've encounted it again, I've attached the tail of my TsWriter.log

Scenario is similar but not same, I have back to back recording again, but I also had another recording overlapping on a different channel but same MUX.

Summary:

Prog1: Channel = BBC1, Prog = BBC London News, EPG time = 13:28->13:40
Prog2: Channel = News24, Prog = BBC News, EPG time = 13:00->14:00
Prog3: Channel= BBC1, Prog = Neighbours, EPG time = 13:40->14:05

What actually happened: (computer turned on @ 13:36)

Prog1: started record @ 13:36:44
Prog2: started record @ 13:36:46
Prog3: started record @ 13:38:10

... as expected ...

Prog1: stopped @ 13:45:11
Prog2: stopped @ 14:05:10
Prog3: stopped @ 14:10:01

..again all as expected....

*However* - Prog2's & Prog3's .ts files stop @13:45 also
I'm judging this by 2 facts;
a) The play length as seen by e.g. vlc/MPC indicates Prog2=9m12s and Prog3=7m49s
b) Prog2 has clock on screen in movie which and last visible frame indicates 13:45

Interestingly the timestamps on Prog2 and Prog3 are 14:05 and 14:10 respectively, i.e. so the 'Stop' messages did at least touch these files even if they weren't being written to anymore.

Not sure what else I can add... other than HELP!

If anyone can share similar experiences, point me at some other thread to read, give me any pointers of ways to investigate futher etc. etc. etc - I'd be most grateful..

2007-04-26, 18:22	#2 (permalink)
marmite Portal Member Join Date: Mar 2007 Posts: 12 Thanks: 0 Thanked 0 Times in 0 Posts Country:	I tried reproducing this a couple of days, by scheduling back to back recordings with 'every day on this channel' and 'Mon-Fri' (I'm not sure which I did the first time I saw this problem) but I was unable to reproduce it. But it had occured multiple times before I reported.. so I was still on the look out for it. Then I thought of something which might explain ( I mentioned at end of previous post) >"I have my DVB-T card in settings 'This card can decode' set to 3." It occured to me, that this was probably not supposed to be set like this. I had thought that you needed to set this to tell TVEngine that it could record multiple shows of the same MUX. But.. I'd revereted it back to 1 now and I see that it quite happily record of the same MUX anyway.... I also hoped this was at the root of the problem here, but alas I've encounted it again, I've attached the tail of my TsWriter.log Scenario is similar but not same, I have back to back recording again, but I also had another recording overlapping on a different channel but same MUX. Summary: Prog1: Channel = BBC1, Prog = BBC London News, EPG time = 13:28->13:40 Prog2: Channel = News24, Prog = BBC News, EPG time = 13:00->14:00 Prog3: Channel= BBC1, Prog = Neighbours, EPG time = 13:40->14:05 What actually happened: (computer turned on @ 13:36) Prog1: started record @ 13:36:44 Prog2: started record @ 13:36:46 Prog3: started record @ 13:38:10 ... as expected ... Prog1: stopped @ 13:45:11 Prog2: stopped @ 14:05:10 Prog3: stopped @ 14:10:01 ..again all as expected.... However - Prog2's & Prog3's .ts files stop @13:45 also I'm judging this by 2 facts; a) The play length as seen by e.g. vlc/MPC indicates Prog2=9m12s and Prog3=7m49s b) Prog2 has clock on screen in movie which and last visible frame indicates 13:45 Interestingly the timestamps on Prog2 and Prog3 are 14:05 and 14:10 respectively, i.e. so the 'Stop' messages did at least touch these files even if they weren't being written to anymore. Not sure what else I can add... other than HELP! If anyone can share similar experiences, point me at some other thread to read, give me any pointers of ways to investigate futher etc. etc. etc - I'd be most grateful..