This is a collaboratively edited question and answer site for power users of Plethra hardware and software. It's 100% free to participate.

Feature Request List - audio|acacia

0 votes

We have hundreds of ideas on how we want to make audio|acacia better. But ultimately it is the requests from our users that drive where we focus our development efforts. For this reason, we have created this official feature request list.

Here is how it works:

-UpVote the Features that you want to see implemented the most
-DownVote the Features that you believe will never be useful to you
-If a Feature you want to suggest doesn't exist, add it as an Answer
-The "Selected Answer" is the requested feature we are currently working on implementing

Once a feature from this list has been implemented, it will be removed and a new feature from the list will be chosen.

asked Oct 10, 2013 by user1 (1,094 points)

41 Answers

+4 votes

Ability to expose each channel of a soundcard individually to create mono outputs. This would be very helpful for zones such as a bathroom which may not require stereo.

answered Oct 7, 2014 by user851 (32 points)
+4 votes

Metadata for Analog/Digital Input Sources
The ability to see metadata for these audio streams, similar to SoundHound or Shazam.

answered Aug 25, 2015 by user1 (1,094 points)
+2 votes

The current version of a|a will not run on Debian stable ("wheezy") due to its dependency on glibc 2.14. Please link the a|a server against a more conservative glibc version to support Debian stable and other non cutting-edge Linux distributions.

answered Oct 13, 2014 by user320 (11 points)
+2 votes

Simplified Events for Automation Integrations

The controller.js file of the web controller can already be used for integration into automation systems and will notify all subscribers to very specific events. However simple events (ie Room now active/idle) have to be derived. This request is for a simplified set of events for easy integration into automation systems.

answered Sep 26, 2016 by user1 (1,094 points)
+1 vote

A Keyboard/Mouse Optimized Front-End Controller:
The current front-end controller is optimized for touch devices. It would be nice to have an interface optimized for the desktop/laptop device for power users (i.e. better use of the screen real estate via smaller elements and text, sortable metadata columns like in iTunes, more accessible room/zone volume control, etc.).

answered Oct 11, 2013 by user1 (1,094 points)
+1 vote

SiriusXM Integration

answered Aug 21, 2015 by user1205 (33 points)
+1 vote

Amazon Prime Music Integration

answered Aug 21, 2015 by user1205 (33 points)
+1 vote

Offer a chromecast "stream to audio|acacia" just like you do for airplay. This would enable android apps to be able to stream to acacia just like their iOS counterparts can via airplay.

answered Dec 12, 2015 by user124 (21 points)
oh and p.s love you guys <3
+1 vote

An Alarm function would be quite useful to me.

Standard stuff: configure days, hours, periodicity, which playlist (or radio, or ...) to play at fire time

answered May 12, 2016 by user1489 (17 points)
+1 vote

Another stuff I use all the time is a Sleep timer...
Ability to pause a given Session/Zone after a specified amount of time would be a nice addition to a|a

answered May 12, 2016 by user1489 (17 points)