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

Search This thread
By:
Advanced…
sindrefyrn

sindrefyrn

Senior Member
Nov 19, 2009
294
78
Oslo
cgutman said:
Did you happen to try v2.5.2 or just v2.5.2.1?

Can you try each of these APKs and report your results? You'll probably need to uninstall the Play Store version of Limelight first.

https://www.dropbox.com/s/31f0fbgb0eqigdf/Limelight-a.apk
https://www.dropbox.com/s/n6o4vawaxx9ba27/Limelight-c.apk
https://www.dropbox.com/s/7j4chqjqe8yf6l3/Limelight-d.apk
Click to expand...
Click to collapse

I have the same issue on my HTC One M8 Google Play Edition. I was using the latest from Google Play (2.5.2.1). Report after trying the three links:

First one: same issue as before. Steam on the computer launches, but I get the error "Starting RTSP handshake failed" and "RTSP Describe Request Failed (500)".
Second one: Exactly the same issue as the first one.
Third one: And exactly the same issue as the two previous.
 
M

MalaBouM

Senior Member
Sep 19, 2008
79
12
sindrefyrn said:
I have the same issue on my HTC One M8 Google Play Edition. I was using the latest from Google Play (2.5.2.1). Report after trying the three links:

First one: same issue as before. Steam on the computer launches, but I get the error "Starting RTSP handshake failed" and "RTSP Describe Request Failed (500)".
Second one: Exactly the same issue as the first one.
Third one: And exactly the same issue as the two previous.
Click to expand...
Click to collapse

Your Gfe is up to date ? Last version 2.1.1

Envoyé de mon LG-D802 en utilisant Tapatalk
 
S

scorpionx

Member
May 9, 2006
37
2
laichung said:
I think both you and he missed this......

NOTE* The following routers from our recommended router list will need manual port forwarding for Remote GameStream to function properly.
ASUS RT-AC66U -> ports 7 and 9
ASUS RT-AC68U -> ports 7 and 9

------
And to be honest , my ddwrt router failed the video streaming too (only control and audio without video)
Click to expand...
Click to collapse

So I am a total rube. It ended up being work blocking ports 7 and 9. it works everywhere else. :)
 
otto888

otto888

Senior Member
Dec 23, 2008
485
64
Alabama
Nintendo Switch
Samsung Galaxy Watch 4
cgutman said:
Did you happen to try v2.5.2 or just v2.5.2.1?

Can you try each of these APKs and report your results? You'll probably need to uninstall the Play Store version of Limelight first.

https://www.dropbox.com/s/31f0fbgb0eqigdf/Limelight-a.apk
https://www.dropbox.com/s/n6o4vawaxx9ba27/Limelight-c.apk
https://www.dropbox.com/s/7j4chqjqe8yf6l3/Limelight-d.apk
Click to expand...
Click to collapse

I'm having the same issue as sindrefyrn with all APKs.
I'm getting a Shield Tablet soon. Would a packet capture of a GameStream session help with this error?
 
C

cgutman

Senior Member
Aug 14, 2010
485
430
otto888 said:
I'm having the same issue as sindrefyrn with all APKs.
I'm getting a Shield Tablet soon. Would a packet capture of a GameStream session help with this error?
Click to expand...
Click to collapse

Yes, that would be very helpful. Can you do one of Limelight not working and one of the Shield Tablet with Shield hub streaming?
 
O

ofb

Member
Aug 4, 2014
16
0
Limelight and GFE 2.1.1 problem

Ok, just a little background info first here. Desktop is running Windows Server 2012 R2 with latest NVidia drivers + GFE 2.1.1 and using a GTX 760, GTE says it is ready to stream to shield devices. GameStream options in GFE are set for on my network and the internet. Before saying it's the server OS, please note that I can use steam in home streaming from this machine to my laptop just fine.

I have a droid bionic phone, an evga tegra note 7 tablet which is basically the shield without the controller and dual band wifi, and a laptop that I have been trying this with. All devices are on the same network and subnet. Desktop is wired, wireless is dual band wireless N, and laptop has been tried both wireless and wired.

On every device, I can see the desktop's GFE, pair with it, see the applications (steam and a couple of games GFE found after scanning), and they can even see when games or steam is running. The problem I have is that I can't connect to a stream session with any of these devices. I can try, if it's a running application, it will ask if I want to resume or quit, I can hit either and nothing happens, I can try to start steam or any of the games and I get a connection error saying there was a streaming error (error 521). This is with the firewall on and with it off on the desktop and the closest I have gotten to a working setup is that every once in a while I get an error saying the GFE is busy instead of getting a streaming error, or the screen goes blank and comes back but nothing launches and I still get a very long "establishing connection: starting app" followed by starting app failed with a long url.

Anyone have any other ideas I can try? Restarting, rescanning for games, and uninstall/reinstall of GFE/nvidia drivers doesn't seem to be working.

I do have Hyper-V role enabled but nothing running, could this be an issue?

Edit: I forgot to mention that even if I load steam first into big picture mode, I still get the same problems/errors.
 
Last edited:
R

Rodn3y

