Hi @69Boss302 and @snappyVol,
I know, I know… late to the party. However, I’ve been working on revamping the plugin(s) <- multiple now, because I wanted to carve out the client part for obvious reasons.
Ok, so your explanation rings true:
- There is little to no multi-arch support in the current plugin
- Failing during install, will not cause the plugin to NOT install, so you can install the plugin (and fail) and install the binaries, after which everything should work.
- There is no iOS client (I’m not gonna touch on this, as this is beyond me)
- A “landscape” exists off of 1 server and x clients (note that the server can run a client, but it’s not necessary)
Some things I’ve been working on:
- Creating a container for both the server and the client; multi-arch when using the ‘latest’ tag (has a manifest containing info for several architectures)
- Revamping the plugin config screen, for clarity
- Carving out the client; effectively making two packages (client and server)
- Supporting the new VolSpotConnect2 configs, SPOP & MPD right out of the ‘box’ (still working on Airplay)
It’s always wise to read the manual and understand what you’re doing. Especially when enabling a secondary stream (not recommended for beginners). You will probably want to test functionality, easiest way is to use the Android client (which can be installed from the App Store). The Android client is also perfect to configure streams and subscribers, the same applies here, only if you know what you’re doing 