Usb Uirt

[audio]

Good v1.0 product!

I'm out of PCI slots and have a USB UIRT on order. I plan to use Girder to change my antenna orientation on each channel change request. I don't see any option for USB in the IR Hardware Setup.
Is the USB UIRT supported? Please forgive me if this question has already been addressed and I've overlooked it.

[Narflex]

Since the USB UIRT is fully supported by Girder (it is, isn't it?) then you can use it with SageTV as a transmitter and/or a receiver. There's an export group already on Girder's site for using the reciever portion. And there's a plugin on our website for using the transmitter portion.

thanks,

[audio]

USB UIRT arrived today. Receiving remote commands to control SageTV is working great. Thanks for the GML template. I'm having a few issues setting up the desired transmit function. In my case, I need the Sage application to tune the capture card to the requested channel and additionally transmit the "change antenna rotation to channel x" IR sequence.

I've installed EXETunerPlugin.dll in Frey Technologies/Common,
created the .../Sage/EXETunerPlugin registry entry with the value C:\Program Files\Girder\event.exe 4308441044F0 75 %CHANNEL% -silent, and have created a Girder command with an equivalent eventString, but cannot get the command to execute.
Any suggestions? I tried "rotateAntenna 203" and "rotateAntenna 112" as well without success.


Additional information.

In setting up SageTV, I was initially prompted as to whether I had an IR transmitter device. Since I didn't have one at the time (and having already experienced the sageTV service needed issue) I responded no to the "have IR transmitter device" question. I can't seem to get this prompt back, despite uninstalling and re-installing. I don't know if this is of any consequence in getting IR commands transmitted. I don't see any property in the Sage.properties file which I can set to indicate that an IR transmitter is available.

[Mark Lamutt]

Audio - in regards to your second question, you need to go back through the setup wizard to get back to the IR transmitter setup.

[audio]

Mark,

That's what I thought as well and I'm glad to hear that setup from the wizard is the solution. When I went back through the wizard setup (3 times, just in case I blinked), it never showed up. I downloaded and installed the latest trial version as well. When I went to enter the code, it didn't like my original code, and it wouldn't take TRIAL, so I used my previous Sage.properties file and was able to launch the application, but still no IR setup is seen in the wizard. Are there registry keys I need to reset or delete or am I still overlooking something?

[Narflex]

IR setup only comes up if you select the composite or s-video input. The reason is because if you're using the RF input the tuning is done on the capture card and no IR transmitter would be needed....but now I see a reason for it. Modifying the properties file won't get around it either.

Your best bet is to use an external source for tuning on the composite/svideo line and then have Girder send an IR event to that and the antenna control.

What were the problems you were having with the Access Codes in the Setup Wizard?

[audio]

Thanks Narflex. I'll try capturing via the svideo input and line-in to the sound card. I'm concerned that this may introduce lip-synch issues (Revo 7.1) but certainly willing to give this a try.

Any chance the ability to transmit external commands upon channel change in addition to internal tuner channel change will see the light of day in the near future?

As for access codes problems - I had accidentally deleted the initially downloaded trial version of the software (across a network mount point, so file was not retrievable) and so I downloaded the latest version to try to re-run the IR setup portion of the wizard.
After installation, I tried entering the access code from the trial SageTV service subscription, but it wasn't accepted. Then I tried (using my name again) to enter TRIAL as I read from the site. This password was not accepted either. At this point, I copied over my saved version of Sage.properties and the application launched normally.