I want to remove them all and reinstall , but in root terminal it report me 0 files has been removed .

so I removed all the pd folder in terminal

after that I reinstalled the extended-intrepid version . but
when I run in terminal , a report shows here:

priority 98 scheduling enabled.
sh: /usr/local/bin/pd-watchdog: not found
priority 96 scheduling enabled.
sh: /usr/local/bin/pd-gui: not found

and I think that because I removed pd-0.40.2 folder which I compiled before.

and then I'm searching from google ,that the files which we compiled that should be install and removed by checkinstall.

so I downloaded the package and installed in terminal .

but checkinstall failed ..

report is here :

checkinstall 1.6.1, Copyright 2002 Felipe Eduardo Sanchez Diaz Duran
This software is released under the GNU GPL.

The package documentation directory ./doc-pak does not exist.
Should I create a default set of package docs? [y]: y

Preparing package documentation...OK

*** No known documentation files were found. The new package
*** won't include a documentation directory.

*****************************************
**** Debian package creation selected ***
*****************************************

This package will be built according to these values:

0 - Maintainer: [ root@mal ]
1 - Summary: [ pd description ]
2 - Name: [ src ]
3 - Version: [ ]
4 - Release: [ 1 ]
5 - License: [ GPL ]
6 - Group: [ checkinstall ]
7 - Architecture: [ i386 ]
8 - Source location: [ src ]
9 - Alternate source location: [ ]
10 - Requires: [ ]
11 - Provides: [ src ]

Enter a number to change any of them or press ENTER to continue:

Installing with make install...

