hi guys! so i've had an oxygen8 for a few years now and i see them everywhere, so i'm sharing this handy little patch i made.

basically you're stuck with 8 knobs, and two sliders (modwheel and data entry). all this patch really does is takes the keyboard's input, numbers those 8 knobs and 2 sliders in sets of 10, and lets you switch between those sets with the hradio for up to 120 different controller values. the key input is passed straight through so even when you switch between various controls you can play the keyboard consistently.

even if you don't have an oxygen8, this patch will give you a little selfcontained set of sliders that you can use as a midi controller... so it's still useful for when you're not at home with your keyboard, or if you don't even have one.

basically all this patch does is take those 10 controls and lets you switch between 12 sets of them. it's useful for me in ableton so when i need to map more parameters than i have knobs for, i can assign more, and the numbering system is much easier to stay on top of than the default control values for those knobs (it's like 17, 80, 74, no consistency it seems).

on linux you should be able to jack the keyboard to pd's midi in, then jack the output to wherever you want. i'm currently on windows and i select usb keyboard in for input, and loopbe for output.

the numbers do nothing but change when you switch the hradio - the sliders are the corresponding controls (with the mod wheel as slider 9 and the data entry knob as slider 10).

come to think of it i don't think i tested the pitch bend wheel, i've been using this patch almost entirely for parameter controlling and not playing the oxygen8 notes at all. [notein] is patched directly into [noteout]

any questions/comments/ideas please, post them. this is a real quick patch i put together that worked almost better than i wanted it to but it can be very expanded upon. i was going to add symbols so you could tag/name all 120 controls but i was having trouble figuring out a way to store them and recall them, and send/receive to the symbols... so i just scrapped that.

basically all i do is make a tiny pd window and make [SCET], and just have that sitting at the bottom of the screen under my DAW (in this case ableton).

i haven't run into any conflicts yet for the most part but it's possible the controller numbering system might conflict with certain apps/synths/etc.

cheers guys!

http://www.pdpatchrepo.info/hurleur/SCET.pd

hello thanks for the info for DIO,

Everytime I click the DIO it gives me a different set of values.

audio I/O error history:
seconds ago error type
1.32 unknown
1.32 unknown
audio I/O error history:
seconds ago error type
1.61 unknown
1.61 unknown
audio I/O error history:
seconds ago error type
2.12 unknown
2.12 unknown
audio I/O error history:
seconds ago error type
2.35 unknown
2.35 unknown
audio I/O error history:
seconds ago error type
2.55 unknown
2.55 unknown
audio I/O error history:
seconds ago error type
2.77 unknown
2.77 unknown
audio I/O error history:
seconds ago error type
2.97 unknown
2.97 unknown
audio I/O error history:
seconds ago error type
3.20 unknown
3.20 unknown
audio I/O error history:
seconds ago error type
4.38 unknown
4.38 unknown
audio I/O error history:
seconds ago error type
5.13 unknown
5.13 unknown

Do you think upgrading to Snow Leopard with help?

thank you for you time
Aqu4

Ta Toxonic - I'll take a look at the patch tonight. Good of you to take the time. Apologies if I've misunderstood though, but I think what you're describing is not quite what I mean: The pitch shift is separated out from the delay time - you're running a pitch shift effect into a separate delay line, which is not going to give the same effect. The delay time will not shorten as the pitch rises. I'll take a look at your patch tonight though as I may have misunderstood what you're getting at.

Maelstorm - thanks also. I understand why the pitch changes on a delay pedal. The pitchshifter patch was a bit of a red herring - though of course it's the same principle. The difference between what you're (both, I think) talking about and what I'm talking about is the way that the pitch changes.

Assuming a stable C tone playing into the delay:
With the standard simple PD delay set up, if you move the read point of a vd~ then you get a glissando as it accellerates, a constant pitch change as it moves at constant speed. So if you turn the knob to change the delay time in the middle of a tone you start with a constant pitch (C), then get a rise of pitch, then it levels out at a new pitch (as you turn then stop turning the knob),
_
___/

If you feed back into the delay, the glissando is repeated as the read speed changed while the write speed was constant:
_ _ _ _
/ |/ |/ |/ |

