xbmc / visualization.projectm

ProjectM visualizer for Kodi

website • docs • community • add-ons

Welcome to Kodi Home Theater Software!

Kodi is an award-winning free and open source software media player and entertainment hub for digital media. Available as a native application for Android, Linux, BSD, macOS, iOS, tvOS and Windows operating systems, Kodi runs on most common processor architectures.

Created in 2003 by a group of like minded programmers, Kodi is a non-profit project run by the XBMC Foundation and developed by volunteers located around the world. More than 500 software developers have contributed to Kodi to date, and 100-plus translators have worked to expand its reach, making it available in more than 70 languages.

While Kodi functions very well as a standard media player application for your computer, it has been designed to be the perfect companion for your HTPC. With its beautiful interface and powerful skinning engine, Kodi feels very natural to use from the couch with a remote control and is the ideal solution for your home theater.

Give your media the love it deserves

Kodi can be used to play almost all popular audio and video formats around. It was designed for network playback, so you can stream your multimedia from anywhere in the house or directly from the internet using practically any protocol available.

Point Kodi to your media and watch it scan and automagically create a personalized library complete with box covers, descriptions, and fanart. There are playlist and slideshow functions, a weather forecast feature and many audio visualizations. Once installed, your computer or HTPC will become a fully functional multimedia jukebox.

Getting Started

Kodi's developers work hard to make it support a large range of devices and operating systems. We provide final as well as development builds. To get started, head over to the downloads section and simply select the platform that you want to install it on. A quick start guide to help you get acquainted with Kodi is available in our wiki.

How to Contribute

Kodi is created by users for users and we welcome every contribution. There are no highly paid developers or poorly paid support personnel on the phones ready to take your call. There are only users who have seen a problem and done their best to fix it. This means Kodi will always need the contributions of users like you. How can you get involved?

• Coding: Developers can help Kodi by fixing a bug, adding new features, making our technology smaller and faster and making development easier for others. Kodi's codebase consists mainly of C++ with small parts written in a variety of coding languages. Our add-ons mainly consist of python and XML. For more information, please have a look at our contributing guide.
• Helping users: Our support process relies on enthusiastic contributors like you to help others get the most out of Kodi. The #1 priority is always answering questions in our support forums. Everyday new people discover Kodi, and everyday they are virtually guaranteed to have questions.
• Localization: Translate Kodi, add-ons, skins etc. into your native language.
• Add-ons: Add-ons are what make Kodi the most extensible and customizable entertainment hub available. Get started building an add-on.
• Documentation: Kodi's wiki pages are the hub for information about Kodi and surrounding ecosystem. Help make our documentation better by writing new content or correcting existing material.

Not enough free time? No problem! There are other ways to help Kodi.

• Spread the word: Share Kodi with the world! Tell your friends and family about how Kodi creates an amazing entertainment experience. Stay up to date on the latest stories about Kodi reading our news section, follow us on Twitter and Facebook, or star Kodi's repo if you want to follow development.
• Donate: We are always happy to receive a donation. Donations are typically used for travel to attend conferences, any necessary paperwork and legal fees, and the yearly XBMC Foundation Developers Conference, where a great deal of coding and planning for the following year occurs. Donations may also be used to purchase necessary hardware and licenses for developers, along with t-shirts, stickers, and other accessories for conferences.
• Buy Kodi merchandise: Purchasing Kodi gear helps just as much as a donation, and you get something in return! Checkout our store for Kodi branded gear. We regularly add new products so check back often.

Building

Kodi uses CMake as its building system but instructions are highly dependent on your operating system and target platform. Fortunately we've got you covered.

Acknowledgements

Kodi couldn't exist without

• All the contributors. Big or small a change, it does make a difference.
• All the developers that write the fantastic software and libraries that Kodi uses. We stand on the shoulders of giants.
• Our fantastic community for the never ending support, inspiration, feedback, and for keeping us on our toes when we screw up!
• Our sponsors. Without them, keeping a huge project like this alive would be next to impossible.

License

