- August 4, 2007
- 861
- 99
- Home Country
- Spain
- Thread starter
- Moderator
- #51
morpheus_xx... I don't know if you've comitted this tsreader&tswriter to SVN... but I've found a problem with them... Exactly with tswriter... It was working right... but suddenly it somehow got broken. To reproduce problem, I do this:
- Start livetv for the first time, in any channel, no prob.
- Stop livetv, and start it again IN SAME channel.
- First time you do this, livetv takes 10 or 15 seconds to work.
- Second time you stop and start, you get a "unable to start graph", and you can't see this channel any more... You must select another channel... then it works again...
So it's a problem when starting livetv in same channel you were watching when you stopped. If you choose any other channel, there's no problem.
I've been reviewing my logs, and I've come across a very interesing message, that I get when I stop livetv for the first time:
TsWriter filter isn't released for some reason, so it can do its job anymore...
Please tell me if you need any more info.
Just going back to last "tswriter only" fix, fixes this issue...
Sorry for the bad news... bye!
- Start livetv for the first time, in any channel, no prob.
- Stop livetv, and start it again IN SAME channel.
- First time you do this, livetv takes 10 or 15 seconds to work.
- Second time you stop and start, you get a "unable to start graph", and you can't see this channel any more... You must select another channel... then it works again...
So it's a problem when starting livetv in same channel you were watching when you stopped. If you choose any other channel, there's no problem.
I've been reviewing my logs, and I've come across a very interesing message, that I get when I stop livetv for the first time:
Code:
2010-05-09 03:03:33.207212 [(12)]: !!! Error releasing TSWriter filter (_filterTsWriter as IBaseFilter was null!)
TsWriter filter isn't released for some reason, so it can do its job anymore...
Please tell me if you need any more info.
Just going back to last "tswriter only" fix, fixes this issue...
Sorry for the bad news... bye!