Open rdkbob opened 3 weeks ago
After diving further into this issue it appears this may be related to SD card corruption. When the connector starts up it attempts to read all media files to calculate hashes for each. If it has trouble reading a hash the FPP can just sit there trying to read the file. This is particularly problematic on BB-based FPPs since they only have a single core which can become fully consumed.
Fix will involve setting a timer on calculating a SHA for each file to skip files that cannot be read.
This may be particularly relevant to users with large mp4 video files that also contain audio tracks.
A workaround exists to install the connector on another device, such as a Pi or using the xSchedule plugin on a Windows computer, and uploading the same files there. After the upload is done the BB device can then be used for playback as the server will no longer request the files from the BB.
The issue seems to be caused by the very limited resources available on the BB devices. Need to investigate possible causes and design a fix.