Feature request: RPi compatibility

[sergiohf]

I want to request a feature, to make this app compatible with raspberry pi 3 or later. I tried to compile (took a long until i discover that i need minimum Cmake 3.15) but after that when i put "make" the compilation fails at https://github.com/thestr4ng3r/chiaki/blob/master/gui/src/avopenglwidget.cpp . In this file the compiler cannot find glEnableVertexAttribArray and others. Someone tell me that with SDL2 and OpenGL ES that works with a RPI, it might just work, butI dont knowif its possible.

[KurtusCobain]

Ok it’s installed works fairly good over a WiFi connection. At one point I had to throw in a Sudo command for a file to copy correctly. Had a slight issue with nanopb but I didn’t cd correctly. I connected via usb with PS4 controller no inputs I may need to grab some drivers for the pi. Overall your directions were easy to follow. Next job I’m going to fiddle with the controller see what will work!

https://youtu.be/ZkAUC0daLpU

[Fredrum]

Thats good to hear! Yep ill have to check with Florian about that or ill have to see if i can figure it out.

Sometimes i have problems with the controller not cinnecting but it generally works if i just re plu it once, then it should work well, maybe until you restart chiaki?

On Nov 13, 2020, at 8:39 PM, KurtusCobain notifications@github.com wrote:

Ok it’s installed works fairly good over a WiFi connection. At one point I had to throw in a Sudo command for a file to copy correctly. Had a slight issue with nanopb but I didn’t cd correctly. I connected via usb with PS4 controller no inputs I may need to grab some drivers for the pi. Overall your directions were easy to follow. Next job I’m going to fiddle with the controller see what will work!

https://youtu.be/ZkAUC0daLpU

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[Fredrum]

:D fun to see your video too! Was that wifi or ethernet?

On Nov 13, 2020, at 8:39 PM, KurtusCobain notifications@github.com wrote:

Ok it’s installed works fairly good over a WiFi connection. At one point I had to throw in a Sudo command for a file to copy correctly. Had a slight issue with nanopb but I didn’t cd correctly. I connected via usb with PS4 controller no inputs I may need to grab some drivers for the pi. Overall your directions were easy to follow. Next job I’m going to fiddle with the controller see what will work!

https://youtu.be/ZkAUC0daLpU

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[KurtusCobain]

I found these drivers for raspberry pi it allowed me to use PS4 controller wired haven’t tested Bluetooth. Pretty sure it’s the same drivers they use in retro pie https://github.com/macunixs/dualshock4-pi

The instructions apparently allow for blue tooth dual shock 4 input but I’m to close to PS4 for testing

I was streaming the game over WiFi also no Ethernet cable! I’m really impressed. And using the drivers listed above my favorite PS4 controller now works on the raspberry pi.

[Fredrum]

Good tip i'll try try that! I had some bad experinces trying to get bluetooth speakers working the way i wanted so i havent even dared to think about trying it for controllers. Great to hear it works!

On Nov 13, 2020, at 9:13 PM, KurtusCobain notifications@github.com wrote:

I found these drivers for raspberry pi it allowed me to use PS4 controller wired haven’t tested Bluetooth. Pretty sure it’s the same drivers they use in retro pie https://github.com/macunixs/dualshock4-pi

The instructions apparently allow for blue tooth dual shock 4 input but I’m to close to PS4 for testing

I was streaming the game over WiFi also no Ethernet cable! I’m really impressed. And using the drivers listed above my favorite PS4 controller now works on the raspberry pi.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[tomblind]

Thanks for putting in the hard work on this! I built it on my Pi Zero and it totally works!

I do have 2 issues, though:

