![]() I am writing this here for the hope that if I put this out there- someone else, with a similar goal of getting the 003 o be a control surface for a DAW other than Logic may both be assisted, and may expand upon what I'm reporting, and help me out.1. and as I'm brand new to Logic, that is some time off. But, first I would have to test Logic for audio mixing, etc. The connection with 003 and Pro Tools is so great, I am reluctant to let go of that until I know I can get equivalent with Logic and some other control surface. My studio desk and space is too small to allow for a 003 and a dedicated Logic Control Surface. The only value in this, for me, is that it would allow me to use 003 for Logic and for Pro Tools.Īnd, not have to mess with also buying a new interface, if I get rid of 003. I am following through on reporting my results on this because I feel like it is possible to get this to work, and I have not figured out how. My guess is that the Logic Controller Assignment custom settings above are not needed. 16 Control assignments created with the following parameters But in case, I will indicate what it is:įirst, deleted any existing controller settings and setups.ģ. Regarding my "custom Controller Assignments" mapping in Logic. 16 discrete tracks is more useful than the 6 I got yesterday. With the 003's stock, MIDI Map, "Standard MIDI" Preset, that I am using here:Ġ03 Faders 1-8 transmit on MIDI Channels 1-8Ġ03 Faders 1-8 transmit on MIDI Channels 9-16 Then, when 003 Bank button pressed, the next 8 Logic Tracks are controlled by 003 Faders 1-8 in "Bank" page. In essence, Logic Track 9 controlled by 003 Fader 1. So I'll mention it later.ġ6 003 Faders to control 16 Logic Tracks, non-motorized.Ĩ audio tracks in Logic (for "free") before the first 003-controlled track. Custom Controller Assignment setup in Logic. Here's something that's even more useful. Same happened with different combinations of hiding. Same happens when I make Tracks 3-6 visible ![]() Then, unhid Track 1.Īnd then in Mixer View under Main Window, I displayed Stereo Out and Master by selecting the Mixer "Output" and "Master/VCA" tabs.Īnd, when I unhide Track 2, adding that to the visible tracks, but that did not change the results.įaders 7 & 8 locked to their Stereo Out & Master assignments, whether they are visible or not. I concealed Stereo Output and Master, and Inspector, and created a new Screenset with only Mixer, and only Tracks 1-7 visible. Hiding Logic Tracks 2&3, led to now expected results:Īll this time (and in preceding post), Mixer View showed Stereo Output and Master. Hiding Logic Track 1 lead to same results as expected. ![]() Pressing Bank on 003 to access 003's Standard MIDI Map Channel 9-16 assignment didn't lead to any correlations. Otherwise, I am better off with a different control surface. I suppose this is only useful if I absolutely need to keep 003 on/in my limited desk/studio space. I believe a smaller, $150 control surface would do this better. This is already less useful than the 003 was when controlling Pro Tools. Difference from 003-Pro Tools, is Fader needs to catch Track level before controlling it.Īnd moreso, 003 does not get info from Logic as to Fader position. Mutes for Tracks 3-6 don't correlate to Logic Tracks.Įven after restarting 003 and computer same works. Same thing continued successfully during each successive addition of a Logic Track up to Track 6. (I believe this can be addressed under those hood, either hood.) This ends up resulting in a scenario where sometimes, 003 Mute LED doesn't correspond to Track Mute status. It works, but requires two clicks to communicate to Logic. With this approach, I believe I should be able to easily get 16 channels of control, with little configuration. Which means I have no Controllers set up in Logic, I went to Logic Pro/Control Surfaces/Set Up: In this "003-Only Approach", I am not mapping anything from within Logic Pro. Digidesign calls this preset "Standard MIDI" and is intended for my goal of controlling a 3rd party audio application. Using 003 in MIDI Mode, set on MIDI Map B, preset 1. Therefore limited functionality relative to what I had with 003>Pro Tools. This approach: Using 003's Standard MIDI Preset, and not mapping within Logic. ![]() First approach I am trying, I will call "003-Only Approach".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |