Windows MCE hates Target!

Forums › Home Theatre (incl HTPC) › Windows MCE hates Target!

Regs

Cloud Guru
4060 posts

Uber Geek

Trusted

Snowflake

Subscriber

# 45915 4-Nov-2009 20:09

i dont know what it is, but nearly every tuesday at 7.30PM target (tv3) fails to record more than about 45seconds. what is really weird is that it did this on both Win7 as well as WinXP MCE. One was fed by xmltvnz epg loads and the other (win7) by OTA EIT Data on DVB-S. As a backup I schedule the re-run of target on Saturday and that appears to work fine. I think that it was OK when i scheduled the TV3+1 episode too. I also havent seen this happen with any other shows or timeslots.

anyone else run into a program that just wont record on MCE?

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs

gbwelly

863 posts

Ultimate Geek

Subscriber

# 270256 5-Nov-2009 10:18

What does it say in the recorded TV history log?

Regs

Cloud Guru
4060 posts

Uber Geek

Trusted

Snowflake

Subscriber

# 270322 5-Nov-2009 13:16

Hmm. I guess i should have checked the error logs first.... that what i tell all my staff. (*sends himself to corner*)

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs

Nety

2584 posts

Uber Geek

Mod Emeritus

Trusted

Lifetime subscriber

# 270626 6-Nov-2009 13:26

Come on out with it.. so what was happening? or are you sending yourself to the corner for not checking the logs before posting?

Media centre PC - Case Silverstone LC16M with 2 X 80mm AcoustiFan DustPROOF, MOBO Gigabyte MA785GT-UD3H, CPU AMD X2 240 under volted, RAM 4 Gig DDR3 1033, HDD 120Gig System/512Gig data, Tuners 2 X Hauppauge HVR-3000, 1 X HVR-2200, Video Palit GT 220, Sound Realtek 886A HD (onboard), Optical LiteOn DH-401S Blue-ray using TotalMedia Theatre Power Corsair VX Series, 450W ATX PSU OS Windows 7 x64

Regs

Cloud Guru
4060 posts

Uber Geek

Trusted

Snowflake

Subscriber

# 271129 8-Nov-2009 23:01

Nety: Come on out with it.. so what was happening? or are you sending yourself to the corner for not checking the logs before posting?

this is what I have in the logs. it didnt help much:

{7:00:12} Close Up was deleted on 27/10/2009 7:00:12 p.m. to make room for a new recording of this series. This series has a limit of 2 recordings.
{7:30:02} Target was deleted on 27/10/2009 7:30:02 p.m. to make room for a new recording of this series. This series has a limit of 2 recordings.
{7:31:05} Close Up started recording on 27/10/2009 7:00:18 p.m. and stopped on 27/10/2009 7:31:01 p.m. as scheduled.
{8:00:02} Portions of Target may not have been recorded. A signal loss occurred during the recording.
{8:00:23} What's Really In Our Food? was not recorded. There was no TV signal when the show was scheduled to record.
{8:31:00} What's Really In Our Food? started recording on 27/10/2009 8:00:27 p.m. and stopped on 27/10/2009 8:31:00 p.m. as scheduled.

I get the "there was no tv signal when the show was scheduled to record" regularly. Usually when i only have one channel scheduled to record. If i record two channels at once - e.g. tv1 and tv3 for news - then i dont seem to get the error. I suspect that this is some multi tuner problem.

As for the "signal loss" error, for some reason this only seems to occur when attempting to record target on tuesday at 7.30. Its odd.

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs

Regs

Cloud Guru
4060 posts

Uber Geek

Trusted

Snowflake

Subscriber

# 271830 10-Nov-2009 20:57

tuesday again.... once more i have a short recording of targer - 47 seconds this time.

same error again: "Portions of Target may not have been recorded. A signal loss occurred during the recording."

Still havent seen this happen for any other show or timeslot. I'm going to try recording on TV3+1 next week and see if the results are better!

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs

tomgeeknz

895 posts

Ultimate Geek

# 271833 10-Nov-2009 21:05

Tonight was the last target episode until next year. Of course you won't know that because you did not see it!

Regs

Cloud Guru
4060 posts

Uber Geek

Trusted

Snowflake

Subscriber

# 271867 10-Nov-2009 22:18

AhA! Problem solved! :D

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs

Nety

2584 posts

Uber Geek

Mod Emeritus

Trusted

Lifetime subscriber

# 271869 10-Nov-2009 22:23

Have you made sure you have the latest drivers for your tuner? I used to get that error sometimes under Vista but a driver update seemed to sort it out.

Regs

Cloud Guru
4060 posts

Uber Geek

Trusted

Snowflake

Subscriber

# 271878 10-Nov-2009 23:11

yeah, updated them *again* since posting.

i have seen a couple of interesting ideas floating around that may be worth trying, one of them is attenuating the signal in case it may be *too* strong. I have an attenuator lying around somewhere as i used to use one with my ihug satellite to prevent the card overheating from too strong a signal.

the other suggestion was that this was a problem that occcurred with multiple cards - not on a card with dual tuners. All the errors also seem to occur only when one channel is scheduled for recording (see the whats really in our food error for the other error). Perhaps I can try playing around with tuner priority and see if that makes a difference to those errors, at least.

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs