moonlight-stream / moonlight-qt Goto Github PK

Our ffmpeg libraries are giant (50+ MBs) because they're prebuilt binaries with every possible option turned on. We just need H.264 and HEVC (with hwaccel support), so we should be able to shrink them to only be a few megabytes.

My friend has a NVIDIA GeForce GTX 1050 Ti. I got a GTX 970.
This is what he get's when he connects to me with video decoder on auto:
https://gyazo.com/9d9b2428a4759647954c984d58546f67
The screenshot is a bit werid tho. When he pressed prt sc it activated my screen taking tool lightshot.
For some reason there's two versions up my desktop at the top,
and what looks as 2 black versions on the bottom.
(He also lagged a bit when we got playing using software decoding)
More info will be added as we test, and brainstorm in the Discord.

Windows 10 Pro - Linux subsystem running Ubuntu
Snapdragon 835 CPU

qmake does nothing

make produces following output

cd moonlight-common-c/ && ( test -e Makefile || /usr/lib/qt5/bin/qmake -o Makefile /home/drbree82/moonlight-qt/moonlight-common-c/moonlight-common-c.pro ) && make -f Makefile Project ERROR: openssl development package not found Makefile:46: recipe for target 'sub-moonlight-common-c-make_first' failed make: *** [sub-moonlight-common-c-make_first] Error 3

In assassins creed origins it looks like the stream is dropping frames constantly and not actually at 60fps most of the time. the ubisoft fps overlay says 60fps the whole time though and streaming through Steam IHS at 140mbps is smooth as butter. Also the quality seems poor in comparison to identical settings through android.

tested:
1440p at 70mbps - 100mbps, HEVC forced, HW decode forced, 5.1, fullscreen.

system:
host - gtx1070 (8gb), i7 6700k (Skylake)
client - gtx1060 (3gb), i5 4460

I understand the software is in alpha! just giving my feedback, happy to test or supply additional information.

Text isn't great from a UI design and localization perspective and it also has issues for accessibility to colorblind people. We should use icons instead.

I propose:

• A play button overlaid in the middle of the running app (like Android)
• A padlock to indicate machines that are not paired
• An exclamation point error icon or some sort of "broken connectivity" icon for offline machines

Describe the bug
The flatpak fails silently from the icon and with a "Could not initialize GLX" error from the terminal.

Steps to reproduce
flatpak run com.moonlight_stream.Moonlight

Moonlight settings (please complete the following information)
The settings have not been adjusted from the default.

Client PC details (please complete the following information)

• OS: Linux Mint 19
• Moonlight Version: v0.3.0
• NVIDIA Driver: 340.107
• Video Card: NVIDIA Corporation GT218M

Logs (please attach)

myamanaka@adell:~$ flatpak run com.moonlight_stream.Moonlight 
00:00:00 - Qt Warning: Qt: Session management error: None of the authentication protocols specified are supported
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
00:00:00 - Qt Fatal: Could not initialize GLX

Additional context
Some googling told me I might be missing the flatpak NVIDIA drivers matching my system drivers, but they appear to all be correct. I have 340.107 installed both via apt and flatpak.

com.moonlight_stream.Moonlight/x86_64/stable            system,current
com.slack.Slack/x86_64/stable                           system,current
com.valvesoftware.Steam/x86_64/stable                   system,current
com.visualstudio.code/x86_64/stable                     system,current
io.atom.Atom/x86_64/stable                              system,current
org.kde.kdenlive/x86_64/stable                          system,current
org.openmw.OpenMW/x86_64/stable                         system,current
org.freedesktop.Platform.Compat.i386/x86_64/18.08       system,runtime
org.freedesktop.Platform.Compat32/x86_64/1.6            system,runtime
org.freedesktop.Platform.GL.nvidia-340-107/x86_64/1.4   system,runtime
org.freedesktop.Platform.GL32.nvidia-340-107/x86_64/1.4 system,runtime
org.freedesktop.Platform.VAAPI.Intel/x86_64/18.08       system,runtime
org.freedesktop.Platform.ffmpeg/x86_64/1.6              system,runtime
org.freedesktop.Platform.html5-codecs/x86_64/18.08      system,runtime
org.freedesktop.Platform/x86_64/1.6                     system,runtime
org.freedesktop.Platform/x86_64/18.08                   system,runtime
org.freedesktop.Sdk/x86_64/1.6                          system,runtime
org.gtk.Gtk3theme.Mint-Y/x86_64/3.22                    system,runtime
org.kde.Platform/x86_64/5.11                            system,runtime
org.kde.Platform/x86_64/5.9                             system,runtime

