Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discord RPC Issues #6

Open
SPIKEYPUP opened this issue Oct 19, 2024 · 0 comments
Open

Discord RPC Issues #6

SPIKEYPUP opened this issue Oct 19, 2024 · 0 comments

Comments

@SPIKEYPUP
Copy link

First off let me say: Thank you @nekusu for this great patcher program! The new script works very well and is easy to follow and use!

Issue: Discord Rich Presence for Tidal App fails to function with Discord if the following conditions occur:

1. If the Tidal App is started before the Discord App, Rich Presence does not work.

  • Discord does not see the app or show any activity if the Tidal app was started while Discord was not running.
  • Toggling the Rich Presence item in the tray icon menu (on-->off-->on) while in this state does not correct the condition.
  • In order to begin to receive Rich Presence in Discord, the Tidal App must be restarted while Discord is running, upon
    restarting the Tidal App, Discord immediately sees the Rich Presence information and creates the activity.
  • This can be a bit inconvenient if you have Tidal set to startup with Windows and Windows loads Tidal before Discord is loaded.

2. Rich Presence stops working if the Tidal App has idled or not played anything for a while.

  • After some time, if there has been no playback in the Tidal App, Rich Presence stops working. In this state no Ridal Rich Presence activity or information is displayed in Discord when you resume or begin new playback.
  • Toggling the Rich Presence option in the Tidal tray menu (on-->off-->on) does not correct the condition.
  • In order to restore Tidal Rich Presence in Discord in this state the Tidal App must be restarted. Upon restarting the Tidal App, Discord immediately sees the Rich Presence information and creates the activity.
  • This is not ideal for the user, who is more than likely expecting the RPC to always be working. Users not aware of the issue will assume it is functioning when in fact it is not. To ensure that the RPC is Working (after a lengthy period of idle activity / no playback) the user must: start playback, go into Discord, then check their activities/profile for the Rich Presence info, this is cumbersome. It's becomes a guessing game of "Is it functioning or not?" which leads to extra steps the user must take or unnecessary Tidal app restarts on occasions the user doesn't check the status and decides to just restart Tidal regardless.
  • Personally, if I've not been listening for a while, I don't waste time verifying the RPC anymore... It's simply faster to just restart the Tidal App without checking the current state of the Rich Presence function, it's probably unnecessary sometimes but it is faster than verifying...

Thanks again for your time and effort, it's much appreciated! If I can be of further assistance please don't hesitate to ask.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant