Member Avatar for dintymoore

If I had an internal MIDI THRU working, I could eliminate a few pieces of rack mount gear, and just use USB to connect my MIDI modules. I found this, and it seems that it's all there:

I've having trouble finding:

/Developer/Examples/CoreAudio

Where is that?
Thanks, and many thanks for the other answers/comments to my earlier questions!

  • 2 Contributors
  • 4 Replies
  • 324 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by dintymoore

Dani AI

Generated

A quick summary and a few practical tips that extend what and already found: a software “MIDI THRU” on macOS is normally done with virtual MIDI endpoints rather than by dropping a single source file into a folder. The source files you found are examples that must be built into a runnable program; if building is not desirable, a small GUI patchbay or an already-built router will give you the same result with far less fuss.

macOS’s built-in way to create virtual MIDI ports is the IAC (Inter‑Application Communication) driver in Audio MIDI Setup — turn the driver online and add one or more buses, then point apps/devices at those buses to route MIDI between them (this is the software equivalent of a hardware THRU). Use a MIDI monitor to watch live traffic while you test so you can see exactly what’s being sent and where. (support.apple.com)

About the example code and compiling: example source files are just that — source. They compile to a binary you run; older Apple example projects target older SDKs and build settings and may require installing Xcode/Command Line Tools and adjusting the project for modern macOS (64‑bit, newer SDKs, updated signing settings). Apple’s build/command‑line guidance is the best place to start if you want to rebuild the sample yourself. If you prefer not to fight old projects, maintained open‑source patchbays exist (and can be built for current macOS), or you can use third‑party libraries/wrappers around CoreMIDI to write a tiny router. (developer.apple.com)

Quick troubleshooting checklist: install the Xcode Command Line Tools before trying to build; rescan MIDI in Audio MIDI Setup if devices don’t appear; use a MIDI monitor to verify messages; and watch out for routing loops when you combine virtual and physical ports (an IAC bus feeding back into the same physical output will echo endlessly). These steps will get a reliable internal THRU without extra hardware. (developer.apple.com)

Recommended Answers

All 4 Replies

Member Avatar for dintymoore

That wonderful learning curve...
I didn't realize that you needed to install the Developer's tools separately from the Tiger DVD.
I did that and found the files I was looking for.
I will now attempt to copy the example.

Member Avatar for dintymoore

Well, here it is...
I'm trying to get a MIDI THRU working on my OS 4.11 G4.
So I installed the Developer package and yes, in Developer/Examples/CoreAudio/MIDI/SampleTools there's "Echo.cpp".

Can someone tell me where I should put "Echo.cpp" to make it active?

Thanks


comment: it's a little bit like if the first time you learned to ride a bike they made you learn how to make the chain from scratch...

Member Avatar for John A

I don't know anything about the program itself, but I can tell you how to compile it:

1. In /Developer/Examples/CoreAudio/MIDI/SampleTools, there's a file named "SampleTools.xcodeproj". Double click on this file, and it will open in Xcode.

2. In the Xcode project window, look for "Active Build Configuration". Change it from "Development" to "Deployment".

3. Hit the "Build" button.

4. After it's finished compiling, you should find the command line tool in the subfolder build/Deployment/midiecho.

Member Avatar for dintymoore

Thanks John A, I will keep that info and try that to learn about this.
The initial problem that lead to this thread has be resolved. There's a free download at:
http://www.apple.com/downloads/macosx/audio/midipatchbay.html
It's a basic MIDI Patchbay that does include a MIDI THRU.
I can run this program and then leave it and go to eBay, play YouTube vids and such and my keyboard's MIDI signal will be routed to my sound module, which is what a MIDI THRU does.
I've been using it for several days and it seems to be glitch free, great with QMidi to play keys.
Thanks everybody for your help.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.