Kodi is GPLv2 licensed. You may use, distribute and copy it under the license terms.

visualization.projectm's Issues

Rendering ignores Video Calibration (Overscan) Settings

If you adjust the overscan settings with the video calibration tool, the projectm rendering window is the correct size but it is not offset accurately (it appears in the top left corner instead of in the center).

Changing presets causes crash

So, love the ProjectM addon but unfortunately it's crashing when it changes a preset.
I though it was due to the one-thread bug but that seems to be solved.

Running on the latest LibreElec (9.2.0) and latest ProjectM (2.3.4.1).
I'll try to search the debug log for some usefull information.
There was a thread on the Kodi forum so at least I'm not the only one :-)

Frequent SIGSEGV crashes in Kodi 18 on macOS & Linux 18.04

ProjectM in Kodi 18 on macOS is crashing frequently with SIGSEGV as shown in the crashlog at https://paste.kodi.tv/fagiqelami. I am running Party Mode when this happens. I do not know how to make it happen on demand.

Build failures on ftgl dependency

I'm currently unable to build visualization.projectm due to a build dependency failure. I've just cloned master, which successfully builds the freetype dependency, but the subsequent attempt to build ftgl, which depends on freetype, fails, complaining that freetype and freetype-config are not available (they are). This is happening when attempting to build against the Kodi master branch. Not sure if the issue is with Kodi's build system, or visualization.projectm specifically. The following is the output of my latest build attempt:

`[ 12%] Built target glm
[ 24%] Built target freetype
[ 26%] Performing build step for 'ftgl'
[ 12%] Performing update step for 'ftgl'
Preparing the FTGL build system...please wait

Found GNU Autoconf version 2.69
Found GNU Automake version 1.16.1
Found GNU Libtool version 2.4.6

Automatically preparing build ... done

The FTGL build system is now prepared. To build here, run:
./configure
make
[ 25%] Performing configure step for 'ftgl'
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking whether make supports the include directive... yes (GNU style)
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to print strings... printf
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @file support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for ANSI C header files... (cached) yes
checking for stdlib.h... (cached) yes
checking for wcsdup... yes
checking for strndup... yes
checking for X... libraries , headers
checking for freetype-config... no
checking for FreeType -- version >= 9.0.3... no
configure: error: FreeType2 is required to compile this library
make[5]: *** [CMakeFiles/ftgl.dir/build.make:105: ftgl-prefix/src/ftgl-stamp/ftgl-configure] Error 1
make[4]: *** [CMakeFiles/Makefile2:73: CMakeFiles/ftgl.dir/all] Error 2
make[3]: *** [Makefile:130: all] Error 2
make[2]: *** [CMakeFiles/ftgl.dir/build.make:114: build/ftgl/src/ftgl-stamp/ftgl-build] Error 2
make[1]: *** [CMakeFiles/Makefile2:279: CMakeFiles/ftgl.dir/all] Error 2
make: *** [Makefile:84: all] Error 2
`

Error building on Fedora 31 after following build instructions

Hallo,

Title explains it all, tried having a look but I'm not smart enough to figure out what's missing here. Hopefully it's just a dependency issue. Here's a snip of the relevant error output:

-- Bootstrapping visualization.projectm addon...
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.projectm
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.projectm/visualization.projectm.txt
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.projectm/platforms.txt
-- Bootstrapping visualization.shadertoy addon...
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.shadertoy
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.shadertoy/visualization.shadertoy.txt
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.shadertoy/platforms.txt
-- Bootstrapping visualization.spectrum addon...
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.spectrum
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.spectrum/visualization.spectrum.txt
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.spectrum/platforms.txt
-- Bootstrapping visualization.vortex addon...
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.vortex
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.vortex/platforms.txt
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.vortex/visualization.vortex.txt
-- Bootstrapping visualization.waveform addon...
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.waveform
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.waveform/visualization.waveform.txt
-- Installing: /home/<user>/git/xbmc/cmake/addons/addons/visualization.waveform/platforms.txt
[100%] Completed 'binary-addons'
[100%] Built target binary-addons
-- 
-- ---- Configuring addon /home/<user>/git/xbmc/cmake/addons/addons/visualization.projectm/visualization.projectm.txt ----
-- Processing /home/<user>/git/visualization.projectm/depends/linux/freetype/freetype.txt
-- freetype url: http://mirrors.xbmc.org/build-deps/sources/freetype-2.4.7.tar.bz2
-- Processing /home/<user>/git/visualization.projectm/depends/linux/ftgl/ftgl.txt
-- ftgl url: https://downloads.sourceforge.net/project/ftgl/FTGL%20Source/2.1.3%7Erc5/ftgl-2.1.3-rc5.tar.gz
-- ftgl depends: freetype
-- Processing /home/<user>/git/visualization.projectm/depends/common/glm/glm.txt
-- glm url: https://github.com/g-truc/glm/releases/download/0.9.9.5/glm-0.9.9.5.7z
-- glm extraflags: -DGLM_TEST_ENABLE_CXX_11=1;-DGLM_TEST_ENABLE=0;-DGLM_TEST_ENABLE_SIMD_SSE2=0;-DCMAKE_INSTALL_LIBDIR=lib
-- Processing /home/<user>/git/visualization.projectm/depends/common/projectm/projectm.txt
-- projectm url: https://github.com/projectM-visualizer/projectm/releases/download/v3.1.1-rc7/projectM-3.1.1-rc7.tar.gz
CMake Error at /home/<user>/git/xbmc/cmake/scripts/common/HandleDepends.cmake:109 (message):
  Missing patch command (we looked in
  /home/<user>/git/visualization.projectm/build/build/depends;/home/<user>/git/xbmc/kodi-build/addons)
Call Stack (most recent call first):
  CMakeLists.txt:386 (add_addon_depends)


-- Configuring incomplete, errors occurred!
See also "/home/<user>/git/visualization.projectm/build/CMakeFiles/CMakeOutput.log".
[<user>@kodiHTPC build]$ vim /home/<user>/git/visualization.projectm/build/CMakeFiles/CMakeOutput.log 
[<user>@kodiHTPC build]$ vim /home/<user>/git/visualization.projectm/build/CMakeFiles/CMakeOutput.log 
[<user>@kodiHTPC build]$ vim /home/<user>/git/xbmc/cmake/scripts/common/HandleDepends.cmake 
[<user>@kodiHTPC build]$ make

Please let me know what other information I should show to make this issue easier to resolve.

KODI: lock preset

Is there any setting to lock certain preset, i.e. no loop or shuffle?
I have been searching around also at KODI forum, seems many users are asking same question.
PS: I know it maybe possible to use "L" with a keyboard, but would be much convenient for users without a keyboard and with a simple tick in setting, right?

thanks in advance

Preset change at the moment only possible without threading!

Currently, ProjectM has a bug within the preset change, when a separate thread is used and Kodi then freezes.

Think it depends on the performance, on weaker system it worked for me but not on my strongest.

Error is reported here: projectM-visualizer/projectm#243

To avoid this, the thread support is currently deactivated, see: 386be2e#diff-610d6e017c2ffd2797e22ea52131ef84

Unfortunately, when a preset change occurs, sometimes a short white screen appears, because creating it is not complete.

Hope this thing gets fixed quickly.

cannot find "/usr/share/projectM"

Since b549160 building fails with

-- Up-to-date: /LE/build.LibreELEC-Generic.x86_64/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/share/kodi/addons/visualization.projectm/resources/settings.xml
-- Up-to-date: /LE/build.LibreELEC-Generic.x86_64/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/share/kodi/addons/visualization.projectm
-- Installing: /LE/build.LibreELEC-Generic.x86_64/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/share/kodi/addons/visualization.projectm/addon.xml
CMake Error at cmake_install.cmake:125 (file):
  file INSTALL cannot find "/usr/share/projectM".


