how do I have multiple instances of the same channel over different sources

[sub]

Thats sounds great, Will you be looking to add a move up/down option to the capture source screen which would make sorting the sources to the best order far easier?

Maybe...but I've been thinking that for the last two years, so probably not any time soon.

[sub]

That would be really good - thanks. I hit this problem quite often.

Ideally, I would like a show to be recording on the "prefered" device UNLESS this would cause a subsequent recording to then fail due to the lack of channel availability.

With 2 tuners, I don't think it would be too hard but I can image it being difficult to write logic that will work with more.

As I said, I am aware of issue, and do intend to fix it, but I couldnt tell you when.

[Mysteryman]

I have a tvcard which has the normal NZ tv channels configured for the antenna, and then I use the composite input on the tv card for my sky receiver.

I have them configured as two separate sources in gbpvr but of course in terms of channel lineup there is two tv1, tv2, tv3, maori, prime and c4 I would like to be able to easily tell on the epg which tv1 is on the sat source and which is on the antenna.
This is only likely to be compounded when I finally set up my second TV card.

I have a similar situation to the OP. On a single PVR 150 using S-Video input for a satellite receiver and the RF tuner for OTA local channels. I'm using Zap2it for the EPG and successfully set up the subscription for both capture sources using the same guide data. I then removed the duplicate channels from the satellite config. This works great....for 24 hours. In the morning when the EPG update happened, it added the duplicate channels back to the satellite capture source.

I do have to say, during the 24 hour period GB PVR works PERFECTLY and switches between RF tuner and S-video seamlessly.

Zap2it allows for multiple listings but I can't see a way to configure GB-PVR to load one listing over another. My only thought is to have TWO Zap2it accounts and configure one with the satellite data and the other with the OTA stuff. Is there a config file/line I'm missing somewhere that I could avoid the two Zap2it accounts?

[Mysteryman]

I have a similar situation to the OP. On a single PVR 150 using S-Video input for a satellite receiver and the RF tuner for OTA local channels. I'm using Zap2it for the EPG and successfully set up the subscription for both capture sources using the same guide data. I then removed the duplicate channels from the satellite config. This works great....for 24 hours. In the morning when the EPG update happened, it added the duplicate channels back to the satellite capture source.

I do have to say, during the 24 hour period GB PVR works PERFECTLY and switches between RF tuner and S-video seamlessly.

Zap2it allows for multiple listings but I can't see a way to configure GB-PVR to load one listing over another. My only thought is to have TWO Zap2it accounts and configure one with the satellite data and the other with the OTA stuff. Is there a config file/line I'm missing somewhere that I could avoid the two Zap2it accounts?

This is a follow up post for my resolution.

Since my local channels appear in both the Local and Satellite Capture sources I only had to uncheck the Locals from Satellite source and uncheck the Satellite ones from the Local source. This has worked for 3 days without issue.

Note: Deleting the channels from the source doesn't work. The next time the EPG runs in will reinsert them.

[dvasco]

This is a follow up post for my resolution.

Since my local channels appear in both the Local and Satellite Capture sources I only had to uncheck the Locals from Satellite source and uncheck the Satellite ones from the Local source. This has worked for 3 days without issue.

Note: Deleting the channels from the source doesn't work. The next time the EPG runs in will reinsert them.

Thanks for letting us know. I am sure this will come in handy for me.

[sub]

The situation has changed since my original comments. In the current v0.97.13 release, the recording conflicts originally discussed in this thread are very unlikely to occur.