========================= Installation results ===========================
cd ../obj; cc -Wl,-export-dynamic -o ../bin/pd g_canvas.o g_graph.o g_text.o g_rtext.o g_array.o g_template.o g_io.o g_scalar.o g_traversal.o g_guiconnect.o g_readwrite.o g_editor.o g_all_guis.o g_bang.o g_hdial.o g_hslider.o g_mycanvas.o g_numbox.o g_toggle.o g_vdial.o g_vslider.o g_vumeter.o m_pd.o m_class.o m_obj.o m_atom.o m_memory.o m_binbuf.o m_conf.o m_glob.o m_sched.o s_main.o s_inter.o s_file.o s_print.o s_loader.o s_path.o s_entry.o s_audio.o s_midi.o d_ugen.o d_ctl.o d_arithmetic.o d_osc.o d_filter.o d_dac.o d_misc.o d_math.o d_fft.o d_array.o d_global.o d_delay.o d_resample.o x_arithmetic.o x_connective.o x_interface.o x_midi.o x_misc.o x_time.o x_acoustics.o x_net.o x_qlist.o x_gui.o x_list.o d_soundfile.o s_midi_oss.o s_audio_oss.o d_fft_mayer.o d_fftroutine.o \
-ldl -lm -lpthread
cc -g -O2 -DPD -Wall -W -Wstrict-prototypes -Wno-unused -Wno-parentheses -Wno-switch -DDL_OPEN -DPA_USE_OSS -DUNIX -DUNISTD -DUSEAPI_OSS -I../portaudio/pa_common -I../portaudio/pablio -I../portmidi/pm_common -I../portmidi/pm_linux -fno-strict-aliasing -O6 -funroll-loops -fomit-frame-pointer -D_LARGEFILE64_SOURCE -o ../bin/pd-watchdog s_watchdog.c
cc -g -O2 -DPD -Wall -W -Wstrict-prototypes -Wno-unused -Wno-parentheses -Wno-switch -DDL_OPEN -DPA_USE_OSS -DUNIX -DUNISTD -DUSEAPI_OSS -I../portaudio/pa_common -I../portaudio/pablio -I../portmidi/pm_common -I../portmidi/pm_linux -fno-strict-aliasing -O6 -funroll-loops -fomit-frame-pointer -D_LARGEFILE64_SOURCE -o ../bin/pdsend u_pdsend.c
cd ../extra/bonk~;make
make[1]: Entering directory `/home/mal/Documents/pd-0.40-2/extra/bonk~'
make[1]: Nothing to be done for `current'.
make[1]: Leaving directory `/home/mal/Documents/pd-0.40-2/extra/bonk~'
cd ../extra/choice;make
make[1]: Entering directory `/home/mal/Documents/pd-0.40-2/extra/choice'
make[1]: Nothing to be done for `current'.
make[1]: Leaving directory `/home/mal/Documents/pd-0.40-2/extra/choice'
cd ../extra/expr~;make
make[1]: Entering directory `/home/mal/Documents/pd-0.40-2/extra/expr~'
make[1]: Nothing to be done for `current'.
make[1]: Leaving directory `/home/mal/Documents/pd-0.40-2/extra/expr~'
cd ../extra/fiddle~;make
make[1]: Entering directory `/home/mal/Documents/pd-0.40-2/extra/fiddle~'
make[1]: Nothing to be done for `current'.
make[1]: Leaving directory `/home/mal/Documents/pd-0.40-2/extra/fiddle~'
cd ../extra/loop~;make
make[1]: Entering directory `/home/mal/Documents/pd-0.40-2/extra/loop~'
make[1]: Nothing to be done for `current'.
make[1]: Leaving directory `/home/mal/Documents/pd-0.40-2/extra/loop~'
cd ../extra/lrshift~;make
make[1]: Entering directory `/home/mal/Documents/pd-0.40-2/extra/lrshift~'
make[1]: Nothing to be done for `current'.
make[1]: Leaving directory `/home/mal/Documents/pd-0.40-2/extra/lrshift~'
cd ../extra/pique;make
make[1]: Entering directory `/home/mal/Documents/pd-0.40-2/extra/pique'
make[1]: Nothing to be done for `current'.
make[1]: Leaving directory `/home/mal/Documents/pd-0.40-2/extra/pique'
cd ../extra/sigmund~;make
make[1]: Entering directory `/home/mal/Documents/pd-0.40-2/extra/sigmund~'
make[1]: Nothing to be done for `current'.
make[1]: Leaving directory `/home/mal/Documents/pd-0.40-2/extra/sigmund~'
install -d /usr/local/lib/pd/bin
install: cannot create directory `/usr/local/lib/pd': No such file or directory
make: *** [install] Error 1

**** Installation failed. Aborting package creation.

Cleaning up...OK

Bye.

root@mal:/home/mal/Documents/pd-0.40-2/src#

I dont know what to do now ....

Hi everybody, i've never write on this forum, but i was always following threads and i must say thanks to all the contributors in here for their help, you all are making an amazing work with this forum.
Now i'm here cause i would like to introduce you C::NTR::L 1.0 (beta).

C::NTR::L is the name of the free software for real-time Human-Computer Interaction exploiting physical computing possibilities. Developed in PureData by Marco Donnarumma. It seeks to be a tool for audiovisual live improvisation. The project started in 2007 and it remains a constant work in progress, i'm always interested in new ideas and collaborations (recently for example i worked a bit with Servando Barreiro and we included a module to use sensors, exploiting his DIY hardware Minia). This is the version 1.0BETA.
I'm planning to publish the patch, but before i want to work more on the interface, and enhance some features to offer a good usability of the tool, also for who doesn't work everyday with graphical programming.

C::NTR::L transforms your standard chord instrument - electric bass, guitar, violin, etc. - in a audiovideo controller without exploiting a specific external hardware or MIDI technology.
Once you connected the instrument to the sound card of your computer, C::NTR::L starts to recognize which notes you play. This is possible trought a complex structure of band pass/low pass/hi pass filters which automatically separate the core frequency of the incoming audio signal.
Then C::NTR::L analyzes the duration and the RMS of each single note and finally translates this data in order to control and trigger a set of audiovideo efx and modules which at this moment features:

**
VIDEO

* playlist
* scratch and loop points
* white/black fade
* color matrix
* blur
* delay
* strobo
* 3D efx
* presets save

AUDIO

* real-time sound in processing
* support multiple sound input (up to as amany as you want and your machine can stand)
* granulator (original module by Matt Davey THANKSSSSSS for the great ispiration!! i put your reference in posts and in the patch itself, but please tell me if you want more specific references.)
* bit-crusher (original module by Matt Davey)
* reverb (original module by Matt Davey)
* oscillators
* presets
**

I'm looking for beta-testers, so If you're interested, please write to info [at] thesaddj.com. Keep on checking www.thesaddj.com for future news.
And www.thesaddj.com/icontrolnature for the live show i perform with C::NTR::L.

An extract of the live project performed with C::NTR::L can be found here (live @ Cinesthesy Festival, France):

Soulful thanks for sharing, supporting and inspiring goes to: Rep (PD'r and Multimedia Artist), AssoBeam (PD'r and Multimedia Artists), Husk (PD'r and Multimedia Artist), Sero (Sound Artist), Brendan Byrne (PD'r and teacher), Jorg Koch (MAX'r and sound artist), Servando Barreiro (PD'r and Multimedia Artist), Hardoff (PD'r) G-noma (Multimedia Artist) and the incredible community on the PD Forum.

Marco / The S.A.D

I'm only working with the mac so some of these things will be different on other platforms:
In essence jack and soundflower are doing the same thing. They create virtual audio connections between applications. You could make a new virtual audio connection between live and pd. You need to route Live's audio out to jack or soundflower. In pure data you will be able to select an audio in (source) from the Jack or soundflower application (instead of your normal audio in like your soundcard and core audio).
I used both some years ago and they worked perfectly. I would start with checking leopard compatibility when choosing between the applications.

IAC is used for making a virtual midi channel. You make a new virtual midi channel and connect them with the new channel. The IAC thing works pretty good. If you trigger the signals in pd you can make a midi mapping in ableton live. Pretty straightforward and very flexible. The IAC thing can be found under applications/utilities/audio midi setup.

Edit: I just started reading your post again. Why not dropping live at all? You can easily read the messages from your external controller in pd.

I think we need a little more explanation. Are you sending raw OSC data to MidiYoke? OSC is a very different syntax than MIDI, depending on what you're getting from the iPhone app, you'd have to filter it and create midi-compatible data from it. If you post your 'glue' patch I can take a look.

@pythonusr said:

I have an application on my iPod touch. It sends OSC data to a Pure data patch (that I downloaded from the TouchOSC website, and then tweaked a little bit). How can I route this data to FL Studio (or MidiYoke) in order to control parameters and plugins inside of FL Studio in real time?

EDIT: I've found the MIDI out setting dialog, and I can send the data out to MidiYoke, and choose MidiYoke as an input in FL Studio, but I can't assign any parameters to the patch.

Solutions? Suggestions?

Hi guys

I'm trying to route MIDI between Ableton Live and PD using Mac OSX 10.4. I've set up a couple of IAC buses and can receive MIDI in PD from Live ok, but when I send MIDI back to Live using a noteout object it is not received by Live's armed MIDI track. The MIDI is reaching Live because the MIDI Track In Indicator in the Top RHC is flashing, it's just not getting to the track.

Looking at the MIDI stream in MIDI monitor Live gives this:

TIME SOURCE MESSAGE CHANNEL DATA

16:24:30.721 From IAC Bus 1 Note On 1 C3 100
16:24:30.846 From IAC Bus 1 Note Off 1 C3 64

whereas PD gives this:

*** ZERO *** From IAC Bus 2 Note On 1 C3 100
*** ZERO *** From IAC Bus 2 Note Off 1 C3 0

So PD does not seem to be outputting any kind of timestamp, could this be the problem? The only other difference seems to be the velocity of the note off message.

Any help would be much appreciated.

Cheers

Ummo

I am trying to write a patch to control ableton live with a monome 40h.

I have input device 1 in PD as 'from monome serial io' and output device 1 as 'IAC 1' (which in turn is set as the midi input for live), which works fine for controlling live with the monome.

I have midi output for live set as 'IAC 2' and input device 2 in PD as 'IAC 2' and the output as 'monome serial io'. I can not get the LEDs on the monome to react to live.

My question is how do i select different devices within PD. I can only get input and output device number 1 to work together.

I seem to remember that in MAX/MSP you can add the relevent letter (a, b or c etc) to the 'notein' object box to select the device. Can this be done in PD, if so how?

I know live is definatly giving out controller messages as I have -midinotefeedback- turned on and if I change the order of devices around in the midi settings I can light LEDs on the monome by moving sliders etc within live.

Hey Ceri! Tristan here.

I created a work for solo piano and live tape part generated by PD. It's called takeover and can be found on my site www.tjevs.com. It uses an interactive cue system, and it's kind of human against machine, and about working together. The full scores on my site too, as well as a live recording. I'll upload it into the PD community very soon, but currently I am exploring the use of midi and live audio alongside live instruments, as well as creating full works within PD.

I'd only been using PD for 2 months when I wrote my takeover patch, and now im getting into more and more intense patches, for example developing my own quad speaker setup for future live performances, which can be controlled by just hitting switches.

Keep PD'in you guys!

Tris.

hi,

i've been playing for a month or two now with pd and this really looks like the toy i've been looking for for a long time. i'd like to try it out on live gigs but i have a few questions. I'm currently on the WinXP 0.38.4 extended edition with a presonus firebox as audio device. So here are my questions :

• what about latency? currently it can't seem to get under 20/25ms because then portaudio starts crackling away. Would this be better under linux with jack, and is my soundcard supported under linux?
• how comes pd freezes (for a couple of milliseconds depending on the size) when loading a sample or a second patch? This is very annoying especially when playing live... are there any plans on improving this in the future or do we have to live with it?
• has anyone has live experience with pd - i'm sure you all have - so how do you overcome the problems mentioned above?

all advice is welcome.

cheers,

domien

I'm not sure I read you correctly
but I think this is what you want
It follows the middle inlet but if
that stops changing then it follows
the leftmost inlet after a delay set
at the rightmost inlet.

#N canvas 477 470 533 436 10;
#X floatatom 24 207 5 0 0 0 - - -;
#N canvas 0 0 482 472 autowobble 0;
#X obj 117 185 average;
#X obj 117 157 delta;
#X obj 117 89 f;
#X obj 110 344 line;
#X msg 110 320 \$1 100;
#X obj 156 237 == 0;
#X obj 165 45 inlet;
#X obj 37 45 inlet;
#X text 20 26 lfo krate;
#X obj 110 368 outlet;
#X obj 140 273 *;
#X obj 117 237 != 0;
#X obj 76 70 t b;
#X obj 80 268 *;
#X obj 110 296 +;
#X obj 117 132 line;
#X obj 117 110 pack 1 200;
#X obj 291 49 inlet;
#X text 144 23 manual fader;
#X text 285 27 idle time;
#X connect 0 0 5 0;
#X connect 0 0 11 0;
#X connect 1 0 0 0;
#X connect 2 0 16 0;
#X connect 3 0 9 0;
#X connect 4 0 3 0;
#X connect 5 0 10 1;
#X connect 6 0 2 1;
#X connect 6 0 13 1;
#X connect 7 0 10 0;
#X connect 7 0 12 0;
#X connect 10 0 14 1;
#X connect 11 0 13 0;
#X connect 12 0 2 0;
#X connect 13 0 14 0;
#X connect 14 0 4 0;
#X connect 15 0 1 0;
#X connect 16 0 15 0;
#X connect 17 0 16 1;
#X restore 24 179 pd autowobble;
#X obj 24 70 vsl 12 64 1 200 0 0 empty empty lfo-period(ms) 0 -8 0
8 -225280 -1 -1 5400 1;
#N canvas 0 0 450 300 ktrilfo 0;
#X obj 186 93 del 10;
#X obj 144 93 t b f;
#X obj 186 135 f 0;
#X obj 220 136 +;
#X msg 235 104 1;
#X msg 276 104 -1;
#X obj 187 175 >= 127;
#X obj 136 177 <= 0;
#X obj 136 202 sel 1;
#X obj 187 203 sel 1;
#X obj 223 71 max 1;
#X obj 223 47 inlet;
#X text 204 27 sweep rate(ms);
#X obj 225 235 outlet;
#X text 226 262 bang per cycle;
#X text 80 259 int val;
#X obj 104 235 outlet;
#X obj 307 70 loadbang;
#X obj 321 44 inlet;
#X text 324 26 phase reset/start;
#X connect 0 0 2 0;
#X connect 1 0 0 0;
#X connect 2 0 1 0;
#X connect 2 0 3 0;
#X connect 2 0 6 0;
#X connect 2 0 7 0;
#X connect 2 0 16 0;
#X connect 3 0 2 1;
#X connect 4 0 3 1;
#X connect 5 0 3 1;
#X connect 6 0 9 0;
#X connect 7 0 8 0;
#X connect 8 0 4 0;
#X connect 8 0 13 0;
#X connect 9 0 5 0;
#X connect 10 0 0 1;
#X connect 11 0 10 0;
#X connect 17 0 2 0;
#X connect 18 0 2 0;
#X restore 24 143 pd ktrilfo;
#X obj 110 101 vsl 12 64 1 127 0 0 empty empty manual 0 -8 0 8 -225271
-1 -1 1500 1;
#X obj 159 101 vsl 12 64 1 1000 0 0 empty empty hold 0 -8 0 8 -261681
-1 -1 3700 1;
#X text 177 138 hold is NOT milliseconds;
#X text 178 172 internal func but is roughly 1/2*square of hold;
#X text 179 155 It's actually complicated because of aymptotic;
#X text 31 254 The value may jump quickly when the lfo resumes \, need
to add a crossing detector for smooth transition;
#X text 21 10 Autowobble - output follows the k-rate LFO input UNLESS
the manual fader is moved \, but after a delay set by HOLD the output
will resume tracking the LFO;
#X text 358 273 ajf2005;
#X connect 1 0 0 0;
#X connect 2 0 3 0;
#X connect 3 0 1 0;
#X connect 4 0 1 1;
#X connect 5 0 1 2;

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

Hi,

I am trying with OSC. I followd the ling you gave me. From there I followed the pd link to http://barely.a.live.fm/pd/OSC/, that it is not working right now. But I found that in http://barely.a.live.fm/pd/OSC/OLD are some files. From those files I tried OSCx.tgz and OSCx.0.15b1.tgz. I tried to followed the instructions and I had a problem with tne m_imp.h with both packages. I got

In file included from dumpOSC.c:71:
m_imp.h:17: error: syntax error before "t_symbol"

followd by a huge list of errors.

I also tried with the flies from [url=http://cvs.sourceforge.net/viewcvs.py/pure-data/externals/OSCx/#dirlist, ]http://cvs.sourceforge.net/viewcvs.py/pure-data/externals/OSCx/#dirlis t,
I downloaded them manually because I don´t know a more smart way to do that. I followd the instructions in the readme file. When I get to execute the command "make OSC" in the folder OSC I get

/usr/lib/gcc/i386-redhat-linux/3.4.3/../../../crt1.o(.text+0x18): In function `_start':
: undefined reference to `main'
OSC.o(.text+0x17): In function `OSC_new':
: undefined reference to `pd_new'

followd by many lines.

How did you install the OSC library? Any idea where is my mistake?
tx