FAILED: CMakeFiles/install.util 
cd /LE/build.LibreELEC-Generic.x86_64/visualization.projectm-b54916007227d49131f7cc4d111d18e6a94c8dd0/.x86_64-libreelec-linux-gnu && /LE/build.LibreELEC-Generic.x86_64/toolchain/bin/cmake -P cmake_install.cmake
ninja: build stopped: subcommand failed.

Could anyone point us (we are no cmake magicians) what we are missing here? We are building visualization.projectm like every other visualization.... addon and it worked before without any problem.
Currently we are unsure if this is an bug or an feature.

LibreELEC 9.2.0 : projectM version 2.3.4.1 "freezing" requiring reboot

Originally posted here : projectM-visualizer/projectm#295

Team Kodi released a slightly newer version of projectM a few days ago. Unfortunately , it looks like the ProjectM version 2.3.4.1 add-on for LibreELEC is still affected by the "rendering freeze after preset change" issue ( #243 ) as well as the previously mentioned presets folder structure issue.

While it is possible to replace the existing /storage/.kodi/addons/visualization.projectm/resources/projectM/presets with the new presets folder structure , visualizations only display for approximately 20 seconds before freezing.

ProjectM freezing seems to leave the Kodi interface completely unresponsive to any navigation input which then requires a full reboot of LibreELEC...

src/Main.cpp:123:14: error: ‘struct projectM::Settings’ has no member named ‘datadir’

Following the direction in README.md and using current master 59bba2, I'm getting a build failure.

I'm running Gentoo Linux (I'm trying to package this addon for Gentoo users), have projectm-3.1.0 installed, and I'm using Kodi master bc4995.

I'm getting this error:

/var/tmp/portage/media-plugins/kodi-visualization-projectm-9999/work/kodi-visualization-projectm-9999/src/Main.cpp: In constructor ‘CVisualizationProjectM::CVisualizationProjectM()’:
/var/tmp/portage/media-plugins/kodi-visualization-projectm-9999/work/kodi-visualization-projectm-9999/src/Main.cpp:123:14: error: ‘struct projectM::Settings’ has no member named ‘datadir’
   m_configPM.datadir = kodi::GetAddonPath() + "/resources/projectM";

Here's CMakeCache.txt: https://pastebin.com/8jQ0Z1Ly
And the full build output: https://pastebin.com/pbG3Vt8S

Also, I noticed that there is a .travis.yml in this directory, but Travis doesn't seem to be hooked up, see https://travis-ci.org/notspiff/visualization.projectm

[Question] Where to put textures...

Hi There,

I am a Happy user of projectM for ages. However I am trying out some new presets. They come with a textures folder supplied. Where do I put the textures?

it is a pretty well known pack from http://ghostco.de/milkdrop_pack/ called tryptonaut

undefined symbol: _ZTI5Shape

Been trying for a while to get project-m working on Ubuntu 17.10 for a while, eventually built Kodi from git/master and rebuilt this repo as per instructions except that it is installed to /usr

Still get this error:

ERROR: Unable to load /usr/share/kodi/addons/visualization.projectm/visualization.projectm.so.2.0.0, reason: /usr/share/kodi/addons/visualization.projectm/visualization.projectm.so.2.0.0: undefined symbol: _ZTI5Shape

Project-m is not installed on the target system.

Any ideas how to solve this?

Cheers

wrong release name

Pls use in the future the default kodi naming pattern, that would make distro packaging a lot easier.

v2.2.0 -> 2.2.0-Leia

Border around visualizer on old TV.

I am using Kodi on a CRT TV and after adjusting the overscan, I am getting a border around the top and right of my visualizer in projectM.

Primarily I have it streaming music, and have a visualizer running while I'm working. I setup this machine primarily to make this TV somewhat useful as it came with my house and it's too heavy to take out of my basement.

As you can see from the first picture other elements are scaled properly like the clock, and the now playing information.

There is about an inch cut off from the top and 2 inches on the right that are blank.

Here is a copy of my debug log
kodi.log

Please let me know if there is any additional information needed.

APP_RENDER_SYSTEM is not being passed to ProjectM

I try to build this addon with:
cmake -DADDONS_TO_BUILD=visualization.projectm -DADDON_SRC_PREFIX=../.. -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr/local -DAPP_RENDER_SYSTEM=gles ../../xbmc19/cmake/addons

But for some reason this isn't passed on to this:

visualization.projectm/depends/common/projectm/CMakeLists.txt

Line 4 in 2ab8803

if (APP_RENDER_SYSTEM STREQUAL "gles")

So I had to remove the if statement in order to successfully build and run it on my ODroid board.

FTGL doesn't seem to detect freetype2

I'm trying to build this addon for Kodi Matrix.
All other addons succeed, however projectm seems to fail with:

...
-- Installing: /mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/depends/lib/libfreetype.a
-- Installing: /mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/depends/lib/cmake/freetype/freetype-config.cmake
-- Installing: /mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/depends/lib/cmake/freetype/freetype-config-release.cmake
-- Installing: /mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/depends/lib/cmake/freetype/freetype-config-version.cmake
make[5]: Map '/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/freetype/src/freetype-build' wordt verlaten
[ 39%] Completed 'freetype'
make[4]: Map '/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native' wordt verlaten
[ 39%] Built target freetype
make[4]: Map '/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native' wordt binnengegaan
make[4]: Map '/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native' wordt verlaten
make[4]: Map '/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native' wordt binnengegaan
[ 41%] Creating directories for 'ftgl'
[ 43%] Performing download step (download, verify and extract) for 'ftgl'
-- Downloading...
   dst='/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/download/v2.4.0.tar.gz'
   timeout='none'
   inactivity timeout='none'
-- Using src='https://github.com/frankheckenbach/ftgl/archive/refs/tags/v2.4.0.tar.gz'
-- [download 100% complete]
-- verifying file...
       file='/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/download/v2.4.0.tar.gz'
-- Downloading... done
-- extracting...
     src='/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/download/v2.4.0.tar.gz'
     dst='/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/ftgl/src/ftgl'
-- extracting... [tar xfz]
-- extracting... [analysis]
-- extracting... [rename]
-- extracting... [clean up]
-- extracting... done
[ 46%] No update step for 'ftgl'
[ 48%] Performing patch step for 'ftgl'
[ 51%] Performing configure step for 'ftgl'
-- The C compiler identification is GNU 11.2.1
-- The CXX compiler identification is GNU 11.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

    BUILD_SHARED_LIBS
    CMAKE_INCLUDE_PATH
    CMAKE_LIBRARY_PATH
    CORE_SYSTEM_NAME
    ENABLE_STATIC
    PACKAGE_CONFIG_PATH


-- Build files have been written to: /mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/ftgl/src/ftgl-build
[ 53%] Performing build step for 'ftgl'
make[5]: Map '/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/ftgl/src/ftgl-build' wordt binnengegaan
make[6]: Map '/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/ftgl/src/ftgl-build' wordt binnengegaan
make[7]: Map '/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/ftgl/src/ftgl-build' wordt binnengegaan
make[7]: Map '/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/ftgl/src/ftgl-build' wordt verlaten
make[7]: Map '/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/ftgl/src/ftgl-build' wordt binnengegaan
[ 12%] Creating directories for 'ftgl'
[ 25%] No download step for 'ftgl'
[ 37%] Performing update step for 'ftgl'
Preparing the FTGL build system...please wait

Found GNU Autoconf version 2.69
Found GNU Automake version 1.16.2
Found GNU Libtool version 2.4.6

Automatically preparing build ... done

The FTGL build system is now prepared.  To build here, run:
  ./configure
  make
