🐛 Bug Report: Stops recognising new songs after 2
Kayrah87 opened this issue · 4 comments
📜 Description
It appears to stop picking up file system changes after the first two tracks. It becomes stuck on the second track and will not proceed
👟 Reproduction steps
When I load a DJuced playlist I play the first track in deck 1. The template shows in in OBS and the twitchbot receives the first track info in the chat.
I load the second track into deck 2. When I hit play the template changes in OBS, and the new track title is sent to twitch chat.
I load the third track into deck 1, but when I hit play nothing changes on the template and no track info is sent to twitch chat.
I have checked playing.txt and can see that DJuced is updating the file accurately. I have also paused Onedrive as I suspected that might be causing issues, but the issue persists
👍 Expected behavior
The template updates and the twicth chat receives the new track info
👎 Actual Behavior
It remains on the second track info, and does not update either the template or the twitch chat.
💻 Operating system
Windows
💻 Chipset/CPU
Intel
💻 Input source
Other
🧱 Your Environment
I use DJuced for local tracks. I use OBS straight to Twitch. I have a number of visual sources in the scene but I doubt they have anything to do with it.
I run Discord in the background and use VRChat in the foreground for my vtube avatar.
Note that the issue persists when VRChat is closed.
I have paused Onedrive syncing but the issue persists.
debug.log
I agree, it definitely sounds like a bug in file change detection. I'll see if I can reproduce. It has been a while since I fired up DJuced so maybe something has changed with it.
For additional info, I have set up Traktor as my main DJ app to test functionality of the now playing software, and that works absolutely fine. The difference obviously being icecast vs file watcher, which probably helps narrow it down. Hope that helps.
Hmm. Trying this on Win 11 w/DJuced 6.0.1 and it is definitely picking up the 3rd track. I'm working on getting a release out and have a few fixes for other things so it may be an existing bug that is already fixed. Let me upgrade to 6.0.6 and see if that broke things.
I'm hoping this one is fixed in 4.2.0 RC1, esp since I can't reproduce this one.