New member
Aug 4, 2014
3
1
I also have the RTSP Handshake failed error.

I used wireshark to capture the traffic on port 48010, here is what it looks like:
OPTIONS rtsp://10.0.0.2 RTSP/1.0
CSeq: 1
X-GS-ClientVersion: 10

RTSP/1.0 200 OK
CSeq: 1
Date: 04/Aug/2014:21:38:53 Mitteleurop.ische Sommerzeit
X-GS-ServerVersion: 10
Public: OPTIONS, DESCRIBE, SETUP, TEARDOWN, PLAY, PAUSE, GET_PARAMETER, SET_PARAMETER
Click to expand...
Click to collapse
Followed by
DESCRIBE rtsp://10.0.0.2 RTSP/1.0
Accept: application/sdp
CSeq: 2
If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT
X-GS-ClientVersion: 10

RTSP/1.0 500 Internal Server Error
CSeq: 2
Date: 04/Aug/2014:21:38:56 Mitteleurop.ische Sommerzeit
X-GS-ServerVersion: 10
Click to expand...
Click to collapse

Unfortunately I do not have an original shield to compare the traffic, but maybe that already helps.
 
Last edited:
C

cgutman

Senior Member
Aug 14, 2010
485
430
Rodn3y said:
I also have the RTSP Handshake failed error.

I used wireshark to capture the traffic on port 48010, here is what it looks like:

Followed by


Unfortunately I do not have an original shield to compare the traffic, but maybe that already helps.
Click to expand...
Click to collapse

It doesn't look like Limelight's fault really. DESCRIBE is not generally a request that would fail because the client is broken. Limelight is simply asking for the video parameters. I suspect that it's a bug with GFE 2.1.1. Interestingly there is a SHIELD owner that had issues with the official streaming app and got an RTSP handshake error with Limelight too. https://forums.geforce.com/default/...es-launch-steam-from-shield-master-thread/11/

I suspect that Nvidia is going to push a fix relatively quickly because it affects some of the new SHIELD Tablet owners too.

