Skip to content

Commit 0db3f20

Browse files
committed
v2026.3.48
* Fixed a critical bug in the script boot sequence following a platform update. (issue #92) * Fixed a minor bug where volume ease up was not triggered on a new session when no audio was played before. (issue #90) * Fixed a minor bug where Subscribe now button was not removed properly. (issue #89) * Fixed a minor bug where the self diagnostic tool was confused about the need to reload the script. (issue #85) * Added a Q&A in troubleshooting documentation for disliked tracks playing when connected to a free account with expired audio rights. And modified the boot notification message. (issue #86)
1 parent 1021524 commit 0db3f20

3 files changed

Lines changed: 8 additions & 3 deletions

File tree

DIUserscript.meta.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,5 +32,5 @@
3232
// @grant GM_xmlhttpRequest
3333
// @inject-into page
3434
// @run-at document-start
35-
// @version 2025.10.956
35+
// @version 2026.3.48
3636
// ==/UserScript==

DIUserscript.user.js

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

doc/troubleshooting.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
# Troubleshooting
22

3+
## Disliked tracks are playing when connected to my free account with expired audio rights
4+
* The script is doing a great job at making audio work as seamlessly as possible at any given time and under any situation, but using a free account with expired audio rights is bound to unravel some unhandled situation like this one where the player is loading disliked audio tracks.
5+
* It is not a fixable issue but a workaround exists: you should create a new account and use the export/import of likes and dislikes to transfer over your new account. If you always use the script, free audio rights should not expire with the new account.
6+
* From issue #86
7+
38
## Sometimes, chrome and firefox will disable tampermonkey or my userscript manager for some reasons.
49
* Please make sure they are installed and enabled before opening any issue here.
510
* Before reporting a problem with chromium, enable developer mode in extensions and Tampermonkey : [issue #81](https://github.com/lethak/LTKDIFMU-userscript/issues/81)

0 commit comments

Comments
 (0)