• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

Powerbook Duo 230 MIDI issues

jgardner

Member
Hello,
I am using a Powerbook Duo 230 for MIDI sequencing. This has worked for quite a while but suddenly no MIDI is coming in or going out, not matter what I try. Appletalk is turned off. I tried resetting PRAM. I've tested the MIDI hardware on my SE/30 and all works fine so it's definitely related to the Powerbook. I've booted from a new disk image, and installed system 7.5.3 and updated to 7.5.5, after which I installed my MIDI sequencer application (M), to no avail. Everything points to a hardware issue, but I've had it working again in some moment during the process on a new install of the OS, after which it stopped again. Since then it has not worked anymore. When running Snooper and testing the modem port, the connected keyboard (Yamaha CBX-K1 XG, with built-in serial MIDI interface for macs) does respond when I run the test. The keyboard shows signals coming in, and it even switches to another program for some reason. This makes me think it's not a hardware issue but I'm pretty lost with this. I've tried different versions of the apple MIDI manager, different MIDI programs, but nothing seems to work. Could it be stuck on some kind of setting configuring the serial port? Is there a clever way I can diagnose these MIDI communication processes to see where it goes wrong? Thanks a lot!
 

Phipli

Well-known member
Hello,
I am using a Powerbook Duo 230 for MIDI sequencing. This has worked for quite a while but suddenly no MIDI is coming in or going out, not matter what I try. Appletalk is turned off. I tried resetting PRAM. I've tested the MIDI hardware on my SE/30 and all works fine so it's definitely related to the Powerbook. I've booted from a new disk image, and installed system 7.5.3 and updated to 7.5.5, after which I installed my MIDI sequencer application (M), to no avail. Everything points to a hardware issue, but I've had it working again in some moment during the process on a new install of the OS, after which it stopped again. Since then it has not worked anymore. When running Snooper and testing the modem port, the connected keyboard (Yamaha CBX-K1 XG, with built-in serial MIDI interface for macs) does respond when I run the test. The keyboard shows signals coming in, and it even switches to another program for some reason. This makes me think it's not a hardware issue but I'm pretty lost with this. I've tried different versions of the apple MIDI manager, different MIDI programs, but nothing seems to work. Could it be stuck on some kind of setting configuring the serial port? Is there a clever way I can diagnose these MIDI communication processes to see where it goes wrong? Thanks a lot!
Where is midi manager installed? In the System Folder, or in the Extensions folder?
 

jgardner

Member
I've tried it in both locations, as I read MIDI manager 2.0.2 needs to be in the system folder? Sadly without success
 

jgardner

Member
Are you able to boot from another disk with a fresh OS install? Try from there?
Yep, tried this as well. I'm using a ZuluSCSI, so I created a new disk image for the Powerbook Duo 230 with Disk jockey and installed 7.5.3 then updated to 7.5.5 using basilisk II. Could it be related to the system 7.5.3 version I'm using? Was there a specific version of the OS for Powerbook Duo's?
 

Phipli

Well-known member
Yep, tried this as well. I'm using a ZuluSCSI, so I created a new disk image for the Powerbook Duo 230 with Disk jockey and installed 7.5.3 then updated to 7.5.5 using basilisk II. Could it be related to the system 7.5.3 version I'm using? Was there a specific version of the OS for Powerbook Duo's?
7.5.3 is fine for a Duo 230. If it boots, you're good.

Check the cable for bent pins?
 

jgardner

Member
Ah that's good to know. No bent pins, and the cable works fine with the keyboard/midi interface on my SE/30...
 

jgardner

Member
OK some progress! I've installed OMS and while this did not work with the two MIDI interfaces I was using (MOTU Fastlane serial, Yamaha CBX K1-XG), it DID work with my Emagic AMT8! While OMS did not recognize it as the AMT8, it is working totally normal, as if it does. So I guess this rules out a hardware issue and indicates a problem with Apple MIDI Manager? I've tried several versions of the MIDI manager, always just copying the extensions into the extensions folder and rebooting without any success, even on a completely new OS. Still very mysterious to me! But at least I have a workable situation now!
 

Phipli

Well-known member
I've tried several versions of the MIDI manager, always just copying the extensions into the extensions folder
Apple MIDI Manager is old so only ever use the newest version and it must  go in the System Folder, not the Extensions folder.
 

jgardner

Member
Apple MIDI Manager is old so only ever use the newest version and it must  go in the System Folder, not the Extensions folder.
It must be that Opcode (and MOTU? I have not tried Freemidi yet!) had a better understanding of how to implement this reliably. The version of the Apple MIDI manager I've used was mainly 2.0.2 and while in the system folder it still didn't solve my issue at least. Unless there is a more recent version than 2.0.2 I could try?
 

Phipli

Well-known member
It must be that Opcode (and MOTU? I have not tried Freemidi yet!) had a better understanding of how to implement this reliably. The version of the Apple MIDI manager I've used was mainly 2.0.2 and while in the system folder it still didn't solve my issue at least. Unless there is a more recent version than 2.0.2 I could try?
I think 2.0.2 is the newest. It is a very old bit of software that predates System 7 and your Duo.

Does this help? I've not used it :

 

Phipli

Well-known member
So just checking things.

The "MIDI Manager" software has several parts.

MIDI Manager - this can go in the System Folder or Extensions folder.
Apple MIDI Driver - this must go in the System Folder
PatchBay - this is available as a DA and an Application. I just use the Application and put it in my Apple Menu Items folder.

Once installed and restarted, with appletalk turned off, no printer etc etc, you need to then use PatchBay to set up your MIDI. Launch the music software, then run PatchBay and plumb it in.
 

jgardner

Member
So just checking things.

The "MIDI Manager" software has several parts.

MIDI Manager - this can go in the System Folder or Extensions folder.
Apple MIDI Driver - this must go in the System Folder
PatchBay - this is available as a DA and an Application. I just use the Application and put it in my Apple Menu Items folder.

Once installed and restarted, with appletalk turned off, no printer etc etc, you need to then use PatchBay to set up your MIDI. Launch the music software, then run PatchBay and plumb it in.
Yep that's how I did it too. Let me try this entire process once more on a clean OS install, to make 100% sure I didn't miss anything or do anything stupid. And then I'll try MIDI mangler if the issue persists to see what happens.
 

jgardner

Member
So just checking things.

The "MIDI Manager" software has several parts.

MIDI Manager - this can go in the System Folder or Extensions folder.
Apple MIDI Driver - this must go in the System Folder
PatchBay - this is available as a DA and an Application. I just use the Application and put it in my Apple Menu Items folder.

Once installed and restarted, with appletalk turned off, no printer etc etc, you need to then use PatchBay to set up your MIDI. Launch the music software, then run PatchBay and plumb it in.
OK after testing again, on a new hard drive, newly installed OS 7.5.5 and closely following the stese steps for MIDI manager and Apple MIDI Driver it still didn't work sadly. Everything looks normal in the MIDI Patchbay, with the M, the sequencer app showing up, and when connected still no MIDI.. MIDI Mangler didn't fix this either through its modem port reset button, though it is kinda useful to see if the serial port is occupied by something or not.

After installing OMS 2.3.8 and Freemidi 1.45, I'm still in the same (workeable) situation where my AMT8 is the only detected MIDI interface, and while it seems to work well, it is detected as a Midi Time Piece for some reason? I think I should just stick with OMS and/or Freemidi for now, and maybe look for another small sized MIDI interface that is supported by Opcode or MOTU. I was expecting the MOTU Fastlane to at least be detected after installing Freemidi but this only works for other MIDI interfaces by MOTU appearantly...
 
Top