Warning: file_put_contents(): Only -1 of 6004 bytes written, possibly out of free disk space in /home/.sites/79/site1030/web/wp-content/plugins/wp-optimize/vendor/rosell-dk/webp-convert/src/Convert/Converters/Imagick.php on line 220
Warning: file_put_contents(): Only -1 of 6220 bytes written, possibly out of free disk space in /home/.sites/79/site1030/web/wp-content/plugins/wp-optimize/vendor/rosell-dk/webp-convert/src/Convert/Converters/Gd.php on line 428
A very crucial and maybe often underestimated point for working with (volume) faders, especially in live electronics application is their curve/behavior. Which range does it cover? How fast does “it” get “loud”. What is the behavior around the +0 dB mark?
I sampled the midi volume fader behavior from several of the most popular Digital Audio Workstations. The difference is quite obvious as you can see in the graph to the right.
I made a Pure Data abstraction as replacement for the frequently used [fadtorms] or [dbtorms]. In connection with the .txt sample files it can be used to scale your midi fader input.
Get the abstraction including sample files and Matlab plots here:
If you are working with Xbox Kinect Sensor here is another goodie for you – A pure data / Gem external to get Kinect rgb and depth streams as well as skeleton tracking and multiple hand tracking via OpenNI
DarwiinRemoteOSC allows to connect via Bluetooth to the WiiRemote controller. It also supports Nunchuk, Classic Controller and Balance Board.
All data from the Wii Controller is forwarded via OSC. IP and Port can be changed by command line argument. OSC can be sent to DarwiinRemoteOSC to turn on Force Feedback, LEDs and retrieve Battery status.
I decided to cancel development on the Kinect plugin for pix_video – please use pix_freenect if you need video streams from Kinect or pix_openni if you need some advanced tracking features as well