Closed insign closed 3 years ago
@insign Can you run which vlc
?
which vlc
/usr/bin/vlc
While I was testing it myself, I also noticed that vlc would sometimes stall. Does this happen all the time or only occasionally? Perhaps we can fix this by waiting much longer for web requests to respond.
Always, but I don't get why need a web request if my file is local. Or it is to install vlc?
To use vlc, we launch the executable with command arguments that make it launch local server that we connect to in order to provide it files to play via VLC API.
Understood. Have you any clue how to fix?
@insign After creating a new Audic instance check if a vlc process ever appears in the process list.
No, it doesn't .
It must be having some sort of trouble hosting the web server. Try running vlc --extraintf http --intf wx --http-host <YOUR INTERNAL IP ADDRESS> --http-port <AN UNUSED PORT> --http-password <ANY PASSWORD>
. If it works, try navigating to the address and port you specified in the command and use the password when prompted.
If the site loads, install the internal-ip
npm package and see if the promise returned by internalIp.v4()
resolves with a value that is not null. If it resolves with null, we can pass this issue to that package.
If the site doesn't load or the command fails, be sure to provide the command output.
Now I'm on Linux, ArchLinux, Gnome. I tried reinstall audic, but clearly it doesnt compile vlc, as did in Windows, not sure if is related to the problem... Maybe in Linux it doesn't need compile vlc, which is already installed here...
ready.js file
yarn v1.22.10