Jump to content

coastcj

Member
  • Posts

    28
  • Joined

  • Last visited

Recent Profile Visitors

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

coastcj's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Glad you found a workaround. One issue with your solution is that you need to use the mouse, but if you want to 'play' it again, set your Recording Preferences (Logic Pro-->Preferences-->Recording) to Merge (I have this the default for Cycle Off, and leave it Create Take for Cycle On). Now you can hear the notes you played, but work the mod wheel 'live' - sometimes this is easier to get the feel, than having to draw it in, other times you need the precision. And you don't have to play the notes and work the wheel at the same time. I hope that helps. Cheers, CJ
  2. I should also mention that it works across sessions, I only had to do it once and it always mutes the proper VCA (Which is named identically). I'm not exactly sure how it knows, but that's awesome.
  3. That worked! Thank you so much. FYI for others who may have Faderport: I chose the "Link" button on the left since that is for Studio One users only and unused in Logic (MCU)
  4. I'm wondering if anyone has an idea how I might have a specific keyboard shortcut, or maybe MIDI message, always mute/unmute the same track. The use case for me is the vocal stacks run through VCAs, and while mixing/producing it's helpful to mute this VCA. But depending on where I'm working on the session I often have to scroll quite a distance. I have been able to set shortcuts to collapse/expand the track stacks to get it somewhat closer, but it's still a slowdown I use a Presonus Faderport controller, but there is no option to 'peg' tracks to certain channels , and the Faderport VCA options do not work on Logic , or that would have been a solution Any ideas appreciated,
  5. I have an issue similar to viewtopic.php?f=1&t=154052 that started with 10.6. I've posted examples from the same session. Some regions drag properly, others do not. It does not matter whether Absolute , Relative or what my division is, it happens randomly. For example, in my "Region To Be Dragged Ultimately Fails.png" (It's track 53 in session 2nd and 4th pictures attached), note it's trying to move it 8 0 0 105 instead of expected 8 0 0 0 . I'll simply start dragging with the option key to copy (or without to move) and I'll notice right away that the indicator which tells you how far you're moving is not going to be precise. If I drag other regions, for example "Region To Be Dragged Ultimately Works.png" (track 56 in session, 1st and 5th pictures) this one will instantly tell me +1 0 0 0 , +2 0 0 0 etc... (8 0 0 0 in the pic) for how many bars I'm moving. Generally I prefer relative because I want to move an exact number of bars, but often the regions have a pickup so they don't always start on grid. Another peculiarity, even regions that usually work will sometimes "land" 1 tick short, that is the starting position will be something like 53 4 4 240, instead of 54 1 1 1 even if the region started dragging from a "x 1 1 1 " location. I've sometimes gotten around it by creating a bounce in place starting from the previous bar's downbeat, and then it seems to "clear up" and I can drag around again until the next random one fails.
  6. NOTE: I moved and updated below post to: viewtopic.php?f=1&t=155366 I have a similar issue that started with 10.6. I've posted examples from the same session. Some regions drag properly, others do not. It does not matter whether Absolute , Relative or what my division is, it happens randomly. For example, in my "Region To Be Dragged Ultimately Fails.png" (It's track 53 in session), note it's trying to move it 8 0 0 105 if you look closely at the 2nd pic. I'll simply start dragging with the option key to copy (or without to move) and I'll notice right away that the indicator which tells you how far you're moving is not going to be precise. If I drag other regions, for example "Region To Be Dragged Ultimately Works.png" (track 55 in session) this one will instantly tell me +1 0 0 0 , +2 0 0 0 etc... (8 0 0 0 in the 4th pic) for how many bars I'm moving. Generally I prefer relative because I want to move an exact number of bars, but often the regions have a pickup so they don't always start on grid. Another peculiarity, even regions that usually work will sometimes "land" 1 tick short, that is the starting position will be something like 53 4 4 240, instead of 54 1 1 1 even if the region started dragging from a "x 1 1 1 " location. I've gotten around it by creating a bounce in place starting from the previous bar's downbeat, and then it seems to "clear up" and I can drag around again until the next random one fails.
  7. I also noticed another peculiarity today, in that once I get the session open with a workaround , if I close this session and don't quit Logic, I can do almost anything, i.e. create new sessions, open other ones, etc... and then re-open an errant one successfully. However, if I quit Logic, then the session will fail on next open and I need to repeat workaround again.
  8. < Double-click the plugged in iLok in the left-hand location column to open the Details Pane. Click the "Synchronize" link and wait until the process completes. Verify that all expected licenses are now seen on your iLok, or in some cases, a license may be in your account instead of on the iLok. All expired licenses will be moved to your account. There is also some software that has been known to interfere with USB recognition. Do you have any of the following applications installed: ~Duet or Duet Display ~USB Network Gate or any other software from Eltima ~Shadow PC >> This is from iLok support. I tried above successfully but still failed to open older sessions that were crashing. I can't confirm if it fixes future sessions yet though. I replied with error log to iLok, and I will post any status updates here. It's one reason why I keep my music computer as clear as possible to avoid things like this, and to be sure I still am not claiming iLok is my issue.
  9. I'm not the OP but I qualify as someone that can tell you if this works and will try this and post results. I can tell you that if you just install the new version and reboot, it is not enough, as I did that already earlier. My related thread is here: viewtopic.php?f=1&t=154825
  10. I did just login and try a session I know crashes every time and it still crashes after iLok software update - so either they didn't fix it yet, or this isn't my issue. nonetheless, I'll keep looking. thanks again
  11. Wow, yes I do - and didn't think of that because Waves and NI are not iLok and I use them the most. Thanks for at least giving me a new place to look, I appreciate it!
  12. I've been experiencing a problem for over a year now, and I am wondering if anyone can offer guidance. Occasionally, but not always, Logic will quit when opening a session and list an offending 3rd party plugin, e.g. Native Instruments Replika, or Waves CLA, etc... I have included a partial example error report below (sorry, couldn't attach txt file to msg). Note that although it happens on many 3rd party manufacturers, I did send to N.I. anyway but they couldn't figure it out (I wouldn't expect them too, but was hoping) WORKAROUND: If I ignore the error, open a blank session, instantiate the offending plug-in, it loads fine, and then close this blank session (but DO NOT QUIT LOGIC) and REOPEN the original session that quit unexepectedly it will also open without issue. If I quit Logic, then re-open session this workaround fails. This workaround is why I put up with the problem since 10.2 or so, but now with bigger sessions and working on several sessions per week, it's become a good 7- 10 minute delay just to get my original session going. I have tried all the usual things (reinstalling the plug-ins, deleting the plist perferences, caches, etc... even reformatted hard drive) to no avail I'm on Catalina now, but this predates Catalina and goes back at least 2 OS ago. Thanks, {\rtf1\ansi\ansicpg1252\cocoartf2513 \cocoatextscaling0\cocoaplatform0{\fonttbl\f0\fswiss\fcharset0 Helvetica;} {\colortbl;\red255\green255\blue255;} {\*\expandedcolortbl;;} \margl1440\margr1440\vieww10800\viewh8400\viewkind0 \pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardirnatural\partightenfactor0 \f0\fs24 \cf0 Process: Logic Pro X [1311]\ Path: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X\ Identifier: com.apple.logic10\ Version: 10.6.1 (5415)\ Build Info: MALogic-5415000000000000~2 (10U119)\ App Item ID: 634148309\ App External ID: 839116456\ Code Type: X86-64 (Native)\ Parent Process: ??? [1]\ Responsible: Logic Pro X [1311]\ User ID: 501\ \ PlugIn Path: /Library/Audio/Plug-Ins/Components/Replika XT.component/Contents/MacOS/Replika XT\ PlugIn Identifier: Replika XT.MusicDevice.component\ PlugIn Version: 1.1.0 [R47] (1.1.0 [R47], Copyright \'a9 2020 Native Instruments GmbH)\ \ Date/Time: 2021-01-14 13:47:29.350 -0800\ OS Version: Mac OS X 10.15.7 (19H2)\ Report Version: 12\ Bridge OS Version: 4.6 (17P6610)\ Anonymous UUID: 2EB92305-0AFA-542D-FF1F-161F1A5A2DE9\ \ \ Time Awake Since Boot: 6000 seconds\ \ System Integrity Protection: enabled\ \ Crashed Thread: 0 Dispatch queue: com.apple.main-thread\ \ Exception Type: EXC_BREAKPOINT (SIGTRAP)\ Exception Codes: 0x0000000000000001, 0x0000000000000000\ Exception Note: EXC_CORPSE_NOTIFY\ \ Termination Signal: Trace/BPT trap: 5\ Termination Reason: Namespace SIGNAL, Code 0x5\ Terminating Process: exc handler [1311]\ \ Application Specific Information:\ Dublin | 6b34edbe1e2428234532a9a90f0dda622834cd344de3e01f645f6cf5be04bce1 | 6929e9fa277a970fca0074748e47266d4dfd6072 | 2020-12-07_19:05:26\ \ \ Thread 0 Crashed:: Dispatch queue: com.apple.main-thread\ 0 Replika XT.MusicDevice.component 0x0000000129744e93 void boost::movelib::op_merge_with_left_placed, std::__1::allocator > >, std::__1::basic_string, std::__1::allocator >, boost::move_detail::identity, std::__1::allocator > > >, boost::movelib::move_op, std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*>(std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*, boost::container::dtl::flat_tree_value_compare, std::__1::allocator > >, std::__1::basic_string, std::__1::allocator >, boost::move_detail::identity, std::__1::allocator > > >, boost::movelib::move_op) + 275\ 1 Replika XT.MusicDevice.component 0x000000012974289f void boost::movelib::adaptive_merge, std::__1::allocator >*, boost::container::dtl::flat_tree_value_compare, std::__1::allocator > >, std::__1::basic_string, std::__1::allocator >, boost::move_detail::identity, std::__1::allocator > > > >(std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*, boost::container::dtl::flat_tree_value_compare, std::__1::allocator > >, std::__1::basic_string, std::__1::allocator >, boost::move_detail::identity, std::__1::allocator > > >, boost::movelib::iterator_traits, std::__1::allocator >*>::value_type*, boost::movelib::iterator_traits, std::__1::allocator >*>::size_type) + 671\
  13. I would like it if the channel fader acted like a global trim for the entire track once Volume automation is written. And perhaps outline the knob in yellow to let you know that's how it's behaving. It would save from having to use the Gain plug in (or VCAs) and open automation for level automations , saving a few steps and making control surfaces more useful in the process.
  14. Hi, I'm wondering if someone can comfirm a bug for me. Since upgrading to 10.6, if I add track notes to a track inside a summing stack (while in ARRANGE view), the notes appear on the Summing stack when switching to Mixer View. (See attached) I was hoping 10.6.1 would have fixed it, but it did not - so I decided to post to see if this is a bug Thanks, CJ
×
×
  • Create New...