Jump to content

fader8

Member
  • Posts

    10,467
  • Joined

  • Last visited

3 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

fader8's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. Try enabling chase on cycle jump in the preferences. This setting actually does more than just make it chase on cycle jump. Might solve your issue.....
  2. Assuming the Touch OSC folks gave you a MIDI driver that talks to Touch OSC and CoreMIDI, then Its likely that having the Logic Template for Touch OSC installed as a control surface is blocking that port. Try opening Control Surface Setup and deleting the icon for that control surface. Then try your new template. If the communication is just in the control surface bundle for the supported control surface, then yes, you'll need Osculator. Sorry I can't be more specific. I use Lemur for custom ipad control stuff, which I highly recommend.
  3. You should let us know something about your setup, too. Please add your Logic version and system info to your signature: Forum Rules - please READ THIS before posting (#5) If you have a low end controller keyboard, A knob or fader could be dodgy and spitting out random controller values.
  4. Wasn't this fixed in Logic 9.1 ? No. I'll check which version is running on the MacBooks here, but they are all pretty recent. But they still truncate and add a numerical code to the end of the name. PITA.
  5. If you want to do this in live performance, don't use controller assignments, they are too volatile. instead, open Logics environment window and hard wire the port from your controller to the channel strips you want to control parameters for. Plugin parameters required "fader" messages, so you will need to do some transforms. To discover the required message, cable a monitor object to the channel strips output. Move the parameter and you will see the appropriate fader message.
  6. You may be able to use Touch Tracks for this. If it's an audio file, use the exs24.
  7. fader8

    I/O plugin

    Solo-safe the output channel strip in your mixer that you're using with that I/O plug.
  8. First thing, open the audio bin and delete all references to unused files. Files that are not used in the arrange. For the remaining files, rename any that are over 24 characters. This is really important. Keep those file names short or your partner is in for a world of headache. Do a save a copy as, and include assets. Close your project. Open the copy and make sure it loads and works. Check all the bin path references for your audio files to be sure none still reference your original folder. If all is ok, zip that new project folder and upload it. Good luck, and be sure to heed my advice on the 24 characters thing!
  9. Or.... Cable them up in OSX Audio MIDI Setup and they will show up in Logics library pane when you create an external MIDI track. You will need to create a device for each and set the channels you'll be using on them too. Having 3 midi ports available on your interface will make this easy, but you can set up "thru" connections there too.
  10. are you absolutely sure about that, Jay? Can you tell me today, for sure, that the hardware and drivers for a pro audio interface, UAD thing, hard drives, and maybe something else you don't know about yet, are all going to just get along perfectly? Every time a new "wonder-bus" comes along, everybody says its the greatest thing. Until you actually start hanging stuff from different manufacturers on it. I've been hearing it since the Nubus and adb days. Someday I'll decide to become encumbered by progress again and I'll buy a new Mac Pro. It will inevitably have an expansion card giving me 2 or more t-bolt busses. Just like I have cards and expansion chassis's now for extra fw, USB, sata, raid, etc. not because the bandwidth isn't there, but because stuff just can't get along with other stuff!
  11. But what does that have to do with the "Create Arrange Tracks for Selected Channel Strips" command?
  12. OK, delete the new cs file that Logic has created, it creates this automatically when the file is missing. You still have your original anyway. Turn off the MCU. Start up Logic. It will create a brand new cs pref file. Open the Control Surface Setup. Don't do anything there. Turn on the MCU. Wait. Does the icon appear? The MCU uses Mackie Control mode, not Logic Control mode. The protocols are very similar, though.
  13. Try dragging the Logic Control Surface preference file to your desktop and restarting Logic: user/Library/Preferences/com.apple.logic.pro.cs Then reinstall the mcu in Logic. Make sure that works before plugging in your m-audio kb. Also be sure no m-audio drivers are loaded.
  14. Ok. Well that may not have been the solution anyway. It may be a matter of setting the scaling parameter just right. Or.... Try setting the encoder to just spit out a value 1 when turning to the right, and a value 0 when turning to the left. Set min and max for 0 and 1 in controller assignments. Not at my workstation at the moment or I would try this.
  15. This may not be possible using a 7 bit MIDI encoder. Can you configure your encoder for 14 bit and try it? The Logic/Mackie Control does this but I believe it snaps to bar positions only, I'll have to check that later.
×
×
  • Create New...