[ 50%] No patch step for 'ftgl'
[ 62%] Performing configure step for 'ftgl'
configure: WARNING: unrecognized options: --with-ft-prefix
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... armv7l-unknown-linux-gnueabihf
checking host system type... armv7l-unknown-linux-gnueabihf
checking whether make supports the include directive... yes (GNU style)
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
configure: ECHO was not defined by configure so defining manually
checking how to print strings... printf
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert armv7l-unknown-linux-gnueabihf file names to armv7l-unknown-linux-gnueabihf format... func_convert_file_noop
checking how to convert armv7l-unknown-linux-gnueabihf file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for gcc option to accept ISO C99... none needed
checking for gcc option to accept ISO Standard C... (cached) none needed
checking for __func__... yes
checking for ANSI C header files... (cached) yes
checking for stdlib.h... (cached) yes
checking for wcsdup... yes
checking for strndup... yes
checking for X... libraries , headers 
checking for cos in -lm... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for FT2... configure: error: Package requirements (freetype2 >= 9.0.3) were not met:

Package 'freetype2', required by 'virtual:world', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables FT2_CFLAGS
and FT2_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

make[7]: *** [CMakeFiles/ftgl.dir/build.make:92: ftgl-prefix/src/ftgl-stamp/ftgl-configure] Fout 1
make[7]: Map '/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/ftgl/src/ftgl-build' wordt verlaten
make[6]: *** [CMakeFiles/Makefile2:83: CMakeFiles/ftgl.dir/all] Fout 2
make[6]: Map '/mnt/sdcard/src/xbmc19/tools/depends/target/binary-addons/native/build/ftgl/src/ftgl-build' wordt verlaten
make[5]: *** [Makefile:136: all] Fout 2

As you can see freetype has been built and installed as a static dependency.
But the configure script seems to complain with: configure: WARNING: unrecognized options: --with-ft-prefix
Therefore I think it doesn't pickup the dependency?

Upcoming projectM changes: Switching to a C-style API

Hi,

I'm a new team member with projectM and currently working on making projectM more stable and easier to integrate and build.

One upcoming change is that projectM will only provide a C-style API in future releases by default. While this switch makes it feel a bit less "native" in C++ projects, it greatly improves portability and stability of the projectM shared library and also enables integrations in other languages that do not use C++ like Python for example.

You may want to follow development in issue projectM-visualizer/projectm#529 and update the Kodi plug-in in preparation for the next projectM release after the changes are stable and merged into master.

PPA version not installable

$ sudo apt install kodi-visualization-projectm
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 kodi-visualization-projectm : Depends: libprojectm3 but it is not installable
E: Unable to correct problems, you have held broken packages.

Random hangs/lag on preset change

• Hardware: Fire Stick 4K
• Kodi version: 19.2 Matrix (armeabi-v7)
• projectM addon version: 19.0.0-Matrix

When using a preset directory containing loads of .milk presets (in my case 2000+), the random change function sometimes takes up to 3 seconds to switch to a different preset, making the audio stream (probably Kodi itself) hang/stop sound. This is weird, since the hardware should handle that easily, I assume. The presets directory is located directly on the internal memory of the Fire Stick 4K.

I already opened an issue over at projectM's main repo here: projectM-visualizer/projectm#545

It would be nice if someone could investigate this. Thank you.

Kodi crashing when projectm is installed

Hi,

I am experiencing crashes when projectm is installed on my system. Crashes occur when starting music or live tv. Disabling the addon in kodi does not make the issue go away, I have to use apt to remove kodi-visualisation-projectm. I do not need to restart kodi to for the crashes to stop, removing the package is enough.

Crash logs of the issue:
AMD gpu
https://pastebin.com/g7BH7qL2
https://pastebin.com/5jUEp7s9
https://controlc.com/b013d3c7
https://controlc.com/acc747c4

Intel GPU
https://paste.kodi.tv/nusotisaho.kodi
https://paste.kodi.tv/idovexupus.kodi

System is ubuntu 20.04 with kodi 19 installed. This issue happens on two systems, both intel cpu's, with one using the igpu and the other using a amd gpu. Both systems have almost identical software installed, with tweaks for each brand of gpu.

I have been able to consistently reproduce the issue/fix on both systems.

Forum thread about the issue below
https://forum.kodi.tv/showthread.php?tid=365755