nvidia-340:
  Installed: 340.107-0ubuntu0~gpu18.04.1
  Candidate: 340.107-0ubuntu0~gpu18.04.1
  Version table:
 *** 340.107-0ubuntu0~gpu18.04.1 500
        500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status
     340.106-0ubuntu3 500
        500 http://mirror.csclub.uwaterloo.ca/ubuntu bionic/restricted amd64 Packages

The glxinfo command dumps out a pretty big list, here's the first section:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
server glx extensions:
    GLX_ARB_create_context, GLX_ARB_create_context_profile, 
    GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
    GLX_ARB_multisample, GLX_EXT_buffer_age, 
    GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
    GLX_EXT_framebuffer_sRGB, GLX_EXT_stereo_tree, GLX_EXT_swap_control, 
    GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_delay_before_swap, 
    GLX_NV_float_buffer, GLX_NV_multisample_coverage, GLX_SGIX_fbconfig, 
    GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync

I've tried OpenMW via flatpak and that works. I've also tried Steam via flatpak and do not have any issues there either.

I'm not exactly sure how to troubleshoot the moonlight-qt issue further.

There's a strange alpha blend / dithering effect / encoding effect that goes across the screen when compared to chrome version.

All -qt versions released up to and including v0.1.0

Lenovo Yoga 720-15ikb
GFE 3.14.1.48
GF Drivers 398.82
Win10 1803 (x64)

Bitrate 150Mbps
1080p
60 FPS
All other moonlight client settings Automatic/Autodetect/Defaults

currently after invoking the quit-stream sequence, the app is left running: there is no way to quit the app.

My technique of requesting a high channel count then letting SDL change it doesn't work on Mac and Linux. We always get 6 channels there, even if the audio output device can't support that many.

I have an issue where I will play any game for a short amount of time, and between 5-10 minutes into my session the client closes it's game window by itself, leaving the game still running on the host computer.

I am able to continue my session by clicking on the game I was playing and launching the streaming process again, as the moonlight application is still left running when the window closes. The problem does not appear to interfere with the host.

I am using an intel HD graphics 520 integrated GPU as the client-side decoder, as my dedicated NVIDIA 940mx does not support DXVA2. I've updated drivers on both the host and client machine. I am running recommended options in the moonlight settings.

Will provide more info/details if this is worth looking into.

Hybrid decoders use a mix of shaders and fixed function hardware to decode HEVC and were common as HEVC was gaining popularity in CPUs/GPUs around 2014-2016. The performance on the Intel implementation is pretty bad (clearly not designed for 1080p60 FPS). We should blacklist HEVC on these platforms to avoid regressing performance when connecting to a PC that supports HEVC encoding.

https://www.techspot.com/article/1131-hevc-h256-enconding-playback/
https://www.anandtech.com/show/10959/intel-launches-7th-generation-kaby-lake-i7-7700k-i5-7600k-i3-7350k/6

Im using the latest release and my mouse is very unresponsive.

I have also tested the Chrome plugin same thing.

I note testing with parsec mouse is working perfectly.

My office is moved to other place, and new desktop can not play moonlight portable 0.3.0.

ios version is still enable to connect my com. (I think Server com or firewall or tcpudp is well)

I think that's qt's problem or desktop..

Client PC details (please complete the following information)

• OS: Windows 10
• Moonlight Version: 0.3.0 portable

Moonlight-1535354427.log

I would like to see an option to disable autodetection of network computers that have Geforce experience installed.
I'm using Moonlight at work and my list is always automaticaly populated by network computers I don't want in my list.
Also the possibily to rename the computers in the moonlight main list would be nice.
Thanks in advance

Hello I am ussing new *.exe app. Moonlight PC v0.2.0 (Alpha 2).
Is working very good, but Brightness not keep while I play on host gamepad. This working fine with google chrome plugin app. But not in this exe app.

