Skip to content

7.2
Compare
Choose a tag to compare
@dkulp dkulp released this 04 Oct 18:00
· 408 commits to master since this release
7.2
This tag was signed with the committer’s verified signature.
dkulp Daniel Kulp
GPG key ID: 858FC4C4F43856A3
Learn about vigilant mode.
a3c7c98
This commit was signed with the committer’s verified signature.
dkulp Daniel Kulp
GPG key ID: 858FC4C4F43856A3
Learn about vigilant mode.

NOTE: The OS level has NOT changed. It is still 2023-08. However, updating from 7.x to 7.2 does install additional OS packages (mp3gain) and thus would require internet access for that functionality to be installed.

Enhancements

  • Added MP3Gain to Audio FileManger to adjust audio levels of selected mp3 files
  • Increase maximum number of virtual strings per port from 30 to 100
  • Increase Colorlight maximum panel size to 24x24.
  • Added PCF8574 channel output
  • Reduce boot time on PocketBeagle/BBB by about 15 seconds by not disabling services that are already disabled

Bug Fixes

  • Add "Player w/ Multisync" to multisync page filters
  • Fix playlist randomization if using Start Playlist command
  • Fix problems with null pixels not cutting off pixels of the actually string
  • Increase receive socket buffers and process more packets per read to increase reliability for large universe/DDP channel counts
  • Fix e1.31/ddp stats table with Bootstrap 5 (three colums)
  • Fix restoring Panel Layout and Single Panel Size settings
  • Fix Remap output processor when source and destination overlap
  • Fix some cases where config.txt/uEnv.txt files could become corrupt adding settings from cape EEPROMS
  • Fix problem with fast restart on BBB's causing infinite crash/restart, requiring reboot to fix
  • Fix FPPD_STARTED event from firing before some FPP Commands are registered (so FPPD_STARTED can trigger a GPIO Command)
  • Fix Port Number String testing to go R->G->B instead of G->R->B
  • Fix some undefined variables in the PHP code preventing some sequence API's from working
  • Fix some issues on the Multisync page when FPP is proxied from another FPP device
  • Make sure the proper .htaccess file is created/updated, particularly from FPP 5.x updates

Installation Instructions

If you have a system running 7.x, you can go to the FPP about page (about.php) and click on the "Manual Update" button. At that point, a big green "Upgrade" bar should appear on the main status page. Click on that to start the update process. It may take a long time to upgrade. Likely 5-10 minutes. You will need to reboot after the upgrade is complete to finish the upgrade process.

For users of FPP 6.x or older, it is strongly recommended to do a full "OS Level" upgrade or re-image instead of attempting to upgrade directly from any older FPP version. There are several new features that will not work if an OS level upgrade is not done. There are two ways to do so:

  • Re-image - you can backup your 5.x/6.x configuration, create a new image, and restore the configuration.

  • In-place upgrade - this requires you to have FPP 5.5 and all the updates for 5.5 or FPP 6.3 already running on the device. Download the appropriate "fppos" file to your computer. Make sure the file extension is still fppos (some browsers will rename it). Upload it to the "File Manager" on the FPP instance. Then go to the about page. Under the normal "Manual Upgrade", a new Upgrade OS button should appear. Click it and wait a LONG time. When done, it should reboot into 7.2. At that point, go to the Uploads tab of the FPP File Manager and delete the fppos file. An alternate method to do an in-place upgrade if you are only upgrading one device AND the device has internet connectivity, is to select the 7.2 fppos (download) file and then click on the Upgrade OS button. This will download the fppos file and then install it as mentioned above. This will still take a LONG time and if you are doing this on more than one device, you will essentially be downloading the same file multiple times so is probably not the best way.

  • NOTE: In SOME cases, the reboot will fail due to library replacement. In that case, a power cycle may be required to get it back up and running.

Selecting an image

For Raspberry Pi series including Pi B, Pi B+, Pi 3, Pi 3+, Pi 4 and Pi Zero use this image

  • FPP-v7.2-Pi.img.zip

For Beaglebone Black, Beaglebone Green, PocketBeagle, and Beaglebone Green Gateway use this image

  • FPP-v7.2-BBB.img.zip
Assets 6