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

Local Soundtrack.io Stuck on "No Playlists" Loop #140

Open
CowDotDev opened this issue Feb 10, 2015 · 1 comment
Open

Local Soundtrack.io Stuck on "No Playlists" Loop #140

CowDotDev opened this issue Feb 10, 2015 · 1 comment

Comments

@CowDotDev
Copy link

@chrisinajar Do you know what is happening here, or what I need to do to get passed this? Martin mentioned that you touched that area, so maybe you'd know.

I am loading Soundtrack.io on my system locally with mongod and redis-server running, and when it gets to the Room portion of the soundtrack.js file it gets stuck on the loop that looks for Playlists. So it just prints no playlists to the console. The initial run of soundtrack.js created the room and asked for a restart, and when I ran it the second time it showed that 1 room was created but got stuck on the loop.

I've check the database to make sure everything was created that should have been and it all looked good. Were there supposed to be default playlist/tracks created as well?

@chrisinajar
Copy link
Contributor

Yes, it's very very hard to break out of. I committed a few other small tweaks already to make this a little easier along with the bandcamp stuff. Here's what I remember...

  • First, find the if (err) line that causes the infinte loop and let it break so that it can continue. Once you get it up, it will error and bitch and moan and freak out
  • queue a bunch of songs anyway using manual posts.
  • Restart it
  • The queue will now work and continue to work until it's empty then it explodes again.

To get the empty queue to work, you must have queued songs at least 24 hours ago. You can get around this by editing that silly time function and making it start from tomorrow, and increase the window from 3 hours to 24.

Your best bet it to just get songs in to it by whatever bashing and mashing you can, then revert all your changes and wait until tomorrow.

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

2 participants