Import/Export Presets
Answered
The ability to import/export presets from one Node to another.
-
Official comment
Interesting. I will pass this forward to our BluOS Dev team for future consideration.
Regards,
Sam R. -
+1
0 -
We have different customers who want to be able to copey their presets from the living room to the bedroom and/or kitchen and vice versa!
0 -
This would be a great functionality, esp because if you have more than one Node they already share the same libraries etc.
My Presets--->Add Preset--->Browse---->:
My Playlists
Inputs
Tunein
Radio Paradise
TIDAL
Node "X" <--------NEW FUNCTIONALITY
2 -
One wonders why this simple concept has not been supported. BluOS wants to have multiple players. So does NAD. I have an M10 AND a C700. But I cant copy from one to another or keep their presets etc in sync.
I'd suggest this get prioritized as a pretty strategic feature to have.
0 -
Agreed, it’s ridiculous that this is not already implemented. I have 5 Bluesound/NAD players and have to replicate presets manually on each one is a real pain!
0 -
+1
0 -
+1
0 -
Guys, Don't forget to push the vote arrow up on Edwards main post - maybe it helps then to get more attantion to the request...
0 -
Good point, thanks Dominik.
0 -
This is an obvious feature to have but I gave up hope long ago as it seemed the dev team was being prioritized on fixes and the new UI. Given the increased competition I would hope the focus on adding features like this would rise.
0 -
Presets do not replicate by design. This is on purpose as not everyone in your home would want the same presets. Listening to News, Weather and Traffic quickly in your bedroom is a nice convenience but not what you want in the living room.
The fastest way to copy a preset...
- On Player A, play your preset.
- Use FollowMe to copy the preset to Player B.
- Save Player B as a Preset from the Now Playing Screen.
0 -
Agreed but there may only be one or two people in a home who would like the option to replicate presets onto at least some of their devices. We have a couple of Pulse Flex 2is in different rooms and it would be convenient to have the same sources allocated to the same number preset in each case. I live with someone who can’t remember what she had for breakfast let alone how to navigate the BluOS app to find her favourite radio station!
The procedure you describe may well work (I haven’t tried it but I definitely will) but it still seems a long-winded way of doing so. Couldn’t you provide an option whereby presets could be stored within the BluOS app much like playlists and then imported onto each device as required?
0 -
The process he mentions does work as I have used it myself. However, if you have eight or 10 presets, it gets to become a pain and it means you have to keep doing that each time you add something or change something.
And what is the harm and just adding the capability to replicate presets? hose people who don’t need it just won’t use it.
This is a perfect example of what I’ve seen from this BlueOs team. They simply don’t want to add features to the product to make it more usable. They don’t seem very interested in soliciting input for new features. They don’t publish any kind of a roadmap of new features. I understand it’s a tough job to support multiple operating systems and multiple pieces of hardware so I do think they’re all hard-working from a developer standpoint. It’s the product management leadership and vision that seems to be lacking on this team.
Compare this to WiiM. I’ve started using their products in part because they seem highly responsive to continually improve the product for the marketplace.
-1 -
I couldn't agree more!
0 -
I think it is really a nice that different family member can have different presets on theire player. It's a great feature that other multiroom systems are not providing. But we have customer who have 10 to 15 Bluesound zones and they want to have the same presets everywhere.
Tonys workaraound is doing it's job - but it's not a very user friendly way to do it :)
1
Please sign in to leave a comment.
Comments
16 comments