Jump to content

fletchtown

Member
  • Posts

    19
  • Joined

  • Last visited

fletchtown's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I'm running Logic Pro 10.3.2 on OSX 10.12.6. I need to lock my video to SMPTE, write a cue starting on bar 1, then export a MIDI file to import in to Pro Tools that will provide SMPTE, meter and measure information that correspond with my Logic session. The MIDI import into Pro Tools isn't getting the proper SMPTE information so the numbers in Pro Tools are off. I hope someone has a suggestion on how to fix this. Here is my process: 1. Create my Logic session at 48 kHz, 23.976 frame rate 2. Import video and with audio from movie as audio file in session. 3. Open session movie preferences and set movie position to the SMPTE TC of the first frame of video. 4. Open my tempo window and change the SMPTE position of bar 1 to match the frame I want to start my cue on. 5. Create a marker with the cue number set and locked to bar 1. 5. Drag the Logic start marker back so I have at least 2 bars count in going into bar 1. 6. Everything is synced to picture in Logic so I write my cue, at which point I am ready to export my MIDI file to import in to Pro Tools for the record session. To export my MIDI file: 1. I make sure my global tracks are displayed in my arrange window. 2. Select all. 3. Export Selection as MIDI file. Should be all good, right? Pro Tools process: 1. The Pro Tools session has the same video and the TC of the session matches the video. 2. Import MIDI file I created from Logic. 3. Import tempo map from MIDI file. The result: Tempo and marker are correct and marker is at bar 1 but the TC doesn't match up. I don't think this is a Pro Tools problem because MIDI files from other DAWs aren't having this issue and I can get around it if I don't change the bar 1 SMPTE position in Logic. The problem with that is that I can't make my cue start on bar 1. Is there a way to fix this on the Logic end? Am I exporting incorrectly?
  2. Hi, Logic has begun taking a very long time to save when I hit command-s on larger sessions. I am using VEPro but that doesn't appear to be a factor because it happens on the same sessions when I load them without VEPro in the equation. VEPro instances are decoupled. It just started happening and wasn't doing it the other day on a session that I am experiencing the issue with. The RAM load for the session is 2.88 GB, so not very big. The slow save problem doesn't happen when I create a new session with only one instrument loaded. Then it saves as normal. I have tried reinitializing preferences and rebooting. Any ideas? Here are my specs: Logic Pro X 10.3.2 OSX 10.12.6 Mac Pro 2 x 3.33 GHz 6-Core Intel Xeon 64 GB of RAM Thank, Fletch
  3. Ok thanks. I see now it wasn't recording. In my preferences, write automation to plugin was unchecked. Thanks for you help.
  4. MIDI faders on my MIDI controller that are sending CC messages to Logic. I set up smart controls to learn specific MIDI ccs. When I go to record at track, notes are recorded but my MIDI ccs assigned to smart controls are not recorded. My hope was to record the MIDI fader movements from my MIDI controller to control the smart controls. Is it only possible to record smart controls in touch or latch mode?
  5. Hi, I'm using Logic 10.3.1 and have smart controls mapped to MIDI faders. The smart controls work fine when I adjust the MIDI faders while playing. However, when I record the smart control movements are not getting recorded from my moves on the MIDI faders. I can record smart control movements by moving the mouse when in touch mode but not when moving the MIDI faders. Any ideas? Thanks, Fletch
  6. Same knob position within smart controller window and same MIDI controller.
  7. Hi, I have an old MIDI controller (Kurzweil PC88, non USB) and I want to assign some of its MIDI faders to control smart control parameters in Logic. I have no problem using the External Assignment learn button to recognize the incoming fader message from the PC88. The problem is that when I create a new External Assignment on another track, then switch back to a track that I have previously created an external assignment on it seems to have forgotten the assignment. I assume this is not normal behavior but I can't seem to fix it. Any ideas? Thanks, Fletch OSX 10.10.5, Logic Pro X 10.2.4
  8. Hi, I want to have an audio track in my session with input monitoring on regardless of what track is selected. Input monitoring works fine, however, when I select an instrument track or another audio track in the arrange or mixer window, the input monitoring for my previous audio track turns off. The input monitoring button stays on but the audio signal shuts off. I seem to remember that I could have input monitoring on multiple audio tracks in the past and the input monitoring would stay on regardless of what was selected but it has been a while since I've done that. Am I missing something? Thanks, Fletch ------------ 2 x 3.33 GHz 6-Core Intel Xeon, 64 gb of RAM, Logic Pro X 10.2.1, OSX 10.10.5, MOTU 2408MK3 wi
  9. I discovered what the problem was. I had view>one track selected in the piano roll. Apparently those functions won't work unless view>selected regions is checked.
  10. The files I am bringing in from Logic 9 don't have any MIDI regions in them. I am simply opening up a template and working from those. On those files, I am unable to "force legato" or "remove overlaps" after I have recorded MIDI. Copying them into a new MIDI region does not fix the problem. If I create a Logic Pro X session from scratch, "force legato" or "remove overlaps" works fine. If I then import project settings from a file originally created in Logic 9, "force legato" or "remove overlaps" ceases to work. It works again if I revert back to the version I saved prior to importing the project settings. It's clearly a bug, at least on my system. Has anyone else experienced this or would be willing to confirm the behavior by opening a Logic 9 session in X and attempting to remove overlaps?
  11. Hi, I have recently upgraded to Logic Pro X and have a number of files and templates that I originally created in Logic 9. I have discovered that the "force legato" and "remove overlaps with selected" functions don't work with files that were originally created in 9. I have confirmed that they do work on a freshly created Pro X file, but the functions cease to work if I import screensets from a 9 project. There may be other functions that don't work but I'm aware of these as use them a lot. Has anyone else experienced this and, if so, is there a way to fix this? I would prefer not to have to recreate templates. Best, Fletcher --------------- Logic Pro X 10.0.6, Mac 2 x 2.8 Ghz Quad-Core Intel Xeon, 24 GB of RAM, OSX 10.9.1, MOTU 2408 mk3.
  12. I think I've found a solution. I reinstalled Logic 9 from the CD (minimal installation). Then I opened the problematic file in Logic 9.02 (I installed that update). It finds the exs samples fine. It seems that when I reopen the same file in Logic 9.1.3 after that it can find the exs samples. I haven't tested this thoroughly but so it far it seems to work. I will be keeping a copy of 9.02 on my system for this reason.
  13. Has anyone found a fix for this? I have the same problem with older sessions ever since upgrading to 9.1.3. Tried reindexing spotlight, relinking with redmatica to no avail.
×
×
  • Create New...