Open Serhann opened 6 years ago
Anything in Lavalink server console?
Its my lavalink.js bot console:
Serhans-MacBook-Pro:Lava serhanergoren$ node index.js
LavaLink testing bot is ready!!!!!!
No available voice nodes.
Its Lavalink server console:
[12:38:41] [ INFO ] [Launcher] Started Launcher in 7.108 seconds (JVM running for 8.511)
[12:38:41] [ INFO ] [Launcher] OS: Mac OS X, Arch: x86_64
[12:38:41] [ WARN ] [Launcher] This system and architecture appears to not support native audio sending! GC pauses may cause your bot to stutter during playback.
[12:38:51] [ INFO ] [[/]] Initializing Spring FrameworkServlet 'dispatcherServlet'
[12:38:51] [ INFO ] [DispatcherServlet] FrameworkServlet 'dispatcherServlet': initialization started
[12:38:51] [ INFO ] [DispatcherServlet] FrameworkServlet 'dispatcherServlet': initialization completed in 31 ms
[12:38:51] [ INFO ] [AudioLoaderRestHandler] GET /loadtracks
[12:38:51] [ INFO ] [GarbageCollectionMonitor] GC monitoring enabled, reporting results every 2 minutes.
[12:38:53] [ INFO ] [AudioLoader] Loaded playlist Search results for: song
Really not sure can you make sure the details are correct for the node like, host, port and password?
its my application.yml:
server:
port: 2333
address: 0.0.0.0
lavalink:
server:
password: "youshallnotpass"
ws:
port: 80
host: 0.0.0.0
sources:
youtube: true
bandcamp: true
soundcloud: true
twitch: true
vimeo: true
mixer: true
http: true
local: false
sentryDsn: ""
bufferDurationMs: 400
and its my lavalink.js nodes:
const nodes = [
{ host: "localhost", port: 80, region: "eu", password: "youshallnotpass" }
];
if you're running localhost host: 0.0.0.0
is not needed same with server address but all looks correct weirdly enough (mind me Lavalink has been recently updated x.x)
Now seeing Lavalink server has been updated let me get the latest build and test
Seems to work fine on my end tho i am on windows
but not working on Mac
i'm tested in windows, its workin nice. its lavalink's problem
This is probably related to this issue: https://github.com/sedmelluq/jda-nas/issues/6
Luckily this can be easily patched downstream by packaging the missing native into the jar that runs lavaplayer with jda-nas (we do that for FredBoat selfhosters). Alternatively turning off the native audio system if OS X is detected could work, with potential drawbacks which might be irrelevant for your scale. Either way, you would need to PR the solution to the lavalink server.
On a side note, I don't quite understand why one would use lavalink on a Mac, as it is mostly intended to distribute the load for giant bots and I'm not aware of affordable and reliable hosting options on OS X, so don't be surprised if there are other pitfalls, because OS X is not really in scope for the project afaik. You can save yourself some hassle by setting up a remote node on a cheap VPS.
I'm testing lavalink and i have a one node now.
And when i say ".play " it saying "No available voice nodes."