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

🐛 Bug Report: Stops recognising new songs after 2 #994

Open
Kayrah87 opened this issue Jan 16, 2024 · 7 comments
Open

🐛 Bug Report: Stops recognising new songs after 2 #994

Kayrah87 opened this issue Jan 16, 2024 · 7 comments
Labels
4.x.x bug Something isn't working

Comments

@Kayrah87
Copy link

📜 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

@Kayrah87 Kayrah87 added the bug Something isn't working label Jan 16, 2024
@aw-was-here
Copy link
Collaborator

aw-was-here commented Jan 16, 2024

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.

@Kayrah87
Copy link
Author

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.

@aw-was-here
Copy link
Collaborator

aw-was-here commented Feb 10, 2024

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.

@aw-was-here
Copy link
Collaborator

I'm hoping this one is fixed in 4.2.0 RC1, esp since I can't reproduce this one.

@RoughTradeRadio
Copy link

RoughTradeRadio commented Oct 17, 2024

New to the program, it seems to be just what I was looking for. I downloaded 4.1.0 and was having the no updating after 2 songs issue as well. I switched to 4.2.0 RC1. Sometimes it'll work flawlessly and then there's other times it won't work at all and then other times it'll do the 2 song and stop. I'm using Windows 10, Xsplit and VirtualDJ and the text file output. It does get pulled by Xsplit so I can display the song title on screen when it works. Please let me know what you need and how to give you feedback here. Update since original post: For science I installed 4.0.6 to see what would happen—it works flawlessly for what I need it to do.

@Kayrah87
Copy link
Author

Kayrah87 commented Oct 18, 2024 via email

@RoughTradeRadio
Copy link

@Kayrah87 I uninstalled the 4.1.x versions off of my PC, cleaned out the C:\Users directory for this program, and did a fresh install of 4.0.6. It works perfectly (except for nagging me to upgrade to 4.1.0 every time I open it; I just click cancel). I spent hours playing with it last night without encountering any glitches. I also turned on OS notifications so I could make sure the data was updating. It was. 4.0.6 is super fast too; it writes the text file in 10 seconds or less, whereas the 4.1.x versions take a minute or more to write the data, if it even does at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.x.x bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants