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

Search This thread
By:
Advanced…
A

Aaronneyer

Senior Member
Sep 4, 2010
56
7
rhx123 said:
Decided to give this a try, it appears to connect OK but then I just get a black screen on my tablet.

Steam Big Picture launches, and touching the tablet moves the mouse on the screen, yet no video is displayed.
Same happens with software or hardware decoding.

Probably something I'm doing, but not sure what.

Seems to be something wrong on my host computer as connecting via the PC client has the same effect.

I'm on the latest drivers and the latest GeForce experience.
Click to expand...
Click to collapse

Are you running on Linux? If you are, try running it with sudo, "sudo java -jar limelight-lin64.jar". There is a problem with the permissions of /dev/input/event*, as irtimmer pointed out. You can also just do a "sudo chmod 644 /dev/input/event*" and then you can run it as root. I'm working on finding a better solution to this.

EDIT: Actually, if it's happening with the android client too, that's probably not the problem, but I'll leave this here for anyone having Linux problems.
 
Last edited:
rhx123

rhx123

Member
Jul 3, 2010
20
2
Colchester
Aaronneyer said:
Are you running on Linux? If you are, try running it with sudo, "sudo java -jar limelight-lin64.jar". There is a problem with the permissions of /dev/input/event*, as irtimmer pointed out. You can also just do a "sudo chmod 644 /dev/input/event*" and then you can run it as root. I'm working on finding a better solution to this.

EDIT: Actually, if it's happening with the android client too, that's probably not the problem, but I'll leave this here for anyone having Linux problems.
Click to expand...
Click to collapse
Nope, both my machines are Windows 8.1 64 Bit.
 
C

cgutman

Senior Member
Aug 14, 2010
485
430
Reporting latency issues

For those of you with issues with Limelight Android or Limelight PC latency issues, I'd like to request some additional information to help find the source of the issues.

1. What kind of latency are you having? Input? Video? Audio? All of them? Is the latency constant (video is always behind) or periodic (video sometimes lags behind)?

1.1 If you're having video latency, what resolution and frame rate are you using? Have you tried different ones? Have you tried the different decoder options?

2. If you're having audio or video latency, is the audio in sync with the video?

3. Describe the connection between your Android/Client PC and the router

4. Describe the connection between your streaming PC and the router

5. If you're streaming to an Android device, what is the model of your device? What SoC is it using?

6. If you're streaming to a PC, what are the specs of that PC? Most importantly, what CPU and network card does it have?
 
Last edited:
C

cgutman

Senior Member
Aug 14, 2010
485
430
rhx123 said:
Decided to give this a try, it appears to connect OK but then I just get a black screen on my tablet.

Steam Big Picture launches, and touching the tablet moves the mouse on the screen, yet no video is displayed.
Same happens with software or hardware decoding.

Probably something I'm doing, but not sure what.

Seems to be something wrong on my host computer as connecting via the PC client has the same effect.

I'm on the latest drivers and the latest GeForce experience.
Click to expand...
Click to collapse

Sounds like it might be a firewall issue. Sometimes Nvidia's installer doesn't set the firewall exclusions up correctly so video doesn't work. Try disabling your firewall.

hjuo said:
On the Android side, anybody has tried this on a x86 pad?
Click to expand...
Click to collapse
The APK doesn't include x86 native libraries due to attachment size restrictions, but I can post an x86 version of the next release. I'd be interested to hear how it works since nobody's tested x86.

mungus said:
Firstly, thanks for this awesome PC app! Have been waiting for people to somehow take advantage of the stream spewing out of my nvidia (if someone could make something to stream it to a TV by DLNA that would also be awesome).

So the only problem is that I can't get it to work. At all. I set both the host and client PCs up, pair them without any issues, hit 'Start Streaming'. I instantly get the error 'Failed to launch application' followed by 'Starting app failed'.

My host PC vitals:
- Windows 8.1 64bit
- Geforce 780 Ti
- Latest GFE and drivers
- Latest Java 64bit

Things I have tried:
- Reboots all round
- Reinstalling Java on client
- Reinstalling GFE on host
- Disabling firewalls on both client and host

Clients I have tried:
- Windows 8.1 laptop
- Windows 8.0 PC
- Windows 7 HTPC

Any guidance would be greatly appreciated!
Click to expand...
Click to collapse
The current client is pretty bad at displaying errors, so it could be anything. The next release for Android and PC will display the error message in the GFE response for easier debugging.

Speedy Gonzalez said:
@cgutman this may sound crazy but is there any way to port this to IOS devices? most of the new ipads and iphones are very fast and splashtop already works on these :)
Click to expand...
Click to collapse
It would definitely be possible, but it would be a lot of code to rewrite since we can't use the pre-existing Java codebase.
 
rhx123

rhx123

Member
Jul 3, 2010
20
2
Colchester
cgutman said:
Sounds like it might be a firewall issue. Sometimes Nvidia's installer doesn't set the firewall exclusions up correctly so video doesn't work. Try disabling your firewall.
Click to expand...
Click to collapse

I have tried disabling it (Windows Firewall) already and no dice. I also tried setting up the GFE computer as a wifi hotspot and connected the tablet directly to that, in case it was the router causing a problem but no.
I also tried connecting another machine with a xover cable and that again had the same problem.
 
Speedy Gonzalez

Speedy Gonzalez

Senior Member
May 4, 2011
266
75
Louisiana
cgutman said:
Sounds like it might be a firewall issue. Sometimes Nvidia's installer doesn't set the firewall exclusions up correctly so video doesn't work. Try disabling your firewall.


The APK doesn't include x86 native libraries due to attachment size restrictions, but I can post an x86 version of the next release. I'd be interested to hear how it works since nobody's tested x86.


The current client is pretty bad at displaying errors, so it could be anything. The next release for Android and PC will display the error message in the GFE response for easier debugging.


It would definitely be possible, but it would be a lot of code to rewrite since we can't use the pre-existing Java codebase.
Click to expand...
Click to collapse

cool I hope someone who knows what to do try this ;)
 
R

Rhedox

Senior Member
Sep 11, 2013
57
3
The video lags often. With both Hardware and Software Decoder. (Snapdragon 600). Kainy works much better.


Sent from my GT-I9505 using XDA Premium 4 mobile app
 
Last edited:
C

cgutman

Senior Member
Aug 14, 2010
485
430
Rhedox said:
The video lags often. With both Hardware and Software Decoder. (Snapdragon 600). Kainy works much better.


Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Okay, I'll need more information than that to narrow down the cause. What does "often" mean? Is it constantly behind or does it periodically lag? Does the audio stay in sync with the video?

What router are you using? How is your streaming PC connected to the router? Have you tried moving your device closer to the router?

See http://xdaforums.com/showpost.php?p=49294304&postcount=224

FWIW: I test on Snapdragon 600 devices and they work fine for me. Since it happens with both software and hardware decoding, that makes me think it's a network issue.
 
Last edited:
C

cgutman

Senior Member
Aug 14, 2010
485
430
Tegra hardware decoding is live plus image quality fixes!

I've released update 11 which uses hardware decoding on Tegra platforms. Tegra's hardware decoder is quite capable. It can do all of our supported settings (720p30, 720p60, 1080p30, and 1080p60) in real-time.

It also fixes the random image corruption bug that caused more artifacting (especially in menus, in-game overlays, text, mouse cursor, and other irregularly updated portions of the frame).
 
Last edited:
I

irtimmer

Member
Jan 7, 2014
17
8
Aaronneyer said:
Are you running on Linux? If you are, try running it with sudo, "sudo java -jar limelight-lin64.jar". There is a problem with the permissions of /dev/input/event*, as irtimmer pointed out. You can also just do a "sudo chmod 644 /dev/input/event*" and then you can run it as root. I'm working on finding a better solution to this.

EDIT: Actually, if it's happening with the android client too, that's probably not the problem, but I'll leave this here for anyone having Linux problems.
Click to expand...
Click to collapse

As far as I know Limelight-pi is the only one who use /dev/input/event* directly (and otherwise I have reimplemented it for nothing).

After looking again at my SPS fix I think I have make a little mistake. Apparently most decoders don't bother but I think I have forgotten the rbsp_stop_one_bit at the end. Adding this could maybe fix problems with using the SPS fix.
 
