RC3 New problem with false conflicts

[Rich A]

This is the first time I've noticed this. Pretty sure it was not like this with RC2. I think the bug reporting is closed, but I'll mention it here.

Since installing RC3 I've had this happen a few times.

A program can not be scheduled to record because of a conflict. Yet there is no conflict. I have three tuners. One Digital and and two analog. At the 10 PM time slot (for example) there is already one show scheduled to be recorded off one of the analog tuners. There is nothing else scheduled. No digital and no other analog. When I try to record another show in that time slot, it tells me cannot record because of a conflict. There are no "over-lapping" recordings prior or post this time period. I CAN select and setup a recording on the digital tuner. But even though I have one unused PVR-x50, I can't set up a record.

[merrypig]

um. 4.1 was released rich- you'll need to file a customer support issue now =)

[Fonceur]

Originally Posted by Rich A

At the 10 PM time slot (for example) there is already one show scheduled to be recorded off one of the analog tuners. There is nothing else scheduled. No digital and no other analog. When I try to record another show in that time slot, it tells me cannot record because of a conflict.

If you use the Guide, do you notice any other show that is prevented from recording at that time (like the second showing of a previous show)? The reason I am asking is that while developping my app I did noticed false conflict that would go away once the first showing was actually recorded.

[Rich A]

Originally Posted by merrypig

um. 4.1 was released rich- you'll need to file a customer support issue now =)

Really? Never got a notice about it. Should I install the "actual release" or stick with the latest RC3 until the next round ??

[Rich A]

Originally Posted by Fonceur

If you use the Guide, do you notice any other show that is prevented from recording at that time (like the second showing of a previous show)? The reason I am asking is that while developping my app I did noticed false conflict that would go away once the first showing was actually recorded.

No that time slot (in this example 10pm to 11pm) only has that one show scheduled and there are not even any "cancelled" or otherwise noted shows. And I also checked for over-lapping from the previous hours and the following hour. For some strange reason I could not schedule two shows in that time slot.

By the way. Another anomaly. But this one must be a problem with their guide source. I missed last week's Stargate Atlantis. It was tagged as a repeat. I'm pretty sure it wasn't. I just seem to be having a few odd things going on with the guide lately.

[btvfreak]

That guide data issue probably isn't just a BTV thing:
http://forum.byopvr.com/dvr/index.php/topic,5026.0.html

[Rich A]

For Fonceur,

You may actually be on to something. I was reporting from a problem I had a couple days ago. Just to be sure (and to check our your idea) I checked again just a few minutes ago. There IS a cancelled recording in the same slot. Here's the exact thing .. ( and I think this is a bug ) For example.

We are talking about two tuners and all shows on the same hour slot.

Channel 2 has the Circle N with the line through it. It is normally scheduled show but NOT set to record because it's a repeat.

Channel 4 is set to do a normal "new shows" recording.

Nothing else is in the time slot.

So I should have only one recording being done. Yet, when I try to schedule another one in that time slot, it tells me it conflicts with one or more other shows.

So I "changed" the one marked to "not record" on channel 2 forcing it to record. It did so and started to record. It now has two channels in the same time slot recording. I then "stopped" the channel 2 recording .. and at that point everything was back to normal. Channel 2 was lined out saying the recording was stopped. And I COULD then select a 2nd show anywhere in that time slot to record.

I think they might have a problem where if a normally recorded show is tagged to NOT record because of it being a repeat .. they aren't re-setting "what-ever" to free up the use of the tuner. Even though the tuner is actually not being used .. BTV thinks it is. When I manually change it to record and then manually stop it, THEN the flag is set again and the tuner is freed up.

Is that kind of what you were seeing ?? Now I have to see what build is the latest full release so I can update my stuff. And install that and see if I can still duplicate it.

[Rich A]

It's more than just that problem. Here's a screen capture to show you yet another weird thing. Originally I had CSI:Miami set to record on the analog channel 2. This afternoon, several hours ago I decided I wanted to watch it in High Def. So I turned off the analog (TV Channel 2) and I selected the HD channel (1031). If you look at the screen shot, channel 2 is set NOT to record.

Well guess what? I just checked. BOTH are still recording. Even though several hours ago I cancelled thel channel two recording .. it's still recording.

I'm still working with the last RC3 .. and just downloaded the official 4.1 release. As soon as it finishes recording I'll install it and see if it's been fixed in the gold release.