On Fri, Dec 11, 2015, at 05:43 AM, WMID wrote: > Or > > UbuntuStudio/Wily/FreedesktopCategories/Audio > <https://wiki.ubuntu.com/UbuntuStudio/Wily/FreedesktopCategories/Audio>(start > QjackCtl first) > UbuntuStudio/Wily/FreedesktopCategories/Audio > <https://wiki.ubuntu.com/UbuntuStudio/Wily/FreedesktopCategories/Audio> > (without QjackCtl) > UbuntuStudio/Wily/FreedesktopCategories/Graphics > <https://wiki.ubuntu.com/UbuntuStudio/Wily/FreedesktopCategories/Graphics> > > UbuntuStudio/Wily/FreedesktopCategories/Video > <https://wiki.ubuntu.com/UbuntuStudio/Wily/FreedesktopCategories/Video> > > In (without QjackCtl) = Audacity u other that working with pulseaudio > >
The categories are meant to be based on freedesktop categories - a standard for how to categorize application starters. You can see the standard here http://standards.freedesktop.org/menu-spec/latest/apa.html IMO, the best way to inform about an error is through the application itself. If an application only supports jack, and jack is not running, the application should show an error dialogue. Often applications will support more than one audio server. If none of them are running, or the application was unable to use any of them, it should show an error dialogue. There are two ways to fix this: 1. code added upstream for the check and error dialogue 2. wrapper script in packaging for check and error dialogue I added a feature definition page for this here https://wiki.ubuntu.com/UbuntuStudio/FeatureDefinitions/JackApplicationsErrorDialogue. -- ubuntu-studio-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
