Re: [PD] User access to the HID object

2008-10-01 Thread IOhannes m zmoelnig
Alex wrote:
 If you use udev you can make a rule..
 I have one for the CUI (create usb interface) in
 /etc/udev/rules.d/10-custom.rules
 
 BUS==usb, KERNEL==event[0-9]*, SYSFS{product}==CREATE USB
 Interface, GROUP=audio, SYMLINK+=input/cui
 
 and I am in the audio group.. I also create a symlink.. which you may or may 
 not
 want to do..  You can also put a MODE=0660 or something in there...

i guess it would be nicer to use another group (e.g. hid) and add 
yourself to the hid group.

fgmasdr
IOhannes

___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] vanilla-knob

2008-10-01 Thread Steffen Leve Poulsen

Thanks, your right,
now the whole area changes the knob.

attached knob.pd

mvh/Stef

Hans-Christoph Steiner skrev:
Nice, I think it would be more useful if the whole area would  
actively change the knob, rather than a small area in the middle.


.hc

On Sep 28, 2008, at 6:27 PM, Steffen Leve Poulsen wrote:


Hi

Made an attemp to make a knob in Pd-vanilla.
might be usefull with endless rotary enconders.
It has a numbox underneath, so you can shiftdrag and use negatives.

mvh/Stef
#N canvas 50 375 402 315 10;
#X obj 104 161 outlet;
#N canvas 327 0 811 712 circle 0;
#X obj 194 221 t f f;
#X obj 230 258 sin;
#X obj 189 258 cos;
#X obj 189 357 i;
#X obj 230 358 i;
#X obj 195 45 t b b;
#X msg 342 44 clear;
#X obj 270 529 s pd-\$0-draw;
#X obj 230 397 pack f f f f;
#X floatatom 323 371 5 0 0 0 - - -;
#X obj 194 189 * 6.28319;
#X obj 189 293 * 20;
#X obj 230 293 * 20;
#X msg 230 426 obj \$1 \$2 cnv 0 \$4 \$4 empty empty empty 20 12 0
14 -24198 -66577 0 \;;
#N canvas 0 0 450 300 fire 0;
#X obj 148 22 inlet;
#X obj 148 186 until;
#X obj 148 228 f;
#X obj 180 228 + 1;
#X obj 171 160 0;
#X obj 148 346 outlet;
#X obj 148 286 /;
#X obj 148 136 t f b f;
#X obj 253 23 inlet;
#X obj 312 316 outlet;
#X obj 148 257 t f f;
#X obj 148 109 128;
#X obj 148 314 * 1;
#X connect 0 0 11 0;
#X connect 1 0 2 0;
#X connect 2 0 3 0;
#X connect 2 0 10 0;
#X connect 3 0 2 1;
#X connect 4 0 2 1;
#X connect 6 0 12 0;
#X connect 7 0 1 0;
#X connect 7 1 4 0;
#X connect 7 2 6 1;
#X connect 8 0 12 1;
#X connect 10 0 6 0;
#X connect 10 1 9 0;
#X connect 11 0 7 0;
#X connect 12 0 5 0;
#X restore 194 82 pd fire;
#X obj 189 323 + 24.5;
#X obj 230 323 + 24.5;
#X obj 289 260 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144
-1 -1;
#X floatatom 290 288 5 0 0 0 - - -;
#X floatatom 283 230 5 0 0 0 - - -;
#X connect 0 0 2 0;
#X connect 0 1 1 0;
#X connect 1 0 12 0;
#X connect 2 0 11 0;
#X connect 3 0 8 0;
#X connect 4 0 8 1;
#X connect 5 0 14 0;
#X connect 5 1 6 0;
#X connect 6 0 7 0;
#X connect 8 0 13 0;
#X connect 9 0 8 3;
#X connect 10 0 0 0;
#X connect 11 0 15 0;
#X connect 12 0 16 0;
#X connect 13 0 7 0;
#X connect 14 0 10 0;
#X connect 14 1 8 2;
#X connect 15 0 3 0;
#X connect 16 0 4 0;
#X connect 17 0 5 0;
#X connect 18 0 15 1;
#X connect 18 0 16 1;
#X connect 19 0 11 1;
#X connect 19 0 12 1;
#X restore 33 32 pd circle;
#N canvas 327 7 827 728 dial 0;
#X obj 194 361 t f f;
#X obj 230 398 sin;
#X obj 189 398 cos;
#X obj 189 497 i;
#X obj 230 498 i;
#X msg 442 333 clear;
#X obj 194 329 * 6.28319;
#X obj 189 463 + 24;
#X obj 230 463 + 24;
#X obj 191 4 inlet;
#X obj 194 301 / 127;
#X obj 270 629 s pd-\$0-dial;
#X msg 90 571 obj \$1 \$2 cnv 1 \$3 \$3 empty empty empty 20 12 0 14
-24198 -66577 0 \;;
#X obj 194 224 +;
#X obj 194 270 mod 128;
#X floatatom 268 410 5 0 0 0 - - -;
#X obj 192 136 t b f b;
#X obj 179 534 pack f f 2;
#X obj 189 433 * 14;
#X obj 230 433 * 14;
#X floatatom 239 224 5 0 0 0 - - -;
#N canvas 0 0 450 300 fire 0;
#X obj 148 22 inlet;
#X obj 148 186 until;
#X obj 148 228 f;
#X obj 180 228 + 1;
#X obj 171 160 0;
#X obj 148 346 outlet;
#X obj 148 286 /;
#X obj 148 136 t f b f;
#X obj 253 23 inlet;
#X obj 312 316 outlet;
#X obj 148 257 t f f;
#X obj 148 109 10;
#X obj 148 314 * 2;
#X connect 0 0 11 0;
#X connect 1 0 2 0;
#X connect 2 0 3 0;
#X connect 2 0 10 0;
#X connect 3 0 2 1;
#X connect 4 0 2 1;
#X connect 6 0 12 0;
#X connect 7 0 1 0;
#X connect 7 1 4 0;
#X connect 7 2 6 1;
#X connect 8 0 12 1;
#X connect 10 0 6 0;
#X connect 10 1 9 0;
#X connect 11 0 7 0;
#X connect 12 0 5 0;
#X restore 155 180 pd fire;
#N canvas 0 0 450 300 speedlim 0;
#X obj 163 70 inlet;
#X obj 274 69 inlet;
#X obj 163 253 outlet;
#X obj 163 158 t a b;
#X obj 163 126 spigot 1;
#X obj 406 136 1;
#X obj 275 146 0;
#X obj 204 187 del 40;
#X connect 0 0 4 0;
#X connect 1 0 7 1;
#X connect 3 0 2 0;
#X connect 3 1 6 0;
#X connect 3 1 7 0;
#X connect 4 0 3 0;
#X connect 5 0 4 1;
#X connect 6 0 4 1;
#X connect 7 0 5 0;
#X restore 191 81 pd speedlim 40;
#X obj 194 247 + 32;
#X connect 0 0 2 0;
#X connect 0 1 1 0;
#X connect 1 0 19 0;
#X connect 2 0 18 0;
#X connect 3 0 17 0;
#X connect 4 0 17 1;
#X connect 5 0 11 0;
#X connect 6 0 0 0;
#X connect 7 0 3 0;
#X connect 8 0 4 0;
#X connect 9 0 22 0;
#X connect 10 0 6 0;
#X connect 12 0 11 0;
#X connect 13 0 23 0;
#X connect 14 0 10 0;
#X connect 15 0 18 1;
#X connect 15 0 19 1;
#X connect 16 0 21 0;
#X connect 16 1 13 1;
#X connect 16 2 5 0;
#X connect 17 0 12 0;
#X connect 18 0 7 0;
#X connect 19 0 8 0;
#X connect 20 0 23 1;
#X connect 21 1 13 0;
#X connect 22 0 16 0;
#X connect 23 0 14 0;
#X restore 83 192 pd dial;
#X obj 110 75 inlet;
#X obj 98 101 nbx 3 48 -1e+037 1e+037 0 0 empty empty empty 0 -8 0
10 -262144 -1 -1 0 256;
#X obj 102 101 cnv 15 49 49 empty empty empty 20 12 0 14 -233017 -66577
0;
#N canvas 0 0 486 336 \$0-draw 0;
#X obj 44 24 cnv 1 1 1 empty empty empty 20 12 0 14 -24198 -66577 0
;
#X obj 44 25 cnv 1 1 1 empty empty empty 20 12 0 14 -24198 -66577 0
;
#X obj 44 26 cnv 1 1 1 empty empty empty 20 12 

