Working moonlight-embedded setup for ODROID C2

Post Reply
thomsongerman
Posts: 4
Joined: Sun Oct 07, 2018 7:13 am
languages_spoken: german, english, hungarian
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Working moonlight-embedded setup for ODROID C2

Unread post by thomsongerman » Sun Oct 07, 2018 7:23 am

Hi together,
the last three weekends I have been searching for a working moonlight-embedded setup for the ODROID C2 but I could not find one on the Internet. Could somebody help me?
I already tried the official Ubuntu distro, Debian Stretch by meveric, DietPI and a custom Manjaro ARM build.
I was only able to install moonlight-embedded on the Debian Stretch distro build by meveric. Pairing worked but streaming only shows a black screen...

Thank you very much!

User avatar
meveric
Posts: 10523
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1, N1, Go, H2 (N4100), N2, H2 (J4105)
Has thanked: 17 times
Been thanked: 148 times
Contact:

Re: Working moonlight-embedded setup for ODROID C2

Unread post by meveric » Sun Oct 07, 2018 8:28 pm

It's been a while since I compiled and tested moonlight for C2. I'm not sure if the current version is compatible with the latest version of GFE.
Also can you try activating the module amlvideodri first:

Code: Select all

sudo modprobe amlvideodri
this might be needed to get hardware acceleration to work properly.
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.

thomsongerman
Posts: 4
Joined: Sun Oct 07, 2018 7:13 am
languages_spoken: german, english, hungarian
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Working moonlight-embedded setup for ODROID C2

Unread post by thomsongerman » Mon Oct 08, 2018 12:01 am

Thank you meveric!
Unfortunately I am still getting a black screen when trying to stream.
Tried moonlight with following arguments

Code: Select all

moonlight stream -1080 -bitrate 10000 -codec h265 -platform auto -surround -app mstsc -unsupported <IP>
Also tried with:

Code: Select all

moonlight stream -1080 -bitrate 10000 -codec auto -platform auto -surround -app mstsc <IP>
and

Code: Select all

moonlight stream -720 -bitrate 5000 -codec auto platform auto -surround -app mstsc -unsupported <IP>
<IP> is the computer I am connecting to.

Getting following log:

Code: Select all

Connect to <IP>..
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Can't map (dpdown:+a1)
Can't map (dpleft:-a0)
Can't map (dpright:+a0)
Can't map (dpup:-a1)
Can't map (dpdown:+a1)
Can't map (dpleft:-a0)
Can't map (dpright:+a0)
Can't map (dpup:-a1)
Can't map (dpdown:+a1)
Can't map (dpleft:-a0)
Can't map (dpright:+a0)
Can't map (dpup:-a1)
Can't map (dpdown:+a1)
Can't map (dpleft:-a0)
Can't map (dpright:+a0)
Can't map (dpup:-a1)
Can't map (lefttrigger:+a3)
Can't map (righttrigger:-a3)
Can't map (dpdown:+a1)
Can't map (dpleft:-a0)
Can't map (dpright:+a0)
Can't map (dpup:-a1)
Can't map (dpdown:+a1)
Can't map (dpleft:-a0)
Can't map (dpright:+a0)
Can't map (dpup:-a1)
No mapping available for vt-input (19000000b41600000107000001000000) on /dev/input/event0
No CEC devices found
Initializing platform...done
Resolving host name...done
Starting RTSP handshake...done
Initializing control stream...done
Initializing video stream...done
Initializing audio stream...done
Initializing input stream...done
Starting control stream...done
Starting video stream...done
Starting audio stream...done
Starting input stream...done
Network dropped an entire frame
Invalidate reference frame request sent (6 to 8)
Unrecoverable frame 10: 12+0=12 received < 17 needed
Network dropped an entire frame
Invalidate reference frame request sent (10 to 14)
Unrecoverable frame 25: 2+0=2 received < 7 needed
Network dropped an entire frame
Invalidate reference frame request sent (25 to 25)
Unrecoverable frame 33: 18+0=18 received < 42 needed
Unrecoverable frame 38: 25+0=25 received < 41 needed
Unrecoverable frame 41: 9+0=9 received < 37 needed
Unrecoverable frame 44: 9+0=9 received < 39 needed
Unrecoverable frame 47: 9+0=9 received < 38 needed
Unrecoverable frame 49: 9+0=9 received < 17 needed
Network dropped an entire frame
Invalidate reference frame request sent (33 to 51)
Network dropped an entire frame
Invalidate reference frame request sent (53 to 53)
Network dropped an entire frame
Invalidate reference frame request sent (55 to 56)
Network dropped an entire frame
Invalidate reference frame request sent (58 to 58)
Network dropped an entire frame
Invalidate reference frame request sent (60 to 60)
Network dropped an entire frame
Invalidate reference frame request sent (62 to 62)
Unrecoverable frame 64: 2+0=2 received < 7 needed
Unrecoverable frame 65: 9+0=9 received < 42 needed
Unrecoverable frame 67: 9+0=9 received < 38 needed
Unrecoverable frame 69: 9+0=9 received < 39 needed
Unrecoverable frame 71: 9+0=9 received < 39 needed
Unrecoverable frame 73: 9+0=9 received < 28 needed
Unrecoverable frame 75: 9+0=9 received < 12 needed
Network dropped an entire frame
Invalidate reference frame request sent (64 to 76)
Unrecoverable frame 80: 18+0=18 received < 37 needed
Unrecoverable frame 82: 8+0=8 received < 37 needed
Unrecoverable frame 84: 9+0=9 received < 42 needed
Unrecoverable frame 86: 0+6=6 received < 42 needed
Unrecoverable frame 87: 3+0=3 received < 37 needed
Unrecoverable frame 89: 9+0=9 received < 42 needed
Unrecoverable frame 91: 9+0=9 received < 42 needed
Network dropped an entire frame
Unrecoverable frame 95: 15+0=15 received < 37 needed
Unrecoverable frame 98: 10+0=10 received < 38 needed
Network dropped an entire frame
Invalidate reference frame request sent (95 to 100)
Network dropped an entire frame
Invalidate reference frame request sent (102 to 105)
Unrecoverable frame 114: 25+0=25 received < 38 needed
Unrecoverable frame 116: 17+0=17 received < 39 needed
Unrecoverable frame 119: 13+0=13 received < 39 needed
Unrecoverable frame 121: 10+0=10 received < 17 needed
Network dropped an entire frame
Invalidate reference frame request sent (114 to 122)
Network dropped an entire frame
Invalidate reference frame request sent (124 to 125)
Network dropped an entire frame
Invalidate reference frame request sent (127 to 127)
Network dropped an entire frame
Invalidate reference frame request sent (129 to 129)
Unrecoverable frame 142: 30+0=30 received < 37 needed
Unrecoverable frame 144: 9+0=9 received < 42 needed
Unrecoverable frame 146: 9+0=9 received < 42 needed
Unrecoverable frame 148: 9+0=9 received < 42 needed
Unrecoverable frame 151: 9+0=9 received < 37 needed
Unrecoverable frame 153: 9+0=9 received < 40 needed
Unrecoverable frame 155: 9+0=9 received < 38 needed
Unrecoverable frame 157: 9+0=9 received < 17 needed
Unrecoverable frame 159: 9+0=9 received < 10 needed
Network dropped an entire frame
Invalidate reference frame request sent (142 to 160)
Network dropped an entire frame
Invalidate reference frame request sent (162 to 162)
Network dropped an entire frame
Invalidate reference frame request sent (164 to 164)
Network dropped an entire frame
Invalidate reference frame request sent (166 to 166)
Network dropped an entire frame
Invalidate reference frame request sent (168 to 168)
Unrecoverable frame 178: 12+0=12 received < 38 needed
Unrecoverable frame 179: 9+0=9 received < 42 needed
Unrecoverable frame 181: 9+0=9 received < 42 needed
Unrecoverable frame 183: 9+0=9 received < 42 needed
Unrecoverable frame 185: 9+0=9 received < 42 needed
Unrecoverable frame 188: 9+0=9 received < 37 needed
Unrecoverable frame 190: 9+0=9 received < 39 needed
Unrecoverable frame 192: 9+0=9 received < 38 needed
Unrecoverable frame 194: 9+0=9 received < 17 needed
Network dropped an entire frame
Invalidate reference frame request sent (178 to 195)
Network dropped an entire frame
Invalidate reference frame request sent (197 to 197)
Unrecoverable frame 211: 3+0=3 received < 38 needed
Unrecoverable frame 212: 9+0=9 received < 37 needed
Unrecoverable frame 214: 9+0=9 received < 40 needed
Unrecoverable frame 216: 9+0=9 received < 39 needed
Unrecoverable frame 218: 9+0=9 received < 17 needed
Unrecoverable frame 220: 9+0=9 received < 10 needed
Network dropped an entire frame
Invalidate reference frame request sent (211 to 222)
Network dropped an entire frame
Invalidate reference frame request sent (224 to 224)
Network dropped an entire frame
Invalidate reference frame request sent (226 to 226)
Network dropped an entire frame
Invalidate reference frame request sent (228 to 228)
Network dropped an entire frame
Invalidate reference frame request sent (230 to 230)
Network dropped an entire frame
Invalidate reference frame request sent (232 to 232)
Unrecoverable frame 245: 12+0=12 received < 37 needed
Unrecoverable frame 247: 9+0=9 received < 42 needed
Unrecoverable frame 249: 9+0=9 received < 42 needed
Unrecoverable frame 251: 9+0=9 received < 42 needed
Unrecoverable frame 253: 9+0=9 received < 42 needed
Unrecoverable frame 256: 9+0=9 received < 37 needed
Unrecoverable frame 258: 9+0=9 received < 37 needed
Unrecoverable frame 260: 9+0=9 received < 40 needed
Unrecoverable frame 262: 9+0=9 received < 38 needed
Unrecoverable frame 264: 9+0=9 received < 17 needed
Unrecoverable frame 266: 9+0=9 received < 10 needed
Network dropped an entire frame
Invalidate reference frame request sent (245 to 267)
Network dropped an entire frame
Invalidate reference frame request sent (269 to 269)
Network dropped an entire frame
Invalidate reference frame request sent (271 to 271)
Network dropped an entire frame
Invalidate reference frame request sent (273 to 273)
Network dropped an entire frame
Invalidate reference frame request sent (275 to 275)
Unrecoverable frame 285: 13+0=13 received < 38 needed
Unrecoverable frame 286: 9+0=9 received < 37 needed
Unrecoverable frame 288: 9+0=9 received < 42 needed
Unrecoverable frame 290: 9+0=9 received < 42 needed
Unrecoverable frame 292: 9+0=9 received < 42 needed
Unrecoverable frame 294: 9+0=9 received < 38 needed
Unrecoverable frame 296: 9+0=9 received < 39 needed
Unrecoverable frame 298: 9+0=9 received < 38 needed
Unrecoverable frame 301: 8+0=8 received < 17 needed
Unrecoverable frame 303: 9+0=9 received < 10 needed
Network dropped an entire frame
Invalidate reference frame request sent (285 to 304)
Stopping input stream...done
Stopping audio stream...ENet wait interrupted
Control stream connection failed
Loss Stats: Transaction failed: 11
done
Stopping video stream...done
Stopping control stream...done
Cleaning up input stream...done
Cleaning up audio stream...done
Cleaning up video stream...done
Cleaning up control stream...done
Cleaning up platform...done
<IP> is the computer I am connecting to.

