Thanks to @smg04 for his recently included features. Delayed stream and audio recovery playing an extremely important role in making this release work. Thanks again buddy.
Moonlight works with just about everything, BUT, moonlight-embedded was designed for low-power embedded devices such as Raspberry Pi and Amlogic chipsets. This project is especially focused on Amlogic chipsets.
AMD gpus are supported with moonlight-qt project. I dont think embedded version supports native hardware decoding for AMD gpus.
What is your usecase? Are you using an HTPC and an older AMD gpu?
Oooh.
Well, moonlight doesnt work without a host PC that has a supported Nvidia GPU. The project is taking advantage of GameStream protocol developed by Nvidia.
So if you have an AMD gpu, youāre out of luck.
Check out steam link. It might work for you.
Thanks for developing the excellent Luna Addon,but:
1.I got the same issue with @sparroxxx. "Once I click āPair Hostā in Luna, then āstarting pairingā pop up appears on my tv, however it does not show actual PIN code - it shows āstarting pairingā all the time. "
2. Another issue :when I clicked to launch the Luna addon(script.luna-0.6.6.2-alpha), the addon animation has been loaded ,after that ,the tv screen became black,however background sound was still playing.
I have never got the issues with the old version Luna Addon (script.luna-0.6.5 ).
Interesting. I havenāt touched any code relating to āpairingā between releases. I havenāt changed anything that could have affected it either. Can you try deleting your Moonlight pairing key via āLuna > Settings > Helper > Delete Pairing Keyā using the following releaseā¦
Incremental Update: Version: v0.6.6.3-alpha
Add delete pair key as an option in Lunaās helper (āLuna > Settings > Helperā)
Once deleted. Try pairing again and let me know what happens.
For everyone elseā¦ When uninstalling/upgrading to new Luna versions. The pairing key is not removed. So after an uninstall or upgrade you do not need to pair again. You might need to enter your Hostās IP address once more, inc customising your configuration settings; but you shouldnāt need to pair again.
Once you have upgraded and confirmed any customisations to Lunaās settings; continue onto āLuna > Gamesā. If at this point your pairing key is missing for whatever reason; Luna will now tell you upon attempting to load āGamesā.
If you are still having trouble pairing. Please ensure you have āGAMESTREAMā enabled within āGeForce Experienceā on your host machine; as a driver update could have reverted the setting.
The toggle can be found at āGeForce Experience > Settings Cog (left of userprofile icon) > SHIELDā
I do acknowledge a blackscreen issue after loading animation. Weāll get a fix out for that as soon as possible. I already know the culpritā¦ Somehow a change we made didnāt make it into the moonlight-embedded release. If you disconnect the session, and relaunch the same game - your session should connect (temporary workaround).
So, when weāve fixed the black screen issue after loading animation, weāll anounce so here. When we do; people will need to update Moonlight via āLuna > Settings > Helper > Setup Moonlight PKGā.
Okay guys/gals. The fix for black screen after the loading animation has been published by @smg04.
You just need to update Moonlight-embedded via: āLuna > Settings > Helper > Setup Moonlight PKGā
More information: @smg04 has included the command āchmod +x /storage/moonlight/moonlightā into the moonlight setup script; so itās now performed after the package is deployed when using āLuna > Settings > Helper > Setup Moonlight PKGā. This may or may not solve pairing issues, so Iād like some reports from the few that experienced itā¦
First Iāll say well done on getting this working, once I tried Luna 0.6.6.1-alpha it was so easy to get up and running and at 4K 60Hz no less and very playable.
Only thing that doesnāt work for me yet is surround sound, starting/resuming a game with the surround sound option enabled results in a āstream initialisation failedā error. Iāve yet to get to the bottom of it but I thought Iād stick my findings here.
When it fails moonlight logs an ALSA errorā¦ [ERR] Alsa error code -22.
When surround sound isnāt selected all works OK with the sysdefault and default audio device options.
Have Coreelec 9.2.5 running on a Le Potato (S905X SoC) outputting to a Denon X2500H AV receiver with a 5.1 speaker configuration.
The PCās running Geforce Experience 3.20.5.70 on Win 10.
Kodi is normally set to output to the ALSA HDMI device with passthrough enabled, which shows up as ALSA:hdmi:CARD=AMLM8AUDIO,DEV=0 as shown in ~/.kodi/userdata/guisettings.xml and multi-channel is fine there.
Tried all of Lunaās available audio device options including the custom audio options in Luna but no beans.
The available audio devices shown in Lunaās custom audio menu matches what is returned by aplay -lā¦
Anyway given up on that for now, my Coreelec SBC is finally a viable contender to replace my Steam Link, the Nvidia game streaming seems a bit more stable than Steamās streaming, at least on my lan.
Moonlight-embedded only supports 5.1 surround audio. Whatās your setup?
EDIT: Sorry, Iāve just noticed you mentioned its 5.1 audio on your post. I will send you a binary with more debugging messages so we can see what is wrong with initializing surround audio.
i have the same Problem as @szlww
If i try to Pair my Device i get the pairing notification on my PC and Kodi shows āStarting Pairingā on my Box, but there is now Pairing Code. Only after i print 4 random digits in the request windows on my pc and press connect.
It shows the correct pairing pin on the box.
It seems like the Starting Pairing notification is overlaying the pin notification on the box
I downloaded āscript.luna-0.6.6.3-alphaā
Installed it through Kodi.
Then Settings --> Helpers --> delete pairng key/clear game cache and after this Setup Moonlight PKG.
No crashes but this line is maybe the reason:
Could not load advanced pairing manager. Reason: ImportError(āNo module named M2Cryptoā,)
NOTICE: [script.luna] [MoonlightHelper] - Attempting to pair host: 192.168.80.10
Either way i will paste my Kodi.log for you
And a few pictures to show the Exact Problem
Only after entering some random digits in the pairng request on my PC (1st picture) and pressing enter.
I get the right pairing Key from Kodi as seen here:
Iāll have a look into this issue. Itās very strange that itās not affecting everyone. Iāll fine comb over the pairing code to see if there is anything that can be altered. Thank you for your report.
The M2Crypto error in the logs isnāt the cause though.
Yeah no problem, found somewhere that an ALSA error code -22 means unsupported format.
If you can point me in the right direction Iāll be happy to test with a different binary.