Re: [PD] Gem pix and PDP failure - tatiana works with many errors.(patch included)

2008-10-01 Thread IOhannes m zmoelnig
Mark Pasquesi wrote:
 Iohannes,
 
 thanks for the quick replies and ideas.
 
 related on the minimac.  Kernel failure after clossing gem examples - or 
 trying to after they failed.
 
 patches...

please always answer to the mailinglist.
i don't have a minimac, but i guess some people on the list do.
they might be able to help more thanme.

and i don't see any problems in the patches

fgmasdr
IOhannes


 
 i think theyare clearly labeled.  As stated, tatiana functions on the mini 
 apple build,(osx 10..4.11, fink-macports conflicts, imaggemagickinstalled) 
 but outputs many error warnings...
 
 the other two cause failure, and function erratically - at times not at all.
 
 thanks,
 
 mark
 --- On Tue, 9/30/08, IOhannes m zmoelnig [EMAIL PROTECTED] wrote:
 From: IOhannes m zmoelnig [EMAIL PROTECTED]
 Subject: Re: [PD] Gem pix and PDP failure - tatiana works with many errors.
 To: Mark Pasquesi [EMAIL PROTECTED]
 Cc: pd-list@iem.at
 Date: Tuesday, September 30, 2008, 9:13 AM
 
 Mark Pasquesi wrote:
 2) This is from the Kernel panic produced on the machine by the pix_film
 help and the mixer patch
 Rather strange, no?

 attached are the 2 patches...

 panic(cpu 1 caller 0x001A49CB): Unresolved kernel trap (CPU 1, Type
 14=page fault), registers:
 [...]
 
 is this related to your other problem? or separate?
 (and you forgot to attach the example patches)
 
 fgmasdr
 IOhannes
 
 
 
   


