exetuner plugin BROKEN

[Nate]

I upgraded to v5 and now my ExeTunerPlugin doesn't work. The source is set to use the ExeTunerPlugin to invoke the channel.exe file that changes the channel through firewire. This had been working fine before upgrade. I ran the channel.exe from the command line and it changes the channel properly. This means that Sage never executes the channel.exe. WTF!? There is not much I can do. I've been trying to fix it for hours. The EXETunerPlugin DLL is in the common folder. The sage.properties is set to use it...

mmc/encoders/1642691032/3/0/available_channels=
mmc/encoders/1642691032/3/0/brightness=135
mmc/encoders/1642691032/3/0/contrast=145
mmc/encoders/1642691032/3/0/device_name=StubDevice
mmc/encoders/1642691032/3/0/hue=129
mmc/encoders/1642691032/3/0/last_channel=1
mmc/encoders/1642691032/3/0/provider_id=2529673206405
mmc/encoders/1642691032/3/0/saturation=158
mmc/encoders/1642691032/3/0/sharpness=170
mmc/encoders/1642691032/3/0/tuning_mode=Cable
mmc/encoders/1642691032/3/0/tuning_plugin=C\:\\Apps\\SageTV\\Common\\EXETunerPlugin.dll
mmc/encoders/1642691032/3/0/tuning_plugin_port=0
mmc/encoders/1642691032/3/0/video_crossbar_index=0
mmc/encoders/1642691032/3/0/video_crossbar_type=3

The source shows EXETunerPlugin as the tuning device in the Sage UI. Ok........ why is Sage not using the EXETunerPlugin!? I removed the source and readded it. I even did a "repair" install. What am I supposed to do? How can I debug it further? AAAAAAAAAAHHHHHHHHHHHHHHHHHHHHHHHHHHH

[Nate]

Is it odd that I don't see EXETunerPlugin in the list of external tuners when adding a new source? All I see is DircTV serial control plugin. What do I have to do to get EXETunerPlugin to appear?

I tried EXEMultiTunerPlugin and had no luck with it either.

BLAH!

Please help!

[Nate]

Attached sage.properties

[Nate]

Copied Sage directories, uninstalled Sage, installed Sage, setup sources, EXETunerPlugin showed up and worked, shutdown, copied my old wiz.bin back, and I'm good now.

I am extremely frustrated with Sage however. This should have never happend and if it did, I should have been able to debug it to detemine why. Software should never just leave you in the dark. Why not have a log file or something?

[ke6guj]

Originally Posted by Nate

I am extremely frustrated with Sage however. This should have never happend and if it did, I should have been able to debug it to detemine why. Software should never just leave you in the dark. Why not have a log file or something?

From the Sage FAQ

Q: I have a problem using SageTV and was asked to enable debug logging. How do I do that?

A: There is a property file setting to enable debug logging.

Edit sage.properties and add this line:

debug_logging=TRUE

Enter the line exactly as shown above. TRUE must be in all CAPS for this property.

Before editing the properties file, make sure SageTV or the service is not running. If you edit the properties file while SageTV is running, the change will be ignored.

If you are using a client, edit sageclient.properties instead.

After this change, SageTV will create a new sagetv_0.txt and/or sagetvclient_0.txt log file each time it is run. Save those files from when a problem occurs to help track down a problem -- they can be emailed to betatest at sagetv.com

[jvfff]

I realize that this is a bit late, but I found myself in the same trap after upgrading from 6.0.17 to 6.0.19. EXETuner just stopped working. I tried searching for information and found only this thread with no real answer. After poking around a bit I did find the reason and solution for my setup and thought I'd post it here.

In my setup I use SageTV service, which requires "Allow service to interact with desktop" to be set. The setup program for the update reset this setting to its default disabled state, which caused the service to fail when trying to issue commands to change channels.

After re-enabling the option and restarting the service everything was back to normal.

Originally Posted by Nate

I upgraded to v5 and now my ExeTunerPlugin doesn't work. The source is set to use the ExeTunerPlugin to invoke the channel.exe file that changes the channel through firewire. This had been working fine before upgrade. I ran the channel.exe from the command line and it changes the channel properly. This means that Sage never executes the channel.exe. WTF!? There is not much I can do. I've been trying to fix it for hours. The EXETunerPlugin DLL is in the common folder. The sage.properties is set to use it...

mmc/encoders/1642691032/3/0/available_channels=
mmc/encoders/1642691032/3/0/brightness=135
mmc/encoders/1642691032/3/0/contrast=145
mmc/encoders/1642691032/3/0/device_name=StubDevice
mmc/encoders/1642691032/3/0/hue=129
mmc/encoders/1642691032/3/0/last_channel=1
mmc/encoders/1642691032/3/0/provider_id=2529673206405
mmc/encoders/1642691032/3/0/saturation=158
mmc/encoders/1642691032/3/0/sharpness=170
mmc/encoders/1642691032/3/0/tuning_mode=Cable
mmc/encoders/1642691032/3/0/tuning_plugin=C\:\\Apps\\SageTV\\Common\\EXETunerPlugin.dll
mmc/encoders/1642691032/3/0/tuning_plugin_port=0
mmc/encoders/1642691032/3/0/video_crossbar_index=0
mmc/encoders/1642691032/3/0/video_crossbar_type=3

The source shows EXETunerPlugin as the tuning device in the Sage UI. Ok........ why is Sage not using the EXETunerPlugin!? I removed the source and readded it. I even did a "repair" install. What am I supposed to do? How can I debug it further? AAAAAAAAAAHHHHHHHHHHHHHHHHHHHHHHHHHHH

[Nate]

Glad you got yours working. I remember my problem, man that was a PITA. I don't use the Sage service (ran into too many problems with it) so our problems had to be different.

[Doubletop]

I've just had the same problem going from V5 to V6. The upgrade didn't work so I went back to V5 now I cant see the exetunerplugin or get it to read the XMLTV plugin. I keep being asked for zip codes and get presented with US/Candian stations that are of no interest in NZ.

I have the autobackup properties file with all the necessary lines in that I have renamned but SagetV doen't appear to be reading it

Just wasting Easter trying to get it fixed. Not happy at all......................

[Nate]

Originally Posted by Nate

Copied Sage directories, uninstalled Sage, installed Sage, setup sources, EXETunerPlugin showed up and worked, shutdown, copied my old wiz.bin back, and I'm good now.

Did you try that? Make sure you keep your wiz.bin safe! You lose all shows you've watched if it gets messed up. Back it up.

[Nate]

Jesus this happened AGAIN! EXEMultiTuner stopped showing up as an option when setting up a source. BLAH!