Game streaming to other Android devices or PCs with Moonlight and GeForce Experience

Search This thread
By:
Advanced…
N

nielo360

Senior Member
Mar 5, 2011
340
38
EDIT: Ran 1st test with shield itself, Used it to play rage,borderlands as noted by the dev there is a delay with Tegra device, the d-pad on the shield did not work,
other buttons worked fine,otherwise streaming is really good. Excellent work! will run a few more tests, and test with z ultra with moga pro .. looking forward to a donate version!


EDIT2: z ultra has lot of blocks black and green etc randomly showing up, streaming is fine and smooth despite that, Moga pro HID mode right stick and dpad dont work :( :( :( only works in native shield streamer so far, ps3 controller worked except the button mapping is a little off, hope you can find they way xinput is emulated would be great:)


In the shield native streamer all or most HID controllers work fine in emulating the 360 controller, however outside that with splashop and droidmote thats not the case.

Have you implemented xinput controller support in this similar to shields? if so would any HID controller do or are you using a wired 360 controller attached to your android device?

Would be awesome if you have found a way to emulate xinput with HID controllers. Droidmote does this but it currently doesnt work with HID d-pads.

---------- Post added at 12:01 PM ---------- Previous post was at 11:29 AM ----------
sofakng said:
Where can I send you a donation?

I have an nVidia SHIELD and Nexus 7, but the only thing I don't like on the shield is the screen size so I'd LOVE to be able to play on my Nexus 7 with a 360 controller, etc so this project looks fantastic!

EDIT: Also, I'm just wondering, but how does this compare to Splashtop THD? Is it using the same NVENC and RTP methods for encoding and sending data? I am thinking about purchasing an ASUS TF701T tablet but one of the main (?) purposes would be remote streaming some games from my desktop. It's confusing that you say that Tegra chips are slower because isn't Splashtop THD (made for Tegra) extremely low latency?
Click to expand...
Click to collapse

Splastop is cpu based, that includes Splashtop THD which just has a few optimizations for tegra chipsets (which are now in splashtop personal too), This app uses gpu based encoding same as the shield and its got something to do with how nvidia has implemented their streamer with regards to tegra devices, which I guess will need to be resolved.
 
Last edited:
Streykatorato

Streykatorato

Senior Member
Mar 9, 2012
220
33
I have a Quadro 2000m in my Laptop and a Geforce 8800GT in my desktop. Is there any way i could get Geforce Experience running with streaming support on atleast one of them? I have a Nexus 7 Tegra 3. Could test it on Note 3 too! Just asking;)
I have Splashtop THD running on both devices! THD works on Note 3 btw;)
Sent from my SM-N9005 using XDA Premium 4 mobile app
 
C

cgutman

Senior Member
Aug 14, 2010
485
430
nielo360 said:
EDIT: Ran 1st test with shield itself, Used it to play rage,borderlands as noted by the dev there is a delay with Tegra device, the d-pad on the shield did not work,
other buttons worked fine,otherwise streaming is really good. Excellent work! will run a few more tests, and test with z ultra with moga pro .. looking forward to a donate version!


