SageTV Community  

Go Back   SageTV Community > SageTV Development and Customizations > SageTV Clients Development

Notices

SageTV Clients Development This forum is for discussions relating to SageTV Open Source Clients Development.

Reply
 
Thread Tools Search this Thread Display Modes
  #841  
Old 07-03-2019, 02:01 PM
Zogg Zogg is offline
Sage Advanced User
 
Join Date: May 2011
Location: Frisco, TX
Posts: 123
Quote:
Originally Posted by jpwegas View Post
Did you mean "Client" or miniclient here? As the only "full" capital "C" Client is the one on Windows.

If you really were asking about porting the full Client to something other than Intel on Windows - I was curious about the possible options as well and asked here about it but got no responses yet.

--John
I meant the Linux client, but I don't know if it's a "mini" or not. My guess is that the Android miniclient is too tied to the Android platform, so the Linux client would be a better starting point. And then if the result for RPi is a new miniclient that's fine too.

Unfortunately my coding skills are way too out of date or I'd look at it myself. I can futz around with things, but this would be way out of my league.
Reply With Quote
  #842  
Old 07-03-2019, 04:15 PM
Tiki's Avatar
Tiki Tiki is offline
Sage Icon
 
Join Date: Feb 2005
Location: Southwest Florida, USA
Posts: 1,801
Quote:
Originally Posted by Zogg View Post
I meant the Linux client, but I don't know if it's a "mini" or not. My guess is that the Android miniclient is too tied to the Android platform, so the Linux client would be a better starting point. And then if the result for RPi is a new miniclient that's fine too.

Unfortunately my coding skills are way too out of date or I'd look at it myself. I can futz around with things, but this would be way out of my league.
There is no full Client for Android. It uses the Placeshifter (which is a version of the Mini-Client. The HDx00 extenders are also considered MiniClients, as is the Android MiniClient. The MiniClients rely heavily on the Server to handle many tasks.

The big challenge with supporting a new platform is handling all the playback functions. The Android mini client simply embeds another player (actually two players) written by someone else. I say ďsimplyĒ but I am sure it was a lot of work to integrate them - and when there are problems with playback, itís mostly out of the Sage Developerís hands: he canít really do much to troubleshoot or fix bugs in those embedded players.
__________________
Server: Athlon II X4 630 CPU, Gigabyte MA770T-UD3P (AM3) Motherboard, VisionTek Radeon HD4670 PCIe w/ Component output to 50" CRT Rear-Projection HDTV (Mitsubishi), Win7-64Bit (Home Premium), 4GB RAM
Capture Devices (8 tuners): Colossus (x1), HD-PVR (x1), HDHR Prime (x2)
,USBUIRT (multi-zone)
Source:
Comcast Cable
Primary Client: Server Other Clients: (1) HD200, (1) HD300
Retired Equipment: MediaMVP, PVR150 (x2), PVR150MCE,
HDHR, HVR-2250
Reply With Quote
  #843  
Old 07-05-2019, 05:25 AM
stuckless's Avatar
stuckless stuckless is offline
SageTVaholic
 
Join Date: Oct 2007
Location: London, Ontario, Canada
Posts: 9,521
Getting a MiniClient to work under linux falls into 3 challenges.
1. Getting the UI to render
2. Handling input from a a remote
3. Playing video

The good news is that sagetv does all 3 of these under linux today, but it's not without additional challenges.

While SageTV MiniClient is primarily a Java program, it does depend on a few native libraries and those need to be recompiled for ARM chips. My guess is that getting the UI to render would be fairly easy, since jogl likely has ARM libraries.

Then you'd need to recompile libImageLoader, libjtx, libSage and libswscale for ARM.

Getting video to work would be much harder. The Linux MiniClient uses a custom version of mplayer that it runs as a slave and embeds into the opengl UI. You'd need to recompile that for ARM as well. All the sources for all these things are there in the sagetv codebase.

The Android MiniClient is a rewrite of the MiniClient, but it borrowed ALOT from the original code. The client/server communication code is pretty much lifted directly. The rest of the code is more modular in that it supports a layered approach and you can have different implementations of the UI technology, input control and video technologies. My goal was to, at some point, provide a new version of the miniclient for linux, mac, and windows. In fact in the current android miniclient project today, there is a "desktop" sub project that does everything except for playing video, because I never found a good (and easy) video playback engine. There is even a prototype webgl engine in there as well to render the sagetv UI in a browser webgl canvas.

There is a lot of potential to do some really cool stuff with the miniclient technology, but, sadly, I've been pulled away from this project for far too long, and the longer I get pulled away, the more I realize that I'm likely not coming back any time soon
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Finally, a fully functional SageTV client on android and iphone! mkanet SageTV v7 Customizations 12 01-12-2013 12:22 AM
SageTV Placeshifter for Android nyle SageTV Placeshifter 5 12-31-2011 10:40 AM
Sage should get an android client running on this Deacon Crusher Hardware Support 1 09-29-2010 11:30 AM
Android client? equalize SageTV Placeshifter 1 07-22-2010 09:37 AM


All times are GMT -6. The time now is 01:31 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Copyright 2003-2005 SageTV, LLC. All rights reserved.