95 result(s) matching "stylophone-midi", (0.09 seconds)
warning: MIDI timing FIFO overflowed, MIDI-Clock Signal and Realtime Termination
I was having problems, getting MIDI-clock / realtime-MIDI to work in PureData. When I start receiving a MIDI-clock-signal freshly for the first time after starting PureData everything works as expected. PureData received the realtime MIDI data. (I use this patch for deriving the clock-data: http://little-scale.blogspot.de/2013/03/dealing-with-midi-clock-in-pd-sync-pd.html). But now... when I stop the clock and restart the thing, I always got the error "warning: MIDI timing FIFO overflowed" in pd-console. I am using Ableton Live 9 as host - MIDI is going over the IAC driver on Mac OS-X. Search on the web only brought old websites and no solution to this, so I experimented a little bit myself and maybe found a solution: What helped was the following: By coincidence, I went to the "preferences..." setting-panel. There I turned of the "Realtime Termination"-flag (I have the version in German, there is it called "Echtzeit Terminierung" - maybe the English translation differs.) **Does anyone knows what the Reatime-Termination Flag does?** Any why this is solving the realtime-MIDI-issues that occur with receiving MIDI-clock signals? I just want to be sure, that this is really solving the problem.
MIDI CC's to MIDI Program Changes
Hello, Has anyone tried to set up PD as a MIDI translator that will take an incoming MIDI CC value and output a Program change value? If so, can you provide a few tips--I'm a newbie. Thanks!
MIDI file playback controlled via MIDI keyboard
Hi all, This is a simple patch I created for an user in this forum, so I may as well share it here. It allows you to load 10 MIDI files that can be played via Pd or by pressing keys in a MIDI keyboard. Download: [midi-player.zip](/uploads/files/upload-a8fa431e-be21-4014-a12e-f5623ab1fe94.zip) ![howto.png](/uploads/files/upload-5d2195b0-5e0c-46b7-804e-c626fbf4fc2a.png) I hope someone will find this useful. Best, Gilberto
How to add/remove MIDI notes from a list using MIDI in and note on/off?
I need to populate a list with the MIDI notes that are being pressed, and remove the note from the list when the key is released. One idea is to use [notein], and if the velocity is> 0 then add the note to the list, and if the velocity == 0 then remove the note from the list. But I have no idea of how to implement this. I think I need [list-extend], [list-find], and [list-delete], but I just can't figure out an implementation. How can I do this? **EDIT: solved the problem and have a working patch. See my reply below for details.**
Monome/androidome live midi looping (plus midi loop abstraction)
i patched up an app for the monome and thought i'd share. included in the zip is a midi looping abstraction i rolled "from scratch" - it (the abstraction) is completely independent from monome requirements and can be used generally in any pd app (provided the cyclone library is installed). [http://monome.org/docs/doku.php?id=app:helix] \[EDIT: HA! alright - i JUST realized i wrote 'androidome' in the title. my mistake, i meant ARDUINOME. jeez.\] : http://monome.org/docs/doku.php?id=app:helix
Midi joystick controller for massive & modul8 or any midi software !
message if interested.... tanks for your time! [http://www.youtube.com/watch?v=sJ6K4cfet\_o&feature=my\_liked\_videos&list=LLdmiAagZxNdcXMVR4LC-Jpg] : http://www.youtube.com/watch?v=sJ6K4cfet_o&feature=my_liked_videos&list=LLdmiAagZxNdcXMVR4LC-Jpg
Midi/notein - isolate midi note + velocity
Hey. Im pretty new to pd and im a bit confused. Im working on my Diploma, a light show for a Band called Brandt Brauer Frick. You can see a layout graphic here [http://www.sebastian-selbach.com/wp-content/uploads/2011/08/Stage.jpg]. The light-show will be composed in Ableton Live an i need a sort of preview screen for midi data. My question is how do i get the velocity of one singel Midi note. I know that i can isolate the channel with notein 1 but how does it work for the midi note? thanks in advance. : http://www.sebastian-selbach.com/wp-content/uploads/2011/08/Stage.jpg
Strange midi issue (delayed midi in data ???)
hi everybody explanation of my problem : config : ableton + touchOSC + loopMidi (also tryed midiyoke) (+ PD of course) I use midi clips, sending CC data (1 cc per clip, only 1 channel used for midi output, to avoid wrong data) so I can use the CC value to make play position cursors on touchOSC. in PD I set something like that : \[ctlin cc\# ch\#\] | | | \[Number) \*\*\*for monitor purpose, easier to read than \[print\] | \[send /fader $1( | \[sendOSC\] My play position faders are sometimes working perfectly and sometimes they are glitchy, jittery. at first i thought it was caused by the big number of OSC messages sent by puredata (I planned to do a trick that would filter values after \[ctlin\] so that it doesn't route redundant values and then only sends different OSC messages. but i got lazy and investigated elsewhere first) I set a number object after \[ctlin\] and found that the values are delayed. sometimes cleanly delayed : everything coming late, and sometimes warped : everything ok, but some intermitent lower values. and sometimes for no reasons either it works perfectly. the delays are several seconds long. in ableton i can see the cursor moving correctly all along the midi clip. if i turn off midi out from ableton during a delay, I still have midi activity for a few seconds in PD other data are sent & received on time (OSC, midi out) I only use 1 midi in and out in PD and ableton, via 2 loopMidi virtual cables. audio is off, no delay (1ms) what could cause that ? it's either between ableton and PD or inside PD thanks in advance
Fiddle~ - signal to midi - better way to generate midi note durations?
Greetings All, I have constructed a patch using \[fiddle~\] that will take a signal from my guitar rig and output midi info via \[noteout\] so that I can play other synths. Right now, if you look at the patch, I have \[timer\] measuring the time between attacks which is then fed eventually into \[noteout\]. This process is retrospective, meaning that it takes the note duration of the last note I played and applies it to the current note I am playing - not so great if I are shredding away and want to end the phrase with a sustained note that is longer than the stream of short notes that I just played because that long note I want will only have a short duration, unless I use an expression peddle through sustain subpatch that would use \[ctlin 64 1\] or something. That works ok, but I would really like to not have to worry about having my foot on an expression peddle to ensure the sustain. Is there another way that I can generate a midi note-on message and have it sustained until I play another note? Any help is much appreciated! Thanks, dkeller [http://www.pdpatchrepo.info/hurleur/SIGNAL-To-MIDI.pd] : http://www.pdpatchrepo.info/hurleur/SIGNAL-To-MIDI.pd
Stylophone as MIDI
Hello there, I was wondering if someone here has ever turned a stylophone into a midi controller? I mean the new one? Found this great and simple tutorial - [http://sites.google.com/site/skriyl/Home/midi-stylophone] , but too shame it's for the original old one stylophone. I opened up my new one - there is no resistor ladder, only two pcb's and i do not knwo where to start there. : http://sites.google.com/site/skriyl/Home/midi-stylophone
Midi to hz, and hz to midi formulas
hello, its me again with more newbie questions. im studying with johannes kreidler book and there is a formula on converting midi notes to hertz on chapter 3 (audio) that im not sure i understand. i know there are \[mtof\] and \[ftom\] objects but since its on the book as a formula im guessing its important and i wouldnt like to skip it just because the computer can do it for me. according to the book the midi to hz formula using the \[expr\] object is expr 440\*(pow (2, (($f1-69)/12))) if the midi note is 39, the frequency is suppossed to be 77.78 but when i try to do it with my calculator i get a wrong result. there is also the inverse formula for hz to midi which is m= 69 + 12 . log2(f/440) if someone could break these formulas down for me it would help me understand how these objects work. (i already know expr and variables, im sure im not reading the formulas right).
Select midi velocity only from specific midi note number
hi, i'm trying to get this to work but frankly i dont understand why this patch does exactly the opposite of what i want ;-) what i'm trying to achieve here is that only if midi note \#65 is coming in i want to know about this notes velocity value. any other midi-\# should just be ignored or even reset the velocity value to zero. any help would be much appreciated! !(http://offspacecenter.com/pd-q.png) [http://www.pdpatchrepo.info/hurleur/velocity\_select.pd] : http://www.pdpatchrepo.info/hurleur/velocity_select.pd
Midi to text? ...or midi import in PD
Howdy, I'd like to import midi files that i make in a sequencer into PD. I've found a few ways to convert midi files to text on windows but was wondering if anyone here has a better solution (i work in osx)...Or if theres already something in the extended versions that can do it?
Midi Clock into Pd from Sequencer?
how can I can get Pd to receive Midiclock (start/stop/continue/tempo) from a sequencer (Logic on Mac in my case)?
Midi controller pads to toggle
I’m trying to get the pads on my midi controller to switch a toggle object on/off. I can get the pad to toggle but only momentarily - switches on when I push then off when I release. I would like to make it so that 1st time I push and release the pad it turns the toggle on then 2nd time it switches off. I’m thinking I need some way of detecting the toggle state or is there a simpler way of doing this. I hope my question is clear and any help would be appreciated. Cheers.
Midi Controller Problems
Hello This is probably a basic answer to a basic problem. I have a midi controller mapped to a number box. As you would expect the numbers in the box when I turn the knob range from 0 - 127. However I want to have the range from -200 to +200. I How do I acheive this ? Any help would be appreciated. Thanks (:
MIDI issues with Windows 7
Hi all, I've been having problems with MIDI in Pd and wondered if anyone had any suggestions. I'm on Windows 7 and Pd 0.43.4. I'm using a Korg nanoKontrol2, and can see the MIDI input fine in MIDI-OX. When I set the nanoKontrol as my MIDI device in Pd, I have to move a fader several times before Pd registers it. Once it does, MIDI data comes in in real time, so it isn't just a latency issue. It's almost as though Pd struggles to recognise which channel the data is coming in on. Also, moving a fader up and down doesn't produce a consistent result (such as the fader down being 0 and the fader up being 127) - pushing the fader all the way up and all the way down produces completely different numbers in Pd each time I do it. Today, I installed LoopBe1 and set this as my MIDI output in MIDI-OX, then set it as my input in Pd. However, this produces no MIDI input whatsoever, even though I can see that everything is working fine in MIDI-OX. Has anyone had any success with a similar MIDI setup? Thanks in advance
NRPN Midi Messages
Hello, I'm trying to send NRPN messages to a microKorg. At first, connected the midi out of the keyboard to midi in of computer to see print the number I needed. Through a ctlin, first outlet gave me 3 numbers (one of them with the parameter, another one I believe with the MSB, and the 99 CC that NRPN uses). The other outlet gave me also 3 numbers. Using those numbers to send it from PD to the microKorg midi in, can't make it work. Tried with a ctlout with a trigger, sending the 3 numbers to first inlet in and the other 2 on the second inlet, didn't work. Tried with 2 ctlout to use CC 98 and CC 99 and that wasn't the answer neither. Does anybody knows how to solve it? Some of you have worked with NRPN? Some example? Thanks a lot!
Arduino MIDI controller - [ctlout] object sending the same cc value for all 4 different pots to Nuendo
hi, I've been building a MIDI controller (pots and buttons) using an arduino connected to PD. I've got the arduino communicating nicely with PD via a [comport] - [repack] - [unpack] style setup. The unpacked values (which have been divided by 8 during my C++ code in order to step them down from 1024 to 128) are then patched into [ctlout] objects with cc numbers entered as arguments. But for some reason when i try to assign these to controls in either cubase or ableton the cc values all come up the same. ie... all 4 pots register as the same cc value. even though they are definitely set to different values in PD. I'm using loopbe30 as my MIDI routing application and have my 'MIDI out' in PD and 'MIDI in' in Nuendo seemingley set correctly. Any help with this would be very much appreciated as I have been trying to get this working for months and will NOT give up as it feels as though I am so close/. Thanks
Heavy MIDI jitter and problematic note-offs
Hi, I have been wondering why is PD's MIDI output so jittery and why it has so many problems with note-offs not working properly (hanging notes every few dozens of notes, with fast sequences even more often). I have recently tested a simple MIDI out patch in Max 7 and its MIDI output is rock solid no matter what. No hanging notes, no noticeable jitter. It is the major thing that is making me considering purchasing Max 7 but I have also found out, during the testing, that it really crashes a lot while doing basic things so I would stay with PD if the mentioned MIDI output problems are fixable. Can there be anything done in/with PD that would make MIDI out solid as in Max 7? I really really want to love PD but this is a major bummer. I really need to output MIDI to a DAW. Thank you.
[learn_midi], an easy way to learn a midi note, controller, or program change
![Screen Shot 2015-03-26 at 10.33.47 PM.png](/uploads/files/upload-4cb53d91-0e5f-4376-974b-b9e44e7ede7d.png) Here's the abstraction: [learn_midi.pd](/uploads/files/upload-9317c24d-6815-4557-a402-312ba05a9979.pd) To use, hit the toggle and then press a note, move a knob, or press a pgm button. The basic premise is to associate a unique number to each type of midi input (note, ctl, or pgm), and packing them into a list. "Learning" a MIDI note, ctl, or pgm number means storing this list in the cold inlet of **[list-compare]** from **[list-abs]**. If any MIDI data coming in the hot inlet of **[list-compare]** matches the stored data in its cold inlet, a **[spigot]** opens up and the data is allowed to pass through its outlets. EDIT: The outlets are meant to mirror those of **[notein]**. Outlets are as follows from left to right: (note, ctl, prgm number), (velocity, ctl value, pgm value), channel no.
Creating a Patch to play Drum Samples with MIDI Input
Hello all, I am brand new to PD and would like to create a patch on my laptop that takes input from a USB MIDI drum controller and plays back the appropriate drum samples (based on velocity and key).. I am trying to write the patch and get it working on my Windows 8.1 64bit laptop, but I later want to upload the patch to my Beaglebone Black. Are there any patches I could maybe start out with and modify to achieve this, or any advice in general on how to do this? Also, does anyone have an idea of probelms I may run into when switching from my laptop to the Beaglebone Black? Thank you for your help, Aaron
Midi input WinXP
when i select my usb keyboard,i get this warning... 'Warning: midi input is dangerous in Microsoft Windows\\; see Pd manual' and if i load a patch synth,my keys don't play the synth. i'm sure pd can alow midi in,is there something i'm doing wrong?
Midi & Audio glitching over IAC bus
Does anyone know whether Pd's Midi runs in the same thread as the GUI? I have managed to get Plogue Bidule synced to a midi clock sent from Pd over the IAC bus (OSx), but when say a window is moved, there is loads of glitching in the audio and the jitter seems to increase enormously. I have tried wacking up the buffer sizes but of course, the increased latency means that Bidule is synced by the order of the buffer size...Or worse if theres jitter involved. ITs not really practical to not touch the computer whilst it is running! How can this be remedied? Is some kind of latency compensation required here I totally long for the day when Jack OSX gets midi then we can have rewire like performance but with all the benefits that Jack currently provides! (does anyone have a clue when this might be?) cheers
Sending Midi to Virtual Keyboard (Windows 7)
Hi there, I'm trying to send a midi from PD to a virtual keyboard. I am using LoopBe1 as my internal midi port. My patch consists of a message box with a value of 60 connected to the hot inlet of a makenote object (velocity 60, duration 500). The first outlet of this is connected to the first inlet of "noteout 1', with the second outlet of makenote connected to the second inlet. I've set the midi output device to LoopBe. I've also set the input device of the keyboard to LoopBe. I can't see anything amiss with this setup, but the keyboard doesn't seem to be receiving any messages from PD. I switched the patch so that the keyboard was inputting midi into PD in order to test if it was a problem with LoopBe, but this doesn't seem to be the issue as pressing keys initialises the bang in the test patch. Can anyone see where I've went wrong?
separate ctlin and ctlout for two MIDI devices
Hello! Is there a way to specify the which midi device sends/receives CC's via ctlin/ctlout? Using ctlin/ctlout currently sends/receives CC's on all devices, which is not very useful. I'm trying to use two midi interfaces to translate MIDI from an external sequencer to a drum machine, and another from the drum machine to the sequencer. Thanks!
What is the difference between [mod] and [%]?
Ok, this might be a very basic question, but I wasn't able to find a satisfactory answer through searches, so here I am. Is there any difference between the [mod] object and the [%] object? In Designing Sound by Andy Farnell and on Karim Barkati's Reference card, the  object is listed as a 'bit twiddling' object, but functionally, I can't find any difference between them and I've been using [%] to get remainders all along and just found out about [mod].
Filter specific MIDI CC's
Hello! I have a hardware sequencer that does not transmit NRPN's, so I'm using PD to translate CC's going from the sequencer into NRPN's to external gear. I also need all the midi data coming from the sequencer such as clock, notes, other CC's, etc... This is why I'm using midiin --> midiout. My only gripe is that the CC's I'm using from my sequencer to modify the external NRPN's still get dumped into midiout. I've thought about skipping midiin-->midiout and instead routing all notes, midiclkin, ctlin... etc. individually, but I feel like that's major overkill. Does anyone know a better way to filter out CC's from incoming midi while allowing all other MIDI data through? Something like: [midi + cc1 + cc2] --in--> PD[-cc1] --out--> [midi + cc2] Thanks!
total newbie - how to set up 16 rotary MIDI CC messages to OSC
Hi there! I'm a total newbie to Pure Data but absolutely loving the possibilites. I need a little help with making a patch that will take 16 rotary MIDI CC controllers and then send those as separate messages to an OSC device. I can get it up and running kinda but keep getting various error messages. Like - packOSC: bad path: 'float' I know I'm doing something monumentally stupid but can't figure it out with my 8 hours experience! Any pointers? Cheers.
My Homemade MIDI Turntable - help
Hello :-) My name is Jorge Pinto and I am from Portugal. I am electronics professional and I like to develop hardware. I am doing a cheap(+-30 Euros) and simple "Homemade MIDI Turntable" to connect on PD. I am looking for information on others projects similar and feed-back, ideas, etc... I hope to release the final version very soon with GPL licence. Please tell me what you think about and give me suggestions. Thank you. Home page of project in English with one video: [http://casainho.net/tiki-index.php?page=Homemade%20midi%20turntable] --- Casainho [http://www.Casainho.net] : http://casainho.net/tiki-index.php?page=Homemade%20midi%20turntable : http://www.Casainho.net
Patch attached to convert MIDI 127 stream to High resolution control
Hi All, I've attached a patch that I constructed that converts a MIDI continuous controller stream of 1~127 into much higher resolution output (currently set to 127^2 steps). It basically ramps between one MIDI number to the next over a time period specified by the amount of time that has elapsed since the previous MIDI number was passed. Of course it still restricts you from stopping on a number in an range between two MIDI numbers, but at least it allows that range to be swept through. For example, if you want to use a controller to sweep through frequencies from 20Hz-20,000Hz, if you use a MIDI controller normally it would pick out only 128 discrete frequencies over that range and step from one to another like stepping stones. But using this patch, if you move the controller from, say, 34 to 35, the result would be a smooth sweep through frequencies of about 5300Hz to 4470Hz over the time period equal to the time taken to change from 34 to 35\. Unfortunately, the major limitation is that the patch only knows the time period at the moment you reach the new number, so the ramp only starts by the time it should have finished. This makes it impractical to use for slow sweeps, but you could use a separate controller for these slower movements (one that is much lower geared). Any suggestions for improving or expanding the patch would be welcomed. I know that pitch bend already performs as a 14-bit controller, but I don't want to be limited to having only one hi-res at a time (I only have one pitch bend wheel!) Cheers, Brett [http://www.pdpatchrepo.info/hurleur/High\_Resolution\_Controller.pd] : http://www.pdpatchrepo.info/hurleur/High_Resolution_Controller.pd
PD 0.40-2 Audio/Midi Settings on MacOSX
Hi all, my first post here... I'm using pd 0.40-2 on MacOSX Tiger 10.4.9, with much fun! But everytime i start the app, i have to set again audio/midi preferences, because pd was back to default parameters (builtin audio i/o and no midi in/out). Yeah, this is not really a problem, but is a little annoyng... Do you know if this happen on osx even with 0.39.2-extended-RC1? Is this version the better one? What are the core differences between the 2 versions (beyond extensions..)? Thank you very much Regards jk
Sending OSC from PD to trigger MIDI in a DAW - a lot of jitter and imprecision - help me to find the cause
Hi, I am not sure if this is a correct forum section to ask. I have tried using MrPeach's OSC to trigger the virtual MIDI keyboard in Reaper to record MIDI on a track. At first I thought this would get me much more precision in timing of the events than if I was sending simple MIDI from Pd. However, there is a lot of timing imprecisions in both beginning and length of the notes. I am using the loopback connection to send the data from Pd so it should be very fast and precise in theory. I have a fast CPU. I suppose the timing in Pd itself is rock-solid and it outputs the OSC messages with correct timing. So what else could be causing this very noticeable imprecisions? Any suggestions would be very welcome. Thank you
Patch to play midi with Makey Makey Arduino Board
Made an error in a patch and now it won't open for me to fix...
Hello everyone, I'm constructing a PD patch for a uni assignment, but in the process of tinkering with my patch I've managed to create some kind of infinite feedback loop; the console says "error: stack overflow". My problem now is that I can't open the patch to get rid of the error; it simply freezes and doesn't open. Other patches work fine. I've got a few loadbangs initialising some parameters in so I put "noloadbang" in the startup flags, but it says "noloadbang: can't load library" on opening PD. I *could* just start again and build it from scratch, but I'd rather not... any suggestions on how I can get at my patch to fix it? Using Windows 7 on a Dell laptop, "pd version 0.42.5-extended" Ta
midi channel problem
Hi. I'm having an strange problem with midi channel using pd. I'm working with two different midi controller, one is assigned to midi channel 1 and another to midi channel 2. If i connect them separately they work right, sending and receiving from their channels, but if I connect the two at the same time (setting first on pd) all works bad. I can see with ctlin than first controller (channel 1) now send to midi channel 17 and sometimes 33... crazy... midi only works with 16 channels, right? I'm missing something? Ah...I'm working with Pd-extended on Debian wheezy 32-bit. Thanks a lot for the help!
Midi file written but does not produce sound when played
I am fairly new to PD, and am working on an algorithmic composition patch as part of a project, and I am attempting to save the midi output to a midi file, using the seq object. I am currently able to write data to the seq object, but when I create the midi file, it plays for the length that I recorded but it does not produce any sound. I have attached the patch - any advice would be extremely appreciated! Here is the patch: [relaxed.pd](/uploads/files/upload-01d42346-af15-4c68-a27b-72624d373dde.pd)
Does pix_film work in single buffer mode?
Hi all, I need to use single buffering mode in order to plot circles that will stay on the screen. I also want to display a video at the same time, using pix_film, but it doesn't seem to work - After sending the buffer 1 message to the gemwin, I am sending bangs via a metro to the gemhead object that outputs to the pix_film. But nothing happens... Does anyone know why? Thank you so much in advance...
[metromidi~} Metronome/MIDI clock source
Hi all, Here is a handy patch if you need a DIY MIDI clock source. This works both as a traditional metronome as well as a MIDI clock source. I created this to use with apps like Sooper Looper which syncs to MIDI clock information, but doesn't have an internal sound generator to keep me in time. Let me know if you need me to explain something because it gets a little confusing at parts. To use this just unzip the files to wherever you keep your patches and open **[metromidi~]** ![Screen shot 2014-11-13 at 1.50.17 PM.png](/uploads/files/upload-7e215a62-f4bf-40c6-b221-14772ade1247.png) [metromidi~.zip](/uploads/files/upload-e6649d14-afa5-4b87-965d-83493796c209.zip)
PD Midi to Logic not working Properly
So I've been using IAC and noteout objects to send midi values to logic. The only problem is even when I have the output channel in PD set, [noteout channelnumber], and the input channel set in logic to the same value, the values are still either sent or received on all channels. I've tested this via a very simple setup sending a note to channel 1, and a note to channel 2, with 2 different software instruments set to the right channels, but whenever any midi value is sent, it still arrives at both instruments. Anybody have any ideas as to why this is happening? (And yes, I have auto demix for multitrack already checked). I'm pretty new to this area in general, so it's possible there's something I'm not understanding about the setup.
I get an error when opening a patch containing an abstraction that I have made
Hello, I have made an abstraction called *"Key"* to easily manage keyboard shortcuts in pd, but everytime that I load a patch containing the abstraction I get this error for every instance of the patch that is loaded: *load_object: Symbol "Key_setup" not found* what can cause this? My abstraction has two creation arguments and I get the error even if they aren't used. Any ideas? However this is the patch: [Key.pd](/uploads/files/upload-76b15aa1-23a3-4923-8d4c-a339101c9fdf.pd)
cc input into MIDI CC and Note input
Hello everybody! I have a question: I have a Brain V1 from Livid Instruments and I have it connected with a couple of FSR sensors sending cc inputs. I would really need to convert that input into note + cc input. Can I do it with PD!?!? (I'm a truly new user of this software so far..:) I thank you in advance guys!
Hello, I'm a little lost here. What i'm trying to do is figure out a way to play a midi file back in a Vanilla PD patch https://email@example.com/msg27247.html After I read my midi file, looks like: setparam 0 Time 0 0 999999 0 1000 200 0; setparam 1 Pitch 0 0 127 60 12 4 0; setparam 2 Vel 0 0 127 64 12 4 0; setparam 3 Dur 0 1 99999 200 800 200 0; setparam 4 Chan 0 1 16 1 8 1 0; setparam 5 Track 0 1 32 1 8 1 0; setparam 6 X1 0 0 999 0 80 20 0; setparam 7 X2 0 0 999 0 80 20 0; restore; 450 78 96 250 1 2 0 0; 250 78 96 250 1 2 0 0; 250 78 96 250 1 2 0 0; 250 78 96 250 1 2 0 0; stop; I figure out what to do next. In the bottom left corner there is this object [ route noteon noteoff polypressure cc pgm pitchwheel ] and it says to copy/paste these commands to possibly filter the data that I want to be played. That's my only idea as of right now. Other than that, I'm completely lost.
midi input for monophonic sinthesizers...
In a monophonic sinthesizer, If we connect the [notein] directly to a [mtof] and then to an oscilator, the effect is not always as expected. Sometimes the note off message turn off a different note that we would like. The system should store the penultimate key pressed, and play it again when release the last one. But in some cases the player can also release that penultimate key (while the last key is still pressed) and the priority should transferred to the antepenultimate key... and so on. So, we need a patch which can memorize at least the 10 last notes and make this work for us. [notein_mono.pd](/uploads/upload-37a7ae14-29c1-4bf4-b585-a55f62000bc0.pd) The explanation of how does it works will be uploaded soon in my youtube channel: http://www.youtube.com/user/canalpuredata
1st time – Test Audio and MIDI, producing only distortion, instead of sine wave
Getting a start with pd today, and my initial issue is the test after installation is producing just distortion instead of a sine wave. This must be wrong. On a windows machine with internal soundcard using ASIO, Not at all far into sound manipulation yet, but have software that does involve the ASIO somehow - REW (Room EQ Wizard - used for room acoustic measurements and loudspeaker measurements). Please advise? Fairly non-technical here, as compared to many of you, I'm sure. Thank in advance...
midi to querty command possible?
Hello everyone, Is there a way to translate MIDI messages into qwerty or mouse commands?
Silly Question, how do i change which modulo the mod object converts to?
So right now ive set up a counter, connected to a trigger. The trigger first bangs a number message (which is connected to the cold intlet of MOD) then sends the float to MOD. But this setup doesnt change the MOD at all.
How can I control the minibrute with Pure Data via Midi?
Hi, I discovered this video on youtube >>> https://www.youtube.com/watch?v=wbXT79_35dk. I can't work out how its done? I am on OS X I've gone through audio midi set up. I can get ableton to pick up midi information from the minibrute with a plug in synth so theres some sort of connection. I've a patch in PD with makenote and noteout but the minibrute won't respond to this. How can I control the analogue circuit of the minibrute with pure data like the video I've linked above, I am not sure what to do now? Thank you very much?
problem with midi notein
i was using my midi in pure data it was working good for a while until today , suddenly i get "notein no such object" and i also get "tabread~ no such array" , i already have a notein and i can see it but the sound goes away how can i fix such problem ? anyone? i work on windows 7 64X
Can't run PD 0.42-4 under OSX 10.4.11
I'm getting a similar problem on 10.5.7\. I'm also getting crashes when trying to select my M-Box Micro as the output in Pd.. ---------------- Process: mds \[21\] Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds Identifier: mds Version: ??? (???) Code Type: X86 (Native) Parent Process: launchd \[1\] Date/Time: 2008-09-23 14:48:39.862 +1000 OS Version: Mac OS X 10.5.4 (9E17) Report Version: 6 Exception Type: EXC\_BAD\_ACCESS (SIGBUS) Exception Codes: KERN\_PROTECTION\_FAILURE at 0x0000000000000000 Crashed Thread: 18 Application Specific Information: /SourceCache/Spotlight/Spotlight-398.18/index/ContentIndex/CIMerging.c:1958: failed assertion 'changes-\>docIds\[0\].count==0' (Error) IndexStore in SIStoreDirytySDBChunks:Error storing dirty sdb pages: 30 Thread 0: 0 libSystem.B.dylib 0x95fb84a6 mach\_msg\_trap + 10 1 libSystem.B.dylib 0x95fbfc9c mach\_msg + 72 2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790 3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88 4 mds 0x00058504 0x1000 + 357636 5 mds 0x0000e6c3 0x1000 + 54979 6 mds 0x00005956 0x1000 + 18774 Thread 1: 0 libSystem.B.dylib 0x95fb84a6 mach\_msg\_trap + 10 1 libSystem.B.dylib 0x95fbfc9c mach\_msg + 72 2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790 3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88 4 mds 0x00058504 0x1000 + 357636 5 mds 0x0000d61d 0x1000 + 50717 6 mds 0x000582d2 0x1000 + 357074 7 com.apple.Foundation 0x9631bf1d -\[NSThread main\] + 45 8 com.apple.Foundation 0x9631bac4 \_\_NSThread\_\_main\_\_ + 308 9 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 10 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 2: 0 libSystem.B.dylib 0x95fb84a6 mach\_msg\_trap + 10 1 libSystem.B.dylib 0x95fbfc9c mach\_msg + 72 2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790 3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88 4 mds 0x00058504 0x1000 + 357636 5 mds 0x0000d640 0x1000 + 50752 6 mds 0x000582d2 0x1000 + 357074 7 com.apple.Foundation 0x9631bf1d -\[NSThread main\] + 45 8 com.apple.Foundation 0x9631bac4 \_\_NSThread\_\_main\_\_ + 308 9 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 10 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 3: 0 libSystem.B.dylib 0x95fb84a6 mach\_msg\_trap + 10 1 libSystem.B.dylib 0x95fbfc9c mach\_msg + 72 2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790 3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88 4 mds 0x00058504 0x1000 + 357636 5 mds 0x0000d663 0x1000 + 50787 6 mds 0x000582d2 0x1000 + 357074 7 com.apple.Foundation 0x9631bf1d -\[NSThread main\] + 45 8 com.apple.Foundation 0x9631bac4 \_\_NSThread\_\_main\_\_ + 308 9 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 10 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 4: 0 libSystem.B.dylib 0x95fb84a6 mach\_msg\_trap + 10 1 libSystem.B.dylib 0x95fbfc9c mach\_msg + 72 2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790 3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88 4 mds 0x00058504 0x1000 + 357636 5 mds 0x0000d686 0x1000 + 50822 6 mds 0x000582d2 0x1000 + 357074 7 com.apple.Foundation 0x9631bf1d -\[NSThread main\] + 45 8 com.apple.Foundation 0x9631bac4 \_\_NSThread\_\_main\_\_ + 308 9 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 10 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 5: 0 libSystem.B.dylib 0x95fb84a6 mach\_msg\_trap + 10 1 libSystem.B.dylib 0x95fbfc9c mach\_msg + 72 2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790 3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88 4 mds 0x00058504 0x1000 + 357636 5 mds 0x0000d6a9 0x1000 + 50857 6 mds 0x000582d2 0x1000 + 357074 7 com.apple.Foundation 0x9631bf1d -\[NSThread main\] + 45 8 com.apple.Foundation 0x9631bac4 \_\_NSThread\_\_main\_\_ + 308 9 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 10 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 6: 0 libSystem.B.dylib 0x95fbf68e \_\_semwait\_signal + 10 1 libSystem.B.dylib 0x960108e0 pthread\_cond\_timedwait$UNIX2003 + 72 2 mds 0x0000a3f7 0x1000 + 37879 3 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 4 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 7: 0 libSystem.B.dylib 0x95fdc1ba read$UNIX2003 + 10 1 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 2 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 8: 0 libSystem.B.dylib 0x95fe8f66 kevent + 10 1 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 2 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 9: 0 libSystem.B.dylib 0x95fb84a6 mach\_msg\_trap + 10 1 libSystem.B.dylib 0x95fbfc9c mach\_msg + 72 2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790 3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88 4 mds 0x00058504 0x1000 + 357636 5 mds 0x0008714c 0x1000 + 549196 6 mds 0x000582d2 0x1000 + 357074 7 com.apple.Foundation 0x9631bf1d -\[NSThread main\] + 45 8 com.apple.Foundation 0x9631bac4 \_\_NSThread\_\_main\_\_ + 308 9 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 10 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 10: 0 libSystem.B.dylib 0x95fb84a6 mach\_msg\_trap + 10 1 libSystem.B.dylib 0x95fbfc9c mach\_msg + 72 2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790 3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88 4 mds 0x00058504 0x1000 + 357636 5 mds 0x00054157 0x1000 + 340311 6 mds 0x000582d2 0x1000 + 357074 7 com.apple.Foundation 0x9631bf1d -\[NSThread main\] + 45 8 com.apple.Foundation 0x9631bac4 \_\_NSThread\_\_main\_\_ + 308 9 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 10 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 11: 0 libSystem.B.dylib 0x95fb84a6 mach\_msg\_trap + 10 1 libSystem.B.dylib 0x95fbfc9c mach\_msg + 72 2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790 3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88 4 mds 0x00058504 0x1000 + 357636 5 mds 0x00054157 0x1000 + 340311 6 mds 0x000582d2 0x1000 + 357074 7 com.apple.Foundation 0x9631bf1d -\[NSThread main\] + 45 8 com.apple.Foundation 0x9631bac4 \_\_NSThread\_\_main\_\_ + 308 9 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 10 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 12: 0 libSystem.B.dylib 0x95fb84a6 mach\_msg\_trap + 10 1 libSystem.B.dylib 0x95fbfc9c mach\_msg + 72 2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790 3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88 4 mds 0x00058504 0x1000 + 357636 5 mds 0x00054157 0x1000 + 340311 6 mds 0x000582d2 0x1000 + 357074 7 com.apple.Foundation 0x9631bf1d -\[NSThread main\] + 45 8 com.apple.Foundation 0x9631bac4 \_\_NSThread\_\_main\_\_ + 308 9 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 10 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 13: 0 libSystem.B.dylib 0x95fb84a6 mach\_msg\_trap + 10 1 libSystem.B.dylib 0x95fbfc9c mach\_msg + 72 2 com.apple.spotlight.index 0x0022a3da \_handleExceptions + 238 3 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 4 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 14: 0 libSystem.B.dylib 0x95fb84a6 mach\_msg\_trap + 10 1 libSystem.B.dylib 0x95fbfc9c mach\_msg + 72 2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790 3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88 4 mds 0x00058504 0x1000 + 357636 5 mds 0x000448f3 0x1000 + 276723 6 mds 0x000582d2 0x1000 + 357074 7 com.apple.Foundation 0x9631bf1d -\[NSThread main\] + 45 8 com.apple.Foundation 0x9631bac4 \_\_NSThread\_\_main\_\_ + 308 9 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 10 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 15: 0 libSystem.B.dylib 0x95fb8506 semaphore\_timedwait\_signal\_trap + 10 1 libSystem.B.dylib 0x95fea84f \_pthread\_cond\_wait + 1244 2 libSystem.B.dylib 0x95fec0d3 pthread\_cond\_timedwait\_relative\_np + 47 3 com.apple.spotlight.index 0x0018b180 si\_scheduler\_run\_waiting\_timeout + 163 4 com.apple.spotlight.index 0x00176e50 runLoop + 77 5 com.apple.spotlight.index 0x00176f3c setattr\_runLoop + 68 6 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 7 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 16: 0 libSystem.B.dylib 0x95fb8506 semaphore\_timedwait\_signal\_trap + 10 1 libSystem.B.dylib 0x95fea84f \_pthread\_cond\_wait + 1244 2 libSystem.B.dylib 0x95fec0d3 pthread\_cond\_timedwait\_relative\_np + 47 3 com.apple.spotlight.index 0x0018b180 si\_scheduler\_run\_waiting\_timeout + 163 4 com.apple.spotlight.index 0x00176e50 runLoop + 77 5 com.apple.spotlight.index 0x00176eaa query\_runLoop + 30 6 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 7 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 17: 0 libSystem.B.dylib 0x95fb8506 semaphore\_timedwait\_signal\_trap + 10 1 libSystem.B.dylib 0x95fea84f \_pthread\_cond\_wait + 1244 2 libSystem.B.dylib 0x95fec0d3 pthread\_cond\_timedwait\_relative\_np + 47 3 com.apple.spotlight.index 0x0018b180 si\_scheduler\_run\_waiting\_timeout + 163 4 com.apple.spotlight.index 0x00176e50 runLoop + 77 5 com.apple.spotlight.index 0x0017705d flush\_runLoop + 65 6 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 7 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 18 Crashed: 0 com.apple.spotlight.index 0x002370af \_dead\_beef + 11 1 com.apple.spotlight.index 0x002307c7 merge\_checkAgainstUpdates + 181 2 com.apple.spotlight.index 0x00230a00 PayloadProcessDocIDRangeBitsReversed + 387 3 com.apple.spotlight.index 0x0020ef96 unpackPostingChunk + 422 4 com.apple.spotlight.index 0x0023517b mergeIndexData + 13180 5 com.apple.spotlight.index 0x001a0da6 \_ContentIndexMergeIndexes + 128 6 com.apple.spotlight.index 0x001a0fe2 ContentIndexMergeIndexes + 248 7 com.apple.spotlight.index 0x0017ec59 OuterMerge + 1310 8 com.apple.spotlight.index 0x001806fe si\_mergeIndex + 4007 9 com.apple.spotlight.index 0x0018aca9 si\_work\_queue\_process + 643 10 com.apple.spotlight.index 0x0018af97 si\_scheduler\_once + 419 11 com.apple.spotlight.index 0x0018af97 si\_scheduler\_once + 419 12 com.apple.spotlight.index 0x0018b322 si\_scheduler\_run\_waiting\_timeout + 581 13 com.apple.spotlight.index 0x00176e50 runLoop + 77 14 com.apple.spotlight.index 0x00176fce compaction\_runLoop + 68 15 libSystem.B.dylib 0x95fe96f5 \_pthread\_start + 321 16 libSystem.B.dylib 0x95fe95b2 thread\_start + 34 Thread 18 crashed with X86 Thread State (32-bit): eax: 0x00000000 ebx: 0x00230733 ecx: 0x00000000 edx: 0x00000000 edi: 0x00000000 esi: 0x00000616 ebp: 0xb0991738 esp: 0xb0991730 ss: 0x0000001f efl: 0x00010286 eip: 0x002370af cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037 cr2: 0x00000000 Binary Images: 0x1000 - 0xb9feb mds ??? (???) <63f8cd1f41b3382ec7d38bb5f76a20c1\> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds 0xd7000 - 0xd8ffd com.apple.MDSChannel 1.0 (1.0) /System/Library/PrivateFrameworks/MDSChannel.framework/Versions/A/MDSChannel 0x14a000 - 0x25fff7 com.apple.spotlight.index 10.5.2 (398.18)
0x6cf000 - 0x6d4ff7 libgermantok.dylib ??? (???) <5608319ae54efad75bb8af543f67134f\> /usr/lib/libgermantok.dylib
0x2bce000 - 0x2bceffd liblangid.dylib ??? (???) /usr/lib/liblangid.dylib
0x30bd000 - 0x31e4feb libmecab.1.0.0.dylib ??? (???) /usr/lib/libmecab.1.0.0.dylib
0x8fe00000 - 0x8fe2da53 dyld 96.2 (???) <5013f43c4d2c33c9619011f103ec3238\> /usr/lib/dyld
0x90291000 - 0x902a0ffe com.apple.DSObjCWrappers.Framework 1.2.1 (1.2.1) <43c5b91223501f917392f59fbf9d7ace\> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWrappers
0x90905000 - 0x9093cfff com.apple.SystemConfiguration 1.9.2 (1.9.2) <8b26ebf26a009a098484f1ed01ec499c\> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x9093d000 - 0x9099affb libstdc++.6.dylib ??? (???) <6106b1f2b0b303b06ae476253dbb5f3f\> /usr/lib/libstdc++.6.dylib
0x9099b000 - 0x909e1fef com.apple.Metadata 10.5.2 (398.18) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x909e2000 - 0x90ac3ff7 libxml2.2.dylib ??? (???) <1baef3d4972ee789d8fa6c1fa44da45c\> /usr/lib/libxml2.2.dylib
0x90aff000 - 0x90bf3ff4 libiconv.2.dylib ??? (???) <3f183527811098bb7332f67a1f902bfd\> /usr/lib/libiconv.2.dylib
0x90bf4000 - 0x90c7ffff com.apple.framework.IOKit 1.5.1 (???) <60cfc4b175c4ef60bb8e9036716a29f4\> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x92417000 - 0x9254fff7 libicucore.A.dylib ??? (???) <5031226ea28b371d8dfdbb32acfb48b5\> /usr/lib/libicucore.A.dylib
0x92551000 - 0x9256fff3 com.apple.DirectoryService.Framework 3.5.4 (3.5.4) /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService
0x92570000 - 0x9264ffff libobjc.A.dylib ??? (???) <99a9ad33ca07114848fdd7580968a572\> /usr/lib/libobjc.A.dylib
0x92650000 - 0x9270afe3 com.apple.CoreServices.OSServices 226.5 (226.5) <7e10d25c615a39fe1ab4d48e24a3b555\> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x92756000 - 0x92756ffa com.apple.CoreServices 32 (32) <2760719f7a81e8c2bdfd15b0939abc29\> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x92b68000 - 0x92c9afff com.apple.CoreFoundation 6.5.3 (476.14) <7ef7f5db09ff6dd0135a6165872803cc\> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x934e8000 - 0x93574ff7 com.apple.LaunchServices 289.2 (289.2) <3577886e3a6d56ee3949850c4fde76c9\> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x93de5000 - 0x93dfbfff com.apple.DictionaryServices 1.0.0 (1.0.0) <7e9ff586b5c9d02b09e2a5527d98524f\> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x93e13000 - 0x93e3efe7 libauto.dylib ??? (???) <2072d673706bbe463ed2426af57a28d7\> /usr/lib/libauto.dylib
0x944dc000 - 0x944e4fff com.apple.DiskArbitration 2.2.1 (2.2.1) <42908e7ecc17a83cec4afef2850ec79e\> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x94991000 - 0x94a13ff3 com.apple.CFNetwork 330.4 (330.4) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x94c22000 - 0x94df0fff com.apple.security 5.0.4 (34102) /System/Library/Frameworks/Security.framework/Versions/A/Security
0x950cf000 - 0x950f3fff libxslt.1.dylib ??? (???) <59399cc446ed903fd9479526ee9f116b\> /usr/lib/libxslt.1.dylib
0x955da000 - 0x95609fe3 com.apple.AE 402.2 (402.2) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x9563b000 - 0x956c2ff7 libsqlite3.0.dylib ??? (???) <11311084bc4be9d4555dfac74fe7218a\> /usr/lib/libsqlite3.0.dylib
0x9573a000 - 0x95741fe9 libgcc\_s.1.dylib ??? (???) <28a7cbc3a5ca2982d124668306f422d9\> /usr/lib/libgcc\_s.1.dylib
0x95ad9000 - 0x95ae7ffd libz.1.dylib ??? (???) <545ca09467025f77131cfac09d8b9375\> /usr/lib/libz.1.dylib
0x95e13000 - 0x95e92ff5 com.apple.SearchKit 1.2.0 (1.2.0) <5abfde5537969168b8a8743ccb9ec735\> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x95fb7000 - 0x96117ff3 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
0x96311000 - 0x9658cfe7 com.apple.Foundation 6.5.5 (677.19) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x9662a000 - 0x9662efff libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x96bec000 - 0x96bf3ffe libbsm.dylib ??? (???) <5582985a86ea36504cca31788bccf963\> /usr/lib/libbsm.dylib
0x96bf7000 - 0x96ed1ff3 com.apple.CoreServices.CarbonCore 786.6 (786.6) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0xfffe8000 - 0xfffebfff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
Fedora 10 : Gem: can't load library
hi there, I've got pd running fine for sounds but I'ld like Gem (for a reactable); but I've got this error at pd startup : Gem: can't load library I am with Fedora 10, kernel : $ uname -a Linux hal 184.108.40.206-170.2.104.fc10.i686 \#1 SMP Mon Oct 12 22:01:53 EDT 2009 i686 i686 i386 GNU/Linux pd version : $ yum info pd Loaded plugins: refresh-packagekit Available Packages Name : pd Arch : i386 Version : 0.39.3 Release : 1.cvs.07.07.23.fc10.ccrma Size : 5.9 M Repo : planetccrma Summary : Real-time patchable audio and multimedia processor. URL : [http://pure-data.sourceforge.net/] License : GPL Description: Pd gives you a canvas for patching together modules that analyze, : process, and synthesize sounds, together with a rich palette of : real-time control and I/O possibilities. Similar to Max : (Cycling74) and JMAX (IRCAM). A related software package named Gem : extends Pd's capabilities to include graphical rendering. Here is what pd tells when started with "pd" : \[import\] $Revision: 1.2 $ \[import\] is still in development, the interface could change! compiled against Pd version 0.41.4 couldn't open MIDI input device 0 couldn't open MIDI output device 0 opened 0 MIDI input device(s) and 0 MIDI output device(s). libdir loader $Revision: 1.8 $ compiled on Oct 27 2009 at 17:32:35 compiled against Pd version 0.41.4.extended Gem: can't load library libdir\_loader: added 'cyclone' to the global objectclass path libdir\_loader: added 'zexy' to the global objectclass path libdir\_loader: added 'creb' to the global objectclass path libdir\_loader: added 'cxc' to the global objectclass path libdir\_loader: added 'iemlib' to the global objectclass path libdir\_loader: added 'list-abs' to the global objectclass path libdir\_loader: added 'mapping' to the global objectclass path libdir\_loader: added 'markex' to the global objectclass path libdir\_loader: added 'maxlib' to the global objectclass path libdir\_loader: added 'memento' to the global objectclass path libdir\_loader: added 'mjlib' to the global objectclass path libdir\_loader: added 'motex' to the global objectclass path libdir\_loader: added 'oscx' to the global objectclass path libdir\_loader: added 'pddp' to the global objectclass path libdir\_loader: added 'pdogg' to the global objectclass path libdir\_loader: added 'pixeltango' to the global objectclass path libdir\_loader: added 'rradical' to the global objectclass path libdir\_loader: added 'sigpack' to the global objectclass path libdir\_loader: added 'smlib' to the global objectclass path libdir\_loader: added 'toxy' to the global objectclass path libdir\_loader: added 'unauthorized' to the global objectclass path libdir\_loader: added 'pan' to the global objectclass path libdir\_loader: added 'freeverb' to the global objectclass path libdir\_loader: added 'hcs' to the global objectclass path libdir\_loader: added 'jmmmp' to the global objectclass path libdir\_loader: added 'ext13' to the global objectclass path libdir\_loader: added 'ggee' to the global objectclass path libdir\_loader: added 'flib' to the global objectclass path libdir\_loader: added 'ekext' to the global objectclass path libdir\_loader: added 'flatspace' to the global objectclass path pdp: can't load library pidip: can't load library And here is part of what pd tells when started with "pd -verbose" : libdir loader $Revision: 1.8 $ compiled on Oct 27 2009 at 17:32:35 compiled against Pd version 0.41.4.extended tried ./Gem.l\_i386 and failed tried /usr/share/fonts/bitstream-vera/Gem.l\_i386 and failed tried /usr/lib/pd/extra/cyclone/Gem.l\_i386 and failed tried /usr/lib/pd/extra/zexy/Gem.l\_i386 and failed tried /usr/lib/pd/extra/creb/Gem.l\_i386 and failed tried /usr/lib/pd/extra/cxc/Gem.l\_i386 and failed tried /usr/lib/pd/extra/iemlib/Gem.l\_i386 and failed tried /usr/lib/pd/extra/list-abs/Gem.l\_i386 and failed tried /usr/lib/pd/extra/mapping/Gem.l\_i386 and failed tried /usr/lib/pd/extra/jmmmp/Gem.l\_i386 and failed tried /usr/lib/pd/extra/maxlib/Gem.l\_i386 and failed tried /usr/lib/pd/extra/memento/Gem.l\_i386 and failed tried /usr/lib/pd/extra/mjlib/Gem.l\_i386 and failed tried /usr/lib/pd/extra/markex/Gem.l\_i386 and failed tried /usr/lib/pd/extra/oscx/Gem.l\_i386 and failed tried /usr/lib/pd/extra/pddp/Gem.l\_i386 and failed tried /usr/lib/pd/extra/pdogg/Gem.l\_i386 and failed tried /usr/lib/pd/extra/motex/Gem.l\_i386 and failed tried /usr/lib/pd/extra/pmpd/Gem.l\_i386 and failed tried /usr/lib/pd/extra/rradical/Gem.l\_i386 and failed tried /usr/lib/pd/extra/sigpack/Gem.l\_i386 and failed tried /usr/lib/pd/extra/pixeltango/Gem.l\_i386 and failed tried /usr/lib/pd/extra/toxy/Gem.l\_i386 and failed tried /usr/lib/pd/extra/unauthorized/Gem.l\_i386 and failed tried /usr/lib/pd/extra/pan/Gem.l\_i386 and failed tried /usr/lib/pd/extra/smlib/Gem.l\_i386 and failed tried /usr/lib/pd/extra/hcs/Gem.l\_i386 and failed tried /usr/lib/pd/extra/freeverb/Gem.l\_i386 and failed tried /usr/lib/pd/extra/ggee/Gem.l\_i386 and failed tried /usr/lib/pd/extra/ext13/Gem.l\_i386 and failed tried /usr/lib/pd/extra/flib/Gem.l\_i386 and failed tried /usr/lib/pd/extra/ekext/Gem.l\_i386 and failed tried /usr/lib/pd/extra/Gem.l\_i386 and failed tried /usr/lib/pd/extra/flatspace/Gem.l\_i386 and failed tried /home/zbl/pd-externals/Gem.l\_i386 and failed tried /usr/local/lib/pd-externals/Gem.l\_i386 and failed tried /usr/lib/pd/extra/Gem.l\_i386 and failed tried ./Gem.pd\_linux and failed tried /usr/share/fonts/bitstream-vera/Gem.pd\_linux and failed tried /usr/lib/pd/extra/cyclone/Gem.pd\_linux and failed tried /usr/lib/pd/extra/zexy/Gem.pd\_linux and failed tried /usr/lib/pd/extra/creb/Gem.pd\_linux and failed tried /usr/lib/pd/extra/cxc/Gem.pd\_linux and failed tried /usr/lib/pd/extra/iemlib/Gem.pd\_linux and failed tried /usr/lib/pd/extra/list-abs/Gem.pd\_linux and failed tried /usr/lib/pd/extra/mapping/Gem.pd\_linux and failed tried /usr/lib/pd/extra/jmmmp/Gem.pd\_linux and failed tried /usr/lib/pd/extra/maxlib/Gem.pd\_linux and failed tried /usr/lib/pd/extra/memento/Gem.pd\_linux and failed tried /usr/lib/pd/extra/mjlib/Gem.pd\_linux and failed tried /usr/lib/pd/extra/markex/Gem.pd\_linux and failed tried /usr/lib/pd/extra/oscx/Gem.pd\_linux and failed tried /usr/lib/pd/extra/pddp/Gem.pd\_linux and failed tried /usr/lib/pd/extra/pdogg/Gem.pd\_linux and failed tried /usr/lib/pd/extra/motex/Gem.pd\_linux and failed tried /usr/lib/pd/extra/pmpd/Gem.pd\_linux and failed tried /usr/lib/pd/extra/rradical/Gem.pd\_linux and failed tried /usr/lib/pd/extra/sigpack/Gem.pd\_linux and failed tried /usr/lib/pd/extra/pixeltango/Gem.pd\_linux and failed tried /usr/lib/pd/extra/toxy/Gem.pd\_linux and failed tried /usr/lib/pd/extra/unauthorized/Gem.pd\_linux and failed tried /usr/lib/pd/extra/pan/Gem.pd\_linux and failed tried /usr/lib/pd/extra/smlib/Gem.pd\_linux and failed tried /usr/lib/pd/extra/hcs/Gem.pd\_linux and failed tried /usr/lib/pd/extra/freeverb/Gem.pd\_linux and failed tried /usr/lib/pd/extra/ggee/Gem.pd\_linux and failed tried /usr/lib/pd/extra/ext13/Gem.pd\_linux and failed tried /usr/lib/pd/extra/flib/Gem.pd\_linux and failed tried /usr/lib/pd/extra/ekext/Gem.pd\_linux and failed tried /usr/lib/pd/extra/Gem.pd\_linux and failed tried /usr/lib/pd/extra/flatspace/Gem.pd\_linux and failed tried /home/zbl/pd-externals/Gem.pd\_linux and failed tried /usr/local/lib/pd-externals/Gem.pd\_linux and failed tried /usr/lib/pd/extra/Gem.pd\_linux and failed tried ./Gem/Gem.l\_i386 and failed tried /usr/share/fonts/bitstream-vera/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/cyclone/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/zexy/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/creb/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/cxc/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/iemlib/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/list-abs/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/mapping/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/jmmmp/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/maxlib/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/memento/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/mjlib/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/markex/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/oscx/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/pddp/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/pdogg/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/motex/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/pmpd/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/rradical/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/sigpack/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/pixeltango/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/toxy/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/unauthorized/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/pan/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/smlib/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/hcs/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/freeverb/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/ggee/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/ext13/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/flib/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/ekext/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/flatspace/Gem/Gem.l\_i386 and failed tried /home/zbl/pd-externals/Gem/Gem.l\_i386 and failed tried /usr/local/lib/pd-externals/Gem/Gem.l\_i386 and failed tried /usr/lib/pd/extra/Gem/Gem.l\_i386 and failed tried ./Gem/Gem.pd\_linux and failed tried /usr/share/fonts/bitstream-vera/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/cyclone/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/zexy/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/creb/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/cxc/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/iemlib/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/list-abs/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/mapping/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/jmmmp/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/maxlib/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/memento/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/mjlib/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/markex/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/oscx/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/pddp/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/pdogg/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/motex/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/pmpd/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/rradical/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/sigpack/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/pixeltango/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/toxy/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/unauthorized/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/pan/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/smlib/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/hcs/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/freeverb/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/ggee/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/ext13/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/flib/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/ekext/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/flatspace/Gem/Gem.pd\_linux and failed tried /home/zbl/pd-externals/Gem/Gem.pd\_linux and failed tried /usr/local/lib/pd-externals/Gem/Gem.pd\_linux and failed tried /usr/lib/pd/extra/Gem/Gem.pd\_linux and failed tried ./Gem/Gem-meta.pd and failed tried /usr/share/fonts/bitstream-vera/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/cyclone/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/zexy/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/creb/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/cxc/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/iemlib/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/list-abs/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/mapping/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/jmmmp/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/maxlib/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/memento/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/mjlib/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/markex/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/oscx/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/pddp/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/pdogg/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/motex/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/pmpd/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/rradical/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/sigpack/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/pixeltango/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/toxy/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/unauthorized/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/pan/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/smlib/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/hcs/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/freeverb/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/ggee/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/ext13/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/flib/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/ekext/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/flatspace/Gem/Gem-meta.pd and failed tried /home/zbl/pd-externals/Gem/Gem-meta.pd and failed tried /usr/local/lib/pd-externals/Gem/Gem-meta.pd and failed tried /usr/lib/pd/extra/Gem/Gem-meta.pd and failed Gem: can't load library I can't locate files like Gem-meta.pd or Gem.pd\_linux on the computer; I keep investigating, but any hint is welcome, thanks : http://pure-data.sourceforge.net/
Separate control of two midi devices
\>\>I had been hooking the sampler up to the midi out from the x-station<< does the x-station have a midi 'thru' port too? or just in and out? because if you want to send midi to the sampler via another device, you'd probably have to have a midi thru port to do that (if i recall correctly) if you don't have a midi through port, then i think it would be best to use the midi-usb device you have. set the electribe to receive on midi channel 1 only. and then attach it to the the midi-usb device with a midi cable. connect the x-station to the electribe's midi 'thru' outlet with a midi cable. set the x-station to recieve on midi channel 2 only. then open pd and set midi output to the midi-usb device name, and then \[noteout 1\] should talk to the electribe only, and \[noteout 2\] should talk to the x-session one more thing: does the x-station have its own power source? if so, then disconnect the usb cable. you won't need it. but if the device needs usb for power, then maybe you can still leave it connected via usb as well, but don't select it as a device in pd, because it will be receiving midi messages via the electribe anyway. one more thing again: really if the x-station has a midi through port, then just attach that to the electribe and all your worries should be gone.
Traktor (will work with others)Coge Midi clock Sync with OSC
This is a cross platform alternative for synchronizing two(or more) different computers to one Midi Clock. Since one will have coge this will be between a Mac OSX and windows running traktor that produces midi clock. For windows Midi Yoke (tested in XP) to wrap Midi clock to Pure Data extended (tested with v 0.41.4) from there the clock will be sent has an OSC message to one or all network computer(s). On the listening side there will be one other Pure Data patch converting a specific OSC message to Midi clock. Then coge can catch this midi clock just by clicking "Midi clk". This is nothing special but it took me almost 3 weeks to accomplish it. Given that i knew nothing about pure data at the time, this site was very helpful. All examples were gathered from here. Also note that this is not the best way. There are Midi cables for this. There are usb to midi converters, for those who don't have midi ports. Also external sound boards quite good with several inputs and outputs. I have experienced a +/- 3 Beats float of BPM count on coge but always around the correct number, over time this seems to float less. This still lacks testing. Anyway. You'll need Pure data extended on every machine. You'll need Midi Yoke on Windows. You can use Yac Driver on Mac OSX for midi wrap. Don't know for linux, sorry. (read somewhere something about jack) On pure data you'll need to define the midi device input or output which ever is the case. On windows it's easy on any pure data windows you can set midi devices, choose midi Yoke (the channel number should be the same in the receiver input and sender output). On OSX it's on the main window, under preferences. If using this with quartz composer one can skip the pure data on the OSC server side (which is the one that listens). If adding more functions to this keep in mind that quartz composer does not understands 0 arguments messages. (I think this should be a bug) You are advised to change the IP on the pure data patch to which ever is your destination. You can use 0.0.0.0 to broadcast. Don't use wireless, it's a 0 security communication protocol. Hope to save someone's time. GL [http://www.pdpatchrepo.info/hurleur/OSC\_MIDIclk\_sync.zip] : http://www.pdpatchrepo.info/hurleur/OSC_MIDIclk_sync.zip
Latency with midi
I'm looking for some help about a latency problem with midi processing using pd under Windows XP. Here is the point : I'm using pd to process some midi data coming from electronic drums. These data are then sent to another software (e.g. Nuendo) thanks to virtual midi ports (MIDI Yoke). Assuming '<-\>' is a midi connection (virtual or physical), it looks like, drums module <-\> Sound Card (Midi Ports) <-\> Pure Data <-\> Midi Yoke <-\> Nuendo The problem is that pd introduces some latency... and pd is definitely responsible for that... because the following setup does not introduce latency : drums module <-\> Sound Card (Midi Ports) <-\> Midi CC <-\> Midi Yoke <-\> Nuendo (Midi CC allows to connect virtual ports between them) The last point is that latency does not seem to be sensitive to the patch. I tried a simple midi thru patch and another patch with complex treatments and nothing changed... Help !!!
Cant get midi signals from Ground Control Pro to Puredata
Hello everyone, I just purchased a Ground Control Pro, a midi foot pedal, from DMC. I was hoping to use it to switch between my patches in Puredata. However when I plug it in, using the factory settings=\>to my Uno midi interface=\>powerbook g4\. I don't get any midi signals in the Test Patch in PD. I have selected the midi interface in the PD midi settings, I have also created a external in Audio|Midi OSX utility. If I switch out the GCP with my midi keyboard, PD gets the signals fine. I am getting midi signals to the Audio/midi OSX utility because when I do a sound test in the utility i get sound response on the "\\/" arrow of the midi interface(the one viewable in the patchable section of the utility) If anyone has had any experience with the GCpro and setting it up with PD I would much apreciate some direction. Just for you knowledge, I have tried this setup with the OSX midi utility open while PD was open(I heard that I should try that)....no luck. Ben
should become a kind of groove box but i guess i tinkered it to f\*\*k. it's a damn cpu hog and it will spit out a whole list of errors to the pd window when loading......... ....BUT BESIDES ALL THAT: it sound pretty nice (in my opinon!) .... ;) so, if you give it a chance, tell me what you think about it. EDIT: Note, when you open the patch (RUMBLE\_BOX.pd) there will be no sound until you assigned midi in and midi out. the sequencer sends out midi notes to the single sound generator channels, so you have to send midi out to midi in - i did this with midi ox and midi yoke, i connected "midi yoke in 1" to "midi yoke out 1" in midi ox and assigned them as midi in/out in pd. [http://www.pdpatchrepo.info/hurleur/Rumble\_Box.zip] : http://www.pdpatchrepo.info/hurleur/Rumble_Box.zip
More midi output device options needed
Yes, I already use something like midi yoke now. It is the standard osx midi routing software called IAC. I forgot to mention in my question that I use one IAC output port to send signals from the PD patch to Ableton. In ableton I route signals from this IAC port to my MIDI outs (connected to the machines). The other output I use to send signals to my controller, so that when I change the parameter of a knob I can send the current value of that parameter to the knob of the behringer (when I turn this knob the value doesn;t jump but starts from the value it is actually on). This liimits my possibilities, I want to be able to filter out signals for certain machines. But now I can only use one actual midi output, The IAC bus. The nice thing about PD;s midi controller interface is that another midi output is a different midi channel. So when I could have 4 midi output possibilities it would enable me to press a button that says to a knob: send to channel 17 (channel one of the second midi output device) instead of sending to channel 33 (channel one of the third midi output device). I hope this is possiible. I think it actually is, because there are four midi inputs available.
Intercept APC40 MIDI
Hi, Does anyone know how I'd intercept the APC40 MIDI so I can start to make changes to it. I've tried using a virtual MIDI cable, feeding the MIDI into PD, then into the cable: and recieving MIDI back from the cable and sending it to the APC40, but: 1: This causes a weird feedback issue: when I turn a knob Ableton gets updated and immediately sends a MIDI response, which PD sends back to the APC40\. This causes slow knob response and flickering: it looks like the APC40 is getting confused by the returning MIDI signals. The same thing does not happen when the APC40 and Ableton are connected together directly: even though there is two-way MIDI. Obviously the issue is solved somehow: but I don't know how to do it. 2: A lot of the APC functions simply doesn't work: although I've simply done midiin --\> midiout with all the available MIDI interfaces. The handshake between the APC and Ableton supposedly goes through MIDI, and other people have got it working with Bome's MIDI Translator: so it's definitely possible. Any ideas on how to get it working? Cheers, Will.
Hello, I have a problem with using pd and MIDI yoke. The thing is that I am sending MIDI information from reaktor through MIDI yoke to pd. For a while everything goes fine after a few seconds things go wrong. I am using different midi-controllers and it seems that after a while information from the different controllers get "messed-up". I am sending MIDI through port 1 of MIDI Yoke and receiving from the same port in pd. This is the only port that I am using. Now I found out (by opening pd in DOS) that I get a MIDI feedback, but I don't understand why... Also when I set-up the midi port I get the message that using MIDI in windows is dangerous: Warning: midi input is dangerous in Microsoft Windows\\; see Pd manual). Can somebody help me pleezze.
V2MSy is out (alpha)
Hi, my patch v2MSy (video to midi synth) is downloadable from <[http://adrjork.altervista.org/puredatatutorials.html]\>. I hope you like it. Basically it's smilar to MetaSynth but my patch works with video or webcam in real time, and not with image. The patch transforms the central Y axis of the video into 128 MIDI signals (from bottom to top) at 25fps (metro at 40ms). The result is a detailed "notation" of the video's central axis where the white pixels represent velocity=127 and black pixels represent velocity=0 (very similar to carillons' mechanism where video stays for the cylinder!) The patch contains also two indipendent subpatches: an interface for BCF2000 and a "poor" interface for keyboard&mouse. You need a receiving software to "play" or "write" MIDI noteouts (like a sequencer). To connect the patch to the receiving-software I use a virtual MIDI cable. I think you can use MidiYoke in Windows, or ALSA in Linux, or IAC driver in Mac. But if you want also feedback for your motorized BCF2000 you should set PD's MIDI settings with "multiple devices"...that doesn't work! Because it seems that only the 1st output device works... So I do in this way: IAC driver (I use Mac) + MIDI Patchbay and I set: -BCF2000 as PD MIDI input -IAC driver as PD MIDI output -IAC driver as Patchbay input -BCF2000 as Patchbay output In this way, Logic receives MIDI signals from v2MSy, and my Behringer has feedback! Please, test the patch in Windows or Linux and write if ALSA and MidiYoke do the work and give feedback. Thanks. But remember that...it's only an "alpha" patch, and it needs powerful hardware. : http://adrjork.altervista.org/puredatatutorials.html
MIDI weird issues with arduino + PD (not pduino)
Greetings! I have some weird MIDI issues I was wondering if anyone here have any idea about what migth be the cause of, and perhaps could offer some pointers towards a potential cure to! I am working on a project that involves the need to get midi messages from arduino to my sound card. This project involves doing stuff in water, so we have allready gotten a wireless MIDI transmitter that works perfrectly. The trouble, however, seem to be in Pure Data for all I can understand. I am using an arduino decimilla, with a regular flex sensor as control. And the problem is: When PD receives MIDI data from the arduino , it all seems good in the beginning, the response is quick, and all is well. However, after running only a short time, not more than a few minutes max, the MIDI messages seem to get delayed, so when i move the flex sensor, it takes a while before the changes registeres in PD. What is even weirder is that in addition to this, there seem to be like a double flow of delayed messages, where at first the "original" message comes along, and then short after, a duplicate message comes along too. So when say I bend my flex sensor, at first, the midi goes from 127 to 60, and then after a short while, jumps back to 127 and ramps back to 60 again. Sometimes they even seem to compete and garble eachother at the same time, with values jumping all over the place. I find the irregularity of the whole troublesome affair really frustrating. I am still a noob with arduinou so even though I do not believe the problem lies in the arduino, I cannot be sure. The reason I believe it is in PD is beacause all i have to do is shut down PD and start it up again, and it works nice.. a few minutes. And needless to say, in a live setting, you don't want to go up and restart PD all the time, especially since I will be submerged in a pool during the performance.. :( (have allways used Pduino before the few times I've used it with PD, but that is not an option this time) I am working in Windows XP with a Edirol UA-25 sound card btw. The arduino code i'm using to produce MIDI was borrowed from this program; [http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1165833586/0\#2] Anyone had similar problems with MIDI in PD? I know the warning says "MIDI is dangerous in PD" but... I have used CC messages before with no problem at all. This is so weird... Any clever suggestions would be hugely appreciated. :) : http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1165833586/0#2
No MIDI output on OS 10.4
Hello, I've been using pd over the last few months on an XP machine, but now poritng a project onto a Mac computer. Using the test audio and MIDI menu I get audio signal (out of a USB audio device) but no MIDI signal. I tested playing back a MIDI file using quicktime - no problem hearing the Beatles at their best(!) What could be happening? the Pd manual directions are a bit esoteric "To get MIDI working, you have to do the Mac OSX magic to get a USB MIDI interface installed. I've seen this done with Midisport devices and I think you just download the OSX driver and follow directions." So i did that, and instaled the driver for an M-Audo MIDISPORT device. From the MIDI Set Up panel, the device shows up with its "online" box checked. From the System Preferences-\> Quicktime -\> advance panel-\> set to "quicktime music synthesizer" is selected. Running pd 0.39.2 test 5 on Mac 10.4.8 Any help much appreciated! i will keep perusing the net for more info meanwhile. jean ps: I don't plan on using any MIDI cintrol, just having Pd play some MIDI files along with some fm synhesis.
PD and creativity: a patcher's lament
Hi, tossing in some cents: in my experience my issue with Pd is the opposite from LiamG's issues: the sound design is straightforward and simple to implement (again, depending on what's being implemented) but the process of algorithmic composition is not as well suited to data flow programming. My main interest in computer music is algorithmic composition and I believe pd was designed as a tool for live performance which makes it unwieldy to use for algorithmic composition but great for what it was designed for. Control of events over time is severely lacking in my opinion Let me give examples: 1. There is no way, at a given point in the program flow of a patch, to call a subpatch with certain input arguments and get the output in a certain format. Instead, copies of the subpatch must be made, increasing memory usage compared to the classical idea of a function. 2. When composing, I like to think in terms of "do this thing at this point in time". Say I have a melody and at a certain point in that melody I want to choose between 2 different notes. One way of doing this would be to have a qlist that plays the melody and have it call a receive object that takes parameters to choose between 2 notes. But what if I want to call that function to play a different instrument? all of a sudden I need an extra argument to that control structure, and need to re-program the subpatch in order to do it. 3. Say you want to quickly edit a score of midi notes or midi automation, which maybe don't control midi directly but rather control algorithmic parameters that change over time. This is very difficult to do. You could set up a DAW to send the midi to pd, but MIDI is not designed (in it's structure or in it's output format) for sending data to programming languages, but directly to instruments. There aren't many open source OSC editors either (although there are a couple of promising ones). recently I have been exploring other programs for algorithmic composition purposes, such as Common Music, based on Scheme. What makes Scheme enticing for algorithmic composition is that it supports continuations natively. What this means is that you can control the program flow manually, and the score for an algorithmic composition could be set up to be the program itself. (Common music does not support this but it could be set up to). So, in the example above, when composing with Scheme set up in this fashion, all that would be required to choose between 2 notes and play it would be 1 line of code, like ```(play myinstrument (choose 49 64 20))``` and to play it on a different instrument all that needs to change is the first argument. Notice that "choose" does not need to be rewritten. Personally, I believe what is needed for the future of algorithmic composition is a dedicated DAW-like environment, (I have been thinking of undertaking such an endeavor). It would have tracks, and each track could have several layers that could output to either OSC, MIDI, or another layer in the project. Layers could be midi note editors (that could be configured to output OSC), automation editors with configurable precision (like if they output ints or floats, and how it is scaled), pieces of code that generate notes, pieces of code that take input data and output other data, containers for more layers, etc. The programming languages used would have to bridge over a common interface somehow, and they would need to support continuations or coroutines (Lua does also). The editors could have functions to, say, bind a specific midi note to a specific function in a specific layer. This would combine the ease of using DAWs to compose temporally with algorithmic composition constructs in my view. But all that is just based on the way I think about composition... everyone's different.
Tarmtott - ep by swamps up nostrils
This lil' thing just got released on the great netlabel Control Valve, it is 6 tracks of whacky looping made with PD. Download @: [http://www.controlvalve.net/] inforz: "ctrlvlv\#007 IS NOW READY FOR DOWNLOADING!!!!!!!!!!!!!!!!&\#8207; ctrlvlv\#007 IS NOW READY FOR DOWNLOADING!!!!!!!!!!!!!!!!&\#8207; ctrlvlv\#007 IS NOW READY FOR DOWNLOADING!!!!!!!!!!!!!!!!&\#8207; artist: swamps up nostrils title: tarmtott artist statement: "Swamps Up Nostrils is a spatiotemporal mishap again and again focusing on both experimental wrongdoings and ancient traditional musical structures like beats and harmonies. What you hear is not what you get but it will however seem pretty close anyway, so why bother? Swirling the eternal wormholes between the familiar and the unknown, we hope to entertain but admit that to most people it must seem like meaningless idiocy, but then again most people seem like meaningless idiots too, including ourselves, so I guess it balances out. Only by admitting to being an idiot yourself will you understand what it means to be one, and understand just how many idiots there are around here. We, the failed abhorritions of monkey-like beings of ancient times, will not let us be controlled by our biological shortcomings, although we admit to them causing us both irritation and confusion. This irritation and confusion is not the source of this music. This music was made by utilizing magick and computers, if you believe in such stuff. If you do not, this music was made by utilizing science and computers, if you believe in such stuff. If you do not, this music was made by utilizing faith and computers, if you believe in such stuff. If you do not, this music was made by utilizing computers and computers, if you believe in such stuff. If you do not, this music was made by utilizing music and music, if you believe in such stuff. If you do not, this mucus was made by utilizing mucus and mucus, if you believe in such stuff. If you do not, this made not was believe and unbelief is by whom was finalized as not more. If you do not, please ignore all above statements as they are irrelevant to the audial experience anyway. There appears not more than what vibrates in your ear, and how your brain interprets that on the basis of your own very personal framework of reference. Anyone telling you otherwise is either trying to highjack your brain or may be lying, or may be convinced of otherwise and acts on a compulsion of good faith, although faith can never exist as something good outside someone's subjective defenition of the matter so the statement is meaningless. Now stop reading this nonsense and listen to the music instead, because, as implied in this body of textual represented idiocies, the point is not to read about this music it is to listen to it. Get it?" swamps up nostrils is arnfinn killingtveit from trodheim, norway. no one can ever be sure what will come out of the speakers when playing a swamps up nostrils release. the first time i heard one it was some sort of drum and bass mixed with circuit bent electronics, with just a tad of field recordings. you might be getting some sort of techno, drone, noise, minimalism, analog, digital, ect...... whatever it might be, it is always top notch sound work, great composition, and a highly enjoyable listen. killingtveit also runs the superb cd-r label Krakilsk 6 tracks of looping-layered sound composition 320kbps. mp3 cover image" : http://www.controlvalve.net/
Noteout into Live (OSX)
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
Only 1 of 2 midi devices found in PD (Gentoo Linux)
I'm running Pd 0.40-3-extended in Gentoo, everything seems to work fine except that I'm having serious problems with getting PD to recognize my Doepfer midi interface (analogue knobs to midi). The only midi interface it does recognize is my midi keyboard which PD find as an OSS device \#1\. However, the Doepfer interface works fine if you look at the raw output with cat: cat /dev/midi But PD just refuses to find find it. Perhaps there is some cheap hack to fool PD to start caring about my /dev/midi instead of only listening to /dev/midi1? Both the midi keyboard and Dopefer midi interface are run over USB. Any one got some special tricks 'n tips perhaps?
TouchOSC -\> Pure data -\> Midi
I'm not seeing anything in there dealing with midi. You are routing the OSC messages to faders and toggles, correct? Midi messages are in the form of: (int=integer 0-127) int (controller value), int (controller number), int(midi channel). <---- for midi "constant controller" values: 'sliders' or 'knobs'... int (midi note \#), int (velocity), int(midi channel). <---- for midi note on/off messages: Toggles, switches, piano keys... You need to re-route the OSC data to an object such as \[noteout\] or \[ctlout\] in the above format to control FLpro. You'll need to also examine FLpro's midi mappings to see which controllers/notes control which desired params. Let me know if you need any more help, maybe I'll DL that iPhone app this weekend and check it out.
Pure Data + Player Pianos?
@discolemonade said: > player piano if the player piano have midi input, then you just need a midi out device plugged in your computer (via a soundcard, external midi device, ...) and pure data with a very simple patch that use ```[noteout]```. In Media, Test Audio and Midi.... click on Midi out toggle (before hand you need to configure midi via Media, Midi settings). That's it. Cheers~
PD to Ableton Live MIDI wierdness - ctlout works, noteout does not???
Hi, this question goes out to those of you who use PD and Ableton live. I am trying to control an instrument in Live, Live's Sampler, from PD, and I have ctlout working just fine, in that I can control parameters of filter knobs etc. on a Live Sampler from a PureData ctlout with no problem. I am using the IAC MIDI driver to route MIDI from PD to Live as I am on a Mac OSX machine. My problem is that when sending noteout signals, Live is receiving the MIDI as evidenced by Live's MIDI receive indicator lighting up, but it is not making notes play in the sampler, even though I have it set to receive MIDI from that IAC bus. Like I say the ctlout has no problem controlling a filter knob, etc... Anyone have any suggestions? I am kind of a noob to MIDI stuff and to interapplication MIDI routing.
Pd-extended 0.40.3 (Windows) midi out problem
Hello all, So I am working with some midi patching, and I noticed my version of pd-extended was terribly out of date (0.39.3). I download and installed the current stable release (0.40.3) and none of my midi out objects work anymore. I have set my audio device, and midi port (using midi-yoke) and I'm monitoring the port using midi-ox. I have uninstalled .40.3 and installed the current test (0.42.0test5) release, and midi works fine, but I can't get the OSC controls working (using the oscx dlls from the extended package). Ideally I would like to get 0.40.3 working with midi, but another option would be getting the OSC controls working in 0.42.0test5\. I know could downgrade back to .39.3, but I would like to do that only as a last resort. Anyone have any thoughts? Thanks, AltReality
Knobs and Sliders PD MIDI Setup?
what i don't understand is, why you need pd if you want to control traktor? isn't it possible to control traktor directly with nintendo? however, have a look at the objects \[noteout\] and \[ctlout\], this way you can send midi from pd via the midi out you selected in pd's properties. so, if you choose for example midi yoke 2 as midi out in pd, then you have to set midi yoke 2 as midi in in traktor. then sliders connectetd to \[ctlout\] should be sent to traktor. an example: create a ctlout object with the arguments 60 and 1, this should look like this: \[ctlout 60 1\] connect a slider to the first inlet of the ctlout object. now the slider values should be send to pd's midi out via controller number 60 on channel 1\.
Once again, "graph on parent" question
and here is a project patch i'm working on at the moment. it demonstrates, how useful it could be, to be able to change views within subpatches - if it would work a little more smoothly... ;) open the folder and run Rumble\_Box.pd. note, that this patch is not fully working and is only to demonstrate the mentioned effect. i guess, this is a too big gui for a view-change to be computed faster - but for more tiny guis this may be a nice feature though! edit: oh, i forgot to mention, that the sequencer works with midi-out, so you have to assign a midi-out that runs into a midi in. i solved this by using midi yoke and midi ox - midi yoke 1 for in and out and connected via midi ox. but for the visual aspect you will need no sound anyways... \*grin\* [http://www.pdpatchrepo.info/hurleur/Rumble\_Box.zip] : http://www.pdpatchrepo.info/hurleur/Rumble_Box.zip
PD midiindev what number?
Hello! I connected my USB MAudio Midisport 2x2 and installed the proper driver. It is soundcard 3\. /proc/asound/cards: 0 \[I82801DBICH4 \]: ICH - Intel 82801DB-ICH4 Intel 82801DB-ICH4 at 0xf4fff800, irq 7 1 \[VirMIDI \]: VirMIDI - VirMIDI Virtual MIDI Card 1 2 \[Modem \]: ICH - Intel 82801DB-ICH4 Modem Intel 82801DB-ICH4 Modem at 0xb400, irq 7 3 \[M2x2 \]: USB-Audio - MidiSport 2x2 M-Audio MidiSport 2x2 at usb-0000:00:1d.0-1, full speed The Ouptup of: aconnect -io: client 0: 'System' \[type=kernel\] 0 'Timer ' 1 'Announce ' client 72: 'Virtual Raw MIDI 1-0' \[type=kernel\] 0 'VirMIDI 1-0 ' client 73: 'Virtual Raw MIDI 1-1' \[type=kernel\] 0 'VirMIDI 1-1 ' client 74: 'Virtual Raw MIDI 1-2' \[type=kernel\] 0 'VirMIDI 1-2 ' client 75: 'Virtual Raw MIDI 1-3' \[type=kernel\] 0 'VirMIDI 1-3 ' client 88: 'MidiSport 2x2 - Rawmidi 3' \[type=kernel\] 0 'MidiSport 2x2 MIDI 1' 1 'MidiSport 2x2 MIDI 2' How can I find out what midiindev I have to use? Thank you a lot.
Virtual MIDI Drivers
So I have been using LoopBE1 on a project. Started a new project that is a little more intensive on the MIDI load. LoopBe1 bites it constantly. Looking at MIDI Yoke and Maple Virtual MIDI Driver. Any experience with these or others. What I am doing is getting a signal from a Beringher BCF2000 to PD. PD then send the input out on 4 channels through the virtual MIDI driver to Cubase to use as a generic remote. There are 6 continuous controllers, 3 switches capable of send MIDI as cc's to PD. Also there are 4 other buttons that send 9 cc messages at once to PD. Any suggestions for unbreakable (given that I do not have midi loops in the system) virtual MIDI drivers? Thanks
Multitrack Analysis Module
hi Matt Black of Coldcut here. as a step towards achieving multitrack audio visualisers, ie video synths which are controlled by multiple simultaneous audio inputs, i am interested in getting the following bit of software built, and think it could be made in PD. Am posting it here to see if anyone is interested. I can offer a fee to get this built. This is the initial spec. I call it a Multitrack Analysis Module , MAM. -MAM works with multi input ASIO soundcards eg RME fireface, and supports up to 16 audio ins. -MAM performs SEPARATE fft /spectrum analysis on EACH AUDIO INPUT , say 16 frequency bands per input . delivers amplitude for each frequency band. -outputs results of fft analysis as midi data. use cc numbers 1-16, with value 1-127 for the 16 frequency bands amplitudes. use midi channel 1-16 to distinguish the 16 audio inputs. Midi data can be routed to available midi interfaces/ports on the host machine, including virtual midi ports such as Maple, MidiYoke. -optionally, output could be via OSC/ethernet which would get round possible MIDI data rate problems. (Do people think MIDI could handle this amount of data? it could be thinned) -the MAM should be a self contained module , a stand alone patch that doesnt require a PD framework to run. As i dont know anything about PD , i dont know how it works, but you probably know what i mean. -ideally, MAM would also be able to run with Ableton LIVE so that one can route the analysis data off to another machine to do the visuals, and still manipulate the audio on the machine with the audio ins in LIVE. this is not essential but i would like to know if people think it would be possible. Hope this makes sense. I am looking for a good PD coder who is interested in working on a cutting edge project. A payment to build this initial module can be negotiated...not a huge one, but something. Interested parties can post here initially. Thanks. Matt Black
Midi devices not showing in 0.40.2
hi, i'm new to pd and started working in 0.38.4-extended under winxp. i just switched to version 0.40.2 (for easier handling of graph-on-parent) and get a problem: although my midi devices are listed properly when invocing pd with the -listdev %1 %2 %3 %4 %5 %6 %7 %8 %9 command line option, they are not selectable in the midi settings (only \#1 is shown for input, and \#1, 3 and 7 for output). do you have any idea what might be the solution? (those are the devices:) MIDI input devices: 1. MPU-401 2. SB Audigy MIDI IO [E000] MIDI output devices: 1. Microsoft MIDI Mapper 2. SB Audigy Synth A [E000] 3. MPU-401 4. SB Audigy Sw Synth [E000] 5. SB Audigy Synth B [E000] 6. SB Audigy MIDI IO [E000] 7. Microsoft GS Wavetable SW Synth
woo! i don't have to learn this programming stuff after all...(wipes brow) the pd list came thru with an answer to midi start/stop/tempo issues: \*\*\*\*\* how about using pd's \[midiin\] or \[ctlin\] objects, then filtering the messages acording to \[url=[http://www.borg.com/~jglatt/tech/midispec.htm] \][http://www.borg.com/~jglatt/tech/midispec.htm] so 0xFA (250 in decimal) will be midi start, 0xFC (252) is midi stop. 0xFB (251) is midi continue. \> also, what about tempo? anyway to send or recieve that? 0xF8 (248) is the midi clock signal, which gets emitted 24 times every quarter note by your midi master. catch this signal and use \[timer\] to calculate the bpm out of it, if you want. last but not least, there is the song pointer 0xF2 (242) which gives the current song position of your master in 16/th notes. hope that's what you wanted to know ::::: thanks a lot, list poster christopher charles :))) : http://www.borg.com/~jglatt/tech/midispec.htm
Is this possible?
Hi I'm a total noob to PureData. I find it a bit confusing at the moment so bear with me if this sounds a bit stupid.. I would like to use PD in conjunction with a hardware MIDI keyboard, to build my compositions in my usual way (I sort of "multitrack" separate instrument parts over a sequenced beat, and then zoom in on graphically-represented MIDI events and shift them here and there or delete them or change note properties). The MIDI events are then played through my soundcard's internal MIDI port. I would like to do ALL this with PD. However, there's something NEW I'd like to do too. Namely, I want to use the aforementioned compositional technique, except define my own instruments using FM synthesis, and then to send certain channels to DSP effects units. I then want to be able to control, with my hardware MIDI controller, the wet/dry and other FX parameters relating to individual software effects, and to automate (i.e. record with MIDI) my own actions as I tweak the effects. So far, no software allows me to have the perfect setup, but it seems that PD might be powerful enough for me to design and implement this environment to my exact requirements. My simple question is: is this a normal use of PD (i.e. can it be done)? Thanks
Guitar multi-effects rig
This is my live guitar effects right as of Feb 14, 2009\. Please let me know if you find it useful or have any ideas for effects or other improvements. If you make some music with it, I'd love to hear it! Once I have some more time to program it, my next effect will probably be a Vocoder. Run effectsrig.pd to load it up. A midi expression pedal is recommended for the best experience - but it's not required. It contains the following effects: whammy~ ------- Digitech whammy style pitch shifter. Allows for smooth changes to the pitch shift amount. Based on the one posted by "kenn" on the puredata.info forums (which in turn is based on the pd example code). shimmer~ -------- A "shimmer" synth-like effect. This is done with a pitch shift in a feedback loop of a very short delay. octfuzz~ -------- Octave-up distortion like you can obtained with the classic transform and 2 diodde rectifier circuit. Basically it just full-wave rectifies the audio signal. This one really brings out the high frequencies (some times a little too much!). leslie~ ------- A stereo leslie (rotating speaker) simulator. This is one of my favorites. If modulation is turned all the way down it becomes tremolo. Take one of the outlets for mono use. Try it in stereo for super-swirley bliss! When using an expression pedal to control the rate, heel down will bypass the effect. Expression pedal control is done by expression.pd. It simply reads in MIDI and scales it to a 0-\>1 range. You can change the midi channel used by editing this file. The preset system is a little hack-ish, but it works for me. If anyone has any better ideas on how to do this, I'd love to hear them. When you load up the main effectsrig.pd file, you will see a bunch of message boxes. This are quick settings buttons - just click one to apply that effect. They are designed so you can click a couple in a row to quickly apply a few different settings. To start over, click the big "default" one on the left. It can also load presets based on midi messages. I use this with my Eventide TimeFactor pedal. When I change presets on the TimeFactor, PD follows along. This is handled by the box in the top right. The symbol box is for song titles, and the number boxes show the current TimeFactor preset. Open this box to see how I've done a couple of example midi controlled presets. "pd your\_love\_never\_fails" is a more complicated example that changes the expression pedal behavior slightly. If you want to use a different midi channel for listening to program changes, just edit preset.pd and presetnum.pd. preset.pd outputs a bang when the preset number supplied as a parameter is chose. presetnum.pd just outputs the number of the selected preset. [http://www.pdpatchrepo.info/hurleur/effectsrig.zip] : http://www.pdpatchrepo.info/hurleur/effectsrig.zip
Random Melody Generation
Basically i tested this on Reason and Ableton. It uses external midi control rather than a built in synth sound in pd. I don't really know anything about Pro Tools but if there is a device that plays midi control notes, then assign channels 1 & 2 to the proper midi driver through Pro Tools. Also you're going to need to set your MIDI output device 1 to the midi driver you use for pro tools. [http://nerds.de/en/loopbe1.html] use this You'll have to set the channels for Pro Tools as well as the midi driver. : http://nerds.de/en/loopbe1.html
MIDI weird issues with arduino + PD (not pduino)
i'm not shure this is your case because it seems you're using a midi software synth and a sensor but i know that "if you hear double notes when playing your MIDI keyboard, (slapback echo or flanging, the chances are that MIDI Thru in your sequencer and Local Control on your keyboard are not set up correctly. This causes the keyboard to sound two notes - the one you play on the keyboard and another being echoed from the computer... On your keyboard you need to switch Local Control to Off. This disconnects the keys from the sound circuitry so sounds can only be played via messages arriving at its MIDI In" ([http://www.practicalpc.co.uk/computing/sound/miditop5.htm]) but i'm not so shure this helps... what midi module are you using? is it hadware or software stuff? you can try to monitor icoming midi messages with midiox to check that everything is going right : http://www.practicalpc.co.uk/computing/sound/miditop5.htm
Open DMX external?
hi there i followed the different forum post on getting the enttec open dmx usb to work in ubuntu and pd. so far i downloaded the dmx4linux-2.6 package extracting it ok patching it ok ./configure ok make gives me this result: ---------------------------------- make -C libs all make\[1\]: Betrete Verzeichnis '/home/maik/externals/dmx4linux-2.6.1/libs' cc -c -o open.o open.c cc -c -o sleep.o sleep.c ar rcs libdmx4l.a open.o sleep.o cc -fPIC -c -o open.lo open.c cc -fPIC -c -o sleep.lo sleep.c cc -shared -Wl,-soname,libdmx4l.so.2 -o libdmx4l.so.2.5 open.lo sleep.lo -lc ln -sf libdmx4l.so.2.5 libdmx4l.so.2 ln -sf libdmx4l.so.2 libdmx4l.so make\[1\]: Verlasse Verzeichnis '/home/maik/externals/dmx4linux-2.6.1/libs' make -C tools all make\[1\]: Betrete Verzeichnis '/home/maik/externals/dmx4linux-2.6.1/tools' cc -Ipointer -Wall -O2 -I/home/maik/externals/dmx4linux-2.6.1/include -c -o dmxtest.o dmxtest.c dmxtest.c: In Funktion »Reader«: dmxtest.c:65: Warnung: Der Rückgabewert von »fgets«, der mit dem Attribut warn\_unused\_result deklariert wurde, wird ignoriert dmxtest.c: In Funktion »Writer«: dmxtest.c:143: Warnung: Der Rückgabewert von »fgets«, der mit dem Attribut warn\_unused\_result deklariert wurde, wird ignoriert cc -L/home/maik/externals/dmx4linux-2.6.1/libs -o dmxtest dmxtest.o -ldmx4l cc -Ipointer -Wall -O2 -I/home/maik/externals/dmx4linux-2.6.1/include -c -o midi2dmx.o midi2dmx.c midi2dmx.c: In Funktion »DMXput«: midi2dmx.c:246: Warnung: Der Rückgabewert von »write«, der mit dem Attribut warn\_unused\_result deklariert wurde, wird ignoriert midi2dmx.c:254: Warnung: Der Rückgabewert von »write«, der mit dem Attribut warn\_unused\_result deklariert wurde, wird ignoriert midi2dmx.c: In Funktion »reset«: midi2dmx.c:297: Warnung: Der Rückgabewert von »write«, der mit dem Attribut warn\_unused\_result deklariert wurde, wird ignoriert cc -L/home/maik/externals/dmx4linux-2.6.1/libs -o midi2dmx midi2dmx.o -ldmx4l cc -Ipointer -Wall -O2 -I/home/maik/externals/dmx4linux-2.6.1/include -c -o uart\_dmxd.o uart\_dmxd.c cc -L/home/maik/externals/dmx4linux-2.6.1/libs -o uart\_dmxd uart\_dmxd.o -ldmx4l cc -Ipointer -Wall -O2 -I/home/maik/externals/dmx4linux-2.6.1/include -c -o dmxconsole.o dmxconsole.c dmxconsole.c:19:20: Fehler: curses.h: No such file or directory dmxconsole.c: In Funktion »mask«: dmxconsole.c:138: Warnung: Implizite Deklaration der Funktion »erase« dmxconsole.c:141: Warnung: Implizite Deklaration der Funktion »attrset« dmxconsole.c:142: Warnung: Implizite Deklaration der Funktion »move« dmxconsole.c:143: Fehler: »COLS« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:143: Fehler: (Jeder nicht deklarierte Bezeichner wird nur einmal aufgeführt dmxconsole.c:143: Fehler: für jede Funktion in der er auftritt.) dmxconsole.c:144: Warnung: Implizite Deklaration der Funktion »addch« dmxconsole.c:148: Fehler: »LINES« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:161: Warnung: Implizite Deklaration der Funktion »printw« dmxconsole.c: In Funktion »values«: dmxconsole.c:199: Fehler: »COLS« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:207: Warnung: Implizite Deklaration der Funktion »mvprintw« dmxconsole.c:249: Fehler: »LINES« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:263: Warnung: Implizite Deklaration der Funktion »attron« dmxconsole.c:263: Fehler: »A\_REVERSE« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:268: Warnung: Implizite Deklaration der Funktion »addstr« dmxconsole.c: In Funktion »crossfade«: dmxconsole.c:362: Warnung: Implizite Deklaration der Funktion »refresh« dmxconsole.c: In Funktion »load«: dmxconsole.c:404: Warnung: Der Rückgabewert von »fread«, der mit dem Attribut warn\_unused\_result deklariert wurde, wird ignoriert dmxconsole.c: In Funktion »changepalette«: dmxconsole.c:470: Warnung: Implizite Deklaration der Funktion »init\_pair« dmxconsole.c:470: Fehler: »COLOR\_BLACK« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:470: Fehler: »COLOR\_CYAN« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:471: Fehler: »COLOR\_GREEN« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:472: Fehler: »COLOR\_WHITE« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:473: Fehler: »COLOR\_BLUE« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:474: Fehler: »COLOR\_RED« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:476: Fehler: »COLOR\_YELLOW« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:492: Warnung: Implizite Deklaration der Funktion »COLOR\_PAIR« dmxconsole.c:503: Fehler: »A\_REVERSE« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:504: Fehler: »A\_BOLD« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:505: Fehler: »A\_NORMAL« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c: In Funktion »calcscreengeometry«: dmxconsole.c:536: Fehler: »COLS« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:543: Fehler: »LINES« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c: Auf höchster Ebene: dmxconsole.c:566: Fehler: expected »=«, »,«, »;«, »asm« or »\_\_attribute\_\_« before »\*« token dmxconsole.c: In Funktion »pointerevent«: dmxconsole.c:613: Fehler: »KEY\_UP« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:616: Fehler: »KEY\_DOWN« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:620: Fehler: »KEY\_LEFT« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:623: Fehler: »KEY\_RIGHT« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:627: Fehler: »KEY\_PPAGE« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:630: Fehler: »KEY\_NPAGE« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c: Auf höchster Ebene: dmxconsole.c:636: Fehler: expected »)« before »a« dmxconsole.c: In Funktion »cleanup«: dmxconsole.c:648: Fehler: »w« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:650: Warnung: Implizite Deklaration der Funktion »resetty« dmxconsole.c:651: Warnung: Implizite Deklaration der Funktion »endwin« dmxconsole.c: In Funktion »main«: dmxconsole.c:793: Fehler: »w« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:793: Warnung: Implizite Deklaration der Funktion »initscr« dmxconsole.c:800: Warnung: Implizite Deklaration der Funktion »savetty« dmxconsole.c:801: Warnung: Implizite Deklaration der Funktion »start\_color« dmxconsole.c:802: Warnung: Implizite Deklaration der Funktion »noecho« dmxconsole.c:803: Warnung: Implizite Deklaration der Funktion »raw« dmxconsole.c:804: Warnung: Implizite Deklaration der Funktion »keypad« dmxconsole.c:804: Fehler: »TRUE« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:811: Fehler: »mmask\_t« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:811: Fehler: expected »;« before »m« dmxconsole.c:812: Warnung: Implizite Deklaration der Funktion »mousemask« dmxconsole.c:812: Fehler: »BUTTON1\_PRESSED« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:812: Fehler: »BUTTON2\_PRESSED« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:812: Fehler: »BUTTON3\_PRESSED« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:812: Fehler: »BUTTON4\_PRESSED« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:812: Fehler: »REPORT\_MOUSE\_POSITION« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:812: Fehler: »m« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:813: Warnung: Implizite Deklaration der Funktion »mouseinterval« dmxconsole.c:855: Warnung: Implizite Deklaration der Funktion »wgetch« dmxconsole.c:961: Fehler: »KEY\_PPAGE« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:979: Fehler: »KEY\_NPAGE« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1012: Fehler: »KEY\_HOME« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1018: Fehler: »KEY\_END« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1026: Fehler: »KEY\_RIGHT« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1031: Fehler: »KEY\_LEFT« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1036: Fehler: »KEY\_DOWN« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1047: Fehler: »KEY\_UP« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1059: Fehler: »KEY\_IC« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1066: Fehler: »KEY\_DC« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1129: Warnung: Implizite Deklaration der Funktion »KEY\_F« dmxconsole.c:1129: Fehler: case-Marke reduziert nicht auf Ganzzahlkonstante dmxconsole.c:1133: Fehler: case-Marke reduziert nicht auf Ganzzahlkonstante dmxconsole.c:1137: Fehler: »KEY\_MOUSE« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1139: Fehler: expected »=«, »,«, »;«, »asm« or »\_\_attribute\_\_« before »oldevent« dmxconsole.c:1139: Fehler: »oldevent« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1140: Fehler: »MEVENT« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1140: Fehler: expected »;« before »event« dmxconsole.c:1141: Warnung: Implizite Deklaration der Funktion »getmouse« dmxconsole.c:1141: Fehler: »event« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1141: Fehler: »OK« nicht deklariert (erste Benutzung in dieser Funktion) dmxconsole.c:1141: Warnung: Implizite Deklaration der Funktion »meventcmp« dmxconsole.c:1184: Warnung: Implizite Deklaration der Funktion »resizeterm« make\[1\]: \*\*\* \[dmxconsole.o\] Fehler 1 make\[1\]: Verlasse Verzeichnis '/home/maik/externals/dmx4linux-2.6.1/tools' make: \*\*\* \[all\] Fehler 2 ----------------------------- any suggestions? something with dmxconsole? i'm really not into all the programming stuff so i basically need everything step by step. hope someone can help greets uisel
More midi output device options needed
I'm not entirely sure I get what you're saying, but I think I do. Are you saying that you want to be able to send MIDI directly from Pd to your MIDI hardware, and you're only using Live as a workaround because you only have two MIDI outputs listed in your MIDI settings? If so, you can do it like this: 1\. Hook up your gear, then go into Preferences -\> MIDI Settings... and click on the device button to open the drop-down menu. 2\. Make note of the order the devices are listed starting from "none" = 0\. Close the window. 3\. Now, open Preferences -\> Startup.... There is a field at the bottom labeled "startup flags." Don't delete what's already there; instead, at the end add "-midioutdev" followed by the numbers corresponding to the devices from step 2\. So if you want to use devices 1, 2, and 4, you would put "-midioutdev 1,2,4" (no quotes). You can put as many as you want, I think. Or at least you can do more than two. 4\. Apply, OK, and restart Pd. Now the MIDI devices can be accessed by multiplying the channel number by the number they appear in your -midioutdev list. The example in step 3 would be channels 1-16 for device 1, 17-32 for device 2, and 33-48 for device 4\. Hope that's what you're looking for.
Pd linux , problems with midiman oxygen
hi folks i´m newbie , and i have a problem with my oxygen midi controller. with other kinds of programs like sooperlooper or muse , i have no problem to make working . qjack recognize it and i can patch the midi program inputs , etc..... but in the case of pd , i can´t start any midi response. i ´ ve tried midiindev 1 and 2..... , and nothing happens with midi. i´m working with crrma fedora packages . by the other hand,is it possible that qjack recognize pd midi ports to patch with the midi controller ? thanks in advance. sergi
Theremin to MIDI Control program in Pd - help needed
Hey Pitch Twit, Charles here. The idea of that patch was to send MIDI control data, and not pitch and amplitude data. It isn't very difficult to change the patch to output pitch information since the fiddle~ object already returns pitch as a midi note value. I think that the best thing for you to do is to follow some of the Pd tutorials (these are in the doc directory inside the application folder) and learn about which objects can output midi notes. I'm not sure how hard it would be to create a patch that can output meaningful MIDI notes from violin. The answer could be \`\`extremely hard" if you're looking for an accurate MIDI transcription of a violin performance. But if you only want to have MIDI information that corresponds (in a simplified way) to what you are playing on violin, it could be quite simple like my theremin patch.
Logic and pd??
I've been using Logic with Pd for the past few months. With the latest version of Pd-extended, Jack seems to work fine. There's an example in Jack's helpfile for using it with Logic. Just remember to set Pd to Jack mode (Media menu). I've been going the IAC route for sending MIDI back and forth between the two apps, and with Logic there's a certain trick you have to do in order to avoid MIDI feedback loops. Logic (like most sequencers I've used) automatically sets tracks to receive on all MIDI input devices when in record mode. This can be a drag with IAC, because when you record MIDI to the IAC track, it sends it to the app (Pd in this case) via the bus, but then reads it back in immediately because it's also set to receive from the IAC bus! To avoid this, you'll need to go into the Environment, and go to the Clicks & Ports layer. Create a new object (it doesn't really matter, but I usually use the Moniter just so I can see what's going out) and connect the IAC port from the Physical Input object to the new object. This takes the IAC bus out of the SUM port, thus keeping it from going back into the sequencer. Note: You only need to do this if you are sending MIDI from Logic to Pd. If you are sending MIDI from Pd to Logic, then it should work fine from the default set-up.
I am really not getting this $ business ;) For example, I am using the \[ctlin\] to receive certain midi CC's. I figured it would be easy to send a variable to select midi channel & midi cc, but having no luck yet. Do i always have to create an "abstraction" when I use the $1 $2 $3 stuff ? Like a sublayer or something, excuse my PD internal ignorance, it will get better I hope ;) \[ctlin $1 $2\] would be enough for now, I just dont know where/how to set $1 $2 ;) so basicly I want to create a user-interface to quickly select: - midi channel - midi cc - type of sub module to process the midi cc signal with - option paramters for the sub module (invert signal, range, ... ) I looked at the $ examples in the browser but I am really missing some understanding of PD. I also do not understand why you can use arguments but not send the arguments to an inlet. Whats the purpose of that ?
Only 1 of 2 midi devices found in PD (Gentoo Linux)
I didn't really get the last part of your reply, however I got it working now :) Doepfer is at /dev/midi = PD midi in 2 Midi keyboard is at /dev/midi2 = PD midi 3 So I launched my simple midi patch which uses ctlin (for doepfer) and notein (for midi keyboard) with: pd -midiindev 2,3 Works perfectly!
Using pd to control logic thru midi?
Hello. I'm very very new at Pd, trying to create NRPN converters to use Alesis ION as MIDI controller in Logic. I'm also interested in general MIDI control of Logic using Pd. I can send MIDI info to my audio interface (M-Audio Firewire 410), but I'm not sure how to get Logic to pick up on MIDI sent from Pd without cabling together the MIDI-In and MIDI-Out on the 410\. Any ideas? Darrell
MakeNote, NoteOut sounds
Use \[pgmout\] to send a program change to that MIDI device. If you have a standard MIDI layout then these are the instruments and numbers to send [http://www.midi.org/about-midi/gm/gm1sound.shtml] : http://www.midi.org/about-midi/gm/gm1sound.shtml
Can Pd "send" keyboard commands
In case it does not, here's a Mac loopbacker link (BTW ~isn't Jack also about this sort of stuff?): LoopBe30 is a virtual MIDI device driver for transferring MIDI data between computer programs. Basically LoopBe30 provides up to 30 independent invisible cables to connect MIDI outports of applications to any other application's MIDI inport. [www.soft411.com/software/midi-mac\_5.html] (was actually just wondering whether I'd understood the question right, to begin with~;o) : http://www.soft411.com/software/midi-mac_5.html
Smooth MIDI clock jitter
I think becasue the events aren't timestamped they are only getting through, not necessarily locked to any grid. This might work if the events can be quantized to a grid somehow? I keep coming back to needing this functionality so it would be good if I could find a solution... I read this in the html help for Pd: > MIDI and sleepgrain > > In Linux, if you ask for "pd -midioutdev 1" for instance, you get /dev/midi0 or /dev/midi00 (or even /dev/midi). "-midioutdev 45" would be /dev/midi44\. In NT, device number 0 is the "MIDI mapper", which is the default MIDI device you selected from the control panel; counting from one, the device numbers are card numbers as listed by "pd -listdev." > > The "sleepgrain" controls how long (in milliseconds) Pd sleeps between periods of computation. This is normally the audio buffer divided by 4, but no less than 0.1 and no more than 5\. On most OSes, ingoing and outgoing MIDI is quantized to this value, so if you care about MIDI timing, reduce this to 1 or less.
Changing midi sounds and more
1\. use "program change" MIDI messages, and optionally "bank select" (a particular "control change" controller) MIDI messages 2\. from Pd's help browser -\> 5.reference -\> 0.INTRO.txt: ------------------------------ MIDI ---------------------------------- notein ctlin pgmin bendin touchin polytouchin midiin sysexin - MIDI input noteout ctlout pgmout bendout touchout polytouchout midiout - MIDI output makenote - schedule a delayed "note off" message corresponding to a note-on stripnote - strip "note off" messages
Changing midi sounds and more
You can use \[pgmout\]. The left inlet sets the program, the right inlet sets the midi channel. For control messages use \[ctlout\] See YOURPDPATH/doc/5.reference/pddp/midi-help.pd For your specific needs these matters pertain more to MIDI than Pd itself. Consult [http://www.midi.org/] : http://www.midi.org/
Your hardware equipment ?
as far as hardware for triggering events goes...you can pretty much use what ever you want. any MIDI compatible device would be fine. my suggestion is to use whatever you have or whatever you're comfortable with. Pd is flexible enough to allow you to map pretty much any input to any event or output. one tip i can offer is that if you are serious about interfacing, consider using OSC (open sound control) for communication between your various components. it is more flexible than midi and is becoming more and more portable and adaptable. even if you are using midi connections, it can still be benificial to implement an OSC messaging system: lets say you have a midi keyboard controlling part of your patch. if you convert incoming midi messages to OSC messages, you can also control your patch from any other hardware or software application that supports OSC and is connected to your patch (either physically or virtually by a tcp/udp connection). sorry if this is more confusing than helpful; let me know if you have questions. sometimes the pd OSC externs can be hard to track down but if you search this forum i know i have posted a link in the past.