A

acid70

Member
Jan 28, 2007
5
0
Hello to everyone involved in this wonderful peace of software,

let me first say thank you for your work. By now i have tried every variation of it. Streaming from my PC to my mobile Phone (Nexus 4, works very well from the beginning), Tablet (Nexus 7, first worked not so well, with the latest version as well as on Nexus 4), to my other not so performant PC (very well, too) and to my Pi, wich was a dream to come true.
Sadly on the Pi i have a few problems. First is that i have no sound but i don´t know by now if its related to the Pi or to limelight, will investigate it this evening. Next issue is that i have no control at all, i have tried each possible /dev/input/eventxy but no control over mouse or keyboard. But i have made a little observation on the pi. When i plugin my selfmade XBox360 Receiver for the Pad i have additional "events" and "jst0" / "jst1" in /dev/input. I have a little hope that if i get input working at all that the pad will work too. Too optimistic? Does it need "drivers" or something else or does it work as a "throughput" to the PC?

PS: i think that the Pi is the ideal solution because its cheap, could be hooked up easily to any TV (even over analog video) an with an additional Motorola Lapdock (by now very cheap, too) you would have something like a "Shield XL" with everything needed for gaming wherever you want (assumed that you have a good connection somehow to the PC).

PPS: forgot to mention that i´m running newest raspbian with no changes.
 
Last edited:
R

ric2b

New member
Jan 12, 2014
2
0
Thank you and a question :)

Your app is amazing, thank you for making it!
It streams great at 1080p on my nexus 7 2013 :)
I do have one issue though:
I have a wireless 360 pad connected to the computer, which works perfectly well on several games, so I was mostly trying to use the nexus as a screen while the controller connected directly to the PC. however, this makes the controls act rather weird, my bet is this is some kind of interference from the tablet trying to aim at the same time as the controller, is there a way to disable any kind of controls from the tablet to the PC, essentially making it work as just a monitor?
Thanks a lot :)
 
A

Aaronneyer

Senior Member
Sep 4, 2010
56
7
irtimmer said:
As far as I know Limelight-pi is the only one who use /dev/input/event* directly (and otherwise I have reimplemented it for nothing).

After looking again at my SPS fix I think I have make a little mistake. Apparently most decoders don't bother but I think I have forgotten the rbsp_stop_one_bit at the end. Adding this could maybe fix problems with using the SPS fix.
Click to expand...
Click to collapse

Oh yep, you're correct. We used to have that problem, but it went away when we removed the dependency on JInput.
 
C

cgutman

Senior Member
Aug 14, 2010
485
430
irtimmer said:
As far as I know Limelight-pi is the only one who use /dev/input/event* directly (and otherwise I have reimplemented it for nothing).

After looking again at my SPS fix I think I have make a little mistake. Apparently most decoders don't bother but I think I have forgotten the rbsp_stop_one_bit at the end. Adding this could maybe fix problems with using the SPS fix.
Click to expand...
Click to collapse
Tegra doesn't seem to mind the missing stop bit. The main problem was the Rockchip decoders didn't like the bitstream_restriction_flag set on non-Intra streams. It's technically only defined for those types of streams in the H.264 specification, but it seems most decoders will respect the flag regardless of the encoding profile. I decided to limit it to Tegra since it's the only hardware that we've tested that has this latency issue.

acid70 said:
Hello to everyone involved in this wonderful peace of software,

let me first say thank you for your work. By now i have tried every variation of it. Streaming from my PC to my mobile Phone (Nexus 4, works very well from the beginning), Tablet (Nexus 7, first worked not so well, with the latest version as well as on Nexus 4), to my other not so performant PC (very well, too) and to my Pi, wich was a dream to come true.
Sadly on the Pi i have a few problems. First is that i have no sound but i don´t know by now if its related to the Pi or to limelight, will investigate it this evening. Next issue is that i have no control at all, i have tried each possible /dev/input/eventxy but no control over mouse or keyboard. But i have made a little observation on the pi. When i plugin my selfmade XBox360 Receiver for the Pad i have additional "events" and "jst0" / "jst1" in /dev/input. I have a little hope that if i get input working at all that the pad will work too. Too optimistic? Does it need "drivers" or something else or does it work as a "throughput" to the PC?

