--- In logic-users@yahoogroups.com, Matt McKenzie-Smith <matt@m...> wrote: > I have a spare BCF2000 lying around since getting the MackieCU and I > wish I could use it for Totalmix, but Logic keeps auto detecting it > at start up and grabbing it for chans 9-16. I would be happy if it > just left it alone. Logic is just far far too agressive about auto-detecting control surfaces. It scans every port in the system. This may have made sense when the LC was the only one it used, and only worked with Logic, but now it's just trying to be too clever, and this supposedly user-friendly setup feature becomes very user-unfriendly indeed. Other apps let the user _specify_ which controllers/ports should be used, and don't do any agressive auto-scanning at startup, which I think is a far more sensible approach. Replace the "Logic Control" control midi device plugin in the Logic 7.1 application package with the one from Logic 7.0.1, boot the spare BCF into MC-emulation. Logic won't see it. Boot the real MC into LC-mode. Logic will find that. Unfortunately, you will lose the LC improvements in 7.1 by doing this (mostly dialog-box related). Alternately, you could try using MidiPipe to "hide" the BCF hardware ports from Logic only, and always startup in this order: LC Xview/TotalMix, MidiPipe, Logic. But this is all just silly workarounds for a problem that shouldn't exist. Is Michael Haydn listening? Can we have the LC module only scan for LC/XTs, not for MC/XTs (so we can add any MCs manually)? Can we have the microKONTROL module as a manual-add only? Can we have a global preference that tells Logic not to auto-scan all unassigned ports for new surfaces? Please? John Pitcairn -------------------------------------------------------------------------- LC Xmu Logic Control emulation, LC Xview software LC/MC display, Logic environments & stuff: http://www.opuslocus.com --------------------------------------------------------------------------