Hi again doveman
Something funky is going on there. Would it be possible to revert to the bog standard Core.dll (ie. remove the subtitles patch)?
mm
Hi again doveman
Something funky is going on there. Would it be possible to revert to the bog standard Core.dll (ie. remove the subtitles patch)?
mm
Yes, I think that is correct. You can use regsvr32 /u cccp.ax to unregister it if you really need to.I just need to restore the backed up Core.dll and remove Core CC Parser from TV Post-Processing, right? It doesn't seem possible to actually remove Core CC Parser from the list of Activated Filters, so will unticking it be enough?
Yes, I think that is correct. You can use regsvr32 /u cccp.ax to unregister it if you really need to.
Great - please report the issue to Sebastiii so that he can look into it. In future it would help if you could remember to remove any patches and test with plugins disabled as it can be *very* confusing for us when strange issues like this are seen - it is not always obvious from the logs that you're using patches.OK, removing the subs patch does seem to have fixed this problem and I haven't experienced it even with Avira and OSS (Firewall only) enabled. I'll test some more with OSS (Anti-Leak) enabled as well.
I was going to comment there: was wondering whether it was possible that sample rate or bit depth issues were not allowing the renderer to connect. I'm not a renderer specialist though.The only time it locks up now is if I'm using Directsound: Speakers (Realtek) as the Audio Renderer, but that's a different problem as I wasn't using that before https://forum.team-mediaportal.com/...renderer-directsound-speakers-realtek-102228/
About the first issue: post logs if you want us to look at it.I'm still having a couple of problems with TV, one where it jumps back and repeats a second or two, and sometimes I get an error when trying to start TV, even though the tuners are set to run in Stop mode. We discussed this latter problem here https://forum.team-mediaportal.com/bugreports-74/livetv-problems-starting-stuttering-100813/ but it never really got resolved.
No comment - totally not my area of expertise I'm afraid.I'm running in dual-screen and have recently set the Power button on my Hauppauge remote to "Toggle Layer" and "Gain focus" to save having to get up and click on MP with my mouse (if it doesn't have focus it's very unresponsive and slow). I've found that this button doesn't give MP focus if I'm watching TV (I can tell from the stats, as it shows 15-20ms when it doesn't have focus and drops to about 6-7ms after I click on it with my mouse).
That can happen with more common issues, however I wouldn't exactly classify the issues you've raised as easy to deal with. You'd be best to start new threads in my opinion.I guess I should really start two or three separate threads about these problems, but I'm tired and thought perhaps they're already known about and someone might point me to an existing thread about them
Great - please report the issue to Sebastiii so that he can look into it. In future it would help if you could remember to remove any patches and test with plugins disabled as it can be *very* confusing for us when strange issues like this are seen - it is not always obvious from the logs that you're using patches.
I was going to comment there: was wondering whether it was possible that sample rate or bit depth issues were not allowing the renderer to connect. I'm not a renderer specialist though.
About the first issue: post logs if you want us to look at it.
About the second: your questions in the last post are hard to answer in detail except to say this (from memory since you seem to have removed the logs):
- TV Server was starting to grab EPG with tuner 1
- you tried to start tuning a channel before TV Server had finished tuning to the other channel for EPG grabbing
- at the time TV Server decided what tuner to use to respond to your request it had not yet registered that it was also attempting to grab EPG with that same tuner
- trying to do 2 tune requests at the same time ends up in a mess
This is what I meant when I said you were "fighting for control" over the tuner. If TV Server was smarter it should not have tried to use tuner 1, but because it did try tuner 1 it messed things up for you (=> unknown error) and the EPG grabbing *and* it did not try tuner 2 (logic for trying the next tuner seems not to handle this case).
So you now know exactly what the cause is in as much detail as I can give you. The only solution right now is to disable the idle EPG grabber or get your EPG in a completely different way (eg. WebEPG), otherwise you will have to put up with that occasionally happening. You could also try disabling EPG grabbing on some of your tuners (ie. tuner 1) so that it is less likely to happen, but the issue will remain while you continue to have idle EPG grabbing enabled.
No comment - totally not my area of expertise I'm afraid.
That can happen with more common issues, however I wouldn't exactly classify the issues you've raised as easy to deal with. You'd be best to start new threads in my opinion.
No problem.Thanks for taking the time to reply in detail.
Tony will correct me if I'm wrong but I think there is specific debug to say that it is modified. Wouldn't hurt to mention it but I would say no reason to disable it.Will do. Does this apply to the DWM_dshowhelper I'm using as well? It might be problematic for me to run without that, as with my dual-screen setup I think TV was pretty unwatchable before.
I know what you mean.I'll try, but with these intermittent problems they never occur when you want them to and unless I run permanently in debug mode, I doubt I'll be able to get logs with plugins disabled.
It isn't about priority - it is that TV Server literally hasn't registered that it is EPG grabbing yet. I think that is because TV Server only registers a tuner as "in use" *after* it finishes successfully tuning to a channel. Could be wrong there but if I'm right then it isn't exactly the greatest design. gibman is working on this.Hopefully someone will find the time to improve the logic so that the TV Server gives priority to TV over EPG grabbing.
Tony will correct me if I'm wrong but I think there is specific debug to say that it is modified. Wouldn't hurt to mention it but I would say no reason to disable it.
I know what you mean.
Any luck over the past couple of days?
It isn't about priority - it is that TV Server literally hasn't registered that it is EPG grabbing yet. I think that is because TV Server only registers a tuner as "in use" *after* it finishes successfully tuning to a channel. Could be wrong there but if I'm right then it isn't exactly the greatest design. gibman is working on this.
Getting back to the topic at hand: are you okay with me marking this thread as "no bug" since it was caused by a patch