PS: i think that the Pi is the ideal solution because its cheap, could be hooked up easily to any TV (even over analog video) an with an additional Motorola Lapdock (by now very cheap, too) you would have something like a "Shield XL" with everything needed for gaming wherever you want (assumed that you have a good connection somehow to the PC).

PPS: forgot to mention that i´m running newest raspbian with no changes.
Click to expand...
Click to collapse
We're working on getting the Raspberry Pi port running on our Pi so we can help improve it.

Rhedox said:
Is it possible to remap the gamepad?
Click to expand...
Click to collapse
Not currently on Android, but it is possible on the PC version in the Options -> Gamepad Settings menu.

ric2b said:
Your app is amazing, thank you for making it!
It streams great at 1080p on my nexus 7 2013 :)
I do have one issue though:
I have a wireless 360 pad connected to the computer, which works perfectly well on several games, so I was mostly trying to use the nexus as a screen while the controller connected directly to the PC. however, this makes the controls act rather weird, my bet is this is some kind of interference from the tablet trying to aim at the same time as the controller, is there a way to disable any kind of controls from the tablet to the PC, essentially making it work as just a monitor?
Thanks a lot :)
Click to expand...
Click to collapse
Limelight only sends input when you press something, so it is effectively disabled if you don't use it. Nvidia's software does some things to forward controller input which might be interfering with things. Is this specific to a certain game or does it happen on any game?
 
I

irtimmer

Member
Jan 7, 2014
17
8
acid70 said:
First is that i have no sound but i don´t know by now if its related to the Pi or to limelight, will investigate it this evening.
Click to expand...
Click to collapse
Take a look at blog.scphillips.com/2013/01/sound-configuration-on-raspberry-pi-with-alsa/ If that doesn't help you propably have to recompile the binary because I link to a newer version of libopus than is provided by Raspbian

acid70 said:
Next issue is that i have no control at all, i have tried each possible /dev/input/eventxy but no control over mouse or keyboard. But i have made a little observation on the pi. When i plugin my selfmade XBox360 Receiver for the Pad i have additional "events" and "jst0" / "jst1" in /dev/input. I have a little hope that if i get input working at all that the pad will work too. Too optimistic? Does it need "drivers" or something else or does it work as a "throughput" to the PC?
Click to expand...
Click to collapse
That's strange. Do you get any input if you execute 'cat /dev/input/eventxy'. A gamepad won't magically work, because the translation from evdev to gamepad is simply missing.
 
H

hjuo

Senior Member
Aug 4, 2011
76
71
I tried with my x86 galaxy tab 3 10.1. I only tried the steam menu using the touchscreen as a mouse. I tried 720p 30fps hardware and software decoding. With software with dedicated x86 build now it works ok, it stutters a little sometimes and there is always a little delay on the tablet. With hardware decoding is similar, the quality seems a little better but the delay is worse. In both case it won't be possible to play anything, especially with hardware. The delay was only on the tablet side because the cursor was moved instantly on the pc monitor. There is a way to exit when streming? I always pressed the home button on the tablet.
 
C

cgutman

Senior Member
Aug 14, 2010
485
430
irtimmer said:
Take a look at blog.scphillips.com/2013/01/sound-configuration-on-raspberry-pi-with-alsa/ If that doesn't help you propably have to recompile the binary because I link to a newer version of libopus than is provided by Raspbian


That's strange. Do you get any input if you execute 'cat /dev/input/eventxy'. A gamepad won't magically work, because the translation from evdev to gamepad is simply missing.
Click to expand...
Click to collapse
The issue is that libopus.so.0 is missing by default on Raspbian so the audio thread dies with an UnsatsifiedLinkError. In my fork, I built a fixed-point static libopus library that I link to nv_opus_dec which removes the shared library dependency. It's faster than the floating point version too because it can use ARMv6 media extensions.

Keyboard and mouse doesn't work for me on v0.1 but it works when I build HEAD (although video doesn't render for me on HEAD).

Also your build.xml doesn't build the submodule so it won't build without the common jar in the libs folder.
 
Last edited:
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