Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Sage Media Server driver (beta)
#41
Fonceur Wrote:Version .90 (and up) now requires CQC beta 2.4.40 and up...

Can the first post be updated with the latest installation information? This fact was killing me because the SagePlayer loaded just fine, but the Media Server was failing to initialize.

I don't mind writing up a quick "how to" if you want Foceur and you could simply copy it into the first post.
Brian

"Really dear, it was too good of a deal to pass up. Besides, look at what it does now...."
I think my wife is getting a little tired of hearing this :-)
Reply
#42
OK, I slightly updated the first post, see if that's enough...
Field Generator 0.65: Create CQC fields on the fly, from external applications.
Mobile templates 0.4: Main resolution of 320x480 with navigation side bars (384x544).
Sage Media Server 1.1.3 + Sage Player 2.7.8: Display and manipulate SageTV information or player.
TaRIVA 1.26: Android RIVA client.
Reply
#43
I decided to write a quick "How To" install this driver. I don't mean to offend either Beelzerob or Fonceur, but with several threads and directions spread out in all of them, I wanted to bring it all back to one spot.

Check your CQC version
Version .90 of the Sage driver (and up) now requires CQC beta 2.4.40 and up. So make sure you have a high enough CQC version to make everything work.

Install Needed Software (other than CQC Driverpacks)
First, there are several things that must be installed on the computer running the SageTV Software in order for the CQC driver to work (in addition to the CQC driver packs). So let's start with GKusnick's Studio Tools. Just download the zip file from the Sage site and all you have to do is extract the zip file components into the C:\Program Files\SageTV\SageTV folder. This will create a new gkusnick.sagetv folder and create a new .jar file in the jar folder.

Second, download the SageTCPServer-vXXX.zip file from the 1st post in this thread. It only has one file, the SageTCPServer.jar file. Simply extract this file into the C:\Program Files\SageTV\SageTV\JARs folder.

Modify Sage.Properties File
Now we are ready to modify the Sage.properties file. This is also located on the computer running the SageTV software in the C:\Program Files\SageTV\SageTV folder. Look for a file called "Sage" since the .properties portion of the name will probably be hidden unless you have the "View Extentions" option turned on. Make sure the SageTV software is not open/running and the SageTV Service is turned off before modifying the file. If the Sage service is left running, you will be able to open and edit the file just fine, but the changes will not be saved.

Here are the modifications that need to be made to the Sage.Properties file:
1. add the line: load_at_startup_runnable_classes=sagetcpserver.StartServers
Note that the line: load_at_startup_runnable_classes= may already exist. If it does, than just add the value to the end of this line
If anything already exists in this line, separate each item with a semicolon ';'
Note that this is case-sensitive and there must be no spaces at all in this line.

2. add the line: sageTCPServer/clients=<client1MACID>.<port>,<client2MACID>.<port >, etc, etc, etc

<clientMACID> = The MAC address of the client you want to control Sage on. This client could be a placeshifter client, or an MVP, or any other client that Sage renders for. The one exception to this is if you wish to control the sage client on the PC that this sage.properties file resides on, then use the name "local" instead of a MAC ID.

Note, to use the SageMediaServer driver, you'll need to have a "client" for it also. That client will always be "local". So it would look like "local.<port>"

<port> = Any valid TCP port. It doesn't matter what port number you choose, so long as it's un-used. Remember this port number, as you'll need to add it when you go through the CQC manifest when installing the driver.

Here is an example of how the line might look if you wanted to install the SageMediaServer on the machine that is running the SageTV software and 1 client/extender.
Example: sageTCPServer/clients=local.9750,01e04cd32eda.9100
The SageMediaServer uses the address of local since it is running on the same machine as the SageTV software and will use port 9750. The client/extender is a separate device with a MAC address of 01e04cd32eda and will use port number 9100.

Here is an example of how the line might look if you wanted to install the SageMediaServer on the machine that is running the SageTV software and 2 client/extenders (one on the same machine as the SageTV software and one separate device)
Example: sageTCPServer/clients=local.9750,01e04cd32eda.9100,local.9101
The SageMediaServer uses the address of local since it is running on the same machine as the SageTV software and will use port 9750. The first client/extender is a separate device with a MAC address of 01e04cd32eda and will use port number 9100. The second client is running of the same machine as the SageTV software, so it uses the local address as well, and will use port 9101.


3. add the line: sageTCPServer/debugOn=false
This value is just what it says, for debugging only. If things are working well, feel free to keep this to false. However, if things go bad and I ask for the sage log, then set this to true and restart sage to reproduce the problem, and then send me the logfile. To get Sage to start logging in general, you'll also need the line: debug_logging=TRUE in the file. This make Sage output debug messages into to a file. Then modify the line: sageTCPServer/debugOn=True which makes sure any debug messages related to the SageTCPServer jar are included in the debug file. The file will have the name "tv0" and it will be located in the SageTV folder I believe.

