FatLab Music logo

Archive for the ‘Digital Performer’ Category

How to disable Ableton Live ReWire in DP7

I’ve been configuring a new audio workstation, and I found that my Reason and Sibelius ReWire audio inputs wouldn’t work in MOTU Digital Performer 7 like they do on our other workstation. I spent the first part of 4 hours trying to decipher whether the problem was with Sibelius’ config or DP’s, only to realize that I hadn’t disabled Ableton Live’s ReWire slave mode and inputs on this new workstation.

I’m not sure the problem is necessarily with Live, but perhaps with DP having to handle so many ReWire inputs — maybe DP (or ReWire) has a 128 channel limit? At least on Snow Leopard 10.6.2 with Digital Performer 7.02 and Live 8.1.1, DP couldn’t handle adding Live’s additional 64 inputs to my existing 64 Reason inputs, 2 Sibelius inputs, and 2 Waves inputs. Note: the Live inputs were not even assigned to a DP input (no rows and no chicklets). Just having Live’s inputs *available* in DP prevented both Reason and Sibelius from passing ReWire audio into DP.

I generally use Live as a standalone DAW, so I don’t need these ReWire inputs in DP. But it’s not immediately obvious how to disable them, and it took me the rest of the 4 hours trying to get DP to forget about Live’s ReWire channels. Turns out It’s stupid-simple. It boils down to setting one preference in Live’s Options.txt file and then deleting two aliases from two different Mac OS X Library folders.

NOTE: Doing the steps below prevents Live from entering ReWire slave mode for all apps. It also completely removes the inputs from Digital Performer’s Bundles > Instruments window. I don’t know what else it might do — proceed at your own risk. :)

To disable Ableton Live’s ReWire slave mode and remove the inputs in MOTU Digital Performer:

  1. Quit both DP and Live if either are open.
  2. Edit (or create) your current “Options.txt” file for Live, according to Ableton’s FAQ page. Add the (undocumented) flag -ReWireSlaveOff. Setting this flag tells Live not to undo what you are going to do in step 4.
  3. Save and close Options.txt.
  4. Navigate to /Library/Application Support/ (that is, your top-level Library folder) and trash the alias named “Ableton Live Engine.bundle”. Navigate to ~/Library/Application Support/ (this one is the Library in your Home folder) and do the same thing to that “Ableton Live Engine.bundle” alias.
  5. Empty the trash for good measure.
  6. Relaunch DP and verify that the Ableton Live channels are gone from the Bundles > Instruments tab.

DP’s VI Instrument Bundles have been a little fickle since v6, so this all may be the result of some bug in DP, or I may be hitting some limitation of ReWire 1.7, or it may be something in Live’s implementation of ReWire. It is curious that every other audio app I have besides Live places a .bundle file in /Library/Application Support/Propellerhead Software/ReWire/ to register their outputs.

Why does Live just stick a lonely alias at the top-level of Application Support? Why doesn’t the file say “ReWire” in the filename like others do? Maybe there is more to that “Ableton Live Engine.bundle” alias than just publishing ReWire outputs. But Live reinstates the alias only when the -ReWireSlaveOff flag is gone from Options.txt. So as long as Live doesn’t repair the alias when -ReWireSlaveOff *is* present, I’d say we’re safe.

What originally started as a quest to fix broken ReWire audio between Sibelius and DP became instead about how DP and Live were working together (or not working together).

Deleting Live’s ReWire inputs from Digital Performer restored ReWire audio from Sibelius and Reason both. I hope that saves you some time.

DP6 Bugs Fixed in Digital Performer 7

MOTU released DP7 recently, and we’ve just installed our upgrade and 7.01 patch. I was very pleased to find that DP7 fixes many bugs introduced in DP6.

  • All Open/Save dialog boxes now remember their last window size, position, & column widths.
  • All sidebar panes in the Consolidated Window now have consistent click-through behaviors. In DP6, if for example the Sequence Editor was popped out and in the foreground over the Consolidated Window, clicks to the body of only certain background Consolidated Window panes would bring that window to the foreground. The problem tabs that are now fixed are Snap Information, Cursor Information, Event Information, Selection Information, and Track Selector. (NOTE: The exception is Track Selector, where clicking *items* leaves its focus in the background as you would hope, while a click to the tab itself or the pane’s border now brings the window to the foreground.)
  • Double-clicking to enter and leave the “Conductor” track in Graphic Editor is fixed. In DP6, if you double-clicked the “Conductor” track in the Tracks window, it would not switch the Graphic Editor (i.e. “MIDI” tab) to the “Conductor” track, even tho Preferences > Edit Windows > Default Edit Windows > Conductor Track was set to “Graphic Editor”. The only way was to select “Conductor” from the Graphic Editor’s mini-menu track list. Conversely, if Conductor was the active Graphic Editor track, it would not respond to a MIDI track double-click either. The only way to exit the Conductor track graphic view was also through a mini-menu selection.
  • More compatible with SampleTank (v2.5.3). DP6 was able to include SampleTank in Bounce to Disk operations without having to freeze or print the track audio, but the instrument’s behavior was always erratic if the VI window was closed. Possibly related to the window having to remain open, Bounce operations would sometimes take up to 5 minutes to begin. This delay also appears to be fixed in DP7.
  • Fully compatible with Omnisphere (v1.0.4g). Omnisphere is now also to be included in Bounce operations without freezing or printing the audio first. (Yay!) Previously, Bounce operations would kick Omnisphere into “Stack” mode, screwing up all your patch and output settings, and requiring you to close and reopen the file to restore.

There are possibly many more things fixed, but these were specific DP6 gripes checked off my list.

Buy Snowferno. $1.99 on the App Store
CPU usage seems much improved, and I’m a huge fan of the UI refinements (namely the more slender automation line weight) and the inline channelstrips. After a bumpy DP6 ride, I feel in good hands again.

I’m not done tho. Next post:
Bugs from DP6 not yet fixed in DP 7.01…


Performance Optimization WordPress Plugins by W3 EDGE