Edit: Another person who had been emailing me saw his RTSP handshake issues go away after he reinstalled Windows (that's dedication). Again this leads me to believe there's a GFE issue causing this.
 
Last edited:
A

Attreyu

Member
Jun 9, 2013
44
3
Works after the latest update, no more handshake issues.
The problem is now lagging at about 40 to 50 ms.
Computer is core i7 with 16 gb RAM and GTX 860m directly linked to Asus RT AC68U.
Phone is Oppo Find7 QHD with Snapdragon 801 and 3GB of RAM. Wireless is 5ghz dual band.
Connecting at 720p with 30fps.
What can I do to improve the lag ?
 
C

cgutman

Senior Member
Aug 14, 2010
485
430
Attreyu said:
Works after the latest update, no more handshake issues.
The problem is now lagging at about 40 to 50 ms.
Computer is core i7 with 16 gb RAM and GTX 860m directly linked to Asus RT AC68U.
Phone is Oppo Find7 QHD with Snapdragon 801 and 3GB of RAM. Wireless is 5ghz dual band.
Connecting at 720p with 30fps.
What can I do to improve the lag ?
Click to expand...
Click to collapse

Using 60 fps would probably help a lot. Most decoders buffer a set number of frames, so sending double the frames means half the lag.
 
T

TankSlayer

New member
Aug 5, 2014
3
0
Hi

I've been trying to stream to my S3, I've downloaded the one that you've specified in the OP But Im have zero luck connecting.

Iv'e tried putting in my local ip and then my normal ip.

I've tried using the latest version from dropbox but that has had the hardware encoder crash problem on my S3

Thanks
 
C

cgutman

Senior Member
Aug 14, 2010
485
430
TankSlayer said:
Hi

I've been trying to stream to my S3, I've downloaded the one that you've specified in the OP But Im have zero luck connecting.

Iv'e tried putting in my local ip and then my normal ip.

I've tried using the latest version from dropbox but that has had the hardware encoder crash problem on my S3

Thanks
Click to expand...
Click to collapse

Finally an S3 owner who has the infamous hardware decoder crash! I've got updated APKs for you to try.

https://www.dropbox.com/s/6flr9xk9ukaol4d/Limelight-bitstream.apk
https://www.dropbox.com/s/uipnb0t3qgld5pi/Limelight-both.apk

If neither of those work, the final APK has additional debugging turned on. If you could send me a logcat log of you trying to stream with the next APK, that would be great. Instruction on how to use logcat: http://xdaforums.com/showthread.php?t=2274119

The APK to use with logcat -> https://www.dropbox.com/s/1hixbz4je8ea4vu/Limelight-debug.apk

There will also be a message displayed when you start to stream that starts with "omx". Please tell me exactly what that message says.
 
A

Attreyu

Member
Jun 9, 2013
44
3
cgutman said:
Using 60 fps would probably help a lot. Most decoders buffer a set number of frames, so sending double the frames means half the lag.
Click to expand...
Click to collapse

Sorry, I mispelled it. I'm actually using 60fps.

I would be interested to know if the 801 is competent at this and to what degree. It's not so much about the 40ms which is by all means impressive. It's just that I saw other posters claiming 3-4 ms, perhaps on Tegra 3-4 devices ?
 
Last edited:
sindrefyrn

sindrefyrn

Senior Member
Nov 19, 2009
294
78
Oslo
cgutman said:
It doesn't look like Limelight's fault really. DESCRIBE is not generally a request that would fail because the client is broken. Limelight is simply asking for the video parameters. I suspect that it's a bug with GFE 2.1.1. Interestingly there is a SHIELD owner that had issues with the official streaming app and got an RTSP handshake error with Limelight too. https://forums.geforce.com/default/...es-launch-steam-from-shield-master-thread/11/

I suspect that Nvidia is going to push a fix relatively quickly because it affects some of the new SHIELD Tablet owners too.

Edit: Another person who had been emailing me saw his RTSP handshake issues go away after he reinstalled Windows (that's dedication). Again this leads me to believe there's a GFE issue causing this.
Click to expand...
Click to collapse

I'm certain you're right. I fixed my RTSP handshake issues this way:

  • Using CCleaner, I uninstalled Geforce experience, graphics driver and physx driver. I rebooted when required.
  • I then ran this tool booted in safemode. I'm assuming this removes userdata, registry entries, etc. for nvidia-programs.
  • After rebooting into normal mode, I installed Geforce experience and the drivers.
  • I then rebooted again, and paired with limelight.

Streaming works great after this. I'm not sure all the steps are required, but that's just how I did it.
 
B

bluegizmo83

Senior Member
Jun 16, 2010
593
168
Las Cruces, NM
ASUS ROG Phone II
Google Pixel 6 Pro
Attreyu said:
Sorry, I mispelled it. I'm actually using 60fps.

I would be interested to know if the 801 is competent at this and to what degree. It's not so much about the 40ms which is by all means impressive. It's just that I saw other posters claiming 3-4 ms, perhaps on Tegra 3-4 devices ?
Click to expand...
Click to collapse

40ms to 50ms is about the average latency I see playing on my Nexus 5 at 720p, 60fps, 10Mbits, Hardware Decoder, and using a 5Ghz connection from a Netgear R6250 router with a link speed showing 433Mbps under Wifi settings. I find most games perfectly playable, even FPS games... I am able to get down to 2-3ms latency, but the only way to do so is to play at 720, 30fps, 1-2Mbits and set it for Software Decoder, which makes the video too grainy and blocky.

edit: my phone is basically the same as yours in terms of hardware. Mine has the 800 cpu instead of 801 but the only difference with yours is 1gb more ram and 200Mhz more CPU speed, the GPU is identical which is whats doing the decoding so I would expect your phone to perform the same as mine on LimeLight, which it sounds like it does.
 
Last edited:
M

MalaBouM

Senior Member
Sep 19, 2008
79
12
Attreyu said:
Sorry, I mispelled it. I'm actually using 60fps.

I would be interested to know if the 801 is competent at this and to what degree. It's not so much about the 40ms which is by all means impressive. It's just that I saw other posters claiming 3-4 ms, perhaps on Tegra 3-4 devices ?
Click to expand...
Click to collapse

Yes with tegra 4 i have 3 or 4 ms in 720/60 and 1080/60 i have 5 or 6 ms, with a lg g2 (snapdragon s800) i have same latency of yours. Yes the tegra 4 is better an S800 for decode h264.

Envoyé de mon LG-D802 en utilisant Tapatalk
 
T

TankSlayer

New member
Aug 5, 2014
3
0
cgutman said:
Finally an S3 owner who has the infamous hardware decoder crash! I've got updated APKs for you to try.

https://www.dropbox.com/s/6flr9xk9ukaol4d/Limelight-bitstream.apk
https://www.dropbox.com/s/uipnb0t3qgld5pi/Limelight-both.apk

If neither of those work, the final APK has additional debugging turned on. If you could send me a logcat log of you trying to stream with the next APK, that would be great. Instruction on how to use logcat: http://xdaforums.com/showthread.php?t=2274119

The APK to use with logcat -> https://www.dropbox.com/s/1hixbz4je8ea4vu/Limelight-debug.apk

There will also be a message displayed when you start to stream that starts with "omx". Please tell me exactly what that message says.
Click to expand...
Click to collapse

Bitsteam dosnt work with auto detect/Hardware decode (But works with software)

Limelight-both APK works without any problems, tried with all of the decoder settings. Works perfectly fine.
 
C

cgutman

Senior Member
Aug 14, 2010
485
430
Last edited:
M

mastertiti2000

Senior Member
Jul 18, 2010
126
7
Hi! I use limelight with my galaxy S4 and I have no problems (rarely some lag but it's ok). Since I have my S5, streaming lag a lot. All the 3 seconds, sound and screen are crappy and also the touch screen is less responding. I must touch 5 or 6 times to have a double or a simple click. I've try with 720p, 1080p, 30 or 60 fps, it's the same. My configuration is the same: 5ghz router, gigabit lan, 780 gtx. Anyone get this troubles? I'm rooted and in the stock rom.

Sent from my SM-G900F using XDA Free mobile app
 
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