Configuring Hauppauge Colossus

[mulletback]

Too big to upload, even when zipped, let me fiddle a bit...

[sub]

If you do an 'empty epg' then you should be able to zip and attach ok.

I suspect a column is missing in your database.

[mulletback]

Interesting, I ran 'empty epg', but the filesize didn't change - no listings though.

[sub]

Can you check if you HDPVR_RECORDER table has a crossbar_filter column?

[mulletback]

No, it does not. I assume it's a varchar type, but how many?

[sub]

These are the commands it was supposed to execute on existing databases.

alter table HDPVR_RECORDER add column crossbar_filter VARCHAR(255)
update HDPVR_RECORDER set crossbar_filter = 'Hauppauge HD PVR Crossbar' where crossbar_filter is null

[mulletback]

I created a crossbar_filter field - the value it was looking for was 'Hauppauge Colossus Crossbar', however. I had to fill the oid field manually, also instance and source. The changer exe and changer args will now stick. However, when I do quick record, it does not call the changer. I already had channels defined, do I need to toss these and make new to have the changer applied?

[mulletback]

The daily report - by hand configuring the db, npvr now sees and uses the Colossus for recording and live tv. I cleared the channels and reassigned channels to the Colossus - the changer_exe info is now in the db, but channel changing still doesn't work. In the record logs there are no calls to the blaster/changer. I use channelw.exe over firewire to change channels - works fine called manually.

[sub]

The daily report - by hand configuring the db, npvr now sees and uses the Colossus for recording and live tv. I cleared the channels and reassigned channels to the Colossus - the changer_exe info is now in the db, but channel changing still doesn't work. In the record logs there are no calls to the blaster/changer. I use channelw.exe over firewire to change channels - works fine called manually.

Reproduce the problem, then post the npvr.log and nrecord.log and I'll take a look.

[mulletback]

OK then, I have the Colossus working in npvr and the changer is working as well. Here's what I found:

First, the channel change command is "c:\NPVR\channelw.exe -f 2 {channel}". The path to the exe and the argument are correct in the HDVPR_RECORDER table.

here's what I found in the CHANNEL_MAPPING table:

Old channels put in before the Colossus was properly configured FAIL to tune and look like this in the "tuning" field:

<tuning>
<type>HDPVR</type>
<locator>
<channel>397</channel>
<input>0</input>
<blaster_executable></blaster_executable>
<blaster_args></blaster_args>
</locator>
</tuning>

There is no "Running blaster" line in the record.log.

New channels defined AFTER the Colossus was properly configured FAIL to tune and look like this:

<tuning>
<type>HDPVR</type>
<locator>
<channel>398</channel>
<input>0</input>
<blaster_executable>c:\NPVR\channelw.exe</blaster_executable>
<blaster_args>c:\NPVR\channelw.exe</blaster_args>
</locator>
</tuning>

Note the <blaster_args> value (I didn't try putting in the proper args)

There is this line in record.log: "Running blaster: c:\NPVR\channelw.exe c:\NPVR\channelw.exe"

Putting in this tuning field works:

<tuning>
<type>HDPVR</type>
<locator>
<channel>405</channel>
<input>0</input>
</locator>
</tuning>

In record.log "Running blaster: c:\NPVR\channelw.exe -f 2 405"

So, I have all the tuning working now. I suppose I could have corrected the <blaster_args> values, but it was easier to globally remove all references to <blaster_executable> and <blaster_args> in CHANNEL_MAPPING.

So the question is "why isn't the <blaster_args> value populated properly"? :confused: