Release is out, links have been updated.
Wait, is the fix in this v0.15.2 or it will be after this version?
yes, should be in
There have been asks to support the project with more than 3$.
So i added a new tier “Patron” for 5$.
There are no additional Featuers coming with this tier, it just helps with:
- developing more features
- possibly buy test devices
Just for those who want to. 
Any plan for jelkyfin as player?
you can configure it as custom player in the settings already
1 Like
After testing it multiple times, issue still exists. Here are my observations using the same test video:
- When I played the video from the start, the issue happens 100% of the time by the time it reaches that slow part
- When I tried seeking directly to the slow part, sometimes it happens sometimes not. Out of 10 times I seek directly there, 9 out of 10 the issue occurred.
- The number of extra strokes in the slow part is less on the tests where I seek directly to the slow part compared to when I started the video from the beginning
Ah very nice.
ok, then it could be something unrelated to what i found, please DM me a diagnostic bundle, the video file and the script (gofile/pixeldrain)
__
found a second thing that could possibly lead to this.
Fixing right now, will send a new build when its ready.
__
i will also add an override option for linerar/oscilate devices in the device settings soon
here is the video and script im using for testing Gofile - Cloud Storage Made Simple
i will check
in the meantime please check if the new fix is helping in any way
We are almost there. The issue happens rarely now. Here are my current observations:
- 9 out of 10 I played the file either from the beginning or from seeking directly to the slow part, the issue did not occur
- Whenever the issue occurs on that entire slow section of the video i’m using to test, only 1 extra stroke is added compared to the previous versions where 3-5 extra strokes occurs on that entire slow section
ok, i did one other change please test this version
the override option is also in this version,
please tell me if the oszilation mode is better than the linear mode
So still the same observations I have last time (where it only happens rarely, maybe around 10% chance of it occurring). Tried forcing linear and it has same results as using auto. Tried forcing Oscillation and it obviously does not follow the script properly as its just speed so its quite understandable.
then i need to dig deeper, please dm me a diagnostic bundle maybe i find something
Considering that it happens very rarely now on my device, we can’t rule out the possibility that maybe this is a now just a bug on lovense solace pro or maybe just on my specific device itself. At this point, we need more testers. If the issue doesn’t happen on other devices besides lovense solace pro using intiface integration, then the issue might really be on my device itself. Unfortunately, I don’t have other devices to test.
i will keep it on my list
I’ve notice this since 2 versions ago I just forgot to report it but sorting in List view is broken, just look at this
Card view totally works fine using the sorting in lower left.
will check, thx for the report
