You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Player interface and playlist screen would have a button to cast the current media/current playlist to another Android device running Tubular. Devices would take the role of either "remote controller" or "dedicated media device".
Why do you want this feature?
For those who have a dedicated Android (or Android TV) device just for playing video and music (possibly even running headless), it would be extremely convenient to control the Tubular app on the dedicated device straight from another remote device, being able to manage playlists and playback status.
Why ist the feature relevant to this fork?
This doesn't seem to me as a feature that should be implemented at the extractor level, but rather at the client level.
Additional information
Would be great to have at least basic features such as playlist management and media playback implemented in remote control mode.
Not sure what's the easiest way to implement this, I thought of a few:
Devices discovering each other on a local network (using proprietary or existing protocols).
If desired to operate devices which aren't in the same network, the devices could be manually paired using player IDs/unique QR code.
Completely different approach, the remote device could run its own shoutcast server on the background (not using the remote device's speakers) and the dedicated media player would connect to this stream. To keep the control truly remote (no interaction required with the dedicated device that may even be running headless), it would be appreciated that whenever the app is restarted at the dedicated device, it immediately tries to connect to the last stream and then to other known/favorited streams. If no streams are found, it keeps listening for when one will be online.
I'm not trying to tell you how to do your magic, these are just some suggestions how it could happen. Million thanks for even considering this feature, and for the awesome work done with Tubular.
The text was updated successfully, but these errors were encountered:
Didn't read/understand all text but you can take a look to SmartTube for Android TV. Also this is related to player so maybe you can also open this issue to TeamNewPipe/NewPlayer to take a place in roadmap in new player...
Hi Asandikci! Thanks for your suggestion. I already have SmartTube but it's far from offering similar functionality to Tubular/NewPipe... My most favorite and important feature is to be able to mix and match media from different sources, and that's something only Tubular/NewPipe offers. I believe many more people would benefit from the functionality I described, if implemented.
Checklist
Feature description
Player interface and playlist screen would have a button to cast the current media/current playlist to another Android device running Tubular. Devices would take the role of either "remote controller" or "dedicated media device".
Why do you want this feature?
For those who have a dedicated Android (or Android TV) device just for playing video and music (possibly even running headless), it would be extremely convenient to control the Tubular app on the dedicated device straight from another remote device, being able to manage playlists and playback status.
Why ist the feature relevant to this fork?
This doesn't seem to me as a feature that should be implemented at the extractor level, but rather at the client level.
Additional information
Would be great to have at least basic features such as playlist management and media playback implemented in remote control mode.
Not sure what's the easiest way to implement this, I thought of a few:
The text was updated successfully, but these errors were encountered: