• 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 7
Linux v18, no visualisations / screensavers work, projectM crashes
#46
(2018-10-01, 22:36)3dfx Wrote: Which issue(s)?
So it should be fixed in the next nightly builds? [emoji848] 
 
these two:
https://github.com/xbmc/xbmc/pull/14491
https://github.com/xbmc/xbmc/pull/14503

yup, please test the next nightly if it fixes your issue.
Do not PM or e-mail Team-Kodi members directly asking for support.
Always read the Forum rules, Kodi online-manual, FAQ, Help and Search the forum before posting.
Reply
#47
to clarify: the codec info screen was removed from kodi in v17.
https://forum.kodi.tv/showthread.php?tid...pid2273270

it was later re-implemented in a different manner, but only for videos.
currently no such functionality exists for music.
Do not PM or e-mail Team-Kodi members directly asking for support.
Always read the Forum rules, Kodi online-manual, FAQ, Help and Search the forum before posting.
Reply
#48
(2018-10-01, 23:13)ronie Wrote: to clarify: the codec info screen was removed from kodi in v17.
https://forum.kodi.tv/showthread.php?tid...pid2273270

it was later re-implemented in a different manner, but only for videos.
currently no such functionality exists for music.
I know, but there is a kinda likel codec info even if it's not that what was in v16 (see the picture I've posted). And what's there is enough for me.
Kodi 21.0α | Ubuntu 22.04.3 | Kernel 6.4.x | intel i5-12600K | Gigabyte Z690 Gaming X DDR4 | Corsair 2x8192MB (DDR4-3200) | HDPlex H5v2 | HDPlex 400W HiFi DC-ATX | Pioneer VSX-934 | LG 65B7D
Reply
#49
@ronie hey man, ok didn't realize that codec info was removed. but still lock preset still isn't working on a build that includes latest fixes.
Reply
#50
Do you build yourself as the newest fix only got merged today so won’t be in nightlies until tomorrow.
Reply
#51
Self compiled, I saw the fix in the list after "git pull".
Reply
#52
Just upgraded from nightly ppa and can confirm that presets are still not lockable.
Kodi 21.0α | Ubuntu 22.04.3 | Kernel 6.4.x | intel i5-12600K | Gigabyte Z690 Gaming X DDR4 | Corsair 2x8192MB (DDR4-3200) | HDPlex H5v2 | HDPlex 400W HiFi DC-ATX | Pioneer VSX-934 | LG 65B7D
Reply
#53
See https://github.com/xbmc/xbmc/pull/14503, ksooo says his fix wasn't really about the issue we are talking about here ... can anyone clarify this? @ronie ?
Reply
#54
i can only repeat what spiff said, there appear to be multiple issues preventing locking to work... we're trying to fix them one by one ;-)

at this moment locking appear to work with some addons (milkdrop) but not with others (milkdrop2).
please list the ones you've tested and whether locking works or not.
Do not PM or e-mail Team-Kodi members directly asking for support.
Always read the Forum rules, Kodi online-manual, FAQ, Help and Search the forum before posting.
Reply
#55
I can only test projectm. Tried to compile milkdrop, milkdrop2 but that didn't seem to work at all. 

Goom, Waveform and spectrum did compile. Goom gives me only a black screen and others don't have any presets to choose from .....

boba
Reply
#56
md and md2 is windows only (they use directx). goom has no presets.
Reply
#57
Ok, thx for the clarification ... btw, a little off topic, but inputstream.rtmp fails to build at the moment as well @spiff, I get recipe failed when trying to build it.
Reply
#58
i need more info. it builds fine for me.
Reply
#59
Well,

clean git checkout, lubuntu 18.04.1, everything else builds fine, kodi itself plus other binaries, just rtmp fails using:

sudo make -j$(getconf _NPROCESSORS_ONLN) -C tools/depends/target/binary-addons PREFIX=/usr ADDONS="inputstream.rtmp"

what other info would u need? other than the recipe failed for rtmp.o errors I don't see much more clarifying output ....
Reply
#60
you pick the line saying the same thing that you are telling me - it didn't work.

i need the real, actual information. the error message from the compiler, not the failure line from make. disable the build jobs. pipe output to a file. show me.
anyways, you did show me how to reproduce. the problem is that it picks up the system openssl libs, and those are 1.1 while add-on relies on 1.0.

i always build against system librtmp etc so i had not noticed. will get it fixed, somehow, but not now, i have lectures to prepare! i need to stop procrastinating lol.
Reply
  • 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 7

Logout Mark Read Team Forum Stats Members Help
v18, no visualisations / screensavers work, projectM crashes0