Linux 64bit MiniClient (issues with mplayer)

[stuckless]

Originally Posted by Narflex

Yeah, that's not used anymore. That was from before we had the more advanced text system....I also thought at one point it was a better way to do things. But then I found too many problems with having the server calculate text positions/size/bounds using the font logic it had...and then expecting that to match on the client. Too many times it was off by a few pixels and things were getting chopped. It is possible to make it still use the DRAWTEXT command by having the GFX_TEXTMODE property return something besides an empty string or 'None'. But I wouldn't recommend doing that.

That is very cool... So, basically, DRAWTEXT is optional (which is good, since drawing text on opengl is hard ) (I just commented out DRAWTEXT in my GFXCMD and to my surprise, I still saw all the text.. this is awesome!)

Originally Posted by Narflex

Remember the Java code will be of no use on iOS...it'll have to be rewritten in Objective C for that platform.

Oh Jeff... You need to keep in touch with mobile technology There is a great little thing called RoboVM that converts Java Bytecode to native ios (AOT compiling). In fact, I used this to create a game, 100% in java, using opengl, and it runs on both iOS and Android

https://play.google.com/store/apps/d...es.rgb.android

http://robovm.com/

RoboVM's performance is better than ARC, and Swift on iOS.
https://medium.com/@harrycheung/cros...g-d0454f5cd4e9

So, if I get a "clean" opengl port working, it is very possible to run the a complete Java based Placeshifter on iOS

Now, the Video handling would have to be done natively, but, could still be done using Java for iOS, since RoboVM contains all/most of the iOS native bindings for the UI widgets.

https://github.com/robovm/robovm-sam...viePlayer.java

[jptheripper]

Originally Posted by Narflex

2. There's EM8622 conditionals in the code...that can all be removed, we'll never build for that platform again (it was the HD100)
.

Im just an observer in this thread, but still a heavy hd100 user (i have 4). Does this mean you arent planning on supporting it?

[stuckless]

Originally Posted by jptheripper

Im just an observer in this thread, but still a heavy hd100 user (i have 4). Does this mean you arent planning on supporting it?

Basically, as it stands we can never replicate a build for any of the Extenders (100,200, or 300). The code that can be released, was released, but we can never build a complete firmware replacement for any of the extenders.

The extenders are still supported in that they will still connect and work with the open source sagetv server. That shouldn't change.

Moving forward, we will need to build new hardware extenders, or more likely, use existing players like AndroidTV, AppletTV (new one that supports apps), Roku, etc.

[stanger89]

Originally Posted by stuckless

Basically, as it stands we can never replicate a build for any of the Extenders (100,200, or 300). The code that can be released, was released, but we can never build a complete firmware replacement for any of the extenders.

The extenders are still supported in that they will still connect and work with the open source sagetv server. That shouldn't change.

Moving forward, we will need to build new hardware extenders, or more likely, use existing players like AndroidTV, AppletTV (new one that supports apps), Roku, etc.

To put it another way:

Extenders will continue to work.

There will "never" be a new firmware/software update for the extenders.

[Narflex]

@stuckless Oh yeah....I guess I had forgotten that Apple lifted the ban on requiring people to write in Objective C that they had awhile back.

[Galaxysurfer]

There will "never" be a new firmware/software update for the extenders

so where does this leave extender status to use with opensource sagetv once supply of sagetv branded extenders is exhausted? it is my understanding that the hauppauge media extender only allows media to be played from server on tvs but doesnt have interactive guide capability. I have a license for sagetv server but no media extenders. I would like to add extenders that can give me the sagetv interactive guide on tvs attached to them. What are my options going forward if sagetv media extenders are all sold out?

galaxysurfer

[Monedeath]

Originally Posted by Galaxysurfer

There will "never" be a new firmware/software update for the extenders

so where does this leave extender status to use with opensource sagetv once supply of sagetv branded extenders is exhausted? it is my understanding that the hauppauge media extender only allows media to be played from server on tvs but doesnt have interactive guide capability. I have a license for sagetv server but no media extenders. I would like to add extenders that can give me the sagetv interactive guide on tvs attached to them. What are my options going forward if sagetv media extenders are all sold out?

Either building a htpc capable of running the SageTV client software (which no longer requires a license in the OS version)

Or waiting for efforts to create a miniclient capable of running on Android and/or iOS to come to fruition if you're not otherwise involved in them.

[stanger89]

Originally Posted by Galaxysurfer

There will "never" be a new firmware/software update for the extenders

so where does this leave extender status to use with opensource sagetv once supply of sagetv branded extenders is exhausted?

I think you're misunderstanding. Just because there will never be updated firmware for the SageTV extenders (HD300, HD200, etc), does not mean there won't be new "extenders". Sage being Open Source means anyone can use the miniclient (extender) protocol to build an extender out of anything they want.

There's already good work going on on an android client, I would think a Raspberry Pi (2) would not be too hard. Who knows what else people will build.

The issue with the current extenders is twofold, for one they use licensed code that (I assume) was not open sourced, and the miniclient code was upgraded beyond their capabilities, so we won't be able to add new features or bug fixes specifically for the HDx00 miniclients.

[Monedeath]

Well, there also is the point that Jeff is going to try keep SAGETV backwards compatible with the legacy extenders for as long as possible. Considering some of them first entered service over 10 years ago, and still receive support. I don't think the extenders are likely to become paperweights due to software changes anytime soon.

The only downside is knowing that the capabilities they have now are the only ones they're going to have without needing the server to work magic for them.

[Monedeath]

Originally Posted by stanger89

The issue with the current extenders is twofold, for one they use licensed code that (I assume) was not open sourced, and the miniclient code was upgraded beyond their capabilities, so we won't be able to add new features or bug fixes specifically for the HDx00 miniclients.

Not exactly accurate, if someone is determined enough, they probably could. It would either involve implementing it server-side and passing it down-stream to the client, or bribing Narflex and Company to make a direct change depending on the nature of the change.

The extenders have proprietary code attached to them which prevents the Open Source side of things from making changes to them directly, but that doesn't mean changes can't be made. They're just very unlikely to occur due to effort required and the limited number of people able to implement, so it is better to not expect any updates on that front.

[Galaxysurfer]

Reading your latest input in this thread sort of gets into what i want to achieve. Basically use alternative extender/client rather than sagetv media extenders that we cant tweak or build more of anyways. I am attempting address the issue of extender hardware failure. I would like the flexibility to deal with extenders/clients the same way we can deal with servers on the hardware end.

[Nelbert]

I think it's safe to say that Sigma Design's won't release the SDK or drivers for the SMP processer in the HD300. The chip was used in multiple devices when it came out and every request for driver releases was denied at the time. While effort was made, with limited progress, when it was a relevant processor to reverse things, nobody will be interested now, especially with low cost arm/atmel based boards available.

In terms of replacing my current HD300 as much as I'd like to use something like the HardKernel C1+ or other low powered, tiny, fanless arm board, they all have short comings compared to a HD300. Whether it's Linux driver availability, unable to bitstream/decode HD audio, broken frame rate switching, the promise of full hardware device support which never actually appears, the list goes on.

I should probably caveat this with the info that I'm a European user and also have no interest in an Android(TV)/iOS/HDHomeRun devices. I'm more interested in support for DiseqC 1.2 (Sat motor), SatIP and running on a tiny, fanless, low power box.

I'm waiting on availability for one of two options at the moment, either the upcoming Minnowboard Turbot or the upcoming Wetek Core device. The Minnowboard because it's a fanless x86-64 based board and the Wetek because it's a full packaged system with active Wetek backed Linux/OpenElec support. A big question mark for me about the Wetek is the status of it's HD Audio support and how easily Sage will cross compile.

Depending on the OpenGL routines used it could be harder to get Sage running on something like the Wetek Core even though it's processor is designed for IPTV/OTT/DVB devices, as it's an Amlogic 812 chip not x86, but with the latest version of JOGL supporting OpenGL ES 3.1 it might have minimal changes required. A quick look suggests the OpenGL code is more likely to suffer deprecated/unsupported functions for recent OpenGL/ES versions, eg gl.quad not being supported, more than anything else.

I'm hoping it should be possible to use at least one of the devices as a dedicated Sage device, ie boot Linux straight into Sage and still keep hardware video decoding and HD bitstreaming. The MinnowBoard Turbot will probably be the simplest as it's a 2GB Dual Core Intel Atom E3826 with Intel HD graphics so should run a normal x32/64 build of the Sage software.

[Narflex]

Just a reminder...there are HD300 devices still for sale...check the Announcements forum.

[tmiranda]

Originally Posted by Narflex

Just a reminder...there are HD300 devices still for sale...check the Announcements forum.

Still the best extender available