I couldn't build with that Qt5.12 package, as it seems to be for Pi4 only and gives illegal instructions on the zero. I suspect it's doing some arm7 specific stuff (so any pi before 4 won't work). This means no sound right now. It seems I'll have to build Qt5.12 myself for arm6, but I have a bad feeling that will require more than a little effort, as the zero can't always handle building large projects like that.

The other issue is that the video stream becomes garbage if I use bitrates higher than 6000. This is surprising since the pi is connected via lan with only a gigabit switch between it and the PS4. Moonlight on the same device can be stable even at 20000, so it seems unlikely it's actually a connection issue. I'll try fiddling with some things and see if I can get better results.

[Fredrum]

Hi Thanks for the feedback! Awesome to hear that it works on the Zero! Re Qt, I wonder if its possible to change some compile flags to build it on a higher Pi version?

About the bitrates I have mine set to 20000 and it works fine. I think the main dev said he thinks it maxes out at 10K. Hmm...if Moonlight work at 20000 then it's a little mysterious and would need some investigations. Maybe Florian has some ideas.

On Sun, Nov 15, 2020 at 2:34 PM Tom notifications@github.com wrote:

Thanks for putting in the hard work on this! I built it on my Pi Zero and it totally works!

I do have 2 issues, though:

I couldn't build with that Qt5.12 package, as it seems to be for Pi4 only and gives illegal instructions on the zero. I suspect it's doing some arm7 specific stuff (so any pi before 4 won't work). This means no sound right now. It seems I'll have to build Qt5.12 myself for arm6, but I have a bad feeling that will require more than a little effort, as the zero can't always handle building large project like that.

The other issue is that the video stream becomes garbage if I use bitrates higher than 6000. This is surprising since the pi is connected via lan with only a gigabit switch between it and the PS4. Moonlight on the same device can be stable even at 20000, so it seems unlikely it's actually a connection issue. I'll try fiddling with some things and see if I can get better results.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thestr4ng3r/chiaki/issues/126#issuecomment-727648877, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJPWUUZOUWVQK4OHJLG6DLSQBJOJANCNFSM4J4ZKTUQ .

[Fredrum]

Actually could you please put in an issue ticket for the bitrate thing maybe on the main Repo https://github.com/thestr4ng3r/chiaki ?

On Sun, Nov 15, 2020 at 2:34 PM Tom notifications@github.com wrote:

Thanks for putting in the hard work on this! I built it on my Pi Zero and it totally works!

I do have 2 issues, though:

I couldn't build with that Qt5.12 package, as it seems to be for Pi4 only and gives illegal instructions on the zero. I suspect it's doing some arm7 specific stuff (so any pi before 4 won't work). This means no sound right now. It seems I'll have to build Qt5.12 myself for arm6, but I have a bad feeling that will require more than a little effort, as the zero can't always handle building large project like that.

The other issue is that the video stream becomes garbage if I use bitrates higher than 6000. This is surprising since the pi is connected via lan with only a gigabit switch between it and the PS4. Moonlight on the same device can be stable even at 20000, so it seems unlikely it's actually a connection issue. I'll try fiddling with some things and see if I can get better results.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thestr4ng3r/chiaki/issues/126#issuecomment-727648877, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJPWUUZOUWVQK4OHJLG6DLSQBJOJANCNFSM4J4ZKTUQ .

[tomblind]

Ok, I filed a bug: #374 . There's a lengthy log in there, maybe that can be of help.

[Fredrum]

Hi @tomblind could you please try to reinstall Qt5.12 with this .deb package? I haven't tried it myself but I ran a build with what I think should be Pi1/Zero build settings so fingers crossed!

https://drive.google.com/file/d/1LGV3iIZni8LQ8ca-bJjLR2pWzFaA3QK4/view?usp=sharing

I would blow away your 'build' directory and make a new one to be safe.

[tomblind]

Thanks for building that! Unfortunately, no luck :(

Unable to query physical screen size, defaulting to 100 dpi.
To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters).
Cannot find EGLConfig, returning null config
QEGLPlatformContext: Failed to create context: 3005
Cannot find EGLConfig, returning null config
EGL Error : Could not create the egl surface: error = 0x3005

Aborted

The 'Failed to create context' error occurs with the stock Qt install, but doesn't seem to affect anything. The rest of the errors are all new though.

[tomblind]

My guess is the issue is what's described here (see "Broadcom EGL library filename fix"). The Pi4 doesn't need that so that Qt5.12 package probably doesn't include it. I've got a VM fired up with a huge swap now and I'm trying to build using those instructions to see if I can get something usable.

[Fredrum]

I think maybe it would be worth testing to swap in the Zero version of the Qt 'multimedia' lib only, and use the rest of the Pi4 Qt5.12. Ugly hack but thats the specific lib file i believe is handling the audio.

The build took about 6h running on 3 cores on my RPi4.

Ill take a look as well see if its possible to change something in the config before the build.

On Nov 17, 2020, at 6:59 AM, Tom notifications@github.com wrote:

My guess is the issue is what's described here (see "Broadcom EGL library filename fix"). The Pi4 doesn't need that so that Qt5.12 package probably doesn't include it. I've got a VM fired up with a huge swap now and I'm trying to build using those instructions to see if I can get something usable.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[Fredrum]

Also the pi Hw decode + display does not use opengl so maybe that bit can be turned off on the source.

On Nov 17, 2020, at 6:59 AM, Tom notifications@github.com wrote:

My guess is the issue is what's described here (see "Broadcom EGL library filename fix"). The Pi4 doesn't need that so that Qt5.12 package probably doesn't include it. I've got a VM fired up with a huge swap now and I'm trying to build using those instructions to see if I can get something usable.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[Fredrum]

Hi Tom, I just tried building on my machine and turning off the GL widget in the streaming window and I can build and run the program.

Could you please in the file gui/scr/streamwindow.cpp around lines 65,66 comment out two lines like this?

//av_widget = new AVOpenGLWidget(session->GetVideoDecoder(), this); //setCentralWidget(av_widget);

Then build the project again with Qt5.12 enabled?

For me this removes the init of the GL and maybe that would skip past that error that you get?

On Tue, Nov 17, 2020 at 7:50 AM Blueroom fred.sund@googlemail.com wrote:

Also the pi Hw decode + display does not use opengl so maybe that bit can be turned off on the source.

On Nov 17, 2020, at 6:59 AM, Tom notifications@github.com wrote:

My guess is the issue is what's described here https://www.tal.org/tutorials/building-qt-512-raspberry-pi (see "Broadcom EGL library filename fix"). The Pi4 doesn't need that so that Qt5.12 package probably doesn't include it. I've got a VM fired up with a huge swap now and I'm trying to build using those instructions to see if I can get something usable.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thestr4ng3r/chiaki/issues/126#issuecomment-728984787, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJPWUVEVLW4HPGRHSASSVDSQKFW7ANCNFSM4J4ZKTUQ .

[tomblind]

Thanks for continuing to help me get this working 😃

Unfortunately, same errors even with that commented out.

[Fredrum]

Hm..I think this is going to be too hard without me having the hardware to test on. So OpenGL vets call somewhere else too.

Maybe in that Qt build an incompatible OpenGL(ES) version gets referenced in or used.

And you get a message saying, "Cannot find EGLConfig, returning null config" that's something to go on.

On Tue, Nov 17, 2020 at 10:31 AM Tom notifications@github.com wrote:

Thanks for continuing to help me get this working 😃

Unfortunately, same errors even with that commented out.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thestr4ng3r/chiaki/issues/126#issuecomment-729119572, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJPWUQHOGTONF5WBFA6T5DSQK6Q3ANCNFSM4J4ZKTUQ .

[Fredrum]

Here's some hints too. You already upped the memory split so its not that.

https://www.raspberrypi.org/forums/viewtopic.php?t=12581

On Tue, Nov 17, 2020 at 10:40 AM Blueroom fred.sund@googlemail.com wrote:

Hm..I think this is going to be too hard without me having the hardware to test on. So OpenGL vets call somewhere else too.

Maybe in that Qt build an incompatible OpenGL(ES) version gets referenced in or used.

And you get a message saying, "Cannot find EGLConfig, returning null config" that's something to go on.

On Tue, Nov 17, 2020 at 10:31 AM Tom notifications@github.com wrote:

Thanks for continuing to help me get this working 😃

Unfortunately, same errors even with that commented out.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thestr4ng3r/chiaki/issues/126#issuecomment-729119572, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJPWUQHOGTONF5WBFA6T5DSQK6Q3ANCNFSM4J4ZKTUQ .

[Fredrum]

You could try changing the GL driver in raspi-config under Advanced Options!?

Also people suggesting commenting out the -kms- or -fkms- in your /boot/config.txt

It's strange as I have tried many times now installing on a fresh Raspian Pi4 maybe there's different presets in the version you and me use? I'm using the 2020-08-20-raspios-buster-armhf.img which is a 3.73 GB file

On Tue, Nov 17, 2020 at 10:48 AM Blueroom fred.sund@googlemail.com wrote:

Here's some hints too. You already upped the memory split so its not that.

https://www.raspberrypi.org/forums/viewtopic.php?t=12581

On Tue, Nov 17, 2020 at 10:40 AM Blueroom fred.sund@googlemail.com wrote:

Hm..I think this is going to be too hard without me having the hardware to test on. So OpenGL vets call somewhere else too.

Maybe in that Qt build an incompatible OpenGL(ES) version gets referenced in or used.

And you get a message saying, "Cannot find EGLConfig, returning null config" that's something to go on.

On Tue, Nov 17, 2020 at 10:31 AM Tom notifications@github.com wrote:

Thanks for continuing to help me get this working 😃

Unfortunately, same errors even with that commented out.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thestr4ng3r/chiaki/issues/126#issuecomment-729119572, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJPWUQHOGTONF5WBFA6T5DSQK6Q3ANCNFSM4J4ZKTUQ .

[Fredrum]

Sorry those last two posts were for someone else.

On Tue, Nov 17, 2020 at 11:07 AM Blueroom fred.sund@googlemail.com wrote:

You could try changing the GL driver in raspi-config under Advanced Options!?

Also people suggesting commenting out the -kms- or -fkms- in your /boot/config.txt

It's strange as I have tried many times now installing on a fresh Raspian Pi4 maybe there's different presets in the version you and me use? I'm using the 2020-08-20-raspios-buster-armhf.img which is a 3.73 GB file

On Tue, Nov 17, 2020 at 10:48 AM Blueroom fred.sund@googlemail.com wrote:

Here's some hints too. You already upped the memory split so its not that.

https://www.raspberrypi.org/forums/viewtopic.php?t=12581

On Tue, Nov 17, 2020 at 10:40 AM Blueroom fred.sund@googlemail.com wrote:

Hm..I think this is going to be too hard without me having the hardware to test on. So OpenGL vets call somewhere else too.

Maybe in that Qt build an incompatible OpenGL(ES) version gets referenced in or used.

And you get a message saying, "Cannot find EGLConfig, returning null config" that's something to go on.

On Tue, Nov 17, 2020 at 10:31 AM Tom notifications@github.com wrote:

Thanks for continuing to help me get this working 😃

Unfortunately, same errors even with that commented out.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thestr4ng3r/chiaki/issues/126#issuecomment-729119572, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJPWUQHOGTONF5WBFA6T5DSQK6Q3ANCNFSM4J4ZKTUQ .

[tomblind]

The good news: I got it to work by passing -platform xcb The bad news: Still no sound :(

[Fredrum]

Awesome! Where did you pass that?

One thing Iv'e done a couple of times is thinking the sound wasn't working and then realising that I had it on hdmi while trying to hear it through the audio jack. Just checking it's not that? And this is with qt5.12 now?

Might have to get you a audio test program. had a simple Qt audio test program that I could verify with, I'll see if I still have it somewhere.

On Tue, Nov 17, 2020 at 11:26 AM Tom notifications@github.com wrote:

The good news: I got it to work by passing -platform xcb The bad news: Still no sound :(

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thestr4ng3r/chiaki/issues/126#issuecomment-729149794, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJPWUWS5NRZUDCPHMOHCCTSQLE6FANCNFSM4J4ZKTUQ .

[tomblind]

I just passed the parameter directly to chiaki.

The audio seems to now be an alsa vs pulseaudio issue. Chiaki is trying to use pulse - as a quick test I removed /usr/lib/qt5.12/plugins/audo/libqtmedia_pulse.so to force qt to use the alsa plugin and I got sound! So I probably just need to get my apt packages in order.

[tomblind]

For the sake of testing, I tried doing the same thing with the standard build of chiaki (not the one with your custom built qt5.12 package). I found where that plugin was located (/usr/lib/arm-linux-gnueabihf/qt5/plugins/audio/libqtmedia_pulse.so) and removed it. Now audio works with that build as well. So, at least in my case, a custom Qt package is not needed. It just needs to be convinced to use the alsa plugin instead of pulse. I don't know if there's a 'proper' way to do this though.

[Fredrum]

Ok link here

https://drive.google.com/file/d/1Q4_6R12dkzMOUUoXxzrQ9zygRTZhRZue/view?usp=sharing

you might have to recompile I dont know?

On Tue, Nov 17, 2020 at 11:51 AM Tom notifications@github.com wrote:

I just passed the parameter directly to chiaki.

The audio seems to now be an alsa vs pulseaudio issue. Chiaki is trying to use pulse - as a quick test I removed /usr/lib/qt5.12/plugins/audo/libqtmedia_pulse.so to force qt to use the alsa plugin and I got sound! So I probably just need to get my apt packages in order.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thestr4ng3r/chiaki/issues/126#issuecomment-729163590, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJPWUTWGQCF65WNBT7MCMTSQLH45ANCNFSM4J4ZKTUQ .

[Fredrum]

Cool good detective work! It would be great to to not have to install a special Qt version! That sounds like it should be a ticket for the main repo 'issues' as Florian would be able to suggest how we could do that maybe!?

On Tue, Nov 17, 2020 at 12:04 PM Tom notifications@github.com wrote:

For the sake of testing, I tried doing the same thing with the standard build of chiaki (not the one with your custom built qt5.12 package). I found where that plugin was located (/usr/lib/arm-linux-gnueabihf/qt5/plugins/audio/libqtmedia_pulse.so) and removed it. Now audio works with that build as well. So, at least in my case, a custom Qt package is not needed. It just needs to be convinced to use the alsa plugin instead of pulse. I don't know if there's a 'proper' way to do this though.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thestr4ng3r/chiaki/issues/126#issuecomment-729170138, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJPWURAQVLEIA3IO3PIACDSQLJLRANCNFSM4J4ZKTUQ .

[Fredrum]

Aha I see now that the Qt5.12 version I have been using that was build for RPi4 does not actually include a _pulseaudio plugin. Only the _alsa plugin. Whereas the one I build for you/PiZero does have both. That combined with Qt seemingly picking the pulseaudio plugin first seems to be the cause of the problem.

On Tue, Nov 17, 2020 at 12:08 PM Blueroom fred.sund@googlemail.com wrote:

Cool good detective work! It would be great to to not have to install a special Qt version! That sounds like it should be a ticket for the main repo 'issues' as Florian would be able to suggest how we could do that maybe!?

On Tue, Nov 17, 2020 at 12:04 PM Tom notifications@github.com wrote:

For the sake of testing, I tried doing the same thing with the standard build of chiaki (not the one with your custom built qt5.12 package). I found where that plugin was located (/usr/lib/arm-linux-gnueabihf/qt5/plugins/audio/libqtmedia_pulse.so) and removed it. Now audio works with that build as well. So, at least in my case, a custom Qt package is not needed. It just needs to be convinced to use the alsa plugin instead of pulse. I don't know if there's a 'proper' way to do this though.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thestr4ng3r/chiaki/issues/126#issuecomment-729170138, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJPWURAQVLEIA3IO3PIACDSQLJLRANCNFSM4J4ZKTUQ .

[Fredrum]

I seem to have found a solution so I'll post it on the main 'issues' section.

On Tue, Nov 17, 2020 at 12:04 PM Tom notifications@github.com wrote:

For the sake of testing, I tried doing the same thing with the standard build of chiaki (not the one with your custom built qt5.12 package). I found where that plugin was located (/usr/lib/arm-linux-gnueabihf/qt5/plugins/audio/libqtmedia_pulse.so) and removed it. Now audio works with that build as well. So, at least in my case, a custom Qt package is not needed. It just needs to be convinced to use the alsa plugin instead of pulse. I don't know if there's a 'proper' way to do this though.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thestr4ng3r/chiaki/issues/126#issuecomment-729170138, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJPWURAQVLEIA3IO3PIACDSQLJLRANCNFSM4J4ZKTUQ .

[Fredrum]

Iv'e added an (locked) 'issues' thread where I will put any updates I do. You could subscribe to it if you want to get notified about these.

https://github.com/Fredrum/chiaki/issues/1

On Tue, Nov 17, 2020 at 9:51 PM Blueroom fred.sund@googlemail.com wrote:

I seem to have found a solution so I'll post it on the main 'issues' section.

On Tue, Nov 17, 2020 at 12:04 PM Tom notifications@github.com wrote:

For the sake of testing, I tried doing the same thing with the standard build of chiaki (not the one with your custom built qt5.12 package). I found where that plugin was located (/usr/lib/arm-linux-gnueabihf/qt5/plugins/audio/libqtmedia_pulse.so) and removed it. Now audio works with that build as well. So, at least in my case, a custom Qt package is not needed. It just needs to be convinced to use the alsa plugin instead of pulse. I don't know if there's a 'proper' way to do this though.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thestr4ng3r/chiaki/issues/126#issuecomment-729170138, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJPWURAQVLEIA3IO3PIACDSQLJLRANCNFSM4J4ZKTUQ .

[Fredrum]

@tomblind Hi Tom, I'd love to start making some install scripts and maybe even .deb packages to make it easier for other people to get this running.
Would it be possible to get the steps that you have had to do to get it working ok on your Pi Zero? I think you had to do some thing for the display manager? And did you turn off logging somewhere? Where did you end up with Qt and the Audio?

[tomblind]

I intend to do PRs for optimizing fullscreen and disabling file logging, which, aside from my controller issue, were the big blockers. I'm a bit busy, but hopefully will get to it soon.

As for sound and qt, your PR fixed that and it works as it should now with regular qt from apt.

[domb84]

@tomblind Hi Tom, I'd love to start making some install scripts and maybe even .deb packages to make it easier for other people to get this running. Would it be possible to get the steps that you have had to do to get it working ok on your Pi Zero? I think you had to do some thing for the display manager? And did you turn off logging somewhere? Where did you end up with Qt and the Audio?

I've just worked this out today...

https://dominicbird.com/knowledge-base-2/emulation/compile-chiaki-and-add-as-a-custom-port-to-retropie/