EDIT2: z ultra has lot of blocks black and green etc randomly showing up, streaming is fine and smooth despite that, Moga pro HID mode right stick and dpad dont work :( :( :( only works in native shield streamer so far, ps3 controller worked except the button mapping is a little off, hope you can find they way xinput is emulated would be great:)


In the shield native streamer all or most HID controllers work fine in emulating the 360 controller, however outside that with splashop and droidmote thats not the case.

Have you implemented xinput controller support in this similar to shields? if so would any HID controller do or are you using a wired 360 controller attached to your android device?

Would be awesome if you have found a way to emulate xinput with HID controllers. Droidmote does this but it currently doesnt work with HID d-pads.
Click to expand...
Click to collapse


In theory, any controller that shows up as a gamepad in Android is supported. The big issue with controller mapping on Android is that nobody actually standardizes their button and joystick mappings. For example, the Ouya controller's right stick X and Y axis are MotionEvent.AXIS_Z and AXIS_RZ, while Xbox controller is AXIS_RX and AXIS_RY. The Xbox controller uses AXIS_Z and AXIS_RZ for L2 and R2.

The controller issues just need more widespread testing since there are so many different mappings. So far the PS3 controller is the best supported (both over USB and Bluetooth). I did notice the SixAxis app has a rotated button mapping by default which may have been the issue you were seeing (PS3: X was Xbox: X, and so on).

The DPAD stuff is broken on the Xbox controller (but working on PS3) so I have something I can test with locally. I can also look at the DPAD stuff on my Shield. I'll see if I can find some documentation on the Moga Pro controller and how it is doing DPAD (possible similar to Xbox) and right stick so I can fix that for you.

The random blockiness is probably just the result of packet loss or reordering. Since UDP doesn't guarantee packet delivery or packet order but we must reassemble the H264 NALs in order, I have to drop NALs when they lose packets. I think what Nvidia is doing with Shield is keeping a packet queue of the last several packets to search when they see a packet sequence number they weren't expecting (there's some logging messages that seem to indicate this). I'll probably implement a similar solution.

EDIT: The latest APK fixes the Xbox controlller (and Shield) d-pad. I've attached it to this post. It would be great if you can test this on the Moga controller.

EDIT 2: I looked up some documentation on the Moga Pro controller and found out that they're doing some really janky stuff. The controller itself doesn't send entirely Android standard keycodes for the buttons, so the SDK defines new keycodes that replace Android's constants so the controller works as expected. The Ouya controller also does a similar thing although the button mappings are even crazier (dpad left is select, dpad right is start, L3 is L1, R3 is R1, A and U are swapped). The Ouya software itself seems to fixup these values since the values I see in Limelight on the Ouya are correct, but other Android devices see the non-fixed key mappings. In Moga's case, there's an app on the Play Store called MOGA Universal Driver which appears to do the same mapping stuff that SixAxis does for the PS3 controller. I'd imagine that using this app would fix Limelight's controller mappings.
 

Attachments

  • Limelight.apk
    545.7 KB · Views: 71
Last edited:
N

nielo360

Senior Member
Mar 5, 2011
340
38
EDIT: Moga pro, only the left stick works properly, in A mode using Moga universal driver, (the right stick up and down seemed to be mapped as triggers) A, B, X ,Y, start, select, RB , LB seem ok.
Dpad, right stick and triggers are an issue.
In A mode moga pivot app it does not work
in HID mode using Moga pivot app only left stick works properly and the rest is same as above.
if you can tell me a way I can see the keys the moga pro is using i can send you a list of which keys are mapped to which button on the device.


Im going to test this out, I do have the moga universal driver installed however it only works for me in A mode which is moga's propietery mode, this mode for some reason works perfectly with shelds native streamer. HID mode just gets detected by android itself.

The ps3 controller is supported natively on the xperia z so I havent used the sixaxxis pair tool.
 
Last edited:
C

cgutman

Senior Member
Aug 14, 2010
485
430
nielo360 said:
EDIT: Moga pro, only the left stick works properly, in A mode using Moga universal driver, (the right stick up and down seemed to mapped as triggers)
Inn A mode moga pivot app it does not work
in HID mode using Moga pivot app only left stick works properly
if you can tell me a way I can see the keys the moga pro is using i can send you a list of which keys are mapped to which button on the device.


Im going to test this out, I do have the moga universal driver installed however it only works for me in A mode which is moga's propietery mode, this mode for some reason works perfectly with shelds native streamer. HID mode just gets detected by android itself.

The ps3 controller is supported natively on the xperia z so I havent used the sixaxxis pair tool.
Click to expand...
Click to collapse

Can you list which buttons on the Moga pro are working properly? I think I know what the issue is with the right-stick and I'm trying to come up with a reasonable fix for it.
 
N

nielo360

Senior Member
Mar 5, 2011
340
38
left stick,A, B, X ,Y, start, select, RB , LB seem ok.
Dpad, right stick and triggers are an issue. the right stick up seems to be Rtrigger and down seems to Ltrigger.
 
C

cgutman

Senior Member
Aug 14, 2010
485
430
nielo360 said:
left stick,A, B, X ,Y, start, select, RB , LB seem ok.
Dpad, right stick and triggers are an issue. the right stick up seems to be Rtrigger and down seems to Ltrigger.
Click to expand...
Click to collapse

Please test dpad, right stick, and triggers on this APK.

EDIT: Sorry, I made a mistake in that APK. I've replaced the attachment with a fixed version.
 

Attachments

  • Limelight.apk
    546.1 KB · Views: 77
Last edited:
Streykatorato

Streykatorato

Senior Member
Mar 9, 2012
220
33
Streykatorato said:
I have a Quadro 2000m in my Laptop and a Geforce 8800GT in my desktop. Is there any way i could get Geforce Experience running with streaming support on atleast one of them? I have a Nexus 7 Tegra 3. Could test it on Note 3 too! Just asking;)
I have Splashtop THD running on both devices! THD works on Note 3 btw;)
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Anyone?

Sent from my SM-N9005 using XDA Premium 4 mobile app
 
N

nielo360

Senior Member
Mar 5, 2011
340
38
cgutman said:
Please test dpad, right stick, and triggers on this APK.

EDIT: Sorry, I made a mistake in that APK. I've replaced the attachment with a fixed version.
Click to expand...
Click to collapse

BRILLIANT!! youv done it, Moga pro on HID Mode works perfectly! could you give some details on how you mapped these buttons it would be a great help with droidmote, or perhaps a way to use our controllers as windows controllers using this method.
only some minor issue with the deadzone being a bit too much for the sticks otherwise its perfect. (this might be input latency ill check with the ps3 controller later.)

also how do i donate?
 
Last edited:
C

cgutman

Senior Member
Aug 14, 2010
485
430
nielo360 said:
BRILLIANT!! youv done it, Moga pro on HID Mode works perfectly! could you give some details on how you mapped these buttons it would be a great help with droidmote, or perhaps a way to use our controllers as windows controllers using this method.
only some minor issue with the deadzone being a bit too much for the sticks otherwise its perfect. (this might be input latency ill check with the ps3 controller later.)

also how do i donate?
Click to expand...
Click to collapse

Glad to hear it's working. The documentation on Moga using the native Android API was pretty sparse.

The left stick is AXIS_X and AXIS_Y which is the same as pretty much all controllers. The right stick is AXIS_Z and AXIS_RZ which seems to be pretty standard for Android too (although Xbox uses AXIS_RX and AXIS_RY instead).

The D-pad shows up as AXIS_HAT_X and AXIS_HAT_Y (like the Xbox controller).

The very odd one was the triggers. Unlike Ouya which used AXIS_LTRIGGER and AXIS_RTRIGGER, the triggers on the Moga are mapped as AXIS_BRAKE and AXIS_GAS. I got the idea for trying this from another thread about the Moga Pro: http://xdaforums.com/showpost.php?p=44865063&postcount=9

If you want to check out the code, it's in Game.onGenericMotionEvent(). https://github.com/cgutman/limeligh...39f606c0246d/src/com/limelight/Game.java#L364

I'm not sure about taking donations yet but I'll update you guys when I figure things out.
 
L

LVNeptune8

Member
Aug 3, 2010
41
4
cgutman said:
Audio is here with the latest code! Turns out that audio was coming in over UDP port 48000. I wrote a JNI binding for the Opus reference decoder and fed the data to the AudioTrack class.


I've attached an APK that you can use for testing to this post.


It should work fine with the attached APK since that phone has a Snapdragon 800 which plays nice with our H264 stream.



Sure, ideas for the new location?
Click to expand...
Click to collapse

No clue...I dig what ya'll are doing it's just not Shield related...
 
Y

yousirname1

Member
Jul 1, 2013
16
5
Just tried this on my S4 and I'm blown away by the proof of concept. Sure, the streaming is still pretty bad (could be my end: g router), but it's quite amazing how it functions like a shield. Geforce Experience compatible games are automatically changed in the settings to match the streaming resolution and once streaming ceases, they're changed back. I had a little trouble at first, but after forwarding all the correct ports I got both the streaming and xbox controller input to work. This is fantastic work and I cannot express how excited I am to see this IN MY HANDS!
 
R

raufemann

Member
Nov 14, 2013
9
1
There is something to do on PC?...

...to get Limelight working? I am typing the IP and clicking on pair button and start streaming but nothing happens, just black screen and timeout connection, I have GFE 1.7.1 and nvstream and nvserver working but can't stream, I am trying this on my Shield because I have a Clevo with 680m (optimus) and nvidia don't support streaming from mobile GPU at the moment (and I guess they never will).

Thanks in advance and sorry because my english speak is limited.
 
Last edited:
  • Like
Reactions: danielb7390
A

Aaronneyer

Senior Member
Sep 4, 2010
56
7
raufemann said:
...to get Limelight working? I am typing the IP and clicking on pair button and start streaming but nothing happens, just black screen and timeout connection, I have GFE 1.7.1 and nvstream and nvserver working but can't stream, I am trying this on my Shield because I have a Clevo with 680m (optimus) and nvidia don't support streaming from mobile GPU at the moment (and I guess they never will).

Thanks in advance and sorry because my english speak is limited.
Click to expand...
Click to collapse

If you have a Kepler based mobile GPU, you could try this: http://xdaforums.com/showthread.php?t=2394478

EDIT: Actually I guess that doesn't work for Optimus
 
Last edited:
R

raufemann

Member
Nov 14, 2013
9
1
danielb7390 said:
If shiled doesn't work this won't work either. It uses the same technology. You have mobile gpu witch are NOT supported
Click to expand...
Click to collapse

Thanks.

---------- Post added at 03:24 PM ---------- Previous post was at 03:15 PM ----------
Aaronneyer said:
If you have a Kepler based mobile GPU, you could try this: http://xdaforums.com/showthread.php?t=2394478

EDIT: Actually I guess that doesn't work for Optimus
Click to expand...
Click to collapse

Thanks, I tried that but no luck.

Splashtop THD work fine with windowed (splashtop don't support direct access) mode but controls are bad.

My hope was Limelight but like said before it don't support too because it is using the same stream method.

Optimus is a bless to the battery but a pain in the &@$& with other purposes like that and I think Nvidia isn't care about mobile Kepler devices or this Optimus **** and the laptop bios are the rock on the road to make gamestream work on mGPU.

Thanks again to everybody.
 
simpelsense

simpelsense

Senior Member
Apr 23, 2010
97
20
thank you very much for your effort to bring us the gamestreaming over to other devices.

my finger was already hovering over the purchase button for a shield and a nvidia card. was still undecided. now i orderd only the card :p
keep up the good work, i will test as soon as my nvidia card arrives.

if you add a possibility for donation, you have allready earned a beer.
 
N

nielo360

Senior Member
Mar 5, 2011
340
38
raufemann said:
Thanks.

---------- Post added at 03:24 PM ---------- Previous post was at 03:15 PM ----------



Thanks, I tried that but no luck.

Splashtop THD work fine with windowed (splashtop don't support direct access) mode but controls are bad.

My hope was Limelight but like said before it don't support too because it is using the same stream method.

Optimus is a bless to the battery but a pain in the &@$& with other purposes like that and I think Nvidia isn't care about mobile Kepler devices or this Optimus **** and the laptop bios are the rock on the road to make gamestream work on mGPU.

Thanks again to everybody.
Click to expand...
Click to collapse

wrong. controls are the same as 360 controller and it is fullscreen.
http://xdaforums.com/showthread.php?t=2506438
 
You must log in or register to reply here.

Similar threads

Kwongger
[Root Guide] SHIELD and SHIELD Tablet, Root and Custom Recovery NO Unlock! NO PC!
Replies
25
Views
78K
scouse83
scouse83
C
[HOWTO] Shield streaming remotely without a VPN
Replies
56
Views
46K
R
rcistano
shimp208
[HOW-TO]Unlock the Bootloader on the Nvidia Shield
Replies
27
Views
108K
Hitti2
Hitti2
C
A quest to stream from mobile Kepler
Replies
253
Views
96K
D
dissidius
L1qu1d
Dreamcast (Reicast) Compatibility List/Troubleshooting (MAR 12 2014) *ALL DEVICES
Replies
223
Views
178K
P
pollet82

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 106
    C
    cgutman
    Please don't ask for Moonlight help on Nvidia's forums! It's not their responsibility to support this app. Ask on this forum, another non-Nvidia forum, by email, etc

    What happened to Limelight?/Why did you change your name?
    On April 21, 2015, we received a Cease and Desist letter from Limelight Networks, Inc. They also do streaming services and were concerned about confusion between this project and their company trademarks. To comply with the terms of their C&D, we've decided to rename our project to Moonlight.

    Quick Links
    Main website: https://moonlight-stream.org
    Help: https://github.com/moonlight-stream/moonlight-docs/wiki/Setup-Guide
    Discord: https://moonlight-stream.org/discord
    PC GitHub project: https://github.com/moonlight-stream/moonlight-qt
    iOS GitHub project: https://github.com/moonlight-stream/moonlight-ios
    Android GitHub project: https://github.com/moonlight-stream/moonlight-android
    Android GitHub releases page (APKs): https://github.com/moonlight-stream/moonlight-android/releases
    Embedded port (for Raspberry Pi and other embedded devices): https://github.com/irtimmer/limelight-embedded
    GearVR port (for GearVR devices): http://sideloadvr.com/detail.php?id=14

    iOS version
    The iOS port of Moonlight is now on the App Store: https://itunes.apple.com/us/app/moonlight-game-streaming/id1000551566

    Windows, Mac, and Linux port
    PC port binaries: https://github.com/moonlight-stream/moonlight-qt/releases
    PC port source: https://github.com/moonlight-stream/moonlight-qt

    Moonlight for Chrome OS
    Download the latest version from the Chrome Web Store.

    General Streaming Latency Information
    The latency of streaming is dependent on the device you're streaming to and the network you're streaming over. Different devices have different H.264 hardware decoding latency. After streaming, a toast will show up with latency numbers. It will show the total client latency and the portion of the total client latency spent waiting for the hardware decoder. Note that the total client latency does NOT include network latency, so the real latency is higher than the number you see. The total client latency is a measure of the time that the first packet in a frame is received to the time that the frame is released for rendering on screen.

    Anecdotal Hardware Decoder Latency Numbers
    These are some latency numbers (from memory) I've seen on my test devices as of Moonlight Android 4.0.1. I'll try to keep updating this as I test.

    Tier 1 devices:
    Tegra 4 - Nvidia Shield - 5 ms - 1080p60 supported
    Intel Atom/Bay Trail/Moorefield - Nexus Player - 8 ms - 1080p60 supported (may need a USB OTG Ethernet adapter for consistent performance)
    Razer Forge TV - 10 ms - 1080p60 supported - H.265 supported
    Tegra X1 - SHIELD Android TV - 10 ms - 4K60 supported - H.265 supported in hardware but needs changes in Moonlight to work well
    Tegra K1 - Nexus 9 - 15 ms - 1080p60 supported
    Tegra 3 - OUYA and Nexus 7 (2012) - 17 ms - 1080p60 supported

    Tier 2 devices:
    Broadcom VideoCore IV - Fire TV Stick - 20 ms - 720p60/1080p30 supported
    Exynos 7420 - Galaxy S6 - 20 ms - 1080p60/4K30 supported - H.265 supported
    Snapdragon S4 Pro (rebranded 600) - Nexus 7 (2013) - 20 ms - 720p60/1080p30 supported
    Snapdragon 801 - HTC One M8 GPE - 20 ms - 1080p60 supported
    Snapdragon 800 - Nexus 5 - 20 ms - 1080p60 supported
    Snapdragon 600 - Fire TV (2014) - 30 ms - 720p60/1080p30 supported

    Tier 3 devices:
    MediaTek devices - Fire TV (2015) - 55 ms - 1080p60 supported - H.265 supported

    Adding games/apps that aren't automatically found
    You can stream any almost any game or app by adding the EXE file to GFE manually (if it's not found by the automatic app scan). Open GeForce Experience, click the Preferences tab, click GameStream on the sidebar, then click the add (+) button on the right. Browse to the app or file you want to add and click OK. You can rename the app using the edit button on the right (near the add button).

    Using Moonlight as a remote desktop solution
    You can stream the entire Windows desktop via Moonlight. Follow step 2 from this guide

    Streaming over the Internet
    Install the Moonlight Internet Streaming Helper on your host gaming PC to enable streaming over the Internet. If your router supports UPnP, you won't need to make any manual changes.

    If the above tool isn't able to enable Internet streaming automatically or your router doesn't support it, forward these ports manually:
    TCP 47984, 47989, 48010
    UDP 47998, 47999, 48000, 48010

    General requirements for current APK:
    SoC capable of decoding H.264 High Profile in hardware (Snapdragon, Exynos, Tegra 3 or higher, Rockchip, and more)
    Android 4.1 or higher
    GeForce Experience with a GTX 600/700/800/900 GPU or GTX 600M/700M/800M (GT-series not supported)
    Xbox, PS3 (with SixAxis app), Moga (B/HID mode), Shield, or Ouya controller (other controllers may work too in HID mode)
    Mid to high-end wireless router (preferably dual-band 802.11n or better)
    Good wireless connection to your Android device

    Troubleshooting tips:
    1. Make sure GeForce Experience is open, up-to-date, and that you've scanned for games.

    2. Make sure your device is on the same network as your computer for initial pairing.

    3. Try disabling any firewall software running on your machine.

    4. Try rebooting your machine. Sometimes the streaming software gets into a messed up state where it won't work normally until the machine is rebooted.

    5. Make sure your Android device has a strong wireless connection (and your PC too, if it's connected wirelessly).

    6. For Internet streaming, make sure to install Moonlight Internet Streaming Helper on your host gaming PC, then run the Moonlight Internet Streaming Tester that it installs to troubleshoot further.

    7. To check if GFE is working properly, try navigating to the following URLs on your GFE PC:
    http://127.0.0.1:47989/serverinfo?uniqueid=1234
    https://127.0.0.1:47984/serverinfo?uniqueid=1234

    For those with latency issues, please see this post.

    Device-related issues
    Depending on the wireless chipset on your phone/tablet, you may have a bad streaming experience if Bluetooth is active while streaming. Unfortunately, there's nothing we can do about this. If you experience significant connection degradation with a Bluetooth controller connected, you could try connecting the controller to your PC (see the section above), a USB Ethernet adapter, or controller that connects directly to your Android device (assuming your Android device supports USB OTG)

    Older Changes:

    Update 12 - March 13, 2014:
    Significant video quality improvements. Lower video latency. New UI that makes it easier to choose the best streaming settings. Transient messages are displayed while streaming if network or device problems are detected.

    Update 11:
    Tegra hardware decoding latency bug is fixed. Hardware decoding is now used by default on Tegra and Rockchip devices. Performance is vastly improved on Tegra devices (1080p60 decodes in real-time, even on Tegra 3). The parser bug causing additional artifacts and image corruption is (finally) fixed.

    Update 10:
    Added options to force either hardware or software decoding. Reduce audio decoding CPU usage. Fix image quality and performance regressions from update 9.

    Update 9:
    Reduced CPU usage of video decoding. Added options to choose target resolution (720p or 1080p) and FPS (30 or 60).

    Update 8:
    Added a checkbox to choose image quality vs performance (only for CPU decoding). Optimize CPU decoding further. The frame rate is now playable on the Ouya with its Tegra 3..

    Update 7:
    Connectivity issues should be resolved now. Update to the latest APK if you were experiencing connection failures with the last couple of releases.

    Update 6:
    There's now GUI feedback when connecting. The whitelist for hardware decoding (that only included Qualcomm decoders) has now been replaced with a blacklist (currently containing TI and Nvidia decoders). The Exynos decoder in Exynos 5 Octa has been confirmed to work.

    Update 5:
    The app will now request a new reference frame if packet loss occurs on the video stream. This means that the stream will recover from blockiness and artifacting that occur when video packets get lost. CPU decoding for non-Snapdragon devices is a bit better. Fixed back button on Shield.

    Update 4:
    Added multithreaded CPU H264 decoding support for non-Snapdragon devices with ffmpeg. Both landscape orientations now work. This grows the APK significantly so don't be alarmed when this download is larger than previous builds.

    Tegra 4 is now very smooth in the games I've tested. Tegra 3 works significantly better than before, but still not perfect (and won't likely ever be as smooth as Snapdragon or Tegra 4).

    For Qualcomm devices, a dual-core SoC (even as old as Cortex-A8 stuff) is sufficient due to the hardware decoder. For other devices, CPU decoding will now be used. These devices will need more CPU horsepower (a quad-core Tegra 3 is almost enough).

    Look forward to keyboard support and a better GUI coming in the next several days.

    Update 3:
    Frame pacing improvements for Snapdragon and Tegra devices, although Tegra still has more latency than Snapdragon devices. If you have issues with blockiness or discoloration in the video stream, make sure that you have a good wireless connection. Moonlight doesn't currently deal with packet loss as well as the Shield streaming app.

    Update 2:
    PS3, Xbox, Shield, and Moga Pro controllers are working with the latest APK.

    Update:
    Audio is now working. Video is working pretty well on Snapdragon devices (with some lag on Tegra devices). I've attached the current APK here for those that want to test. Due to the framework we're using for video decoding, this app requires Android 4.1 or higher. This is still in alpha so expect bugs.

    Original post:
    Here is a demo of a WIP app that uses the same Shield streaming technology to stream to any Android device. Controller and mouse input works. Keyboard input isn't implemented yet. Video support works (minus some artifacts at rare points and minor frame pacing issues). Audio doesn't work yet (not sure what format it is).

    We've had success with very low H264 decoding latency on Snapdragon S4 Pro/600 devices (like the 2013 Nexus 7 and HTC One), but the Tegra 3/4 decoder has a high latency per frame (~1 second) that makes streaming more laggy on devices like the Ouya, 2012 Nexus 7, and even the Shield itself.

    The next big step to a release-ready app is audio support (and the obligatory code cleanup). I'd be happy to respond to any questions about the way the app or the GFE streaming protocol works. If there's significant interest in this, I'll try to put more time into finishing it ASAP.


    Demo video (a bit old now):
    http://www.youtube.com/watch?v=0VOti83qZRU

    Downloads:
    I'd recommend downloading the app from the Play Store. Updates are automatically applied through the Play Store when they are released. Crash reports also get to us automatically if you use the Play Store version and click the Report button if Moonlight crashes.

    Google Play Link

    Sometimes APKs are more convenient for sideloading and other things, so they will continue to be posted.

    You can find the latest APKs on the GitHub page here: https://github.com/moonlight-stream/moonlight-android/releases
    View
    6
    C
    cgutman
    Moonlight Chrome Test Build (Alpha 1)

    Since there seems to be some interest in this Moonlight port for Chrome, I've decided to put a binary up for testing. Please report your thoughts on it.

    Working:
    - Pairing and streaming
    - Hardware accelerated video decoding up to 1080p60
    - Game controllers (currently limited to those for which Chrome has a built-in mapping, like Xbox and DualShock controllers)
    - Keyboard and mouse input (with the caveat of Esc kicking the app out of full screen)

    Not working:
    - No feedback when starting a stream - just be patient and wait for the video stream
    - mDNS auto-discovery of PCs
    - (Very) Non-final UI
    - A few settings are missing
    - Error handling needs work
    - Controller detection can be wonky at times (try fully exiting and restarting Chrome)

    To install, drag the CRX file into the Extensions (Menu -> More Tools -> Extensions) page of Chrome.

    To launch, use Chrome App Launcher, the Extensions page, or just search for Moonlight on your PC and you should see it installed like a normal program.

    https://www.dropbox.com/s/ml92xvot25yn23x/moonlight-chrome.crx?dl=0
    View
    6
    C
    cgutman
    Good News about Qualcomm Decoder Latency

    I found by luck that the SDP attributes on the new GFE beta 2.4.0.9 allow the client to adjust video slicing parameters. I've released a new build that enables slicing on GFE 2.4 to reduce latency of Qualcomm devices (hopefully back to 2.1.3 levels). It will also improve the latency on the Fire TV as it's also a Qualcomm device.

    The build is rolling out on Play Store, waiting for review on Amazon store, and up on GitHub now.

    Remember, you MUST have GFE beta updates turned on and be running GFE 2.4.0.9 or higher with Limelight v3.1.4.

    You can enable beta updates for GFE on the Preferences tab in the General pane.
    View
    5
    C
    cgutman
    Another GFE 2.1 status update: success!

    I've figured out secure pairing and encrypted input (required for GFE 2.1) and implemented them in Limelight-common. There's just a bit more work to do for platform-specific support (certificate and private key generation and storage) on Android and PC. My PoC code was able to stream from a GFE 2.1 box over the Internet to a custom version of Limelight-PC.

    I'm off for some much needed rest (4:54 AM here), but we're on the home stretch. Expect a release for Android and PC in the next day or so.

    Update: It's done! Limelight Android version 2.3 is rolling out on the Play Store, waiting for approval on the Ouya store, and posted https://github.com/limelight-stream/limelight-android/releases. Limelight PC is released too https://github.com/limelight-stream/limelight-pc/releases
    View
    5
    C
    cgutman
    Moonlight Chrome Test Build (Alpha 2)

    Changes from Alpha 1:
    - Fixed Esc key kicking the app out of full-screen (press Ctrl-Alt-Shift-Q to quit)
    - Fixed sometimes requiring a restart of Chrome for gamepad detection to work
    - Added mDNS auto-discovery of PCs

    Working:
    - Pairing and streaming
    - Hardware accelerated video decoding up to 1080p60
    - Game controllers (currently limited to those for which Chrome has a built-in mapping, like Xbox and DualShock controllers)
    - Keyboard and mouse input
    - mDNS auto-discovery of PCs

    Not working:
    - No feedback when starting a stream - just be patient and wait for the video stream
    - (Very) Non-final UI
    - A few settings are missing
    - Error handling needs work

    To install, drag the CRX file into the Extensions (Menu -> More Tools -> Extensions) page of Chrome.

    To launch, use Chrome App Launcher, the Extensions page, or just search for Moonlight on your PC and you should see it installed like a normal program.

    https://dl.dropboxusercontent.com/u/19391088/moonlight-chrome-alpha2.crx
    View

New posts