El 25/01/2014 11:29, "Ken Restivo" <ken@restivo.org> escribió:
>
> On Fri, Jan 24, 2014 at 01:12:01PM +0100, Brendan Jones wrote:
> > Hey all,
> >
> > I've been reading with interested that some of you use
> > netbooks/small form factor pc's/rasberry pi's on stage for live
> > performance. I'm currently developing an LV2 plugin and am wondering
> > what the lowest common denomination screen resolution I should be
> > shooting for.
> >
> > During performance, what if anything, do you actually need to see
> > apart from what the the current preset is? Is there a use case for
> > making all parameters for a synth plugin (for example)
> > available/accessible on screen, or using midi learn to hide/unhide
> > parameter tabs etc. Examples of current programs plugins would be
> > great.
> >
>
> Screen?
>
> What is this screen thing of which you speak?
>
> My goal for a synth is MIDI buttons and knobs, not a screen.
>
> The last gig I did, after I started up my system I stuffed the netbook in a corner and nobody even saw it.
>
> A completely headless command-line setup was the ideal. I have a Raspberry Pi and might try getting JACK to work on it.
>
> Back when I was gigging regularly I kept the screen up only to have the setlist and/or lyrics.
>
> -ken
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user

I'm also getting deeper and deeper on that Headless Musicstation road/paradigm during lasts years. I'm still developing processes, workflows and software tools around the idea of "More Music, Less Tech", that's what I like when improvising, using touch devices and mini PCs as Raspberry.

(Still trying to prepare things to release them properly)

So, for me a screen on stage would be mainly for displaying info in a dashboard as a feedback to make sure everything is ok. Then MIDI pedalboards/surfaces and touchscreens to control and create on the fly.