Other useful info:
1) To enable the console window, define the following value under HKEY_LOCAL_MACHINE\SOFTWARE\Frey Technologies\Common:
consolewin REG_DWORD 1

Install CQC Drivers
Download the driverpacks (x2), the XML macropack, and Sage Channel template pack from the first post and use the Admin Interface to install them all.

Use the Admin Interface to load the drivers. The SageMediaServer driver has many fields related to the core SageTV software. Things like "upcoming recordings", "recent recordings", "TV channels", etc, etc. You will only need one SageMediaServer driver per system. The SagePlayer driver is used to control a specific client or extender. You will want to install one SagePlayer driver per client/extender that you wish to control. If you have two extenders then you will install two SagePlayer drivers. It is not required that you load both types of drivers (SageMediaServer and SagePlayer), but most people will probably want to install both types to insure they have access to all the potential driver fields.

When installing the drivers, it will ask you for the IP address and port number. The IP address requested is the address of the computer running the SageTV software because this is where the java code is executing. Do not use the IP address of each client. However, you do use the unique port number that you used in the sage.properties file for each device. So every driver you install will have the same IP address, but a different port number.

For example, if you are running the SageTV Software on a computer with the IP address 192.168.1.10 and the Sage.properties file was modified to include this line: "sageTCPServer/clients=local.9750,01e04cd32eda.9100,local.9101" , when you go to install the three separate sage drivers, you would use the IP address 192.168.1.10 and port 9750 for the SageMediaServer driver, address 192.168.1.10 and port 9100 for the first SagePlayer driver, and address 192.168.1.10 and port 9101 for the second SagePlayer Driver.

Conclusions
Hopefully everything is up and running and connected! If you feel empowered now, you might want to install the Sage Information Popup driver. This will allow you to cause a custom message to popup on a client or extender.
Brian

"Really dear, it was too good of a deal to pass up. Besides, look at what it does now...."
I think my wife is getting a little tired of hearing this :-)
Reply
#44
No offense at all...in fact, I was going to suggest it. "How-to"'s are usually written best by those trying to figure it out on their own, as they'll find all the little details that the experienced people tend to overlook.

I'd suggest moving/copying it to the How-to forum, as it'll just quickly again get buried here, I think...and hopefully the How-To will remain mostly accurate.
Reply
#45
Quote:Version .90 of the Sage driver (and up) now requires CQC beta 2.4.40 and up. So make sure you have a high enough CQC version to make everything work.

At this point, anyone on any of the beta versions should be moving up to the latest. Speak now or live with the bugs.
Dean Roddey
Explorans limites defectum
Reply
#46
I upgraded to the new version of CQC and this new media driver and I am getting connection errors however when I read the logs it looks like it is passing messages to the server. My clients connect fine, just the server is failing.

I believe I installed all the new TCP drivers, made sure GKusnick tools were latest, the xml driver etc.. The only thing I didnt install was the files in sage_channels.zip. Is that now a required file?

These are the only errors I see in the log but in CQC I basically see driver toggling from waiting for resources and connecting.

Is the sage_channels.zip the likely cause of this? I have a zip of my log file but it is too big to host here, I can post it somewhere if needed.

