Closed irishgordo closed 3 months ago
Will have to look at the startup sequence & variable instantiation 😄. Thanks for the solid issue! Luckily it doesn't affect anything after the first song.
I guess I'm curious as to what the difference is between running this from source off the master branch in comparison to running this off a .deb / .snap package. As with running from an installed .deb package in my system, for some reason, Discord isn't really getting any updates from Tidal HiFi, it just seems to hang at "Browsing Tidal".
Snaps are sandboxed by default and need to be allowed to talk to system interfaces.
Hey there, this project is awesome!
I was noticing some strange issues with Tidal HiFi updating Discord with either a:
On my loadout (system) of:
I decided to try to build it from source (after uninstalling either .snap or .deb) utilizing:
And after tossing some
Logger.log
messages inside thesrc.scripts.discord.ts
I was noticing that it seems to be resolving itself mostly!The one thing is that I guess on launch, if a music file was already present in tidal hifi, like picking up where the user was previously listening to the track, I was catching a lot of logs w/ my custom log entry of
media is paused...
but the media wasn't paused it was playing.In the
discord.ts
I had just modified this chunk to see some log data:Workaround
Even if it is displaying media is paused when the media is playing at first launch, the moment you switch to another track it resolves itself to actually show that track information in Discord accurately.
Questions
master
branch in comparison to running this off a .deb / .snap package. As with running from an installed .deb package in my system, for some reason, Discord isn't really getting any updates from Tidal HiFi, it just seems to hang at "Browsing Tidal".Additional context, Discord is installed on my little rig via just the package manager.
I think for now, just doing an
npm compile
&npm run start
alleviates Discord from not seeing updates - wondering though if it's possible to debug the .deb package to see what differences might be in the loadout.