24 Jan
2014
24 Jan
'14
1:12 p.m.
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.
cheers,
Brendan
24 Jan
24 Jan
3:10 p.m.
On Fri, Jan 24, 2014 at 12:12 PM, Brendan Jones
<brendan.jones.it(a)gmail.com>wrote;wrote:
am wondering what the lowest common denomination
screen resolution I
should be shooting for.
I was approached about making the smallest window size for Luppp smaller,
so it would fit on the OpenPandora screen:
The size this can manage is 800x450: that's smaller than all netbooks I
know of... so going with 800x450 you've got all bases covered!
Screenshots (are a little squashy, but its all there!) :
http://repo.openpandora.org/?page=detail&app=luppp
During performance, what if anything, do you actually
need to see apart
from what the the current preset is?
I'd argue everything should be visible: tabbed UI / expanders can be used
to maximise pixels usage.
Its tabbed / expanders are *not* and ideal workflow
3:12 p.m.
On Fri, Jan 24, 2014 at 2:10 PM, Harry van Haaren <harryhaaren(a)gmail.com>wrote;wrote:
During performance, what if anything, do you actually
need to see apart
</me replies to self, hit send too soon>
Tabs / expanders are not and ideal workflow, however if tabs can be
side-by-side as well as behind-eachother this is a win-win.
That's my expereince anyway, HTH, -Harry
from what the the current preset is?
I'd argue everything should be visible: tabbed UI / expanders can be used
to maximise pixels usage.
Its tabbed / expanders are *not* and ideal workflow
3:17 p.m.
On Fri, Jan 24, 2014 at 6:11 PM, Harry van Haaren wrote:
There are all sorts of smart solutions for that where you can tweak
things without making your content move around.
Example: top toolbar in MyPaint. A brush icon displays the currently
selected brush, and when you click on it, a small configuration dialog
slides down on top of your content to let you configure brush
settings.
Alexandre
I'd argue
everything should be visible: tabbed UI / expanders can be used
to maximise pixels usage.
Its tabbed / expanders are *not* and ideal workflow
</me replies to self, hit send too soon>
Tabs / expanders are not and ideal workflow, however if tabs can be
side-by-side as well as behind-eachother this is a win-win. 
25 Jan
25 Jan
8:21 a.m.
On 01/24/2014 04:17 AM, Alexandre Prokoudine wrote:
On Fri, Jan 24, 2014 at 6:11 PM, Harry van Haaren
wrote:
There are all sorts of smart solutions for that where you can tweak
things without making your content move around.
Example: top toolbar in MyPaint. A brush icon displays the currently
selected brush, and when you click on it, a small configuration dialog
slides down on top of your content to let you configure brush
settings.
Ages ago, AT&T had a line of pro video capture cards with corresponding
graphic software. The Targa line of hardware, with Targa TIPS as the
graphics editor. The UI was the current image frame you were working on.
Right-click brought up a popup menu, you navigated your way to whatever
tool/setting you needed, then hit OK when you were done.
Very low impact on what needed to be displayed on screen. Could do
something similar for small screens where the screen displays current
status/info, and clicking on a region brings up menus for changing things.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
I'd
argue everything should be visible: tabbed UI / expanders can be used
to maximise pixels usage.
Its tabbed / expanders are *not* and ideal workflow
</me replies to self, hit send too soon>
Tabs / expanders are not and ideal workflow, however if tabs can be
side-by-side as well as behind-eachother this is a win-win.
24 Jan
24 Jan
5:50 p.m.
On 01/24/2014 03:10 PM, Harry van Haaren wrote:
On Fri, Jan 24, 2014 at 12:12 PM, Brendan Jones
<brendan.jones.it(a)gmail.com <mailto:brendan.jones.it@gmail.com>> wrote:
am wondering what the lowest common denomination screen resolution I
should be shooting for.
I was approached about making the smallest window size for Luppp
smaller, so it would fit on the OpenPandora screen:
The size this can manage is 800x450: that's smaller than all netbooks I
know of... so going with 800x450 you've got all bases covered!
Screenshots (are a little squashy, but its all there!) :
http://repo.openpandora.org/?page=detail&app=luppp
Wow nice! But ..ouch- tiny.
I really like the performance mode from in guitarix, but changing a
mapped parameter should
probably bring it into view somehow
25 Jan
25 Jan
8:24 a.m.
On 01/24/2014 02:12 AM, 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.
Hmm, I record on a netbook (1280x800 resolution). Not performing. But I
think if I was using it to perform, I'd want the ability to get to or
switch presets quickly. Just a simple button click. Those folk who
designed pipe organs knew what they were doing when they put thumb
pistons above each manual!
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
11:28 a.m.
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
26 Jan
26 Jan
5:54 p.m.
El 25/01/2014 11:29, "Ken Restivo" <ken(a)restivo.org> escribió:
On Fri, Jan 24, 2014 at 01:12:01PM +0100, Brendan Jones wrote:
a corner
and nobody even saw it.
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 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(a)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.
3746
days inactive
3748
days old
linux-audio-user@lists.linuxaudio.org
8 comments
6 participants
participants (6)
-
Alexandre Prokoudine -
Brendan Jones -
Carlos sanchiavedraz -
david -
Harry van Haaren -
Ken Restivo