Re: [LAD] LAC 2017 Program - Linux Audio Conference in Saint-Etienne - Wednesday evening

2017-05-16 Thread Will Godfrey
On Tue, 16 May 2017 21:28:50 +0200
IOhannes m zmölnig  wrote:

> On 05/12/2017 07:56 PM, Laurent Pottier wrote:
> > I have booked a table for 15-20 people at "le GRILLON », french food, at 
> > 08:00 pm.  
> 
> see you tomorrow (hopefully).
> 
> ganrds
> IOhannes
> 

And I shall make sure I arrive hungry :)

-- 
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev


Re: [LAD] LAC 2017 Program - Linux Audio Conference in Saint-Etienne - Wednesday evening

2017-05-16 Thread IOhannes m zmölnig
On 05/12/2017 07:56 PM, Laurent Pottier wrote:
> I have booked a table for 15-20 people at "le GRILLON », french food, at 
> 08:00 pm.

see you tomorrow (hopefully).

ganrds
IOhannes



signature.asc
Description: OpenPGP digital signature
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev


Re: [LAD] Implementing software knob behaviour

2017-05-16 Thread immanuel litzroth
This has a bunch of good information.
https://thorwil.wordpress.com/2007/05/01/fan-sliders/
I'll try to get some time this weekend to formulate a considered reply.
Immanuel

On Tue, May 16, 2017 at 9:25 AM, Christopher Arndt 
wrote:

> Hi all,
>
> I'm currently trying to write a software MIDI/OSC control panel in
> Kivy/Python [1]. I want to implement a sensible knob behaviour but I
> have trouble getting this right. The general idea is:
>
> - Click (starting somewhere in the area of the knob control) and drag
> upwards/downwards (y-axis) increases / decreases the value.
> - Dragging left/right (x-axis) decreases step size of increments /
> decrements.
> - Each knob has a min/max value.
>
> My questions are:
>
> - What should I use as the reference point for finding the distance of
> the movement? The centre of the knob or where the first touch event
> occurred?
> - Should I apply the distance to the value directly or use the distance
> as a relative value (i.e. increment / decrement to the value when the
> touch started)? If the former, how do I prevent value jumps?
>
> - Or, to put it another way: how do you guys actually implement knob
> behaviour?
>
>
> Chris
>
>
>
> [1] http://kivy.org/
>
>
> ___
> Linux-audio-dev mailing list
> Linux-audio-dev@lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-dev
>
>
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev


Re: [LAD] Implementing software knob behaviour

2017-05-16 Thread Christopher Arndt

Am 16.05.2017 um 12:47 schrieb Thorsten Wilms:

In case inspiration regarding the visuals is welcome:
https://thorwil.wordpress.com/2007/04/27/not-knobs-5/
https://thorwil.wordpress.com/2007/05/01/fan-sliders/


Very welcome. Your series of blog posts seems to tackle exactly the 
questions I was asking myself and more. I'll read them carefully and 
then come back - probably with more questions ;)



Chris
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev


Re: [LAD] Implementing software knob behaviour

2017-05-16 Thread Thorsten Wilms

On 16.05.2017 09:25, Christopher Arndt wrote:

- What should I use as the reference point for finding the distance of
the movement? The centre of the knob or where the first touch event
occurred?


First touch.

Elsewise, if that point is above the center and the cursor/finger moves 
down, what are you going to do until the center has been passed?




- Should I apply the distance to the value directly or use the distance
as a relative value (i.e. increment / decrement to the value when the
touch started)? If the former, how do I prevent value jumps?


I don't quite understand what you are trying to describe here.

I think the behavior should be as if a slider was brought up, with the 
current value, positioned such that the indicator (top of the value bar) 
is right below the pointer/finger. You should probably actually display 
a slider. For touch, it's worth thinking about not (only) showing 
something right in place, as the finger/hand may obstruct it.


The slider area may end up  partially off screen. You could rely on the 
user to slide twice if they want to reach an extreme in such a case. Or 
implement a scroll-fully-into-view feature. With a mouse, you could 
allow the pointer to go off-screen / wrap-around (this works quite well 
in the 3D app Blender). At the same time the pointer goes over the edge, 
the slider could be moved appropriately. For a touch interface, you'd 
have to move the slider as the finger approaches the edge, though.


In case inspiration regarding the visuals is welcome:
https://thorwil.wordpress.com/2007/04/27/not-knobs-5/
https://thorwil.wordpress.com/2007/05/01/fan-sliders/


--
Thorsten Wilms

thorwil's design for free software:
http://thorwil.wordpress.com/
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev


[LAD] Implementing software knob behaviour

2017-05-16 Thread Christopher Arndt
Hi all,

I'm currently trying to write a software MIDI/OSC control panel in
Kivy/Python [1]. I want to implement a sensible knob behaviour but I
have trouble getting this right. The general idea is:

- Click (starting somewhere in the area of the knob control) and drag
upwards/downwards (y-axis) increases / decreases the value.
- Dragging left/right (x-axis) decreases step size of increments /
decrements.
- Each knob has a min/max value.

My questions are:

- What should I use as the reference point for finding the distance of
the movement? The centre of the knob or where the first touch event
occurred?
- Should I apply the distance to the value directly or use the distance
as a relative value (i.e. increment / decrement to the value when the
touch started)? If the former, how do I prevent value jumps?

- Or, to put it another way: how do you guys actually implement knob
behaviour?


Chris



[1] http://kivy.org/



signature.asc
Description: OpenPGP digital signature
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev