Android/AndroidTV Placeshifter client (Discussion)

[Fuzzy]

Originally Posted by tvmaster2

Hi. Can this be used for remote access testing purposes, for example from a dns server

PS admin please delete double entry sorry

I have not been able to connect remotely yet. Guessing there is something the server is sending differently for a remote connection as opposed to a local IP, and it crashes out immediately on connection. Haven't looked any further into it yet, as he's busy working on the rendering aspects of it.

[tvmaster2]

Ok, good to know. Thanks

[jm9843]

For those of you considering which Android TV device to pickup, the details of the promised Shield update have been revealed. Coming tomorrow, it's a big one.

Do note that the table will be incorrect after the Nexus Player receives the Marshmallow update which enables MPEG2.

Shield Android TV OTA 2.0

[PLUCKYHD]

Dang those are nice specs especially the audio passthrough...

[stuckless]

That is pretty impressive... but in Canada, by the time I add in Shipping (and possibly taxes)... that's a $300 extender... that's a little rich for my blood

[cgruelle]

The table above lists that the Nexus Player does not support MPEG2. I know that it does in Android M Preview 3. I've been using one for several months with a HDHomerun, and as a frontend for MythTV. The HDHomerun View app / Live Channels app doesn't do the best job at deinterlacing though. However, Kodi with the MythPVR addon has been working great.

[PLUCKYHD]

Originally Posted by stuckless

That is pretty impressive... but in Canada, by the time I add in Shipping (and possibly taxes)... that's a $300 extender... that's a little rich for my blood

you need richer blood lol jk totally understand.

[tmiranda]

Originally Posted by stuckless

That is pretty impressive... but in Canada, by the time I add in Shipping (and possibly taxes)... that's a $300 extender... that's a little rich for my blood

I'm happy with the $49 Nexus

[FreshOne]

Originally Posted by jm9843;577949[URL="http://nvidiashieldzone.com/index.php/shield-android-tv-ota-2-0/"

Shield Android TV OTA 2.0[/URL]

And they also added:

• MPEG2, VC-1, and WMV9 hardware-acceleration

• M2TS, ASF, and WMV container support for VC-1

• WMA audio support (including WMA Pro, and WMA Lossless)

I am seriously thinking of getting one, seeing how they came through on the promised upgrades.

[ranger]

Originally Posted by FreshOne

And they also added:

Just for clarity does "they" refer to nVidia?

[SHS]

Guest what Google Pixel C is packing a Nvidia's Tegra X1

[dinki]

Just an update, v0.3 works great on my FireTV Stick. I only have an HD200 to compare it to but aside from minor differences in fonts and some color/shading differences in the program guide, it is definitely on par performance wise as the HD200. Incredible!

The lack of buttons on the FTV remote does make things a bit more challenging.

[FreshOne]

Originally Posted by ranger

Just for clarity does "they" refer to nVidia?

Yes

[Galaxysurfer]

On a side note this is what is coming to next roku not sure if and/or how this fits into the sagetv world

http://cordcutting.com/roku-4-specs-leaked/

[tvmaster2]

getting a lot of "unfortunately SageTV mini client has stopped".
when I can get the app to open, I don't remember if I ever got a video to play.
anyone else?
Galaxy S5, Lollipop...

[Fuzzy]

Originally Posted by tvmaster2

getting a lot of "unfortunately SageTV mini client has stopped".
when I can get the app to open, I don't remember if I ever got a video to play.
anyone else?
Galaxy S5, Lollipop...

Playback is not implemented. So far he's just got the UI rendering, and some rudimentary control inputs.

[stuckless]

Originally Posted by tvmaster2

getting a lot of "unfortunately SageTV mini client has stopped".
when I can get the app to open, I don't remember if I ever got a video to play.
anyone else?
Galaxy S5, Lollipop...

Originally Posted by Fuzzy

Playback is not implemented. So far he's just got the UI rendering, and some rudimentary control inputs.

I've updated the first POST to make it clearer as to what is working and not working. This is a long haul project, it will be months before it is completed. Video playback is especially challenging, but it is being worked on. To date, I have yet to get a video to play, but the infrastructure parts are coming together. This morning, and tomorrow morning is my window to work on this, so hopefully I make some good progress.

[tvmaster2]

Originally Posted by stuckless

I've updated the first POST to make it clearer as to what is working and not working. This is a long haul project, it will be months before it is completed. Video playback is especially challenging, but it is being worked on. To date, I have yet to get a video to play, but the infrastructure parts are coming together. This morning, and tomorrow morning is my window to work on this, so hopefully I make some good progress.

ok, thanks for clarifying...sorry I missed that. It looks fantastic, just the sight of our extenders on a portable, remote device

[stuckless]

Just wanted to give an update on the state of video playback. To date, I have not been able to get a video a to play, but I do have much of the communication code written that is responsible for initiating the playback and reading video chunks.

I discovered to my surprise that the HDPVR .ts files that are produced for my recordings do not play, as is, on my device. This is odd, since they are h264 encoded files, but the player doesn't like the ts stream. Also when I have sagetv transcode to mp4, on the fly, the format that it produces, results in a player error on the android device, with a cryptic message like "profile 4 not supported".

Despite this, I think there is still some good progress happening... It's just taking time

[tmiranda]

Originally Posted by stuckless

Just wanted to give an update on the state of video playback. To date, I have not been able to get a video a to play, but I do have much of the communication code written that is responsible for initiating the playback and reading video chunks.

I discovered to my surprise that the HDPVR .ts files that are produced for my recordings do not play, as is, on my device. This is odd, since they are h264 encoded files, but the player doesn't like the ts stream. Also when I have sagetv transcode to mp4, on the fly, the format that it produces, results in a player error on the android device, with a cryptic message like "profile 4 not supported".

Despite this, I think there is still some good progress happening... It's just taking time

Thanks again for taking this on Sean.

h264 compression is a generic term. There are many h264 "profiles" that specify the specifics of how the video is compressed.