Configuring Hauppauge Colossus

[sub]

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

I've attached a patch that'll fix it for channels created in the future.

[mulletback]

I've attached a patch that'll fix it for channels created in the future.

Excellent! Thanks so much! Comcast is going all digital in my area on April Fools Day (?!?) :eek:, not clear QAM, so the Colossus is going to get more channels assigned soon.

[mvallevand]

Sub, I do hope you rethink this. Setting the blaster parameters takes a bit of tweaking and if you have unmap all the channels and re-add them this will quickly become frustrating.

Martin

[sub]

Sub, I do hope you rethink this. Setting the blaster parameters takes a bit of tweaking and if you have unmap all the channels and re-add them this will quickly become frustrating.

I do want a better scheme (have done for the last couple of months), but nothing has come to me so far. I need to accommodate multiple channels from different inputs with potentially different blasters, and I need it to fit in with the current UI and be easy for people to understand.

The scheme storing copies of the current settings in the tuning information was a model I'd already been using for DVB-S etc, which allows for very complicated setups with all sorts of channels with different satelittes and lnb/diseqc settings, so I followed a similar module for the HD-PVR. With DVB-S though, no one ever has to go back and tweak those values. With the HDPVR, the user doesnt need to go back and tweak the video input (and this works well under this new model), but the blaster does seem to be one that needs to be able to edit regularly (and on multiple channels at the same time, though not always all channels). I'm not really sure what to do about this.

[SickBoy]

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

Pardon the question but how (exactly) do I run these on my install? Haven't modified sqlite db's before.

[sub]

You'd need to download a utility like SQLiteSpy, open the npvr.db3 file, then execute each of these statements.

[mvallevand]

Sub, is there any harm in modifying config.xml replacing 2.0.3 with 1.5.6 in the top part and running setup again?

I hope you say no problem, because I just tried and got this in my log

Code:

2011-03-07 22:50:18.851    [DEBUG][1]    Executing SQL: update CAPTURE_SOURCE set priority=-1 where priority is null
2011-03-07 22:50:18.853    [DEBUG][1]    Executing SQL: alter table HDPVR_RECORDER add column crossbar_filter VARCHAR(255)
2011-03-07 22:50:18.854    [DEBUG][1]    Error excuting SQL (probably already applied in previous release): System.Data.SQLite.SQLiteException: SQLite error
duplicate column name: crossbar_filter
   at System.Data.SQLite.SQLite3.Prepare(SQLiteConnection cnn, String strSql, SQLiteStatement previous, UInt32 timeoutMS, String& strRemain)
   at System.Data.SQLite.SQLiteCommand.BuildNextCommand()
   at System.Data.SQLite.SQLiteCommand.GetStatement(Int32 index)
   at System.Data.SQLite.SQLiteDataReader.NextResult()
   at System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
   at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
   at NShared.UpdateManager.DoDatabaseUpdates()

I just wish VARCHAR was lower case like all the other instances? It's a tiny thing but it drives me crazy.

Martin

[SickBoy]

I downloaded SQLite Spy - and I think I did that - no change, though.

[SickBoy]

Actually, I take that back. It does work, it just never shows the executable path/params in the source setup GUI for the HDPVR. If I manually enter them when adding the channel everything works.

[autumnmist]

We're trying to set up a Colossus card and getting an error "Unable to locate crossbar filter (#1)." I found this thread and saw mulletback's posts. I went into the npvr.db3 database to add the crossbar_filter column, which I did successfully. However I realized that the Colossus card isn't even listed in the HDPVR_RECORDER table. That table is completely empty, with no rows whatsoever.

I saw mulletback said that he had to insert a row and manually set the oid, instance, input source, etc. I know how to do that, but I don't know what values to use. Presumably device_instance=1, but I am not sure about input_source or capture_source_oid.