___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Device: OCZ NIA

2008-10-01 Thread Max
Am 30.09.2008 um 17:29 schrieb Max:
 it has only windows drivers.

there is a sourceforge linux driver page, but no code yet.
http://sourceforge.net/projects/nia4linux/

and a posting on the forum:
http://www.ocztechnologyforum.com/forum/showthread.php?t=38441

aparently it doesn't need drivers at all since it behaves as a hid  
device.
http://www.ocztechnologyforum.com/forum/showthread.php?t=43298

but


 on OSX it shows up on the system profiler like this:

 
 Neural Impulse Actuator Prototype 1.0:

Version:   0.01
Bus (mA):  500
Speed: Bis zu 12 MBit/s
Vendor:Brain Actuated Technologies
Vendor-ID: 0x1234
 

i tried hans hid object in pd. it does not show the device when i  
list the connected items.
open by vendor/product-ID doesn't work since i have no poduct id,  
just a vendor id.

hans, any ideas?

max

___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] [PD-dev] abstraction caching

2008-10-01 Thread Luke Iannini
2008/10/1 Claude Heiland-Allen [EMAIL PROTECTED]:
 Benchmarking an Abstraction Cache for Pd
 

 I implemented a rudimentary abstraction caching mechanism for Miller
 Puckette's pd-0.41-4, which stores the parsed text (binbuf) associated
 with the class name instead of looking for files to load every time it
 is instantiated.


 Benchmark Mechanism
 ---

 Run 4 times, discarding first report:
 $ time pd -open layer_2.pd -send ; pd quit /dev/null

 layer_2.pd contains 99 layer_1.pd contains 99 layer_0.pd,
 total 9901 = 9801 layer 0 + 99 layer 1 + 1 layer 0


 Results: Without Cache
 --

 real0m0.524s
 user0m0.260s
 sys 0m0.256s

 real0m0.530s
 user0m0.224s
 sys 0m0.276s

 real0m0.527s
 user0m0.224s
 sys 0m0.296s


 Results: With Cache
 ---

 real0m0.082s
 user0m0.068s
 sys 0m0.004s

 real0m0.148s
 user0m0.120s
 sys 0m0.008s

 real0m0.085s
 user0m0.052s
 sys 0m0.012s


 Conclusion
 --

 Abstraction cache gives a speed boost of more than 500% when loading
 patches containing a large number of abstractions.

Claudius, this is awesome.  I'm going to build this later and see how
it does with my stuff, which has become a nightmare to work with (5-10
layers of depth, tons of instances, 3-15 minute loadtimes) (of course,
it's sufficiently fun after loading to engender my patience thus far :
)).

