HEVC does not play on RetroELEC-RPi4.arm-9.2-devel-20200430025740.
Was just reviewing the LibreELEC.tv github and found that there is a RPi4 patch specifically for HEVC. Seems likely that your build is either missing it or it is out of date.
Posts by jaykass
-
-
HEVC does not play on RetroELEC-RPi4.arm-9.2-devel-20200430025740.
Full logs attached.
Code
Display More2020-05-13 20:43:05.139 T:2551341904 ERROR: CMMALVideo::Open : Video codec unknown: 173 2020-05-13 20:43:05.139 T:2551341904 NOTICE: CDVDVideoCodecFFmpeg::Open() Using codec: HEVC (High Efficiency Video Coding) 2020-05-13 20:43:05.143 T:2551341904 NOTICE: Creating video thread 2020-05-13 20:43:05.144 T:2451366736 NOTICE: running thread: video_thread 2020-05-13 20:43:05.144 T:2551341904 NOTICE: Opening stream: 1 source: 256 2020-05-13 20:43:05.144 T:2551341904 NOTICE: Finding audio codec for: 86018 2020-05-13 20:43:05.162 T:2551341904 NOTICE: CDVDAudioCodecFFmpeg::Open() Successful opened audio decoder aac 2020-05-13 20:43:05.162 T:2551341904 NOTICE: Creating audio thread 2020-05-13 20:43:05.162 T:2527064912 NOTICE: running thread: CVideoPlayerAudio::Process() 2020-05-13 20:43:05.162 T:2551341904 NOTICE: Opening stream: 2 source: 256 2020-05-13 20:43:05.164 T:2451366736 NOTICE: CDecoder::Open - fmt:188 2020-05-13 20:43:05.173 T:2527064912 NOTICE: Creating audio stream (codec id: 86018, channels: 8, sample rate: 48000, no pass-through) 2020-05-13 20:43:05.366 T:3002267216 ERROR: eglSwapBuffers failed (EGL_BAD_DISPLAY) -
RetroELEC-RPi4.arm-9.2-devel-20200420002059.img.gz
When I update, Kodi will not start, loops like before. Logs attached.
When I flash a clean card, I get this error message.
-
Kodi will not start in RetroELEC-RPi4.arm-9.2-devel-20200409193626. Logs attached.
Last known working version for me is RetroELEC-RPi4.arm-9.2-devel-20200203142405-28eddc2
-
RPi 4 - RetroELEC-RPi4.arm-9.2-devel-20200313023133.img
EmulationStation also does not start from under KODI - black screen
Providing a zip of the log files as described in the first post will help escalade identify the root problem.
-
RetroELEC-RPi4.arm-9.2-devel-20200220171357-28eddc2.img still boot looping
log attached
-
Trying to upgrade from LibreElec to RetroElec, but can't get past boot.
Try flashing a clean image. I suspect upgrading from LibreELEC will not work properly.
-
RetroELEC-RPi4.arm-9.2-devel-20200216230808-28eddc2.img
Bootloop.
Logs attached.
-
RetroELEC-RPi4.arm-9.2-devel-20200216110647-28eddc2.img
Boots to Kodi but does not accept any input from my flirc (should be recognized as a usb hid) or from yatse (android remote app for kodi). Though, using yatse, I was able to get videos to play. When a video is playing, there is no sound.
Logs attached.
I tried the new RPi2 version but I have the same issue. I see the RetroELEC logo which freezes after 4/5 minutes. When I use the arrow buttons I can see a command line which sais "Starting debugging shell for boot step: mount_storage... type exit to quit"
There seem to be some existing issues with RPi2.
escalade, any chance you still have RetroELEC-RPi2.arm-9.2-devel-20200208153230-28eddc2.img available? If not, would you mind if I posted it for Bub4 to test out? Since that one seemed to work for me when I tested it previously.
-
RPi4 is bootlooping with RetroELEC-RPi4.arm-9.2-devel-20200214162214-28eddc2.img
Logs attached.
-
Hi,
Thank you very much for your hard work!! I need a little help to begin. I have a RPi 3b+. So which version should I use? RPi2 or RPi4? I tried both, and both hang during booting at the RertoELEC logo. So I guess there is no working image with RPi3b+...?
Thanks!
RPi2 is for RPi2/3/3+ as they are more or less built on the same architecture.
I had an earlier version working properly with my RPi2 (specifically RetroELEC-RPi2.arm-9.2-devel-20200208153230-28eddc2.img). I likely have some time today to test out the latest version that escalade has posted.
-
Thx again for all the time you spend on this.
Installed. Kodi works incl. passthrough. No audio in ES. RA (n64) works. Audio is there but crackling.Audio crackling is commonly due to having a system not powerful enough to handle the emulation. are you getting full FPS on n64 games?
-
RetroELEC-RPi2.arm-9.2-devel-20200208153230-28eddc2
RPi2 seems to be mostly working fine. I noticed one error about sdio on the terminal/console display when I would switch between Kodi and ES.
Browser initially crashed but then worked the second time. Its god awfully slow on Pi2 (as I would expect).
ES works correctly.
Retroarch good. Though I only tested one NES rom for now.
I tried playing a 1080p video that wasn't running at full speed. I thought the Pi2 handled h264 decode in hardware but maybe I'm remembering incorrectly.
Logs attached.
-
I can't see any issue actually, looks like RetroArch exits cleanly after starting. I have uploaded a build that I think will fix it
RetroELEC-RPi4.arm-9.2-devel-20200203142405-28eddc2.img
Wifi appears to be working.
glcore appears to be working.
Retroarch exits to kodi as expected.
I tested out a variety of shaders. Many work at full speed. Some make games unplayable dropping as low as 15-20 FPS on SNES games. crt-frutbunn runs about 58 fps in SMW and Yoshi's Island. Playable but very slightly degraded from 60fps.
This is the image that I am going to keep until you have new improvements.
Prior to this I was still using a 1/26 build.I'll probably take a look at RPi2/3/3+ soon.
-
Ok, I’ve reverted the kernel to 5.4 branch same as LE master, perhaps the 5.5 branch isn’t quite ready yet. Just uploaded, let me know how it goes.
RetroELEC-RPi4.arm-9.2-devel-20200202070310-28eddc2.img
Kodi boots again.
Wifi appears to be corrected.
When quitting retroarch, it still closes and then restarts without going to Kodi.
What I think is the relevant log snippet from "journalctl --no-pager -b -0" below, full log attached.
Code
Display MoreFeb 02 10:06:26 LibreELEC systemd[1]: Started /usr/bin/kodi-retroarch.sh. Feb 02 10:06:26 LibreELEC kodi.sh[1225]: Running as unit: run-rfd3ae2d41bbc4a3b915bf5152ab689ae.service Feb 02 10:06:26 LibreELEC systemd[1]: Stopping Kodi Media Center... Feb 02 10:06:26 LibreELEC systemd[1]: Started Retroarch. Feb 02 10:06:26 LibreELEC systemd[1]: run-rfd3ae2d41bbc4a3b915bf5152ab689ae.service: Succeeded. Feb 02 10:06:27 LibreELEC systemd[1]: retroarch.service: Main process exited, code=exited, status=1/FAILURE Feb 02 10:06:27 LibreELEC systemd[1]: retroarch.service: Failed with result 'exit-code'. Feb 02 10:06:29 LibreELEC systemd[1]: retroarch.service: Scheduled restart job, restart counter is at 1. Feb 02 10:06:29 LibreELEC systemd[1]: Stopped Retroarch. Feb 02 10:06:29 LibreELEC systemd[1]: Started Retroarch. Feb 02 10:06:29 LibreELEC wpa_supplicant[681]: wlan0: Failed to initiate sched scan Feb 02 10:06:29 LibreELEC systemd[1]: retroarch.service: Main process exited, code=exited, status=1/FAILURE Feb 02 10:06:29 LibreELEC systemd[1]: retroarch.service: Failed with result 'exit-code'. Feb 02 10:06:29 LibreELEC systemd[1]: kodi.service: Succeeded. Feb 02 10:06:29 LibreELEC systemd[1]: Stopped Kodi Media Center. Feb 02 10:06:31 LibreELEC systemd[1]: retroarch.service: Scheduled restart job, restart counter is at 2. Feb 02 10:06:31 LibreELEC systemd[1]: Stopped Retroarch. Feb 02 10:06:32 LibreELEC systemd[1]: Started Retroarch. Feb 02 10:06:37 LibreELEC systemd[1]: retroarch.service: Succeeded. Feb 02 10:06:39 LibreELEC systemd[1]: retroarch.service: Scheduled restart job, restart counter is at 3. Feb 02 10:06:39 LibreELEC systemd[1]: Stopped Retroarch. Feb 02 10:06:39 LibreELEC systemd[1]: Started Retroarch. Feb 02 10:07:02 LibreELEC systemd[1]: retroarch.service: Succeeded. Feb 02 10:07:04 LibreELEC systemd[1]: retroarch.service: Scheduled restart job, restart counter is at 4. Feb 02 10:07:04 LibreELEC systemd[1]: Stopped Retroarch. Feb 02 10:07:04 LibreELEC systemd[1]: Started Retroarch. -
I synced up the brcmfmac_sdio-firmware-rpi from master and updated to the recently updated 5.5.0 kernel, could someone test the latest RPi4?
RetroELEC-RPi4.arm-9.2-devel-20200201151833-28eddc2
Kodi goes into a crash loop. The screen goes from "waiting on Network to come online ..." to a blank screen, and then continuously repeats.
Logs attached.
-
When I review the video settings in retroarch, glcore is selected. If I change to a different driver (e.g. gl) in the UI then I cannot select glcore again.
As far as I know, glcore is the current driver. Is this something that can be confirmed via the log files?
I found this in the attached logs (this is from retroarch):
Code
Display More[ERROR] Couldn't find any video driver named "glcore" [INFO] Available video drivers are: [INFO] gl [INFO] null [WARN] Going to default to first video driver... [INFO] [Environ]: SET_PIXEL_FORMAT: RGB565. [INFO] Redirecting save file to "/storage/.config/retroarch/savefiles/.srm". [INFO] Redirecting savestate to "/storage/.config/retroarch/savestates/.state". [INFO] Version of libretro API: 1 [INFO] Compiled against API: 1 [INFO] [Audio]: Set audio input rate to: 30000.00 Hz. [INFO] [Video]: Video @ fullscreen [ERROR] Couldn't find any video driver named "glcore" [INFO] Available video drivers are: [INFO] gl [INFO] null [WARN] Going to default to first video driver... [ERROR] [Wayland]: Failed to connect to Wayland server.So that explains not finding the slang shaders. I suspect that not finding glcore also means degraded performance.
Bard I'll check if wifi is working on my Pi4 when I get back home. I've been using ethernet so I never reviewed wifi before.
I have no options in RetroELEC settings for Wifi. So it would seem that in RPi4.arm-devel-20200126145032-28eddc2, the RPi4 wifi is not recognized.
Exiting Retroarch results in Retroarch closing and then immediately reopening in both RetroELEC-RPi4.arm-9.2-devel-20200128073910-28eddc2.img and RetroELEC-RPi4.arm-9.2-devel-20200130140619-28eddc2.img.
-
The slang shaders requires either the glcore or vulkan driver. Check that you are using glcore, which should be selected automatically by the retroarch.sh script. With the gl driver only glsl shaders would be visible.
When I review the video settings in retroarch, glcore is selected. If I change to a different driver (e.g. gl) in the UI then I cannot select glcore again.
As far as I know, glcore is the current driver. Is this something that can be confirmed via the log files?
Bard I'll check if wifi is working on my Pi4 when I get back home. I've been using ethernet so I never reviewed wifi before.
