Jump to content

billscores

Member
  • Posts

    69
  • Joined

  • Last visited

billscores's Achievements

  1. Same. I just updated to 10.7.8 and I have the same problem. All multi-out midi instruments (like Kontakt, Omnisphere, etc.) only allow recording into the first channel of the instance. No other channels. I can play-thru the other tracks, and hear my performance in real-time when playing my MIDI controller, but if I try to record said midi input, it won't record. Strangely, a MIDI region forms, as if recording (with the note data in it), but the region disappears on pressing stop.
  2. I don't know what conditions are causing this, but I've experienced this in three sessions in 10.5 and one so far in 10.5.1. Never previously. In these aforementioned sessions, using 'repeat section between locators' yields a chaotic mess - new bars are created, but some midi is shifted vertically to adjacent tracks - and most tracks aren't repeated at all. Sessions are corrupted from that point on and 'repeat section between locators' can't be used with usable results. I'm using pattern regions and DMD in these problematic sessions with no live looping. One thing in common with these sessions is that they all have one pattern region placed earlier by a 16th note on the timeline after its construction. Could be related -- although changing these patterns to midi regions does not correct the issue once it is present. Please add on to this thread if you experience the same issue. Thanks.
  3. This keeps occurring in Logic for me. I'm hoping there is a known fix or workaround. Normally, when I create a midi region (and then double click it to enter the Piano Roll editor) the automation lane at the bottom of the window defaults to show 'velocity'. This is default behavior I prefer. Alternatively, if I had just been editing CC1 in a region, then option drag copy that region to another track, the copied region (when double clicked) will default to display CC1. This is all good. I would love to see this consistently in Logic. However, this behavior never lasts. As I work, for reasons I cannot explain, Logic will begin to default the automation portion of the piano roll window for all newly created midi regions to 'display off'. (see attached image.) Once this behavior starts, it exists project wide (for all newly created regions). The issue persists even after quitting and restarting Logic. Sure, I can click on 'display off' label and select to view velocity. But after doing this even just a few times, it becomes a very frustrating task. I can typically trigger this behavior within a couple simple moves. For example, if I create a new MIDI region. Draw a note. Draw some CC1 in the region. Option Drag copy the region to another track -- and viola, the problem exists. Of course, all my sessions begin with my default template. I spent a few minutes today trying to trigger this behavior in a new session not derived from my template, and of course, I couldn't trigger the behavior, which leads me to believe the problem lives in my template. My template took me many months to create and perfect. I could probably recreate it, It wouldn't be easy or overnight. And certainly there's no guarantee that if I go through the whole painstaking process of creating a new default template, that this behavior won't magically resurface again. Anyone else dealing with this? Can anyone suggest a remedy? I couldn't find a default setting for this window in the preferences. Personally, I don't even understand why 'display off' is a needed option, when one can easily hide the automation portion of the window. Please help.
  4. Very cool. I've been overall happy with Logic. It's a great program with a ton of powerful features that I'm becoming dependent upon. My old workflow for orchestral scores is going to have adapt to the way Logic likes to do things. No worries. I like changes as long as they don't slow me down too much. I'm a MIDI veteran too. My first synth a Yamaha DX9 back in 1984. By '89 I was using Cakewalk (for DOS). I had a sequencer on an Atari before that but I can't remember what it was. I haven't used the step editor in Logic yet. For legit type orchestral and band arrangements, my new weapon of choice on that front is Dorico. For realism, I need to finesse all that notation in a DAW (for me it was DP for several years, then ProTools for another 10, now Logic!) CC contouring is a huge part of my workflow. My clients expect my orchestral cues to sound indistinguishable from the real thing, and it takes a ton of finessing in the piano roll to get it there. For me it's all about massaging note starts, note ends, velocity, multiple types of CC, Articulation Sets -- so I basically live in the piano roll editor.
  5. Agreed. I never said Logic added 'MIDI CH stamp' data to imported midi. I said Logic uses this stamped MIDI ch. data (unlike any other DAW) to create "separate CC lanes" and "separate velocity lanes" in a single track's piano roll. This is fundamentally different than all other DAWs. My experience making music with MIDI spans 30 years. I compose music for a living. Talk about multi-timbral -- I've got three dedicated servers running VEP in my equipment closet beside me right now, so no stranger to multi-timbral MIDI here. Just Logic.
  6. Thanks. I found the work-around for this issue. It wasn't my MIDI controller at all. I thought I'd post this discovery for those who might be new to Logic like me and having the same issue. Logic handles MIDI fundamentally differently than the other DAWS I've used, specifically with regard to the Piano Roll and the graphic representation of MIDI events. LOGIC taught me something I didn't know about MIDI. I had no idea that every single MIDI event has a MIDI origin channel stamped into it's very being. Yes, the MIDI 'input channel' THAT CREATED that MIDI event is essentially etched into the event itself, like a watermark. You can see these watermarks in the LOGIC MIDI event list in the MIDI channel column. Other DAWS don't show this information. They'll show you the MIDI routing of the event (where you've assigned the data), but not its origin channel. These origin channel stamps or 'watermarks' are hidden in every other DAW I've worked with, in fact the user need not ever be aware this MIDI information exists because it is not viewable. LOGIC, however, treats these 'creation stamps' as valid data with regard to the display of MIDI graphically. I believe this is because Logic is the only DAW that allows independent MIDI channel assignment within a single region on a per note (per event) basis. No other DAW treats MIDI this way. This is a blessing (and a curse if you are not aware of it.) Here's the curse (and the workaround): If you compose music in a notation program (Finale, Sibelius or Dorico) with the intent of importing that MIDI into Logic for fine tuning, you are in for a rude awakening. If you don't work this way ever, you'll probably never encounter this issue. When importing MIDI into Logic, every event comes in with a 'MIDI channel' stamped into it. Not the MIDI channel where the event lives, but the MIDI channel that created the event! Insanity. EVERY EVENT! For example a single Flute region imported into LOGIC, may come in listing 4 different midi channels in the midi EVENT list, and these channels are event specific. This is because if when working in your notation program, you copied and pasted into that flute staff from another staff at some point, the notes you dropped into that staff are stamped differently than the notes created directly onto the flute staff. Yep. Insane. Similarly, a hairpin crescendo (CC 11) in your notation app might be stamped with MIDI channel 1, yet most of flute notes are stamped with MIDI channel 2, etc. You can see this watermark data when you import the MIDI into Logic. You can't see this midi origin stamp data in Dorico, Finale, Sibelius, ProTools, DP or Sonar -- it's hidden -- because this data is irrelevant to the app. It's historic data only. It has no value in the application. So here's the rude awaking: Say you assigned that newly imported flute track to your favorite flute sound in Kontakt within Logic, and you begin sweetening the performance with some CC 11, Mod Wheel, Key Switching, etc. from your keyboard controller. You may soon discover you have 2 or three lanes of note velocities, two lanes of the same CC, and a big cluster-F in your piano-roll because Logic is keeping the channel stamps discreet for all the data. i.e. your MIDI controller is most likely coming in on channel 1, and those notes don't mix well with channel 3 stamped notes in Logic. All the notes in the region are viewable in the Piano Roll, but their velocities are only viewable or separate lanes. Fun! Next you may decide you love the intensive CC contouring you did for your French Horn 1 track, and you want to copy all that data onto your 'French Horn 2.' Well this is going to add a couple more lanes of Mod Wheel and CC 11 to French Horn 2. In fact every time you copy a note, or bit or CC data around between tracks you will be populating your piano roll with more CC lanes i.e. - "Ch 1: Velocity" "Ch 3. Velocity" Ch. 8 Velocity" Ch.4 Mod Wheel. Ch 6. Mod Wheel, etc. All of these can exist in a single region, and Logic treats them discreetly graphically. No other DAW does this. It's madness. I eventually had 10 lanes of Mod wheel on my violins 1 track just from copying and pasting into the track from other tracks. Worse, there is no way to consolidate this data into one lane after the fact (except for manually editing every event in the EVENT list to show the same origin channel.) In conclusion, don't import midi into LOGIC from a notation program with the intent to fine tune it graphically in the Piano Roll! The workaround: Import notated music into Logic as MusicXML! All the data comes into Logic stamped with channel 1! And... you won't get any of that crappy CC from your notation app (patch changes, pan, volume, etc.) that you normally need to delete anyway. Only the notes get imported -- that's it. And as long as your MIDI controller is also entering data stamped with 'channel 1', you won't have any of the above issues.
  7. I'm hoping someone out there can help me wrap my head around this problem and squash it once and for all, as it is the single most debilitating issue I deal with in Logic on a day to day basis. It has to do with Logic's interaction with my MIDI controller, a Nektar impact LX49, and how Logic is labelling incoming MIDI data. Normally when I record into Logic from my MIDI controller, everything is fine. When I view a newly recorded midi region in the Piano Roll, velocity and CC data is neatly displayed -- one lane of velocity, one lane of mod wheel, etc. This is normal and what I expect to see. Logic is correctly receiving all data from my controller on MIDI channel 1, and as such, there are no issues viewing or copying MIDI data from track to track. This is normal and how I'd like things to work-- but this is not always this case. Occasionally, as I work, Logic may begin assigning a 'MIDI channel number' to new notes recorded from my controller. I don't know why it starts doing this, but once it begins, there is no logical way to fix it or explain it. Mind you, I haven't changed anything on my controller to trigger this behavior. If I exit the project and start a new project, my controller works just as it should, sending on MIDI channel 1, so this unique MIDI channel labeling issue is specific to this particular Logic project from here on out. Here's the problem in detail: Say, I want to record some CC mod wheel contour onto a trumpet line -- I'll open the piano roll for that region and record a mod wheel pass over it. But that new mod wheel might be labeled "MIDI Ch. 7: Mod wheel" in the piano roll instead of just 'MOD wheel'. Why? I do not know. I didn't change anything on my controller. It's still sending data exclusively on MIDI channel 1 as far as I can tell. As a result my trumpet now displays two lanes of "Mod wheel" in the piano roll, one for each channel present in the region. Next, I might move to the violin track and record a few new notes. These new notes might be labeled as "MIDI ch, 11: Velocity" for some reason, and now my violin has two lanes of 'velocity' in the piano roll. Further, these MIDI channel labels are sticky, meaning if the notes are copied to another MIDI track, the track I've copied it to will now show two lanes of note velocity in the Piano Roll as well. A single region could easily have five independent lanes of velocity. (See attached video to see what I'm talking about.) If I start a new project, the problem instantly goes away and all data entered from my controller is again received on channel 1. This data can be freely copied from track to track, and everything is fine. When I reopen the project with the MIDI labeling problem, the problem persists and all MIDI data entered from my controller has a seemingly arbitrary channel assigned based on the track I record into. Any ideas on how to prevent or correct this behavior in Logic? Is there any way to set up Logic so that it never attaches a MIDI channel label to MIDI data (other than channel 1)? This, for me, would be the best solution. I can't think of a reason for needing to stamp a midi channel label onto a note. I'd love to turn this 'feature' off if I can. Please help!!! Thanks.
  8. That's a really good idea. 3 frame nudges at 30FPS is 100 ms. Great workaround.
  9. The first note of a legato phrase and all other articulations in the same patch (short bows, marcatos, trems, harmonics, etc.) need not be shifted at all. What I need is a surgical nudging tool within legato phrases. Looks like Key Maestro might be the right tool for the job. Thank you for the recommendation. I'll look into it. A '100ms' key command nudge was recommended ideal for this library because the user pressed it 3 times for slow transition notes, twice for medium notes, and once for fast notes. I suppose if I buy Key Meastro, I could set it to run a '10ms nudge' command 30 times, 20 times, or 10 times respectively. However, the ability to set a user-defined nudge value within Logic (I feel) is a fundamental feature, so I'm going to pass this on as a feature request. These new orchestral sound libraries (the first of their kind really) are designed to sound incredibly realistic with minimal effort, specifically because of their fixed and consistent delays across the library with regard to legatos.
  10. Thanks, I thought about that, but the first note of a legato phrase should be on the grid. The "nudge" is recommended only for the internal notes of a legato phrase.
  11. Is there a way to set the nudge value in Logic to 100ms? To achieve realistic legato lines with Cinematic Studio Strings, the creator of the library recommends shifting notes early (in relation to the grid) by 100ms for fast legato transitions (velocity 100-127), 200ms for medium (vel. 65-99), and 300ms for slow (vel. 1-64). This process is demonstrated using a nudge key-command in Cubase. I'd like to set up the same nudge key-command in Logic (100 ms) but I'm not seeing how. Any help would be greatly appreciated. Thanks.
  12. Okay, I think I got it now. One must hover, click, and hold the click in the down position for a half second. Then the menu appears. That's a new one for me.
  13. Hey guys, first time here trying to use independent pan on a send. In the Logic help menu it says in order use independent pan on a send one must first access the "SEND POP-UP MENU" by hovering over the arrows on the send, and click. Sounds easy, but I'm having serious trouble getting this 'send pop-up menu' to appear in this way. I just posted a video of me trying to access this menu. The menu finally shows up after a minute of hovering and clicking. What am I doing wrong? Anybody using this independent pan feature for sends? What's your trick to get this 'send pop-up menu' to appear? Can anyone reproduce this behavior?
  14. Thanks. First time in the environment. There was one 'general midi instrument' that I couldn't rationalize being there so I deleted it. I normally have my mixer set to 'tracks' mode. I hope that 'instrument' isn't responsible for running some vital background midi task or something because it's gone now. It's not the click, because that still works. My session still seems to function fine without it, so it was probably just the residual effect of deleting a networked instrument after printing it to audio.
×
×
  • Create New...