Kodi 18.2 Visualizations

Hi on the old kodi i had a Visulisation that worked, is there any for the new version?

1 Like

Which visualisation did you want to use?
Unfortunately the Shadertoy add-ons no longer work as expected.


any sam, yeah thats the one i had installed.

Just something so when musics on its not a plain screen

You could configure the Artist Slideshow addon to give you something to look at while the music’s playing …

yeah i’ve got that, just like something that moves, thanks any ways

I really would like to be able to use Waveform, something simple to work along with my Ambilight.

Bumping this as I too miss visualizations from Kodi. Shadertoy has never worked for me. And when you look to install another visualization from the repo. There is none listed to install.

Hope somebody can pass a link to a download of a visualization that 100% works with Vero4K+

Thanks for reading.


I would also like to be able to use the Music visualizations when playing music.

Thanks in advance!

Unfortunately I still don’t have a solution for this, but I am looking in to it.

I have the goom visualization working on the vero. (goom is basically a bunch of smoke effects)
you can get it from my repo:

I’ve also got a working shadertoy. But I don’t have it in my repo. (I don’t recall if the one I have is the one I compiled myself, or the one I got from kodirepo/zips/visualization.shadertoy at master · virserg/kodirepo · GitHub ) Note for shadertoy, I couldn’t get any version newer than 1.1.10 to work.

1 Like

Have you, or perhaps @virserg, or @gmc attempted to build ProjectM lately? It seems more compatibility improvements have been made…

I’m trying to give projectM another shot. Some of the dep projects they included in it and are forcing a build on are a bit messed up, (and a decade out-of-date). I don’t think they are giving ARM much love. At least not on the Leia branch. (seems to be more going on in Matrix) I think I may be able to get it to build, but I’m not holding my breath that it will work. From what I recall when running it under i686, it was quite the CPU hog, so not sure if the Vero has the horse-power for it.

Well, the good news is that I was able to compile and install it. The bad news is it immediately crashes kodi when I switch to the music/visualization screen. The debug logs don’t seem to be capturing anything useful about why.

2020-08-04 00:47:17.892 T:4049593056 DEBUG: LIRC: - NEW 174 0 KEY_ZOOM linux-input-layer (KEY_ZOOM)
2020-08-04 00:47:17.896 T:4067569664 DEBUG: HandleKey: 213 (0xd5, obc42) pressed, action is FullScreen
2020-08-04 00:47:17.896 T:4067569664 DEBUG: Activating window ID: 12006
2020-08-04 00:47:18.219 T:4067569664 DEBUG: ------ Window Deinit (MyMusicNav.xml) ------
2020-08-04 00:47:18.222 T:4067569664 DEBUG: FreeVisualisation() done
2020-08-04 00:47:18.228 T:4067569664 DEBUG: ------ Window Init (MusicVisualisation.xml) ------
2020-08-04 00:47:18.228 T:4067569664 INFO: Loading skin file: MusicVisualisation.xml, load type: KEEP_IN_MEMORY
2020-08-04 00:47:18.295 T:4067569664 DEBUG: FreeVisualisation() done
2020-08-04 00:47:18.296 T:4067569664 DEBUG: ADDON: Dll Initializing - projectM
2020-08-04 00:47:18.296 T:4067569664 DEBUG: SECTION:LoadDLL(/home/osmc/.kodi/addons/visualization.projectm/visualization.projectm.so.2.3.5)
2020-08-04 00:47:18.296 T:4067569664 DEBUG: Loading: /home/osmc/.kodi/addons/visualization.projectm/visualization.projectm.so.2.3.5
2020-08-04 00:47:18.300 T:4026528480 DEBUG: CActiveAE::ClearDiscardedBuffers - buffer pool deleted
2020-08-04 00:47:18.337 T:4067569664 DEBUG: CAddonSettings[visualization.projectm]: loading setting definitions
2020-08-04 00:47:18.339 T:4067569664 DEBUG: CAddonSettings[visualization.projectm]: loading setting values

1 Like

I tried your build of the goom visualization (thanks for that) but the performance was quite poor on my Vero 4K so I guess I shouldn’t be that hopeful for projectM anyway…

Then gain, Milkdrop ran great on my circa-2000 PC so it can’t require that much computing power, can it?!

Goom is OK on the vero if you leave it at the lowest resolution (512x256 I think), which I had set as the default I think.

You did. It looks quite poor though when compared to it running in the higher resolution on a RPi 4 w/ LibreElec unfortunately. I for one appreciate the effort to get this working though.

1 Like

CPU/GPU wise, I’m not sure what is different between the Vero and a RPi that would make a difference on performance.

I suppose it’s possible that there are compile settings (eg,using different libraries, etc) that would work better. Maybe Sam would have some suggestions along those lines. I was just happy to get it to compile and run at all.

1 Like