Streaming with a Raspberry Pi 3B+ works without problems.

User avatar
meveric
Posts: 10523
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1, N1, Go, H2 (N4100), N2, H2 (J4105)
Has thanked: 17 times
Been thanked: 148 times
Contact:

Re: Working moonlight-embedded setup for ODROID C2

Unread post by meveric » Mon Oct 08, 2018 12:21 am

yeah you might not want to put your platform auto parameters there.. either use directly aml or leave this option out completely. VDPAU won't work on the C2.
Also you should start simple and not go for surround and what not right from the start.

You can also try the starter from the menu, rather than typing everything in the command line. There's a script that handles all the background stuff so you don't have to type everything yourself (and accidentally use parameters that won't work).
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.

thomsongerman
Posts: 4
Joined: Sun Oct 07, 2018 7:13 am
languages_spoken: german, english, hungarian
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Working moonlight-embedded setup for ODROID C2

Unread post by thomsongerman » Mon Oct 08, 2018 12:30 am

Tried without any special parameters as you suggested (only -1080) - still black screen.
Unfortunatey I don't find the app in the MATE apps list. (Using currently your Debian Stretch image.)
I am wondering about the platform aml thing - When I specify the parameter, the log produces a

Code: Select all

Platform 'aml' not found
Am I missing something?
(I am using the fbturbo driver)

User avatar
meveric
Posts: 10523
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1, N1, Go, H2 (N4100), N2, H2 (J4105)
Has thanked: 17 times
Been thanked: 148 times
Contact:

Re: Working moonlight-embedded setup for ODROID C2

Unread post by meveric » Mon Oct 08, 2018 1:02 am

well according to the config file (/etc/moonlight.cfg) and moonlight --help "aml" should be a valid target (while platfrom auto does not exist btw).

Sadly I currently can't test Moonlight as I currently have no Windows PC to try this on.
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.

thomsongerman
Posts: 4
Joined: Sun Oct 07, 2018 7:13 am
languages_spoken: german, english, hungarian
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Working moonlight-embedded setup for ODROID C2

Unread post by thomsongerman » Sun Oct 14, 2018 5:42 pm

Tank you for your help!
I know, that there is no auto option for the platform argument, I was also a bit surprised about no error.
When I have time, I will try to compile it manually, maybe it will work that way.

scoobydrvr
Posts: 4
Joined: Sun Apr 14, 2019 3:31 am
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Working moonlight-embedded setup for ODROID C2

Unread post by scoobydrvr » Wed Jun 12, 2019 1:17 pm

Any follow up to this? There's a lot of chatter about getting this to work but no one seems to have cracked it...

Post Reply

Return to “Games and Emulators”

Who is online

Users browsing this forum: No registered users and 1 guest