Are the nodes you found node red nodes or just npm nodes? Only node red nodes are referenced in the flows database. If they are node red nodes then please share some links to them.
But as some time in the past I am sure I saw a VLC node for Node-Red.
I was going to design a remote control but never got around to it because of a machine being difficult. Now I have the machine back online: the node isn't there any more.
VLC supports remote control via sockets but I am not good enough to understand what the syntax is to make my own flow the hard(er) way by messages sending discreet messages rather than the luxury of using a node.
This is a link - which yeah: says NPM - but also says/mentions Node-Red.
My flow is nowhere ready to be shared but I’ve succeeded to do this by running an MQTT wrapper daemon on the pi that listens to specific music related commands. I use Music for Console (sudo apt-get install moc, then start it as mocp) as audio player, as it allows to be fully controlled through commands, and the interface is just an ncurses thing connecting to the internal server doing exactly that.
From Node-RED I send commands over MQTT that are subscribed by the daemon on the remote pi. Those commands are then interpreted and used to call a subprocess task to execute those commands. Works perfect, but creating an interface I’m happy with is taking time. So now I press the correct inject button for half of the commands, and still do the “ssh -> type mocp command manually” route most of the time as I’ve yet to connect those in the wrapper.
The library you linked is indeed a node-red library, but because it is missing the “node-red” keyword it is not shown in the flows library. That is likely deliberate, as the official advise is to only add that keyword when it is ready for general usage.
As you can see it says “early stages”, as well as version 0.0.3 and last updated 4 years ago. Sounds to me that the development was stopped before a stable version could be released.
Far from optimised yet, but this is how I do the Node-RED side of the MQTT wrapped handlers. At the moment these are still inject buttons as I'm still working on the file-indexing aspect of the remote pi. When I'm happy with that part I can design the rest of the interface, and move those inject buttons out/away.
If you just want to play MP3 files from some sort of collection, why not have a look at Music Player Daemon (MPD)? I've been using it for many years now.
It's available as a package on all major Linux distributions, has a plethora of clients (web-based, GUI, ncurses, console), supports many audio formats and many different forms of output targets (ALSA, streaming, ...).
Just that I use VLC as the generic player before NR. So if I could get NR to talk to VLC, it would help keep things simpler in that there would only be one player.
For using VLC as a desktop application with graphical UI, I agree. But running it as a music player to be controlled remotely... I don't believe that it is the right tool in this case, especially when running it headless, without GUI.
There are alternatives that are specifically designed for that use-case, MPD being one of them.