I play on my notebook in same room like is my PC. So all remote things/controllers I have connected to the PC (not notebook), it means gamepad Xbox one. But when I didnt touch my laptop then after 15minut my brightness fall down. (windows power save actions)

So, if i use my laptop only like monitor, not like remote, then I have to change rules for sleep and etc. in windows.

My idea is change options of *.exe app and disable to pc sleep and sleeping modes. Same rulles like has aplications for movies/videos.

BR

Roman

Describe the bug
GFE is not setting the correct resolution when launching a game. It is launching my monitor resolution (3440 x 1440) instead of what I pick in moonlight.

Steps to reproduce
launch moonlight for pc on any pc (surface laptop, msi gs63vr, dekstop pc.

Screenshots

Moonlight settings (please complete the following information)
standard 1080p setting in moonlight. reduced to 8 Mbits for online streaming

Client PC details (please complete the following information)
moonlight version 0.02
windows 10 enterprise edition (surface pro) all others windows pro

Logs (please attach)
attached
Moonlight-1534387482.log

Additional context
everything works fine except i have to manually set the resolutuion once in game to avoid stretching and shrinking from the 3440 x 1440 local resolution.

Please add suport for fullscreen scaling (with black bars if possible) on some resoltions.
Namely on 1920x1200 the full screen scales to about 3 quarters of the image from the top leaving a quarter of the desktop still visibile on the bottom. In the chrome version it used to scale to full screen with black bars, while on the android version it goes for a full pixel to pixel scaling

SmartScreen really doesn't like us without signed binaries. I think the only way to gain reputation that's not immediately lost on the next release is to sign with the same certificate.

I applied for one with DigiCert and I'm waiting to hear back from their Verification Team.

Tried on Windows and Linux

any chance controller vibration could passed trough?

This might be a useful (non essential) feature: an auto updater (or at least a popup message saying there is a new build available).
So people don't have to check the github page every so often

The qt version is great, very responsive to controls and great quality, but I experience some strange stuttering from time to time.
The laptop it is running on has a dual graphic card setup and I guess only the iGPU does hardware video deconding because I have not seen the descrete GPU getting any of these tasks in other apps (youtube in chrome etc)
Here is the log. Hope it helps
Moonlight-1534114108.log

Bug Description
When compiled from git (either with head or with tag 0.3.0) on a Gentoo system with the following components (and versions):

• dev-libs/openssl-1.0.2o-r3
• dev-qt/qtquickcontrols2-5.9.6
• media-libs/libsdl2-2.0.8-r1
• media-video/ffmpeg-4.0.2
• x11-libs/libva-1.7.3
• x11-libs/libvdpau-1.1.1
• x11-drivers/nvidia-drivers-396.45

I get the following when starting moonlight:
`
rich@graendal ~ $ moonlight

00:00:00 - Qt Warning: QQmlApplicationEngine failed to load component
00:00:00 - Qt Warning: qrc:/gui/main.qml:73 Cannot assign to non-existent property "icon"
`

On a guess, "icon" was not available in QtQuickControls2 under version 5.9.6? Which version do you operate under? Also, I see no errors in the above output - only warnings...

Steps to reproduce
Appears to be reproducible whether running from local (pre-install) environment or after install via ebuild. Just clone, checkout, qmake, compile, and run (or fail to run) with the above dependencies...

Moonlight settings (please complete the following information)

• Have not reached the point where settings can be manipulated...

Client PC details (please complete the following information)

• OS: Gentoo Linux with GCC 7.3.0
• Moonlight Version: 0.3.0 and git head
• Video Card: GeForce GTX 960

USE flags for each component include:

`
rich@graendal ~ $ emerge -pv openssl qtquickcontrols2 libsdl2 ffmpeg libva libvdpau nvidia-drivers

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] dev-libs/openssl-1.0.2o-r3::gentoo USE="asm kerberos sslv3 tls-heartbeat zlib -bindist -gmp -rfc3779 -sctp -sslv2 -static-libs {-test} -vanilla" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="(sse2)" 0 KiB
[ebuild R ] x11-libs/libvdpau-1.1.1::gentoo USE="dri -doc {-test}" ABI_X86="32 (64) (-x32)" 0 KiB
[ebuild R ] media-libs/libsdl2-2.0.8-r1::gentoo USE="X alsa dbus haptic joystick opengl pulseaudio sound threads udev video (-altivec) (-aqua) (-custom-cflags) -gles -libsamplerate -nas -oss -static-libs -tslib -wayland -xinerama -xscreensaver" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="mmx sse sse2 -3dnow" 0 KiB
[ebuild R ] x11-libs/libva-1.7.3::gentoo USE="X drm opengl vdpau -egl -wayland" ABI_X86="32 (64) (-x32)" VIDEO_CARDS="i965 intel nouveau nvidia -dummy" 0 KiB
[ebuild R ] dev-qt/qtquickcontrols2-5.9.6:5/5.9::gentoo USE="widgets -debug {-test}" 0 KiB
[ebuild R ] x11-drivers/nvidia-drivers-396.45:0/396::gentoo USE="X acpi driver kms multilib static-libs tools uvm -compat -gtk3 -pax_kernel -wayland" ABI_X86="32 (64) (-x32)" 0 KiB
[ebuild R #] media-video/ffmpeg-4.0.2:0/56.58.58::gentoo USE="X alsa amr amrenc bzip2 celt encode fdk gme gmp gpl gsm hardcoded-tables iconv jpeg2k kvazaar ladspa libass libcaca libdrm libilbc librtmp libsoxr lzma modplug mp3 network openal opencl opengl openh264 opus postproc pulseaudio sdl snappy svg theora threads truetype twolame vaapi vdpau vorbis vpx wavpack webp x264 x265 xcb xvid zimg zlib zvbi (-altivec) (-appkit) -bluray -bs2b -cdio -chromaprint -chromium -codec2 -cpudetection -debug -doc -flite -fontconfig -frei0r -fribidi -gcrypt -gnutls -iec61883 -ieee1394 -jack -libaom -libressl -libv4l -lv2 (-mipsdspr1) (-mipsdspr2) (-mipsfpu) (-mmal) -openssl -oss -pic -rubberband -samba -speex -ssh -static-libs {-test} -v4l -zeromq" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="aes avx avx2 fma3 mmx mmxext sse sse2 sse3 sse4_1 sse4_2 ssse3 -3dnow -3dnowext -fma4 -xop" FFTOOLS="aviocat cws2fws ffescape ffeval ffhash fourcc2pixfmt graph2dot ismindex pktdumper qt-faststart sidxindex trasher" VIDEO_CARDS="nvidia" 0 KiB

Total: 7 packages (7 reinstalls), Size of downloads: 0 KiB
`
Logs (please attach)

• No logs found - not running "flatpak"
• On Linux, logs print to the terminal when running via flatpak run com.moonlight_stream.Moonlight

From what I understand currently all settings and host information is saved to Windows registry.

This means if I run the portable version on say a USB drive and connect to my PC the next user can simply install moonlight and connect unless I manually delete host settings. Likewise if that user changes any other settings such as changing hosts or changing other program settings would be carried over.

I'm wondering if this can be changed to within the application folder to be more truly portable?

observed: menu is anchored to upper-left

expected: menu should open where the mouse is

Tested on my Venue 8 Pro:

• Computer name text exceeds bounds of the grid item and overflows into the item below
• Video scaling in portrait windowed mode is screwed up badly (video is like 30 pixels wide)

The Session class has 2 signals displayLaunchError() and displayLaunchWarning() that we need to wire up in the QML StreamSegue code.

Launch warnings should show up the toasts on Moonlight Chrome did. displayLaunchError() should just pop up a dialog.

Randomly, the moonlight client will exit my stream to ask me for an unknown keychain password. The only way to get around this is to force quit the application.

I get "Unable to create opengl context" on any title I try to stream. Re-paired it with GeForce and did fresh install and restart of the moonlight pc client, still get the OpenGL error.

no issue here, but i'd like to mention that this new client is in fact the first and only game-streaming client solution that works blazingly fast, reliable and hw-accelerated on my linux intel-hd ultrabook (the chrome version never worked for me with hw-acceleration) - way better than vpn-only steam-inhome-streaming, parsec, rainway, you name it, and last but not least it is opensource too. and kudos for using flatpak for linux distribution

thanks for your great work!

=(+) key, NumpadEnter, and NumpadDot key doesn't react.

P.S.
Windows Key, Ctrl+Esc, Alt+Tab are not in Stream but in Client..

P.S.2
Moonlight Stream have greatly speed of high quality video.. It is the best remote computer solution of nvidia graphic card.
Thanks for Contributors.

computers can be deleted through context menu, but reappear on restart. Possibly not being committed to storage.

The user receives an endless stream of keychain prompts if they lock their Mac while Moonlight is running. I filed a bug on Qt here: https://bugreports.qt.io/browse/QTBUG-69677

We probably need to make a custom build of QtNetwork to work around it (switching from SecureTransport to the OpenSSL backend should do it).

Describe the bug
If there are 2 displays connected to the client, the mouse is not fixed on the display and the Moonlight client always turns off.

Steps to reproduce
Play in any action)

