You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
some modders decides to be "outsmart" watermedia and uses native callbacks to handle events in native threads (which causes deadlocks and a lot of JVM complains)
this was something addressed by watermedia using the tick-based api and some helpers but nothing stops devs to still use vlcj callbacks
Objective
remove lib-vlcj and base the new new PlayerAPI on native methods (vlcj-natives) instead of the VLCJ
Expectations
v3 API was conceptualized to make possible have multiple impl of a player (including VLC) and let API decide witch player is way better for your PC (FFMPEG or VLCJ). Next implementations might be placed on https://github.com/WaterMediaTeam/watermedia-binaries
The text was updated successfully, but these errors were encountered:
some modders decides to be "outsmart" watermedia and uses native callbacks to handle events in native threads (which causes deadlocks and a lot of JVM complains)
this was something addressed by watermedia using the tick-based api and some helpers but nothing stops devs to still use vlcj callbacks
Objective
remove lib-vlcj and base the new new PlayerAPI on native methods (vlcj-natives) instead of the VLCJ
Expectations
v3 API was conceptualized to make possible have multiple impl of a player (including VLC) and let API decide witch player is way better for your PC (FFMPEG or VLCJ). Next implementations might be placed on https://github.com/WaterMediaTeam/watermedia-binaries
The text was updated successfully, but these errors were encountered: