-- Sent from my HP TouchPad
On 10.02.2013 23:30, Paul Davis <p...@linuxaudiosystems.com> wrote:
On Sun, Feb 10, 2013 at 5:05 PM, <gerald.mwa...@gmx.de> wrote:
what you are describing is basically the "monolithic app" experience (from a user perspective) but created using a set of independent applications and processes.
speaking personally, i think there are better things to do with our time.
Well just for the initialization of the project. The diversity experience of the multiple programs , ecosystem shall still be preserved
Gerald
Auto mode for JACK latency is a good idea.
I have another proposition: a dedicated graphical front-end for jack session. It could help users setup their workflow , by providing a list of all the jack aware programs installed, categorized by type (sampler, daw, synth). The program should aid in setting up a project , eg firing up ardour with several tracks, firing up synths (lv2 instruments/hosts incl) with presets selectable from the front-end with a preview sound. The front-end could trigger the synth in question with a midi note when selecting a preset. Lv2 plugins, that is pure audio effects, could also listed with the ability to directly send a signal from the audio interface through the selected plugin to quickly hear what it does. One could then associate the selected plugin with, say a track in ardour, and another plugin with a track in hydrogen or so.
what you are describing is basically the "monolithic app" experience (from a user perspective) but created using a set of independent applications and processes.
speaking personally, i think there are better things to do with our time.
Well just for the initialization of the project. The diversity experience of the multiple programs , ecosystem shall still be preserved
Gerald
_______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
