|
Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Firewire channel tuning woes
Over the weekend I had to reinstall windows 10 from scratch and fortunately I had a recent backup of my SageTV directory and the drivers to install the STBs for Firewire channel changing. I'm using the EXEMultituner plugin and Timmmoore's channel.exe. I have no problem changing channels on my two boxes from the command line. However, in Sage, only one box responds. I double checked my registry settings etc. and everything seems fine. I did have channel changing working on both boxes before the crash. Any suggestion?
|
#2
|
|||
|
|||
You must have incorrect settings for one of the tuning devices in the sage.properties file. That is where it picks up the parameters that it sends to the channel.exe program.
__________________
New Server - Sage9 on unRAID 2xHD-PVR, HDHR for OTA Old Server - Sage7 on Win7Pro-i660CPU with 4.6TB, HD-PVR, HDHR OTA, HVR-1850 OTA Clients - 2xHD-300, 8xHD-200 Extenders, Client+2xPlaceshifter and a WHS which acts as a backup Sage server |
#3
|
|||
|
|||
Quote:
I've attached the proprieties file in case anyone wants to give it a go. Last edited by gdippel; 11-11-2017 at 04:05 PM. |
#4
|
|||
|
|||
Is it possible that you have a typo in one of the device line names - one of these two lines:
mmc/encoders/-1674637831/90/0/device_name=7ea6afd71b00 mmc/encoders/-431556906/90/0/device_name=164b42d45ff4 And what is your setting for the registry entry for exemultituner?
__________________
New Server - Sage9 on unRAID 2xHD-PVR, HDHR for OTA Old Server - Sage7 on Win7Pro-i660CPU with 4.6TB, HD-PVR, HDHR OTA, HVR-1850 OTA Clients - 2xHD-300, 8xHD-200 Extenders, Client+2xPlaceshifter and a WHS which acts as a backup Sage server |
#5
|
|||
|
|||
Quote:
This is my registry entry: C:\Firewire\channelw.exe -f -a0 -n %DEVICE% %CHANNEL% Same result using tuning panel numbers (without the -n flag) The above encoder names work from the command line. |
#6
|
|||
|
|||
Solved
I finally was able to get firewire channel changing to work on both of my stbs using FWChannelProxy in lieu of EXEMultituner. As I could change channels from the command line it obviously was a mis-configuration in the Sage properties file. In my case it was just easier to track it down using FWChannelProxy.
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Firewire Set Top Box channel tuning, circa June 2011 | stevech | Hardware Support | 16 | 07-03-2014 06:07 AM |
Hep with Firewire tuning on SA4250's and 2 Colossususususuuses | btrcp2000 | Hardware Support | 1 | 04-07-2014 09:51 AM |
Problem with firewire tuning | Muchacho | Hardware Support | 2 | 03-24-2014 07:01 PM |
Firewire tuning and 64 bit OS | UgaData | Hardware Support | 3 | 11-13-2009 12:51 PM |
SA4250 and Firewire tuning? | pat_smith1969 | Hardware Support | 1 | 07-12-2008 11:12 AM |