RC3 - choppy livetv / no signal / on dvb - thread restart (1 Viewer)

[davej00]

OK.

Having seen this issue [no signal/choppy video] with RC3, I have been using RC2 for a little while [+31/1 CVS]. Yesterday I thought I would give RC4+latest SVN a go.

Well, it worked. I did a clean install of MP [read uninstall and then delete MP directory]. Using the latest 5/5 SVN and so far so good.

I will post back in a few days, as Hoppy seems to have seen the issue go -- to then come back.

The only change for me between RC2+CVS and RC4+SVN is I have added some memory [512->1G] To be clear...

RC2 OK
RC3 choppy + no signal
RC2 OK
added memory
RC2 OK
RC2 + 31/1 CVS OK
RC4 + 5/5 SVN OK [clean installed]

- Dave

 

[ohdarklord]

I thought I would see if every one else still has this bug

ive noticed than if the program im watching goes to black suddemly (eg lost does this a lot) then media poral thinks this is a nosignal

And if the hard drive runs out of space durring a recording it thinks its a no signal too

There is also the bug where it will lose signal with 10seconds when you change channel



i dont think there is just the one bug here and thats why we get mixed reports on what svn are okay and which are not.

 

[Marcusb]

I can't test this as I'm overseas at the moment, but I agree that there seem to be a few different issues.

One is that the No Signal messge appears a little too eager. Early in the thread it was stated that the message can appear if there are no new frames for a time period, IE, this can be triggered if "Lost" fades out for a little too long. In this case maybe it needs to wait a little longer before the message appears.

The second and most disturbing is when the message appears after channel changes. I think this is similar to the above. Maybe it takes a few seconds too long to lock onto a signal and causes the message. Sometimes it recovers but other times it doesnt.

 

[ohdarklord]

One is that the No Signal messge appears a little too eager. Early in the thread it was stated that the message can appear if there are no new frames for a time period, IE, this can be triggered if "Lost" fades out for a little too long. In this case maybe it needs to wait a little longer before the message appears.

I created a thread about how the no signal detection thing should wait longer before giving the message
https://forum.team-mediaportal.com/viewtopic.php?t=15061

 

[davej00]

Just to confirm -- the choppiness/no signal that I was seeing in RC3 is gone for me. See my post above from a few days ago.

As ohdarklord points out -- I think there has been more than one issue and that has led to some confusion.

- Dave

 

[ohdarklord]

i think what needs to be done is




1 When there is a problem with the hard drive durring a recording or ts media poratl should give a harddrive related error rather than no siganl


(if you dont beleive me record onto an external hard drive and unplug it during the record and you will get a no signal error)


2 The the way media portal detects no sigal should be changed so that it doesnt think that a black screen is no signal.




Once these two things have been done it will make it easyer to sort the remaining problems


What does everyone else think.

 

[davej00]

I agree.

As someone once said "you can the see the wood for the trees"

- Dave

 

[Molokoids]

I had the the No signal problem with a floppy DTV cable. I just bought a TT 1500 cable (CAM). With the latest CVS I have no signal messages on every channel change. At the beginning pressing ok after a "no signal message" make it possible to watch a channel but after some randome time I get a final no signal and it's really hard after this to catch anything.
When this final no signal comes all the channel are black and there's nothing to see and I can't listen to any DVB radio anymore.

With the floppy DTV, the free to air channels were more robust to no signal messages, but now it seems they react exactly as the encrypted channels.

Looking at the logs when I use Mpeg2Dec filter I get an error log with "filter not found" and a mediaportal log saying that the CAM is not ready. I don't get this with Nvidia filter but the problems are the same.

Also some channels seem to make the no signal message appear more than others (not related to encrypted/FTA).



MP Version: mediaportal-svn-05-16-2006--01-03.rar
Skin: Blue two
Windows Version: XP SP2
CPU Type: Athlon XP 2500
Memory: 768 Ram
Motherboard Chipset: Nforce (A7N8X-E)
Video Card: Geforce 6600
Video Card Driver: 84.21
Video Card Resolution: 1360x758
Video Codec Type & Version: Mpeg2Dec & Nvidia
Audio Codec Type & Version: MPEG/AC3/DTS/LPC & Nvdia
TV Card: Technotrend Budget C-1500 + CAM
TV Card Type: DVB
TV Card Driver: latest bda

Mpeg2Dec mediaportal.pg
Mpeg2Dec error.log
Nvidia mediaportal.log

 

[ohdarklord]

Are the developers still reading this thread?

Its just it would be nice to know that we are not alone.

 

[ronald2oo2]

I also have the choppy live stream. The longer MP is running the worse it gets, unitl loosing the signal almost continuously.

It appears to be coming from M$ messenger. msmsgs.exe is taking peaks of up to 70% CPU load which seem to cause the freezes. Strange thing is that I am not using messenger on my HTPC.

Does anybody know why MP does not start up when msmsgs.exe is terminated????

I have a FireDTV-S and have this problem from "annoying" with RC4 svn 05-07-2006--01-05 up to now "not possible to watch TV" with SVN 05-15-2006--13-33.