I'll post my results
Best
Luke




 Further Work
 

 The main drawback (and the easiest issue to resolve) of the current
 implementation is that once an abstraction is in the cache, it stays
 there forever, no matter if the file is modified within or without Pd.
 This could be fixed by flushing the cache immediately after the patch
 is loaded (perhaps using Pd's scheduler).

 Another drawback are that abstractions in different directories with
 the same file name can clobber each other - the first one loaded is the
 one true abstraction with that name, resolving this issue will be more
 difficult.



 #N canvas 0 0 450 300 10;
 #X obj 28 24 inlet;
 #X obj 33 262 outlet;

 #N canvas 0 0 450 300 10;
 #X obj 8 9 layer_0;
 #X obj 8 29 layer_0;
 #X obj 8 49 layer_0;
 #X obj 8 69 layer_0;
 #X obj 8 89 layer_0;
 #X obj 8 109 layer_0;
 #X obj 8 129 layer_0;
 #X obj 8 149 layer_0;
 #X obj 8 169 layer_0;
 #X obj 8 189 layer_0;
 #X obj 8 209 layer_0;
 #X obj 8 230 layer_0;
 #X obj 8 250 layer_0;
 #X obj 8 270 layer_0;
 #X obj 68 9 layer_0;
 #X obj 68 29 layer_0;
 #X obj 68 49 layer_0;
 #X obj 68 69 layer_0;
 #X obj 68 89 layer_0;
 #X obj 68 109 layer_0;
 #X obj 68 129 layer_0;
 #X obj 68 149 layer_0;
 #X obj 68 169 layer_0;
 #X obj 68 189 layer_0;
 #X obj 68 209 layer_0;
 #X obj 68 230 layer_0;
 #X obj 68 250 layer_0;
 #X obj 68 270 layer_0;
 #X obj 128 9 layer_0;
 #X obj 128 29 layer_0;
 #X obj 128 49 layer_0;
 #X obj 128 69 layer_0;
 #X obj 128 89 layer_0;
 #X obj 128 109 layer_0;
 #X obj 128 129 layer_0;
 #X obj 128 149 layer_0;
 #X obj 128 169 layer_0;
 #X obj 128 189 layer_0;
 #X obj 128 209 layer_0;
 #X obj 128 230 layer_0;
 #X obj 128 250 layer_0;
 #X obj 128 270 layer_0;
 #X obj 188 9 layer_0;
 #X obj 188 29 layer_0;
 #X obj 188 49 layer_0;
 #X obj 188 69 layer_0;
 #X obj 188 89 layer_0;
 #X obj 188 109 layer_0;
 #X obj 188 129 layer_0;
 #X obj 188 149 layer_0;
 #X obj 188 169 layer_0;
 #X obj 188 189 layer_0;
 #X obj 188 209 layer_0;
 #X obj 188 230 layer_0;
 #X obj 188 250 layer_0;
 #X obj 188 270 layer_0;
 #X obj 248 9 layer_0;
 #X obj 248 29 layer_0;
 #X obj 248 49 layer_0;
 #X obj 248 69 layer_0;
 #X obj 248 89 layer_0;
 #X obj 248 109 layer_0;
 #X obj 248 129 layer_0;
 #X obj 248 149 layer_0;
 #X obj 248 169 layer_0;
 #X obj 248 189 layer_0;
 #X obj 248 209 layer_0;
 #X obj 248 230 layer_0;
 #X obj 248 250 layer_0;
 #X obj 248 270 layer_0;
 #X obj 308 9 layer_0;
 #X obj 308 29 layer_0;
 #X obj 308 49 layer_0;
 #X obj 308 69 layer_0;
 #X obj 308 89 layer_0;
 #X obj 308 109 layer_0;
 #X obj 308 129 layer_0;
 #X obj 308 149 layer_0;
 #X obj 308 169 layer_0;
 #X obj 308 189 layer_0;
 #X obj 308 209 layer_0;
 #X obj 308 230 layer_0;
 #X obj 308 250 layer_0;
 #X obj 308 270 layer_0;
 #X obj 368 9 layer_0;
 #X obj 368 29 layer_0;
 #X obj 368 49 layer_0;
 #X obj 368 69 layer_0;
 #X obj 368 89 layer_0;
 #X obj 368 109 layer_0;
 #X obj 368 129 layer_0;
 #X obj 368 149 layer_0;
 #X obj 368 169 layer_0;
 #X obj 368 189 layer_0;
 #X obj 368 209 layer_0;
 #X obj 368 230 layer_0;
 #X obj 368 250 layer_0;
 #X obj 368 270 layer_0;

 #N canvas 0 0 450 300 10;
 #X obj 8 9 layer_1;
 #X obj 8 29 layer_1;
 #X obj 8 49 layer_1;
 #X obj 8 69 layer_1;
 #X obj 8 89 layer_1;
 #X obj 8 109 layer_1;
 #X obj 8 129 layer_1;
 #X obj 8 149 layer_1;
 #X obj 8 169 layer_1;
 #X obj 8 189 layer_1;
 #X obj 8 209 layer_1;
 #X obj 8 230 layer_1;
 #X obj 8 250 layer_1;
 #X obj 8 270 layer_1;
 #X obj 68 9 layer_1;
 #X obj 68 29 layer_1;
 #X obj 68 49 layer_1;
 #X obj 68 69 layer_1;

[PD] [polywavesynth] and [polygrainsynth] bug fix

2008-10-01 Thread Phil Stone
Hi again,

If you use either of these synthesizers, please grab the latest.  The 
previous versions moved gain to a global parameter.  I should have 
known better; this causes glitches in already-sounding notes when 
presets change.  I had a similar problem last year with [polywavesynth], 
but forgot about it.

This is the tradeoff to using [poly] to manage voices; if you want the 
ability to change presets cleanly, most parameters (i.e., those stored 
to make up the preset) can only be changed on new attacks.  I haven't 
thought of a way around this conundrum yet.

At any rate, the latest versions fix this issue.  Sorry for any 
inconvenience.

This leads to the web pages and download links for both synthesizers: 
http://www.pkstonemusic.com/pd_code.html


Phil Stone
http://www.pkstonemusic.com



___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list