Screenshots

Moonlight settings (please complete the following information)
Full-Screen on

Client PC details (please complete the following information)

• OS: [e.g. Windows 10 1803]
• Moonlight Version: [e.g. v0.3.0]

Logs (please attach)

Additional context

Filing this for Lightn1ng on Discord. I have repro with my Quadro P400 running the proprietary driver.

I get the following error when Moonlight starts up:

No functioning hardware accelerated H.264 video decoder was detected by Moonlight. Your streaming performance may be severely degraded in this configuration. Click the Help button for more information on solving this problem.

However, I configured VAAPI and VDPAU and they work fine, I tested with a video in VLC and there is a noticeable difference in CPU usage, more info:

➜  ~ vainfo                               
libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.39 (libva 1.7.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 1.7.0
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Simple            :	VAEntrypointEncSlice
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileH264MultiviewHigh      :	VAEntrypointVLD
      VAProfileH264MultiviewHigh      :	VAEntrypointEncSlice
      VAProfileH264StereoHigh         :	VAEntrypointVLD
      VAProfileH264StereoHigh         :	VAEntrypointEncSlice
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileNone                   :	VAEntrypointVideoProc
      VAProfileJPEGBaseline           :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointEncPicture
      VAProfileVP8Version0_3          :	VAEntrypointVLD
      VAProfileVP8Version0_3          :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice

➜  ~ vdpauinfo                                                                                            
display: :0   screen: 0
libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
API version: 1
Information string: OpenGL/VAAPI/libswscale backend for VDPAU

Video surface:

name   width height types
-------------------------------------------
420     1920  1080  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
422     1920  1080  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
444     1920  1080  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 

Decoder capabilities:

name                        level macbs width height
----------------------------------------------------
MPEG1                          --- not supported ---
MPEG2_SIMPLE                   --- not supported ---
MPEG2_MAIN                     --- not supported ---
H264_BASELINE                  51 16384  2048  2048
H264_MAIN                      51 16384  2048  2048
H264_HIGH                      51 16384  2048  2048
VC1_SIMPLE                     --- not supported ---
VC1_MAIN                       --- not supported ---
VC1_ADVANCED                   --- not supported ---
MPEG4_PART2_SP                 --- not supported ---
MPEG4_PART2_ASP                --- not supported ---
DIVX4_QMOBILE                  --- not supported ---
DIVX4_MOBILE                   --- not supported ---
DIVX4_HOME_THEATER             --- not supported ---
DIVX4_HD_1080P                 --- not supported ---
DIVX5_QMOBILE                  --- not supported ---
DIVX5_MOBILE                   --- not supported ---
DIVX5_HOME_THEATER             --- not supported ---
DIVX5_HD_1080P                 --- not supported ---
H264_CONSTRAINED_BASELINE      51 16384  2048  2048
H264_EXTENDED                  --- not supported ---
H264_PROGRESSIVE_HIGH          --- not supported ---
H264_CONSTRAINED_HIGH          --- not supported ---
H264_HIGH_444_PREDICTIVE       --- not supported ---
HEVC_MAIN                      --- not supported ---
HEVC_MAIN_10                   --- not supported ---
HEVC_MAIN_STILL                --- not supported ---
HEVC_MAIN_12                   --- not supported ---
HEVC_MAIN_444                  --- not supported ---

Output surface:

name              width height nat types
----------------------------------------------------
B8G8R8A8         16384 16384    y  
R8G8B8A8         16384 16384    y  
R10G10B10A2      16384 16384    y  
B10G10R10A2      16384 16384    y  
A8               16384 16384    y  

Bitmap surface:

name              width height
------------------------------
B8G8R8A8         16384 16384
R8G8B8A8         16384 16384
R10G10B10A2      16384 16384
B10G10R10A2      16384 16384
A8               16384 16384

Video mixer:

feature name                    sup
------------------------------------
DEINTERLACE_TEMPORAL             -
DEINTERLACE_TEMPORAL_SPATIAL     -
INVERSE_TELECINE                 -
NOISE_REDUCTION                  -
SHARPNESS                        -
LUMA_KEY                         -
HIGH QUALITY SCALING - L1        -
HIGH QUALITY SCALING - L2        -
HIGH QUALITY SCALING - L3        -
HIGH QUALITY SCALING - L4        -
HIGH QUALITY SCALING - L5        -
HIGH QUALITY SCALING - L6        -
HIGH QUALITY SCALING - L7        -
HIGH QUALITY SCALING - L8        -
HIGH QUALITY SCALING - L9        -

parameter name                  sup      min      max
-----------------------------------------------------
VIDEO_SURFACE_WIDTH              -  
VIDEO_SURFACE_HEIGHT             -  
CHROMA_TYPE                      -  
LAYERS                           -  

attribute name                  sup      min      max
-----------------------------------------------------
BACKGROUND_COLOR                 -  
CSC_MATRIX                       -  
NOISE_REDUCTION_LEVEL            -  
SHARPNESS_LEVEL                  -  
LUMA_KEY_MIN_LUMA                -  
LUMA_KEY_MAX_LUMA                -  

And this is what I get when running Moonlight from console:

➜  ~ flatpak run --branch=stable --arch=x86_64 --command=moonlight com.moonlight_stream.Moonlight
(process:2): Gtk-WARNING **: Locale not supported by C library.
	Using the fallback 'C' locale.
00:00:00 - Qt Warning: Qt: Session management error: None of the authentication protocols specified are supported
00:00:00 - Qt Warning: qrc:/gui/PcView.qml:287:13: QML Rectangle: Binding loop detected for property "implicitWidth"
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
00:00:00 - SDL Error (0): Failed to initialize VAAPI: -1
Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory
[AVHWDeviceContext @ 0x1a52d40] VDPAU device creation on X11 display :99.0 failed.
00:00:00 - SDL Error (0): Failed to create VDPAU context: -1313558101
00:00:00 - SDL Info (0): Using SDL software renderer
00:00:00 - SDL Info (0): FFmpeg-based video decoder chosen
00:00:00 - Qt Info: Loaded unique ID from settings: "96e93d6ecb75901e"
00:00:00 - Qt Debug: Current Moonlight version: "0.2.0"

My guess is that has something to do with flatpak sandbox environment, maybe I'm missing an extension or some other package?

Full disclosure, first time using flatpak so I'm pretty much lost when it comes to troubleshooting it.

I opened up Moonlight and added my machine. When I right click on the machine, a "Delete PC" option appears but if you click on it, nothing changes and there doesn't appear to be a way to remove a PC.

Not really an issue, more of a feature request or recommendation request. Is there any sort of SSO integration that I can use with moonlight to connect to a Windows 10 remote machine that is not yet logged in and running GFE?

Linux command line support, no documentation available on this currently and previous java based command line options do not function with recommended run commands associated with flatpak

Can the installer be configured so we can disable the "add to desktop" icon? This would be useful for some people like me who like to have their desktop clean and are participating in the alpha.

Version: 0.0.3
Tags: #improvement

Please add support for multimonitor configurations.
While the window can be moved and full screened on different monitor than the default one, it seems to be somewhat buggy as you get locked into that monitor and ALT+Tab moves the moonlight window to the main monitor..

hey guys, Iam using ubunt 16.04

I installed the devel packages but it seems that I forget something and I dont waht ?

Matthias

Feature request

Moonlight should register as a uri protocol handler so that a user can directly start a streaming session with a certain app on a certain host by opening an uri. If the host is not available, it should try to send a wake on lan request first.

The Steam browser protocol can be used as an example for such an api.

Why?

Using this method allows to create desktop shortcuts to immediately start a streaming session without the need to open the moonlight gui and select your host/game first.

It could also allow for integration in other launchers like Gnome Games in the future.

How?

Qt provides the QDesktopServices class which has a setUrlHandler method. This should be enough to register as uri handler on Windows and Mac. On Linux, the uri scheme must additionally be defined in the .desktop file and added to the mimeapps.list (See https://superuser.com/questions/162092/how-can-i-register-a-custom-protocol-with-xdg)

Api

Print a list of all available hosts to std::out:
moonlight://hosts

Print a list of all available apps on the specified <host> to std::out:
moonlight://hosts/<host>/apps

Start a new streaming session on <host> running the specified <app>:
moonlight://hosts/<host>/apps/<app>

Got several reports of this and reproduced it myself. Attaching logs for analysis later.
Moonlight_Game_Streaming_Client_20180806190239.zip

I think this issue is related to how our MSI schedules the major upgrade. There are also some issues here with downgrade and installation of same version MSIs that should be fixed.

I think I'm having 2 problems on this:

In v0.1.0 (Alpha 1) if I force HW HEVC I get the pop-up message "Using software decoding due to your selection to force HEVC. This may cause poor streaming performance". After that it fails to stream and returns to the game list instead of decoding in SW HEVC. If I manually select SW HEVC it works fine (as does H.264 SW/HW).

This is from 1070Ti to a Skylake / GTX 980M which showed no issue decoding the 1080P/60fps HEVC stream in v0.0.5 (Pre-Alpha 5) when forcing HW HEVC. Even 4K/60fps works on the Chrome version (and I assume will on v0.0.5 (Pre-Alpha 5) though I didn't try) so I think the system itself is capable, but it's just not happening with v0.1.0 (Alpha 1).

Any ideas?

Describe the bug
When streaming, every few seconds, an old frame will reappear. This frame will typically not change for the duration of the streaming. The duration in between the frame appearing is inconsistent, and can range from 0.1-5 seconds. The duration that the frame stays visible also changes, and ranges from what I believe to be 10-300ms.

Steps to reproduce

1. Obtain an asus c302ca laptop.
2. Install galliumos, use the default WM (Xfce4).
3. Install moonlight-qt (from the flatpak source).
4. Attempt to stream something.

Screenshots
N/A

Moonlight settings (please complete the following information)

• Have any settings been adjusted from defaults
  Yes.
• If so, which settings have been changed?
  I have tried with many different combinations of settings (hardware/software renderer, hevc/h.264, muliple resolutions, framerates, bitrates).
• Does the problem still occur after reverting settings back to default?
  Yes

Client PC details (please complete the following information)

• OS: GalliumOS - Ubuntu 16.04 Xenial.
• Moonlight Version: v0.3.0 & v0.2.0

Logs (please attach)
I'll attach these in an edit later, when I have time.

Moonlight should have a disableable auto-update prompt that hits moonlight-stream.com or something to see what the latest version is and prompts for update on startup if enabled.

It should also show an option to update on the error dialogs if the version is out of date.

We should also add a little icon in the corner of our toolbar that shows up if your client is out of date (like Chrome does). Clicking on that should take you to the GitHub releases page.

the new version has a problem with the alt+tab shortcut.
Now wen I use the shortcut to see the Host screen, wen i try to get back to the stream the program crashes

If I alt+tab moonlight it's loosing the gamepad control untill I reselect the moonlight window, something that didn't happen with the chrome version.
Is this a something that can be fixed?

UI scaling is too big on GPD Win 2 when run in landscape orientation. It probably has something to do with default screen orientation (portrait) and that Gnome treats portrait as landscape and landscape as portrait for some reason. Althoungh this doesn't happen in other apps nor in Windows. Streaming by itself works perfectly.

Latest master / latest Arch/Gnome

Screenshots:

Landscape	Portrait	Orientations