PortMidi 'Invalid Device ID'
I have been having this issue (maybe non-issue) for some time.
Here is my set up:
Teensy 2.0 MIDI Device
Late 2013 Macbook Pro
I am using a Teensy MIDI device in Pd.
If I connect the Teensy device, then launch Pd, I get the following error message:
could not open midi input 0 (Teensy MIDI): PortMidi: 'Invalid device ID'
could not open midi output 1 (Teensy MIDI): PortMidi: 'Invalid device ID'
Under my MIDI settings I have "Teensy MIDI" selected both as my input and output.
If I re-select "Teensy MIDI" in both dialogs of the MIDI preferences menu, and hit OK the same error message will reappear in Pd's print window.
Though I get this error, it seems to not effect the use of the device in any way.
When I connect the device to a windows machine, I don't have this PortMidi error message.
I have also connected this device to my iPhone using MobMuPlat, no issues.
Any advice would be helpful.
throbbing midi note.
I can't seem to set the midi up right. I'm sure it's a simple fix I'm missing, but I honestly did spend a lot of time with google trying to find the answer. Hopefully someone can help out a poor newb.
I'm using a Firepod interface.
Input device: PreSonus FirePod MIDI in
Output device: PreSonus FirePod MIDI out
In "testtone.pd" patch, when I click on the MIDI OUT box, I get a "throbbing" sound from my rack-mounted synth. "wah wah wah wah..." about 500 milliseconds each.
...it sounds maybe almost like a memory cutout? or something is breaking up the tone.
The hardware is all fine. If I set it up the same way with Reaper or Sonar I get a nice steady tone.
I just want PD to hold a steady pitch for MIDI out on my synth. Should be easy right? I'm on my third day trying to get it to work. Any help would be great!
MIDI Controller experiences/suggestions
@lovelovevideo Hello again.......... if your computer can talk to to the midi device then Pd will work fine. So the real question is "what usb midi devices will work with your computer".
The most future proof for you will be a usb soundcard with midi connectors, or just a usb midi card...... because then any and all midi devices will talk to it through standard 5-pin din connectors. But if a midi device will talk to your computer then it will talk to Pd.
That was a bit long winded... the question is...... "does my computer have the drivers available........ that work!........... for the device?....."
I don't use midi much nowadays as for control I use the "new midi" called osc. Pd works well with osc and you could try it if you have a tablet. I use this app http://hexler.net/software/touchosc which apart from being very reasonably priced and being available for ios and android (sounds like an advert!) will let you draw toggles buttons sliders and XY pads and more on your tablet.
Musicians still use midi for the notes (better timing) but are increasingly using osc for control....
It is far easier to understand than midi.
Usefull sends messages to pd
@heyok I have a similar question: for pd .46-7 on a raspberry pi, do you know how to open the OSS-MIDI, or MIDI settings window?
I'm having a similar issue that I've been dealing with in this thread:
the "; pd midi-properties" message opens up the ALSA-MIDI or ALSA MIDI settings window, I'm trying to open the OSS-MIDI or MIDI Settings window.
I tried "; pd midi-settings" message.
Let me know if you have any ideas.
Initialize midi settings
OK. Well I think I made some progress.
Here is a little more info on what I am doing: I am using an arduino as a midi controller by installing MIDI/MOCO for LUFA on the USB port of the Arduino. I don't know if that's OSS midi device or not.
I put "-alsamidi" in the startup flags and that sort of worked. when I started pd some of the midi inputs worked, but the midi outputs were not working ( I am sending messages from Pd to turn on LEDs). When I went into the OSS-MIDI dialog box in the media drop down menu I just had open it and everything was fine. I don't even need to hit OK or APPLY, just open dialog box and everything is good.
I'm guessing perhaps having OSS and ALSA midi is confusing my controller. If I could turn off the OSS part maybe I would be fine, or if I could find a way to open that dialog box when I launch Pd.
Thank you all for your suggestions. Let me know if you have any other things I can try.
'Swallow' keyboard key press
Thank you for the answer! I 've been looking for so long for a way to use the qwerty keyboard as a midi instrument and controller without having to focus on the program windows and only glovepie could do that but it's dead now.
Auto Hot Key should be able to swallow input but I haven't tried the midi side yet.
For people curious about this, here's what I found until now that can be useful:
http://www.bome.com/products/mousekeyboard is very nice with keyboard, mouse and joystick midi control. You can also trigger chords. But the window needs to be on top to receive the keys..
http://freepiano.tiwb.com/en/ Open source and allows to self record midi. Still needs window focus.
http://www.nosuch.com/keykit/ is quite fun for the geeks. Maybe a bit similar to puredata. Needs window focus.
http://midi-control-center.software.informer.com/ Very old but a lot of midi messages and notes customization with joystick, keyboard and mouse. Need window focus.
http://www.vanilin.org/v7/7.html How frustrating! This one finally is able to swallow keys even when not in focus and you can customize the keys a bit but no midi control and no use of special keys.
Need help to slightly modify a PD project (Rythmboy)
I recently stumbled upon a PuraData based step sequencer for my QuNeo MIDI controller, the so called Rythmboy:
I want to use it as a step sequencer to use with the remix decks in Traktor, so I can add drums to the tracks I play.
Unfortunately, the Rythmboy has an internal MIDI clock, so I can't sync it with an external clock. I already tried to replace the BPM rotary in the patch with "MIDIrealtimein" and the stuff that's also needed, but I can't get it to work.
I managed to do all the other stuff that is needed to work with Traktor (changing the note output, optically mirroring the rotaries, limiting the notes ranges etc.), so I tried, but I don't know how to work with an external midi clock. Another problem that may occur is that the Rhythmboy then needs two MIDI inputs, #1 is the QuNeo and #2 is the external clock (Traktor or my Xone4D mixer).
This is the part of the Rhythmboy that controls the MIDI clock:
The blue box is a tap button to tap in the tempo. This is not needed.
The red box converts a rotary MIDI input between 0 and 127 into a BPM value between 60 and 240 bpm and gives out that value. This is where the changes need to happen I think. I need something that changes the MIDI clock in into a numerical BPM value.
The green box gives output to the rotary LEDs to show the current BPM. This is also not needed.
The other stuff lets a LED blink a metronome, I think.
So, would one of you please tell me what to put in instead of the red box, to make the magic happen?
animate image sequence with MIDI
I just started out with Pd for a vey specific project, but I'm pretty inept with computers so please be patient!
I'm trying to control and animate image sequences via MIDI, with the MIDI Clock signal (or a fraction therof) working as the framerate and using MIDI Note messages to select the animation, as well as MIDI CC messages to control visual effects (colour hue, rotation, inversion and so on).
I've managed to make a MIDI clock counter and tried using it to cycle through the images of a "pix_multiimage" object, but it won't cycle through the image sequence (only the first image of the sequence is displayed) as it is recieving a bang rather than a float.
I assume there is something missing between the clock output and the multiimage input. I've tried addind a "float" (and "float 0" and "float "1") message inbetween and the error message stops, but the image still doesn't cycle.
That's my main question for the moment, further down the line I'd also be greatful for any info on how I would go about setting up the "notein" values to select from a matrix of multiimage objects, ideally with the option to layer images when polyphonic input is recieved, and how to implement the CC controlled visual effects, but that would probably be asking too much.
Filter out midi clock information
I am currently using a pd patch to take incoming MIDI values from a drum pad, manipulate them, and pipe them into another program for sound generation. Unfortunately, my drum pad seems to be constantly sending MIDI clock information. Here's a screenshot to view incoming MIDI messages to my system.
In my patch, I use a custom abstraction to "learn" MIDI notes coming into pd. Basically, when I enable my abstraction to "learn", I tap a note on my MIDI keyboard or drum pad and it instantly becomes mapped to that abstraction. It's basically a really easy way to set the arguments for [notein], [ctlin], etc. However, this MIDI timing signal is screwing everything up. Now when I try to "learn" a MIDI note, the note "0" from channel "10" keeps triggering before I even have a change to tap my keyboard or drum pad.
Any idea how I should filter this out? I would like to just ignore all messages from channel 10, but that's where all my actual note data comes in as well.
Midi to hz, and hz to midi formulas
The circles we calculated the orbits to be proved each to be slightly short of a true, pure circle, thus returning the satellites to the ground. Pi more precisely can be evaluated to 3.1446055, and not the perpetuation of imperfection, and the maintenance of ignorance still taught today.
Sorry to be blunt, but what you are stating is awfully incorrect and the way you proclaim to know this "hidden truth" is really awufully ignorant. So you are stating that there is a mistake on the 3rd decimal digit of pi... It so happens that this decimal place was precisely calculated centuries ago, and the result still (obviously) stands today. There are tons of different approaches on how to get correct digits of pi, such as by using certain convergence series as mentioned by @seb-harmonik.ar. One can manually calculate the 3rd digit of pi using these type of series, and this result has been known for more than a millennium (in the year 480, the value known was 3.1415926, which is way more precise than what you state. By the early 18th century, we knew 100 digits of pi, none of which have been "corrected" later on. See: https://en.wikipedia.org/wiki/Chronology_of_computation_of_π). There is no way that in the 1960's pi had to be defined as 3.1446... instead of 3.1415..., that is just pure ignorance and witchery.
But reading about your number on the internet, I found that this 3.1446055 appears in several articles about satellites, pyramids and all that "dark hidden world that nobody tells you about open your eyes sheep people controlled by the illuminati" kind of talk, but not a single time in a serious mathematical or physics website/journal/wiki. Sorry but the world is not a dark place controlled by people with magic powers trying to keep you in the shadows... simply do not use random blogs as source of information.
The assumption of equal temperament proves a repetitious vexation, denotes ignorance, apathy, laziness, and/or unfamiliarity with the math of music. Worse, this assumption proves far too common among engineers / mathematicians / scientists / software programmers. Which then deprives us musicians of useable tools, and the stupidity of the need for MIDI tuning standard / scala / etc, is the vacuum such engenders.
As for the "stupidity" of using a tempered system, that is just as stupid as using a non-tempered one: it is simply a convention, upon which we built centuries of music. Western music has been based on it for long time (although contemporary composers, myself included, often choose to use micro-intervals), and the decision to create MIDI around this is as logical as it gets when you think what they were aiming at. Or should we have went through all sorts of trouble to incorporate all crazy stuff in the MIDI protocol (which is an Western creation), such as the possibility of having Indian micro-tonal scales? But wait, then what about gamelan scales? No wait, what about <insert ethnomusic genre here> scales?
From a practical point of view, you can still use MIDI cents, and you can also directly use frequencies if you want to precisely define the pitch of a sound. You can compose music in 12-tones, 27-tones or 193-tones if you wish to. The tools are here, and Pd allows you to do whatever you want with them (I myself have composed works using Pd and MIDI that deals with microtones and microtonal glissandi in real-time).
I hope you won't get personally offended with my message, but I can't really read this type of statement, which tries to propagate pseudo-scientific kind of stuff, without writing a strong reply.