Hi and thank you for this very promising app. Combined with Music Assistant, this is very nearly the "one app to rule them all" for my music playing use case. If Ensemble could gracefully switch from connected to my Music Assistant instance to a standalone, local only playback mode, that would just about clinch it.
I can VPN into my home LAN when away from home wifi and continue streaming (at the cost of a lot of cellular data used). However, I live in an area with very very very many gaps in cell signal coverage. So, I am pretty much guaranteed to lose Music Assistant connection at some point during nearly any sortie away from my home. This, combined with the in progress Android Auto features, means I would try to use Ensemble as my main player in my truck. However, it is distracting while driving to have to switch from Ensemble to another app and back every so often.
So, here are a few options I have thought of to gracefully handle the loss of connection while mobile use case:
-
Have Ensemble automatically queue a certain number of tracks from a specific on device folder in case of loss of connection to the Music Assistant server. I have no idea how close Ensemble is to being able to play in local only mode from a code perspective. If it is prohibitive from an app size, elegance, etc standpoint, I am perfectly fine with hearing "no" to this idea. But, here are a couple of possibly lighter ways to achieve similar:
-
Have a hook that could tell IFTT, Tasker, etc of loss of connection so that second party app could fire the playback start intent in a third party app.
-
Have Ensemble directly fire an intent for a specified third party app.
Curious to hear thoughts about how practical any of the above are, alternate ideas, etc.
Hi and thank you for this very promising app. Combined with Music Assistant, this is very nearly the "one app to rule them all" for my music playing use case. If Ensemble could gracefully switch from connected to my Music Assistant instance to a standalone, local only playback mode, that would just about clinch it.
I can VPN into my home LAN when away from home wifi and continue streaming (at the cost of a lot of cellular data used). However, I live in an area with very very very many gaps in cell signal coverage. So, I am pretty much guaranteed to lose Music Assistant connection at some point during nearly any sortie away from my home. This, combined with the in progress Android Auto features, means I would try to use Ensemble as my main player in my truck. However, it is distracting while driving to have to switch from Ensemble to another app and back every so often.
So, here are a few options I have thought of to gracefully handle the loss of connection while mobile use case:
Have Ensemble automatically queue a certain number of tracks from a specific on device folder in case of loss of connection to the Music Assistant server. I have no idea how close Ensemble is to being able to play in local only mode from a code perspective. If it is prohibitive from an app size, elegance, etc standpoint, I am perfectly fine with hearing "no" to this idea. But, here are a couple of possibly lighter ways to achieve similar:
Have a hook that could tell IFTT, Tasker, etc of loss of connection so that second party app could fire the playback start intent in a third party app.
Have Ensemble directly fire an intent for a specified third party app.
Curious to hear thoughts about how practical any of the above are, alternate ideas, etc.