The effect I'm looking to emulate on the other hand is more akin to changing the speed of a phasor~ reading an array - the pitch change is not a blip, but a stable interval's transposition - eg: you turn the knob, the pitch of the repeats rise by a given interval and stays at that pitch as it repeats (now more quickly):
______
___/

If you play a constant C tone, then speed up the delay until it is a major third higher, you get a major third diad (until the delay dies away), rather than a C tone with a repeating squiggle overlaid.
The effect is the same as you get by speeding up a tape loop delay (though the pedal I'm trying to imitate is a digital delay) which is why I think the rate of the write and read heads are being increased by the same amount.

[edit, just tried to make this clearer and removed a couple of errors]

I'll take another stab at a knob.

check this one out. You can send it [label $1( and [background $1( to change the color, and the knobs work much better. Still eats way too much cpu.

http://www.dafe.lukifer.net/pdpatches/crazymachineredux/knob.pd

Still needs to:

autoresize eg. [knob 100] for big knob
eat less cpu.
etc... what else?

you have multiple connections "fanning out" from one outlet. this means the execution order is undefined (read Pd's html manual for more detailed explanation). solution for this subproblem is [trigger] aka [t] - check the help patch.

Pd's depth-first chain of processing coupled with Gem's "not particularly dataflow" way of working (it modifies OpenGL's internal state directly at each object instead of passing the actual state along the patch cords) it leads to weirdness.

However, there is a solution: use both [trigger] for ordering, and [separator] to save/restore the OpenGL state (see also [pix_separator]).

something like:

[gemhead]
|
[trigger a a]
| \
[separator] [separator]
| |
|
or even maybe just use separate [gemhead] objects, if you have a simple scene?

Join us in Madrid!

http://medialab-prado.es/article/avlab_10

Wednesday 1th October

6 p.m. at Medialab-Prado
Presentation of the conclusions of the workshop by Javier Duero.
Presentation of projects by each work group. Opening of the showcase that
will be on until October 26th.

8 p.m. at Medialab-Prado: performance Waves to Waves to Waves

11 p.m. at Tempo Club: TRANS-AVLAB EXPRESS
Last sonic station of AVLAB 1.0, con actuaciones sonoras,
experimentales y audiovisuales de artistas participantes en el taller:
Olaconmuchospeces aka Diego Javier Alberti / Sotaques (VJ Xorume + DJ/MC
Gérson De Veras) / Servando Barreiro / Noish ~ aka Oskar / James Webb /
Groundrush aka Simon Dell / Hans Christoph Steiner / Raúl Bri Díaz
Pobrete / Tom Tlalim / Josecarlos Flores / Lena Schniewind / Jaime Lobato
/ Alberto Cerro / Roberto Moreno Maya / DJ Hidráulico.

at Tempo Club <http://www.tempoclub.net> (Duque de Osuna, 8. Metro Plaza
de España). Free admission.

Miércoles 1 de octubre

18:00h en Medialab-Prado
Presentación de conclusiones del taller por Javier Duero. Presentación de
proyectos por parte de cada grupo de desarrollo. Inauguración de la
muestra de resultados del taller, que estará abierta hasta el 26 de
octubre.

20:00 en Medialab-Prado: performance Waves to Waves to Waves

23:00h en Tempo Club: TRANS-AVLAB EXPRESS
Última estación sónica de AVLAB 1.0, con actuaciones sonoras,
experimentales y audiovisuales de artistas participantes en el taller:
Olaconmuchospeces aka Diego Javier Alberti / Sotaques (VJ Xorume + DJ/MC
Gérson De Veras) / Servando Barreiro / Noish ~ aka Oskar / James Webb /
Groundrush aka Simon Dell / Hans Christoph Steiner / Raúl Bri Díaz
Pobrete / Tom Tlalim / Josecarlos Flores / Lena Schniewind / Jaime Lobato
/ Alberto Cerro / Roberto Moreno Maya / DJ Hidráulico.

En Tempo Club <http://www.tempoclub.net> (Duque de Osuna, 8. Metro Plaza
de España). Entrada gratuita.

there's [separator] for OpenGL stuff and [pix_separator] for PIX stuff, as explained in the help patch for [separator].

Usually for 3D stuff I use it like:

[gemhead]
[t a a a]
[separator] [separator] [separator]

but I don't know if that's exactly how it should be.

some of you may be interested in this. it would be great to get some Pd papers or performances or lectures at this conference at my school coming up next july. here's the info:

> CALL FOR PROPOSALS
>
>
>
> SECOND INTERNATIONAL CONFERENCE FOR DIGITAL
> TECHNOLOGIES AND PERFORMANCE
> ARTS (DTPA 2005)
>
> SCHOOL OF INTERMEDIA AND PERFORMANCE ARTS
>
> DONCASTER COLLEGE
>
> DONCASTER, ENGLAND
>
>
>
> JULY 5-6, 2005
>
>
>
> This interdisciplinary conference provides a forum
> for those in the
> fields of theatre, dance, music and performance
> (researchers,
> practitioners, educators, systems developers) for a
> dynamic and exciting
> exchange of approaches surrounding the use of new
> media technologies in
> live performance.
>
>
>
> Proposals are invited for papers, performances,
> presentations, workshops
> and poster presentations on the following topics:
>
>
>
> * Live performance and interactive systems
> * Motion capture/motion-sensing technologies
> * Performance pedagogy, education and new media
> * HCI and live performance
> * Web-based performance and virtual performance
> spaces
> * Realtime music control
> * Gesture and interactive multimedia
> * Interdisciplinarity and new media
> * Performance software/hardware development
>
>
>
> All proposals should be approximately 200-300 words.
> Proposals for
> performances and installations should be submitted
> with an outline, CD
> or DVD support, as well as full details of technical
> and spatial
> requirements. Workshop proposals should also
> include information on
> technical and spatial requirements.
>
>
>
> All expressions of interest should be forwarded by
> January 5, 2005 to:
>
>
>
> Dr. Dave Collins
>
> Reader
>
> School of Intermedia and Performance Arts
>
> Doncaster College
>
> High Melton
>
> Doncaster
>
> DN5 7SZ
>
>
>
> Email: david.collins@don.ac.uk
>
>
>
> Notification of acceptance will be sent out by the
> end of March 2005.
>
>
>
> Performing arts companies and independent artists
> may have conference
> fees waived but will be responsible for travel and
> accommodation fees.
>
>
>
> Presenters may also wish to submit written papers
> for publication prior
> to or following the conference to the new
> International Journal of
> Digital Media and Performance Arts.
> [url=http://www.intellectbooks.com/journals/padm.htm
]http://www.intellectbooks.com/journals/padm.htm

>
>
>
> Full registration information will be available
> shortly on the School
> for Intermedia and Performance Arts web-site at
> [url=http://www.don.ac.uk/ipa
]http://www.don.ac.uk/ipa


if you have questions you can contact me and i might be able to help, or else just use the contact info above.
--zac

I like that track, kept me interested and made me smile, and when it finished I wanted to listen to it again - I've listened to it about 5 times this evening. Good work!

I've been trying to make similar sounds. I'm working on doing more live stuff with Pd, it's mighty fun, I can spend hours twiddling with midi knobs making freaky noises. I think I spend too much time fiddling with the knobs and not enough time enhancing my patches - I've not got much to show for the last six months of Pd-ing.

At first I was mapping each midi knob to a single control of the patch, but poorly thought out - in one patch I have 4 breakbeats, and I had 4 knobs mapped to the bpm control of each beat - "bpm 1", "bpm 2", "bpm 3", "bpm 4" - and it was a nightmare trying to get anything to sound good with it. Now I am trying to have more useful controls - "master bpm", "second pair/first pair bpm ratio", "pair 1 bpm spread", "pair 2 bpm spread". Still having 4 knobs to control the 4 bpms, but in a more musically useful way. Like a mathematical change of basis or change of coordinate system.

Another way I am trying to make live performance easier is using algorithmic processes - instead of controlling every beat I control aspects of a process that generates the beats - instead of being the drummer and the bassist and whatever else I am more of a conductor or director, controlling "jitteryness" or "density" or whatever. These processes can have a random part, so the live performance takes on a new element of reacting to the unpredictable output.