Controlling pure data with Logic Midi
I have read this:
http://lists.puredata.info/pipermail/pd-list/2005-07/029545.html
and followed the instructions, but Logic keeps crashing, and does not output midi notes all of the time (they sort of come in clusters). It has been very laggy and inaccurate.
Any ideas?
Thor thinks it might be a bug with Logic or something.
Thanks.
IAC bus is quite crap.
i highly doubt that logic has simple bugs like that though.
Might be time to change daw. Have people managed to do it successfully with Ableton or Reaper?
Have you checked out this? http://www.mazbox.com/pandemonium/
It runs Pd as a plugin in Logic
Doesn't appear to run on OS 10.5.6
I don't have the newest version of Logic, but had this going with Logic 8 and OSX 10.5 just fine using the setup I posted here:
It still isn't working for me although going into the environment and connect the iac to a monitor did help somewhat, (it stopped it glitching and lagging). But using midiin in pure data I am only getting values of 0 and 80 momentarily.
I am also using Logic 8 and OS 10.5 so this is really weird.
When I look at it in Logic as well in the environment, it is only outputting values of 80 and 0, but the sequence I have written varies a lot more.
Half of the problem was that the notes were overlapping. Now the only problem is that every note on the piano roll comes out at 80. Does anyone know why this is? When I change the note velocity the pitch changes.
check your midi signals with this midi monitor app (it's free):
http://www.snoize.com/MIDIMonitor/
then, at least you will know whether the glitch is on the logic side or the pd side.
if it's on the logic side, then focus on that to see if you can find the error. As i said, i highly doubt logic has any serious bugs like the piano roll not working; but there might be some setting that is not obvious, or something like that. You're probably not the only one to encounter such a problem, so have a google.
Sometimes cracked software has weird glitches though, and of course no one here would use anything like that (cough), but that could be a possibility.
Unless the problem is with pd, though, not sure how much help any of us lot will be.
I think the problem is with Logic, I will have a look around.
I am proud to say that I own all of my software. Which doesn't consist of a massive amount. This is why I love pure data!
I have found out what the problem was after some searching and speaking to people on the Logic forums.
I managed to get it to work with notein, not midiin. The left outlet of midiin appears to have been sending out the velocity value, not the note value. I assumed that it was sending out the note value and that was something wrong with Logic.
So not a problem with Logic, a problem with Pure Data, my mistake. It would have been good if somebody could have noticed that I was using midiin however, are other people using midiin successfully or notein?
Who says no one noticed? You didn't say how you were using [midiin], so we couldn't really tell that you didn't know how to use it. That's why we suggest attaching patches.
[midiin] sends raw, unparsed MIDI data. It should send three numbers in a row when you press a key: 145, <note>, <velocity>. My guess is you're "only getting" the velocity value because you're not parsing it, and you have it hooked up to one thing (like a number box). The velocity is just the last value, and the other two happen too fast to notice. Stick a [print] after [midiin], and you should see all three values.
If you want to use [midiin], I suggest using [midiparse] to format all the data coming in.
ah thankyou very much! That is very helpful.
I said I was using midiin in the 7th post, " But using midiin in pure data I am only getting values of 0 and 80 momentarily."
All working now.
Thankyou ever so much for all of your help, I can't thank you enough.
in hindsight, it all makes sense now.
Oops! Looks like something went wrong!
