Jump to content

remark391

Member
  • Posts

    10
  • Joined

  • Last visited

remark391's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Brilliant, this is working flawlessly now. Thank you so much for your help!
  2. Oh, that's the easy part of the problem. I just have the two different articulations on different tracks and set the track with the overlay to a negative delay. Forgive my ignorance, I'm still new to logic midi scripting... How do you go about assigning a midi message to that thru button?
  3. This is super informative, thank you! My specific problem is this - I'm trying to add an "overlay" staccato articulation to the new Symphonic Motions from spitfire. I want to overlay with fluid shorts from Performance samples, but they have a very long "head" to the sample (very realistic sounding because you can hear the whole natural attack, but not the most "playable"). So when I play the two articulations at once, they are hitting at very different times and makes it very difficult to perform. My hope was to mute the overlay while performing, but still have it heard on playback. I see now from your logic midi signal flow chart that scripter probably is not the right solution for this problem. Unless...is there a way to assign a controller or key command to that thru button?
  4. I'm trying to figure out how to mute incoming midi via a software instrument, but still have that midi recorded to the track. I.e. nothing is heard when you initially play via your keyboard, but the notes ARE heard on playback. I realize the brute force way to do this is to simply mute/unmute the track, but I'm trying to write a midi script which would do it automatically. Any thoughts?
  5. I'm looking to create a script that will redirect incoming CC messages (like the midi modifier plug can), but only for a specific channel. i.e. All incoming CC1 data gets remapped to CC11, but only on channel 1. All other midi data gets passed through. I'm still pretty new at coding in midi scripter, and can't quite figure it out. Any help would be greatly appreciated!
  6. Strange, I've been dealing with this frustrating issue for a while now. It seems like there might be something to this work-around of selecting a track that doesn't have any fades on it before pressing play. Sometimes restarting logic helps, but sometimes it doesn't. At least for me, deleting the fade files in the audio menu very rarely works. Thanks for the tip speakerfood!
  7. Now that I've done a bit more testing, it looks like the culprit is having too many Guitar Rig 4 fx plugins loaded. The breaking point seems to be around 8 or so plugins. Any more than that, and logic hits the mat. Anybody experience working with a lot of guitar rig 4's loaded with no problems??
  8. Thanks for all your replies, I appreciate it! Unfortunately for me, the new 9.1.4 logic update did not fix things. I'm getting closer to the problem, and now it seems like logic crashes when you put a Guitar Rig FX plugin on top of a Kontakt 4 instrument track. Either that, or the other possibility is that lots of guitar rig plugs loaded makes things crash. It's hard to tell at this point. I'm fairly sure that the issue is rooted in Guitar Rig though. Hopefully, I can get Native Instruments on the phone next week and get to the bottom of this. I'll post any discoveries. Thanks again!
  9. So... I've done a bit more sleuthing, and I removed some AU components from the library folder to see how logic reacts. It turns out that loading Guitar 4 IN COMBINATION with Kontakt 4 makes the session crash. Anybody every run into this problem? BTW, I'm using a bunch of instances of Guitar Rig as an effects plugin on my software instrument tracks, not just standard audio tracks.
  10. As usual, I'm under a tight deadline, and the project I'm working on began to crash as soon as I loaded LA Scoring Strings in Kontakt 4.2.3. I was working in 64 bit mode with instances of PLAY, Kontakt 4, Trillian, and Guitar Rig 4. I have several version of the project saved. When I open the latest version with LASS loaded the project will not open and logic crashes. When I open the pre-LASS-loaded version, if a menu is brought up (save as, preferences, etc...) it'll crash logic. I read that sometimes certain 3rd party plugins will cause problems with the Logic GUI. Is that whats going on? I appreciate any advice! Crash report with selected thread that caused the crash: Process: Logic Pro [265] Path: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro Identifier: com.apple.logic.pro Version: 9.1.3 (1697.87) Build Info: Logic-16978700~1 Code Type: X86-64 (Native) Parent Process: launchd [165] Date/Time: 2011-05-19 10:00:43.604 -0700 OS Version: Mac OS X 10.6.7 (10J869) Report Version: 6 Interval Since Last Report: 45599 sec Crashes Since Last Report: 22 Per-App Interval Since Last Report: 17218 sec Per-App Crashes Since Last Report: 17 Anonymous UUID: 1A995987-5BA6-4684-985F-A6FDDD5BC6F4 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000000011bc00008 Crashed Thread: 508 Dispatch queue: TFSVolumeInfo::GetSyncGCDQueue Thread 508 Crashed: Dispatch queue: TFSVolumeInfo::GetSyncGCDQueue 0 libSystem.B.dylib 0x00007fff808a3d8d _dispatch_queue_drain + 150 1 libSystem.B.dylib 0x00007fff808a3c54 _dispatch_queue_invoke + 57 2 libSystem.B.dylib 0x00007fff808a37fe _dispatch_worker_thread2 + 252 3 libSystem.B.dylib 0x00007fff808a3128 _pthread_wqthread + 353 4 libSystem.B.dylib 0x00007fff808a2fc5 start_wqthread + 13 Thread 508 crashed with X86 Thread State (64-bit): rax: 0x000000011bc00000 rbx: 0x000000011fa00b30 rcx: 0x00007fff700cf630 rdx: 0x00000000057ddca0 rdi: 0x000000010360aa00 rsi: 0x0000000103700000 rbp: 0x0000000205ff3e90 rsp: 0x0000000205ff3e40 r8: 0x0000000000000001 r9: 0x00000001037eb970 r10: 0x000000011fa0c600 r11: 0x0000000000000005 r12: 0x000000011bc00000 r13: 0x000000011fa00b30 r14: 0x0000000000000000 r15: 0x00007fff700cdbf8 rip: 0x00007fff808a3d8d rfl: 0x0000000000010206 cr2: 0x000000011bc00008
×
×
  • Create New...