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

Multi-instance Support #10

Open
pmm26 opened this issue Nov 25, 2023 · 1 comment
Open

Multi-instance Support #10

pmm26 opened this issue Nov 25, 2023 · 1 comment

Comments

@pmm26
Copy link

pmm26 commented Nov 25, 2023

Are there any plans on adding multi-instance support?

I'm doing this Web Application for my TeamSpeak server where people can make channels. I was thinking of giving each channel a MusicBot and for this multi-instance would be great because it would save a lot of resources.

I know things like Spotify would not work because you can only play 1 song at a time but even if it's just YouTube would be really nice.

Before I was using:
https://github.com/Splamy/TS3AudioBot
Which has multi-instance and uses a self written TeamSpeak Client.
But the project has been dead for a while now.

Are you still interested in developing this bot? I'm also a developer maybe we can share some notes if you are still interested?

If you want add me on discord: hardrevo

@Bettehem
Copy link
Owner

Multiple instances is technically possible even with spotify (if using ncspot as the player), but the current issue is that the bot just monitors your default output device so anything outputted to it would be captured by the bot.

There are two workarounds currently:

  • Add another user onto the system and use the second instance of the bot there, though this works best if you can have a new audio output for each instance. I haven't looked at pulseaudio to see how e.g. a new dummy output could be added for each instance, but that is probably something we need to figure out for proper multi-instance support.
  • Have a vm for each instance of the bot. This is the easiest way and doesn't need any workarounds, but is also the most resource-intensive option. Running a new vm for each instance isn't very efficient.

As an upcoming option, docker support will be a less resource-intensive option than running a full vm.

This project is still in active development so you are welcome to contribute :)

I don't use Discord though. One of the reasons I started developing this bot was because me and my friends moved back to TeamSpeak and away from Discord😄

We can continue the conversation here or via email, or if you want to use some instant messaging platform, you can find me on telegram: @bettehem

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