Jason Gray
Jason Gray
Do you need it to be the device name for any reason in particular? If it's just for the sake of having a unique name I strongly suggest using what...
Pids don't change over the course of a program's life. You're prob getting a pid of a child process/thread of Spotifyd mixed up with the main process/thread.
Not to mention that 2 equally valid device names could be sanitized into the same name thus breaking the uniqueness guarantee.
My guess would be that you want the pid of the Tokio runtime.
If you try to grab a pid before you're in the runtime it may be wrong?
> I suppose either is useful but I've been debugging something that uses this feature and I've been running into issues with Spotifyd's PID not being the same as the...
This whole PR could be as simple as: ```rust let busname = format!( "org.mpris.MediaPlayer2.spotifyd.instance{}", std::process::id() ); conn.request_name(&busname, true, true, true) .await .expect("Failed to register dbus player name"); ```
> Hi, since librespot now uses libmdns 0.7 which added support for binding to interface(s), would it be possible to implement this option? > > I would try a PR...
It would probably be something like `discovery-interfaces` that would be a comma separated list or a single interface, that defaults to "any" or "all" (I'll have to look at libmdns...
I'd create a systemd unit file to run the python scripts as system services. Stopping the service should kill the script. Something like this might do the trick: ``` #/etc/systemd/system/led-visualization.service...