Fri 6/12 7:40:53.600 [[SageCQC-SageServer(001e40b5a028)]]: Connected to client, waiting for messages...
Fri 6/12 7:40:53.848 [[SageTCPServer-SageServer(001d6a4cf691:5010)]]: There is 1 message to be sent.
Fri 6/12 7:40:53.850 [[SageTCPServer-SageServer(001d6a4cf691:5010)]]: Sending data: VER:1.0.0 (beta 273)
Fri 6/12 7:40:53.899 [[SageTCPServer-SageServer(001d6a4bff78:5009)]]: There is 1 message to be sent.
Fri 6/12 7:40:53.900 [[SageTCPServer-SageServer(001d6a4bff78:5009)]]: Sending data: VER:1.0.0 (beta 273)
Fri 6/12 7:40:54.106 [[SageCQC-SageServer(001e40b5a028)]]: EXCEPTION java.lang.NoSuchMethodError: gkusnick.sagetv.api.AiringAPI$List.SortLexical(ZLjava/lang/StringWinkLgkusnick/sagetv/api/AiringAPI$List; AT sagecqc.SageServer.getUpcomingRecordingsList(SageServer.java:563)

Fri 6/12 7:40:54.107 sagecqc.SageServer.getOutgoingData(SageServer.java:686)

Fri 6/12 7:40:54.107 sagecqc.SageServer.run(SageServer.java:126)

Fri 6/12 7:40:55.354 [[SageTCPServer-MessageType]]: Found match with MOD

------------------

Fri 6/12 7:45:54.644 [[SageTCPServer-SageServer(local:5008)]]: Message received: ACH
Fri 6/12 7:45:54.645 [[SageTCPServer-SageServer(local:5008)]]: Now 1 incoming message(s) in list.
Fri 6/12 7:45:54.646 [[SageTCPServer-SageServer(local:5008)]]: (Processing messages) There is now 1 incoming message.
Fri 6/12 7:45:54.647 [[SageTCPServer-SageServer(local:5008)]]: The following UI context are available:
Fri 6/12 7:45:54.647 [[SageTCPServer-SageServer(local:5008)]]: (Processing messages) ACH
Fri 6/12 7:45:54.648 [[SageTCPServer-SageServer(local:5008)]]: Finding all the channels for lineup: DIRECTV New York - New York.
Fri 6/12 7:45:54.783 [[SageCQC-SageServer(001e40b5a028)]]: EXCEPTION java.lang.NoSuchMethodError: gkusnick.sagetv.api.AiringAPI$List.SortLexical(ZLjava/lang/StringWinkLgkusnick/sagetv/api/AiringAPI$List; AT sagecqc.SageServer.getUpcomingRecordingsList(SageServer.java:563)


----------
Rich
Reply
#47
personalt Wrote:Fri 6/12 7:45:54.783 [[SageCQC-SageServer(001e40b5a028)]]: EXCEPTION java.lang.NoSuchMethodError: gkusnick.sagetv.api.AiringAPI$List.SortLexical(ZLjava/lang/StringWinkLgkusnick/sagetv/api/AiringAPI$List; AT sagecqc.SageServer.getUpcomingRecordingsList(SageServer.java:563)
That is due to a mismatched version of the studio tools (gkusnick), most likely your version is too old, or the latest version has broken something...
Field Generator 0.65: Create CQC fields on the fly, from external applications.
Mobile templates 0.4: Main resolution of 320x480 with navigation side bars (384x544).
Sage Media Server 1.1.3 + Sage Player 2.7.8: Display and manipulate SageTV information or player.
TaRIVA 1.26: Android RIVA client.
Reply
#48
I downloaded what I thought was the latest version of the studio tools. I extracted the files into the sage folder and restarted the whole box.

Hmm.. is this the home of the latest version?
http://forums.sagetv.com/forums/download...ile&id=128

Looks like version .72
Rich
Reply
#49
Version .72 of GKusnick's Studio Tools is the latest. In fact it was added just a week or so ago.

I just checked my version and I think I have version .71. So if you did install version .72 maybe something has changed in it that is causeing the error.
Brian

"Really dear, it was too good of a deal to pass up. Besides, look at what it does now...."
I think my wife is getting a little tired of hearing this :-)
Reply
#50
personalt Wrote:Looks like version .72
I've just installed version .72, and it works fine. Make sure it's not your browser caching the older file or something (I hate when people don't put the version number in the filename)... The folder SageTV\SageTV\Jars\ should contain the file gkusnick.sagetv.jar and be dated from June 9th 2009... Make sure to restart SageTV and/or it's service...
Field Generator 0.65: Create CQC fields on the fly, from external applications.
Mobile templates 0.4: Main resolution of 320x480 with navigation side bars (384x544).
Sage Media Server 1.1.3 + Sage Player 2.7.8: Display and manipulate SageTV information or player.
TaRIVA 1.26: Android RIVA client.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  New Driver - How hard would this be? kblagron 4 503 05-20-2019, 11:28 AM
Last Post: zaccari
  Cytech Comfort Driver znelbok 6 471 04-10-2019, 05:39 PM
Last Post: znelbok
  OpenHAB Driver whozeawhat 6 2,313 01-16-2019, 06:45 AM
Last Post: greymatter
  LIFX Driver bobskie708 14 3,902 01-10-2019, 06:36 PM
Last Post: Dean Roddey
  XBMC Driver wuench 428 185,581 12-28-2018, 11:07 AM
Last Post: dogman
  Amazon Echo Hue Simulator Driver wuench 117 49,645 12-24-2018, 11:10 AM
Last Post: Dean Roddey
  RunTimer2 driver rbroders 15 5,580 12-14-2018, 05:28 PM
Last Post: rbroders
  Driver for Bigass Fan lleo 7 922 11-25-2018, 08:57 AM
Last Post: Dean Roddey
  Generic Modbus Driver - Serial & IP znelbok 25 14,509 10-09-2018, 08:59 AM
Last Post: Ron Haley
  Issues debugging IP based driver jnolting 5 1,267 09-24-2018, 11:52 AM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 2 Guest(s)