hi,......... a little delayed solution to the keyrepeat problem. o-o
noKeyRepeat.pd
#N canvas 0 0 812 395 12; #X obj 86 13 table norepeat 256; #X obj 144 137 tabread norepeat; #X obj 109 110 t f f; #X obj 144 162 == 0; #X obj 109 190 pack; #X obj 109 241 route 1; #X msg 109 215 $2 $1; #X msg 109 267 $1 ; norepeat $1 1 ;; #X obj 109 315 pack f 1; #X obj 304 316 pack f 0; #X obj 262 351 print; #X msg 304 267 $1 ; norepeat $1 0 ;; #X obj 109 51 key; #X obj 304 210 keyup; #X obj 304 236 select 0; #X obj 109 76 select 0 8 27; #X text 225 78 <--some keys send 0 , Esc and backspace don't send keyup (8; #X text 703 78 27).; #X msg 269 51 ON win23:; #X connect 1 0 3 0; #X connect 2 0 4 0; #X connect 2 1 1 0; #X connect 3 0 4 1; #X connect 4 0 6 0; #X connect 5 0 7 0; #X connect 6 0 5 0; #X connect 7 0 8 0; #X connect 8 0 10 0; #X connect 9 0 10 0; #X connect 11 0 9 0; #X connect 12 0 15 0; #X connect 13 0 14 0; #X connect 14 1 11 0;
#X connect 15 3 2 0;
Thank you so much Steffen!!! thats exactly what i need i dont yet know how it works but i will learn my way around
best wishes m
-------- Original-Nachricht -------- Datum: Tue, 10 Oct 2006 15:54:19 +0200 Von: Steffen Leve Poulsen slagmark@worldonline.dk An: pd-list@iem.at Betreff: [PD] Re: polyphonic ? key, keyup setup question
hi,......... a little delayed solution to the keyrepeat problem. o-o
noKeyRepeat.pd
#N canvas 0 0 812 395 12; #X obj 86 13 table norepeat 256; #X obj 144 137 tabread norepeat; #X obj 109 110 t f f; #X obj 144 162 == 0; #X obj 109 190 pack; #X obj 109 241 route 1; #X msg 109 215 $2 $1; #X msg 109 267 $1 ; norepeat $1 1 ;; #X obj 109 315 pack f 1; #X obj 304 316 pack f 0; #X obj 262 351 print; #X msg 304 267 $1 ; norepeat $1 0 ;; #X obj 109 51 key; #X obj 304 210 keyup; #X obj 304 236 select 0; #X obj 109 76 select 0 8 27; #X text 225 78 <--some keys send 0 , Esc and backspace don't send keyup (8; #X text 703 78 27).; #X msg 269 51 ON win23:; #X connect 1 0 3 0; #X connect 2 0 4 0; #X connect 2 1 1 0; #X connect 3 0 4 1; #X connect 4 0 6 0; #X connect 5 0 7 0; #X connect 6 0 5 0; #X connect 7 0 8 0; #X connect 8 0 10 0; #X connect 9 0 10 0; #X connect 11 0 9 0; #X connect 12 0 15 0; #X connect 13 0 14 0; #X connect 14 1 11 0;
#X connect 15 3 2 0;
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Does it work on Win?
I get a fail here on Linux. :(
Any idea why? Does Windows send a different event for a real key-up than a repeat?
On Tue, 10 Oct 2006 17:40:46 +0200 "Marten Rieger" kali.84@gmx.net wrote:
Thank you so much Steffen!!! thats exactly what i need i dont yet know how it works but i will learn my way around
best wishes m
-------- Original-Nachricht -------- Datum: Tue, 10 Oct 2006 15:54:19 +0200 Von: Steffen Leve Poulsen slagmark@worldonline.dk An: pd-list@iem.at Betreff: [PD] Re: polyphonic ? key, keyup setup question
hi,......... a little delayed solution to the keyrepeat problem. o-o
noKeyRepeat.pd
#N canvas 0 0 812 395 12; #X obj 86 13 table norepeat 256; #X obj 144 137 tabread norepeat; #X obj 109 110 t f f; #X obj 144 162 == 0; #X obj 109 190 pack; #X obj 109 241 route 1; #X msg 109 215 $2 $1; #X msg 109 267 $1 ; norepeat $1 1 ;; #X obj 109 315 pack f 1; #X obj 304 316 pack f 0; #X obj 262 351 print; #X msg 304 267 $1 ; norepeat $1 0 ;; #X obj 109 51 key; #X obj 304 210 keyup; #X obj 304 236 select 0; #X obj 109 76 select 0 8 27; #X text 225 78 <--some keys send 0 , Esc and backspace don't send keyup (8; #X text 703 78 27).; #X msg 269 51 ON win23:; #X connect 1 0 3 0; #X connect 2 0 4 0; #X connect 2 1 1 0; #X connect 3 0 4 1; #X connect 4 0 6 0; #X connect 5 0 7 0; #X connect 6 0 5 0; #X connect 7 0 8 0; #X connect 8 0 10 0; #X connect 9 0 10 0; #X connect 11 0 9 0; #X connect 12 0 15 0; #X connect 13 0 14 0; #X connect 14 1 11 0;
#X connect 15 3 2 0;
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Wed, 2006-10-11 at 06:35 +0100, padawan12 wrote:
Any idea why? Does Windows send a different event for a real key-up than a repeat?
[key]/[keyup]/[keyname] do *NOT* behave the same on linux and on windows (don't know about OSX).
[keyname]'s left inlet on linux,when a key is pressed:
1..........01..01..01..01..01..01..01..01..01..01
the time between 0 and 1 is [at least on my two linux boxes] very short.. about 3ms. this makes it possible to skip a 0-1 pair with a delay: if a 0 is followed by a 1 within lets say 10ms, both are skipped. this adds a little delay (10ms) to the release event, though.
the same on windows:
1..........1..1..1..1..1..1..1..1..1..1..1..1
that also means, that [keyup] doesn't repeat on windows, but it does on linux, whereas [key] repeats on both.
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Cheers Roman, that clears up the different behaviour in Steffens patch and something to be aware of in the future too.
I guess this is why we should generally favour [hid].
thanks, andy
On Wed, 11 Oct 2006 00:12:40 +0200 Roman Haefeli reduzierer@yahoo.de wrote:
On Wed, 2006-10-11 at 06:35 +0100, padawan12 wrote:
Any idea why? Does Windows send a different event for a real key-up than a repeat?
[key]/[keyup]/[keyname] do *NOT* behave the same on linux and on windows (don't know about OSX).
[keyname]'s left inlet on linux,when a key is pressed:
1..........01..01..01..01..01..01..01..01..01..01
the time between 0 and 1 is [at least on my two linux boxes] very short.. about 3ms. this makes it possible to skip a 0-1 pair with a delay: if a 0 is followed by a 1 within lets say 10ms, both are skipped. this adds a little delay (10ms) to the release event, though.
the same on windows:
1..........1..1..1..1..1..1..1..1..1..1..1..1
that also means, that [keyup] doesn't repeat on windows, but it does on linux, whereas [key] repeats on both.
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Hello all, I'm working on a keyboard patch using [hid]. I'll post it when I'm finished, and perhaps we can somewhat "settle" this issue once and for all (hopefully with the assistance of our resident pd gurus) as it seems to be an oft requested component!
On 10/11/06, padawan12 padawan12@obiwannabe.co.uk wrote:
Cheers Roman, that clears up the different behaviour in Steffens patch and something to be aware of in the future too.
I guess this is why we should generally favour [hid].
thanks, andy
On Wed, 11 Oct 2006 00:12:40 +0200 Roman Haefeli reduzierer@yahoo.de wrote:
On Wed, 2006-10-11 at 06:35 +0100, padawan12 wrote:
Any idea why? Does Windows send a different event for a real key-up than a repeat?
[key]/[keyup]/[keyname] do *NOT* behave the same on linux and on windows (don't know about OSX).
[keyname]'s left inlet on linux,when a key is pressed:
1..........01..01..01..01..01..01..01..01..01..01
the time between 0 and 1 is [at least on my two linux boxes] very short.. about 3ms. this makes it possible to skip a 0-1 pair with a delay: if a 0 is followed by a 1 within lets say 10ms, both are skipped. this adds a little delay (10ms) to the release event, though.
the same on windows:
1..........1..1..1..1..1..1..1..1..1..1..1..1
that also means, that [keyup] doesn't repeat on windows, but it does on linux, whereas [key] repeats on both.
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail:
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
attached are the solutions i use for key and keyup to bypass the retrig problem
I've finished Crikey 1.5 using HID. There is a larger mail in the list with details!
On 10/11/06, hard off hard.off@gmail.com wrote:
attached are the solutions i use for key and keyup to bypass the retrig problem
Interesting non-solution* :)
If it's any consolation I also failed twice, in two very different ways to solve this from inside Pd.
There is no general solution to the problem, apart from stopping the key repeat. There is no way to distinguish between typomatic key-up events and the genuine thing.**
- interesting and creative use of the table!
** actually it can be done with an awkward system of timers and spigots in the style of a monostable switch debouncer, but afaics it would cause all keys to hold for a minimum period of one typomatic cycle thus spoiling the user input timimg. Furthermore you would need one such circuit for each key number.
On Tue, 10 Oct 2006 15:54:19 +0200 Steffen Leve Poulsen slagmark@worldonline.dk wrote:
hi,......... a little delayed solution to the keyrepeat problem. o-o
noKeyRepeat.pd
#N canvas 0 0 812 395 12; #X obj 86 13 table norepeat 256; #X obj 144 137 tabread norepeat; #X obj 109 110 t f f; #X obj 144 162 == 0; #X obj 109 190 pack; #X obj 109 241 route 1; #X msg 109 215 $2 $1; #X msg 109 267 $1 ; norepeat $1 1 ;; #X obj 109 315 pack f 1; #X obj 304 316 pack f 0; #X obj 262 351 print; #X msg 304 267 $1 ; norepeat $1 0 ;; #X obj 109 51 key; #X obj 304 210 keyup; #X obj 304 236 select 0; #X obj 109 76 select 0 8 27; #X text 225 78 <--some keys send 0 , Esc and backspace don't send keyup (8; #X text 703 78 27).; #X msg 269 51 ON win23:; #X connect 1 0 3 0; #X connect 2 0 4 0; #X connect 2 1 1 0; #X connect 3 0 4 1; #X connect 4 0 6 0; #X connect 5 0 7 0; #X connect 6 0 5 0; #X connect 7 0 8 0; #X connect 8 0 10 0; #X connect 9 0 10 0; #X connect 11 0 9 0; #X connect 12 0 15 0; #X connect 13 0 14 0; #X connect 14 1 11 0;
#X connect 15 3 2 0;
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
But there must be some solution, because other software applictations make use of this feature successfully (i.e., Ableton Live, Reaktor, et al). What is it in their supersecret proprietary $$$ code that allows this to happen?
~Kyle
On 10/11/06, padawan12 padawan12@obiwannabe.co.uk wrote:
Interesting non-solution* :)
If it's any consolation I also failed twice, in two very different ways to solve this from inside Pd.
There is no general solution to the problem, apart from stopping the key repeat. There is no way to distinguish between typomatic key-up events and the genuine thing.**
- interesting and creative use of the table!
** actually it can be done with an awkward system of timers and spigots in the style of a monostable switch debouncer, but afaics it would cause all keys to hold for a minimum period of one typomatic cycle thus spoiling the user input timimg. Furthermore you would need one such circuit for each key number.
On Tue, 10 Oct 2006 15:54:19 +0200 Steffen Leve Poulsen slagmark@worldonline.dk wrote:
hi,......... a little delayed solution to the keyrepeat problem. o-o
noKeyRepeat.pd
#N canvas 0 0 812 395 12; #X obj 86 13 table norepeat 256; #X obj 144 137 tabread norepeat; #X obj 109 110 t f f; #X obj 144 162 == 0; #X obj 109 190 pack; #X obj 109 241 route 1; #X msg 109 215 $2 $1; #X msg 109 267 $1 ; norepeat $1 1 ;; #X obj 109 315 pack f 1; #X obj 304 316 pack f 0; #X obj 262 351 print; #X msg 304 267 $1 ; norepeat $1 0 ;; #X obj 109 51 key; #X obj 304 210 keyup; #X obj 304 236 select 0; #X obj 109 76 select 0 8 27; #X text 225 78 <--some keys send 0 , Esc and backspace don't send keyup (8; #X text 703 78 27).; #X msg 269 51 ON win23:; #X connect 1 0 3 0; #X connect 2 0 4 0; #X connect 2 1 1 0; #X connect 3 0 4 1; #X connect 4 0 6 0; #X connect 5 0 7 0; #X connect 6 0 5 0; #X connect 7 0 8 0; #X connect 8 0 10 0; #X connect 9 0 10 0; #X connect 11 0 9 0; #X connect 12 0 15 0; #X connect 13 0 14 0; #X connect 14 1 11 0;
#X connect 15 3 2 0;
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hallo, Kyle Klipowicz hat gesagt: // Kyle Klipowicz wrote:
But there must be some solution, because other software applictations make use of this feature successfully (i.e., Ableton Live, Reaktor, et al). What is it in their supersecret proprietary $$$ code that allows this to happen?
Maybe they use [hid]?
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
I hope so, because then we'd finally get their source bounty.
AAAAArrrrrg! (Pirate yalp.)
~Kyle
On 10/10/06, Frank Barknecht fbar@footils.org wrote:
Hallo, Kyle Klipowicz hat gesagt: // Kyle Klipowicz wrote:
But there must be some solution, because other software applictations make use of this feature successfully (i.e., Ableton Live, Reaktor, et al). What is it in their supersecret proprietary $$$ code that allows this to happen?
Maybe they use [hid]?
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hallo, padawan12 hat gesagt: // padawan12 wrote:
There is no general solution to the problem, apart from stopping the key repeat. There is no way to distinguish between typomatic key-up events and the genuine thing.**
** actually it can be done with an awkward system of timers and spigots in the style of a monostable switch debouncer, but afaics it would cause all keys to hold for a minimum period of one typomatic cycle thus spoiling the user input timimg. Furthermore you would need one such circuit for each key number.
You could differentiate between automatic and manual keyups by measuring the time between keyups: Automatic keyups happen instantly.
However most systems have a delay before autorepeat sets in, which would have to be taken into account as well. All this IMO is too much work to do in Pd when you can just switch off autorepeat temporarily for the time of a performance.
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
-
Frank Barknecht -
hard off -
Kyle Klipowicz -
Luke Iannini (pd) -
Marten Rieger -
padawan12 -
Roman Haefeli -
Steffen Leve Poulsen