Are You Having Midi-related Problems In Dp4, get rid of SBFH - midiexcl is culprit |
Fri 1 Aug 2003, 00:49
Post
#1
|
|
Moderator Group: Team Posts: 370 Joined: 19-Mar 03 From: Umeå - SE Member No.: 14,645 |
I will post this - here at this forum as well. Have already posted it at http://www.unicornation.com/.
Hope this can help someone else: ----------------------------------------------------------------------------------------- As of late I have been having progressively more/worse midi-related problems with DP4. ( I readily confess to NOT being very versed in things midi ) With much appreciated help of Nathan (tech-support) at Motu, we have formulated a long & rather boring process for eliminating these particular problems. In short when I'm working with audio only, everything is smooth sailing, steady as a rock. As soon as I'm doing any midi-recording and/or midi-editing, the infamous "SBFH" puts in an encore. Either forcing a "Force quit" from the Apple-menu, or killing off the MIDIServer process - in the terminal window. Below is the entire 22-step proces for coming to grips with this: -------------- 1:) Remove all FW USB adio & midi-interfaces from your computer. 2:) Reboot your computer 3:) Uninstall all fw and usb-drivers 4:) Open a new project in DP4/DP4.0.1 5:) Put DP in MIDI only mode. "Setup"-menu --> Audio System --> MIDI Only 6:) Go to: "Setup"-menu --> Interapplication MIDI... 7:) In the "Interapplication MIDI" - dialog -- check the "Software Synthesizer" 9:) Create a number of midi tracks - 6 to 8 tracks will do. 10:) Using the pencil tool only, add midi notes into the tracks 11:) Loop the sequence let it play for an hour or two or 24, whatever. 12:) If this plays along fine start adding things back in. 13:) Reconnect your usb/fw - midi-interface and install the proper latest driver. 14:) Reboot your computer. 15:) Go To "Audio/MIDI Prefs" - utility. Setup your minimum studio. Connect "ONE" cable from your interface to the midi-in on your synth-module. 16:) Do the same in the real world, i.e. between your interface and & your synth. Only one cable from Interface midi-out to your synth midi-in, will prevent midi log jams. 17:) If this plays back without a hitch, through your synthesizer module. Connect the next cable in both the "Audio/MIDI prefs" - utility and between your interface and synth. From interface midi-in - to synth midi-out 18:) If this plays back OK, add your other synth:s and keyboard controller back in one cable at a time. Like in paragraphs 15,16 & 17. 20:) If this plays back OK, start recording over or add more midi-tracks using your keyboard-controller as input. 21:) If this plays back OK with the new tracks added your are probaly green-lighted and set to go. If NOT, open the eventlists (select the tracks & press Shift+E keys at the same time) for the newly recorded tracks. Look or search for recorded midi-exclusive messages if any. 22:) Select and remove all the system exclusive messages. At least as many as possible. Do the same for any midi-track you see midi-exclusives in. ------------------------------------------------------------------------- ( I suspect the midi-exclusives to be the culprit - you can try to take the short route and only do paragraph 22 ) After doing this my midi-problems seem to have disappeared. I hope this can be of help to someone. Cheers: Dixiechicken -------------------- ================== Oh my God it' full of stars? ================== posted July 31, 2003 06:12 AM Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â PS- forgot to mention. When you have successfully come to paragraph 22, without falling asleep - you can add your favourite audio interface back in and install the proper latest driver for that as well. Cheers: Dixiechicken -------------------- ==================
Oh my god it's full of stars… --------------------------------------------------- Mac-G5-2x.2.0, OS-X 10.5.1, 250/200Gb HD - 7.0Gb ram DP-5.13, Motu 828 MK-II, MTP AV Usb, ltst drvs, Kurzweil-2000, EPS-16, Proteus-2000, Yamaha 01V Emes Kobalt monitors ================================ |
|
|
Posts in this topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members: