Jump to content

gpax

Member
  • Posts

    41
  • Joined

  • Last visited

Recent Profile Visitors

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

gpax's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • One Year In Rare
  • Week One Done
  • One Month Later Rare

Recent Badges

0

Reputation

  1. Hi macmicke, It still happens to me all the time, several times a day. At some point during that past 10 months I’ve had three different audio interfaces I was trying out, to downsize my studio. So I’m not inclined to think this was related given the issue persisting. My sense , was and still is a Logic glitch that, while not universal, is happening to some of us. I’ve seen others mention this elsewhere. Per JakobP’s question posed last year, and today, I can only add that my Komplete S-61 is the other connected device. Per my brainstorming last year, all relative devices and hardware have been updated to run natively. I’m in the habit of turning off the cycle when I need to not interrupt playback. But yesterday I needed to dub in MIDI and it jumped back to the start of the cycle before my take. The fact this got no traction after posting last year was as baffling then as now, and I had even forgotten I’d come here to try and resolve. Would love to see this go away, but it did but happen on its own yet, lol. I edited my typos, sorry!
  2. Hi JakobP Only while sitting back to listen to something I have just added to the orchestration, so in playback mode. Never while recording, although the one caveat is that I do often use the capture take as recording feature, so it has spoiled a couple of those moments by jumping back before it reaches the measures I am working on. I am retraining myself to disengaged the cycle mode while composing this way.
  3. I always feel guilty for posting here when I rarely visit, but always know someone will take a stab at whatever it is I'm trying to sort out! I'm more a cause-and-effect person, so tend to be obsessive about tracking down why something happens in the first place. But yes, both replies suggest a couple of possibilities relative to the fact the Komplete keyboard on my desktop is not yet officially supported yet in an M1 environment. I will try using a different controller for a bit to see if this still occurs. Just the fact that hitting a stop/start transport button on the controller will sometimes send the highest piano note at full velocity is a clue - not dissimilar to what you both are suggesting. I will post back in the off-chance it might help someone else sorting through similar woes.
  4. Thanks for the tip. Can you give me a bit more insight? I use my controllers like breathing, so the question is a bit like asking me not to breathe for a while to see what happens, lol.
  5. So, I just began to experience the same issues the OP reported (in 2017) and which my search showed me a few others have reported in the interim as well. @ckeyes888 can you say more about how or why an audio box converter would cause This? I don’t use one in my setup, but am curious how you came to this conclusion. For me, this behavior started immediately after setting up my new Mac Studio two weeks ago. It happens dozens of times every day now, where the playhead jumps back to the left indicator while in the middle of a cycle. If I don’t have the cycle on, it’s not an issue. Typically, I am working with only MIDI, btw. Like David, I had never seen this before, and I’ve been using Logic for twenty years. It literally just began since moving from my Intel iMac to an M1 Max Studio Pro, and is happening all the time now. I’m stumped.
  6. Hi Polanoid Per my lengthier, initial post, the underlying regions in the track are what is being destroyed and/or altered, after this scenario in the Piano Roll editor occurs. One of two behaviors takes place: the underlying regions are truncated to a small sliver in the track, which I think have to manually extend. Sometimes all the notes are intact, at other times I've seen them completely wiped out (totally blank). The second thing I've seen is an underlying region disappear entirely from the track, though this seems to be the lesser occurrence. And more to the point, this happens when simply hitting cancel in the unsolicited window, where LPX then performs a fairly intrusive and/or destructive action that is invisible to an undo history. I am not sure anyone here is capable of solving this mystery, to be honest, and I never interpreted this as something in need of a fix as much as I have seen it as a glitch that was introduced sometime after an update last year. (Note, I'm a prudent user who has only posted 30+ times since 2007 when I am certain there is something to draw attention to). At this point, it's really a matter of hoping for clues in how to report or detect what is going on, though it's feeling a bit like a desert island now. It seems this only happens with keyboard virtual instruments, by the way, where many overlapping notes are potentially involved.
  7. This particular project is tied to commercial work, but I do not believe this behavior is project specific. I’ve encountered it dozens of times with different projects since last year. I could send another project with similar overlapping regions, but this is not a reproducible behavior and I’ve worked entire days without this quirk popping up. What I just noticed here is that the cursor is placed as if to spilt a note, though that is not my intention. I’m simply selecting a note to either then move it along the scale, mute, or even delete it. i also think this is coincidence I captured this - I’ve seen this when the cursor was not over what I was attempting to edit, though perhaps Logic is interpreting wherever else the cursor may be at the time as a split point? Just a hunch. Under what circumstances would the above even be intentionally triggered? I split notes and regions constantly via an assigned key, with a straightforward series of options similarly worded. But unlike this random oddity, canceling leaves everything untouched.
  8. Today, I managed to get a screenshot of the behavior I detailed in my initial posts. Yes, even as I am now more routinely working by opening up additional tracks using the same instrument, I still have a number of instances where there is overlap of some of my previous piano parts for an ongoing project. What is happening in this picture is where I'm stumped. I have simply clicked on a MIDI note to move it, and then the window opens up - triggered inadvertently. Moreover, as described before, if I simply hit Cancel, all underlying regions are either truncated or get deleted entirely, with no recourse to bring them back via an undo. In the case of this event today, I actually clicked on Keep for the first time, which avoided the destructive action. Any clue what is triggering this behavior, which is a separate question from why a simple "Cancel" nevertheless proceeds with an unwanted and destructive action? If this is not a bug, I don't know what is.
  9. Fuzzfilth - I’m still waking up. Reread your post after I replied, and realized that is absolutely a workflow solution, but my old habits die hard. In the piano roll I’m constantly nudging notes relative to hearing the notes from the underlying performance, as well as physically moving them along a scale to get the harmony I hear in my head (my theory skills lag). I will lasso notes of overlapping takes without even thinking, to hear the more complex chord.
  10. Thanks fuzzfilth. Yes - that is what I also do for single instrument orchestrations when comparing takes. The esoteric workflow I am describing would seem to be relative to piano tracks which are the basis of the eventual orchestration. I’m guessing more competent keyboardists don’t go where I go, lol, but the magic for me is frequently capturing improvised takes as recordings, which overlap. I’m looking for confirmation of a recently introduced bug here, apparently, which I can only take screenshots of when this next happens. What distresses is that LPX is performing an action when I decline, and then does so destructively with no recourse for a simple undo. And it’s MIDI.
  11. Overlap. As this is how I will often build up part/ voices. With no overlap, I would not be able to to do this at all, I believe. Or, at least that was the case when an update some time ago reverted to n overlap as a default, and sent me scrambling to turn it off. The only "clue" I have is that something is inadvertently triggering what LPX thinks is region editing functions, though I have multiple regions lassoed while working strictly in the piano editor.
  12. I posted this over at the composer forum I frequent, and got a number of views but not a single response. I am seeing this recent, but infrequent occurrence while editing MIDI notes with overlapping regions selected, where data from underlying regions will disappear and cannot be restored. It happens right after a window pops up asking me if I want to split something, though while I’m only nudging notes manually in the piano roll (similar to the options when I’m intentionally editing regions). Then, despite declining the unsolicited action, Logic proceeds to either truncate and/or wipe out the MIDI notes from an underlying region. Neither undo or history will bring the notes back at that point. Only closing an unsaved project will restore this data when reopening again. Two behaviors occur in the context of when this infrequent and seemingly random event happens: Sometimes I can reach for the truncated sliver of the underlying region and expand it to see the notes again. At at other times when I do this, the notes have all been erased, and the region is blank. I’ve lost entire performances this way. This is not something I can intentionally reproduce. I work on hundreds of tweaks per day in the piano roll, and this event happens infrequently. On average, a few times per week. I believe it began after an update earlier this year, but cannot be certain. Indeed I’ve not encountered this in many years of working this way, where I build complex piano parts with several overlapping takes, then edit within the lassoed regions before eventually merging. Is it just me?
  13. First, let me say that I cannot presume to take credit, as many people have noted different aspects of Logic Pro X's GUI that have been visually challenging. Months ago I posted that I had contacted Apple directly regarding my vision impairment, and the new LPX interface. In short, Apple had inadvertently created an additional impediment for me, as I suffer from a degeneration of the retina. Their response this past July was immediate, and resulted in several emails and a conference call that included a lead from the Logic Pro team, and a member of Apple's accessibility department. In that conversation, I conveyed my own personal wish for a return to better contrast, particularly in the MIDI Piano Roll where I spend much of my time. I also noted that the velocity color hues were difficult for me to distinguish (resulting in always setting those colors to a brighter region color, "brighter" meaning almost always the very dark ochre or top tier of colors). And, we discussed the way in which lack of contrast between foreground elements and background grid did not create a cohesive canvas for me to work with; I had come to take that for granted in earlier versions of Logic, as I became increasingly dependent on adjustments to meet my changing visual needs. At one point I told them that I needed to "turn the lights back on." Needless to say I was both stunned and grateful when I saw a simple button that allowed me do just that. As I don't process low light well, this is beyond what I could have hoped for, though obviously there are areas throughout I would love to see improved as well. It was in these forums I learned I could edit the plist, which I've been doing - and redoing after each update. I was about to go with a custom theme as well, but the changes today meet my needs. Perhaps most importantly, I feel as if I was heard and understood, and Apple made that clear to me several times. I am most grateful. Greg
  14. Please report it to Native Instruments if you haven't already. I am concerned that the only way we're going to get them to fix it is to make sure they know it is affecting more than a few of their users, and I'm not seeing a peep about this in their forums yet. (If they haven't responded to my bug report by early next week I may have to broach the topic in their forums myself.) I just posted over at NI. Cheers.
  15. I too am experiencing a dismaying increase in crashes since the recent Kontakt update. LPX in Mavericks is now becoming unusable, as about 90 percent of my libraries are loaded into Kontakt. I contacted NI tech support yesterday... Since July (when LPX was released - pre mavericks), I would infrequently experience Kontakt crashing LPX while trying to access an active instance, but always while in playback. Hence, I began stopping playback to avoid this, working comfortably for days without an incident (unless I got careless and clicked on the channel strip while in playback). This pattern continued right after the Mavericks install as well, though I became more focused on the increased performance for my older MP. Since the recent K5 update, crashes occur quite frequently when trying to access an instance (irrespective of playback). Hence I cannot say with any certainty that Mavericks is a factor, particularly as I enjoyed a period of relative stability in the interim leading up to the last round of NI updates. pax
×
×
  • Create New...