Thanks. I can see why you get that result, but I canāt tell whatās causing it 
. Can you provide me a 30 second clip that can be used to reproduce that issue? Just send me a PM with the link to it if possible.
Done.
I am having problems with Goom visualisation for music.
So far only have been watching videos since the Kodi 21.1 update. Today I am listening to music and noticed Goom not starting when listening to music.
I have deactivated and activated it again, and restarted system, however goom wonāt start up.
Goom version 21.0.0
While typing in this post on pc which is in another room, going back to the tv goom was running in the backround.
Iāll make some more tests and will give an update.
We need more information to advise.
Donāt know why goom got triggered to start while typing the last post.
What happend when it got activated:
Entered music album directory, selected first song and started playing it. After goom not getting activated after 2 minutes went back to main kodi screen and entered the addons directory and displayed the info of the goom plugin (music still playing). After I posted the first entry on it here, going back to the tv room in the background of the goob plugin information displayed on screen and the music still playing, in the background the visualisation was running. Somehow it got activated.
However I could not reproduce it 
Goom wonāt start/activate, even when doing the same as before while posting the first entry on it
Have also activated two other visualisations plugins to check if these are getting triggered to start: shadertoy and starburst
None of the three trigger when selected. No clue, why goom got triggered once in the addon/plugin selection menu while the details of the plugin were displyed on screen for a while.
Will probably make tomorrow a debug log, if this could help to identify the problem.
redacted
Still a happy user 
Actually this isnāt quite right (In relation to the Vero, we never set a custom cache on the Raspberry Piās). I did extensive testing on a Vero 4K and V to determine the optimal cache setting and found there was no longer a benefit to running that large of a cache with the current OSMC builds. I tested it with a variety network configurations (including speed limited) with files of different types and sizes and could not find any gain from going above 40MB. Kodi v21 default is 20MB and that size I found caused crashes in some situations during repeated playback. We therefore configured the default setting in OSMC such that it would automatically get set at 40MB during the upgrade, or if you press the reset default button in its settings page. I found that setting the cache to 512 actually slowed how long it took for playback to start which was an additional factor in favoring a smaller cache size. As for the buffermode 1 has been Kodiās default setting for a while now but it just never got taken out of our system level advancedsettings.xml file. I let the read factor and chunk size stay with Kodiās defaults as they seemed to work as well as any other sane setting I tried.
Feel free to experiment to see if you can find something that works better in your particular setup. Iād suggest to actually test it instead of just assuming bigger is better, or what used to be optimal, still is after many changes to the software stack.
Actually this isnāt quite right (In relation to the Vero, we never set a custom cache on the Raspberry Piās).
Youāre absolutely right. I forgot to mention this is only for the Vero devices.
We therefore configured the default setting in OSMC such that it would automatically get set at 40MB during the upgrade, or if you press the reset default button in its settings page.
I had a whole other experience testing out different configurations on my Vero V. Perhaps due to my personal setup (NFS via systemd unit, Wired, UTF-6 and UTF-8 lines, Gb Switch, DS923+ with link aggregation, Gb Router, fiber connection).
Anyway, you made a very good point. Should have thought about that before posting. Iām sorry. I will redact my post.
Canāt get visualisation to run.
Goom is selected for visualisation. Debug log:
https://paste.osmc.tv/ajutolocun
@RStr I activated Goom visualization on a Vero V and Vero 4k+ ā¦ and it works like a charm (at least with the lower both resolutions settings; the highest resolution setting looks a bit jerky). I canāt see in the logs what your local problem is ā¦ but it is not a general class issue affecting all others.
Previously it worked without problems. Havenāt changed anything on the system except for updating the vero. I think before the last update it took the visualisation addon goom to kick in 2 minutes after starting a music track. Not sure anymore, if it was after 2 or 1 minute, but tending to the 2 minutes.
This doesnāt sound right. Were you using the screensaver to show visualizations? Have you tried manually switching to full screen during music playback?
Here the Gloom visualization addon starts immediately with the playback. Not sure whether this helps but these are my skin settings perhaps being related:
settings -> interface -> screensaver -> Audio -> Disable Screensaver ... (enabled)
settings -> interface -> skin -> configure skin -> Background -> Show Background visualization (enabled)
settings -> interface -> skin -> configure skin -> OSD -> Music OSD -> Open music fullscreen automatically (enabled)
settings -> interface -> skin -> configure skin -> OSD -> Music OSD -> Idle time until ... (1 min)
There is also this option to automatically switch to fullscreen when music playback starts.
settings > media > music > switch to visualization on playback
Indeed, @darwindesignās found setting hides in the setting
<setting id="musicfiles.selectaction" default="true">false</setting>
in the logs but the default is
<setting id="musicfiles.selectaction">true</setting>
Means, this feature is deactivated to start immediately on your system.
Addition: @darwindesign informed me that the logic is the other way around. Anyway, try enabling this flag in the menu.
That did the trick It was switched off and after enabling it, it is back to pre update functionality
First time ever I have been in the skins settings menu.
Thanks a lot!
I wanted to do a fresh installation of OSMC/Kodi21 on a Vero 4K+ via an USB stick.
I utilized the Windows version of the downloader and selected the latest August image.
When the installation was finished, system information within Kodi showed a version of 20.5 compiled May 25th. I had to go to MyOSMC and update to Kodi 21. Is this is a bug in the August image or an expected behavior?
The installation images tend to trail the release of updates with a bit of a delay. I assume Sam probably wants to make sure that any minor updates and fixes are out of the way before building a full image.