Jump to content

splunk

Member
  • Posts

    89
  • Joined

  • Last visited

Recent Profile Visitors

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

splunk's Achievements

Apprentice

Apprentice (3/14)

  • Conversation Starter Rare
  • Reacting Well Rare
  • Helpful Rare
  • Dedicated Rare
  • First Post Rare

Recent Badges

5

Reputation

  1. I'm having this same problem with 10.7.9. I have the tempo fader set up the way you do and it records correctly about 1 out of 10 times. But, most of the time, I see the fader events being recorded in the event list and all looks good, but when I stop the recording, the tempo events don't go to the tempo track and actually change into something that makes no sense: The tempo events self destruct into whatever that unnamed event is and then there are a few straggler tempo control events at the bottom. I have Allow tempo change recording checked, but I get this result whether it's checked or unchecked. This is a new project, so there shouldn't be any corruption or settings that would be getting in the way. It occasionally works, but only on shorter passages. If I try to record tempo events for an entire song, then I just get a longer list of those bizarre, no status events that were formerly tempo control events. Is anyone else seeing this or have an idea about what might be causing this?
  2. You're right. It seems to be a bug. The selection doesn't update until you open the transform window. Since I usually change the high and low values of the crescendo or relative crescendo, I've always fired this from the transform window, so I never noticed this. It should work correctly with a key command. Bummer!
  3. That's a bummer. I seem to be running into an unusual number of roadblocks in Logic, lately. In my case, I would prefer to have 8th notes as the division for the metronome and grid, but I want the default score quantization to be 16, 24. But, I can't ever seem to get that quantization value unless I set the division to 16th notes. It isn't a deal breaker, but it's definitely not the way it's supposed to work, according to the manual. Just to make things even more complicated, I'm one of those people who never puts Logic into record when I'm working with MIDI. I play in the parts and when I get something I like, I use the capture recording command. I have a feeling that this feature isn't even taken into consideration with the default score setup, but I did my testing by recording normally and that didn't work either. Thanks, volovicg!
  4. OK, so either this has been fixed or there's something odd going on with my setup. I'll do some more tests. Unfortunately, I didn't update the OS before Apple released Ventura, so I'm stuck on 10.7.4 on this computer until I update the OS. I'm not sure if all my third party stuff is Ventura ready, though. Thanks for checking this, Atlas007!
  5. I'm having a problem in 10.7.4 with getting the desired quantization on new regions. If I deselect all regions and get the Default region, I can set the quantize value to 16,24, since that's what I want to see with all new regions. But, when I record a new region, the score quantization always goes to 8,12. I can override this by setting the division to 16, which seems to force the score quantization to 16, 24, but I'm pretty sure I'm not supposed to need to do this unless I set the quantization to Default on the Default region. Is this a known bug or am I doing something wrong or is this one of those weird things that's only happening on my machine?
  6. The problem is that the two ranges have to be identical. My current solution is to select the CC1 data in the piano roll or event list and press U to select that range. But, when I go to the destination track and press shift-L to select between locators, the selection includes everything between the locators, not just CC1 data. It would be great if I could just select the same data that's on the clipboard, but I can't find a command for that. By accident, I found out that if make the selection between locators and then shift-click in a CC1 region automation lane or in the CC1 automation in the piano roll, then everything but CC1 is deselected. Yay! Then I can hit Delete and then Paste and I get the correct curve pasted in. But, that's a lot of moves. I was hoping to find a simpler solution, but there may not be one. Thanks, Atlas007!
  7. I keep thinking I'm missing something obvious here, but I can't figure out a way to copy a MIDI controller in a specific range on one track and paste/replace that controller to another track. Specifically, I've got a string section with each instrument (vln1, vln2, vla,...) on their own track. All of the tracks have their own controller data. If I decide to change the attack of a phrase by altering CC1, I can go to one of the instruments, solo it and then make the changes that get me the attack I'm after. Now, the question is: how do I put that same curve for just the attack on the other tracks? Copy/Paste doesn't work because it just adds the new curve to the existing curve in the destination track and makes a big jagged mess. Paste Replace gives me the correct CC1 curve, but erases the notes and other controllers. It literally replaces the paste area with just CC1. So, this doesn't work, either. I have a workaround method, but it takes 10 steps, because I have to select the proper range in the destination tracks and then jump through a bunch of hoops to just select CC1 so I can erase it before pasting the new version. This seems like a crazy bunch of work to just duplicate a small range of CC data. Does anyone have a simple method of doing this?
  8. Yes, that's correct. I don't like ever contradicting David because he knows about 100x more about Logic than I do, but I believe that if you look at the action menu graphic that he posted above, you'll see a selection at the bottom called "Selection defines position and/or pitch range." This is your friend.
  9. That's really weird that you have different behaviors than I do, but the end result is, neither one of us is getting the behavior we expect. I wasn't sure if this inability to customize the automation lane view was a bug or Apple never thought this feature through very well, so I sent them a feature request to allow us to make custom lane views that we could recall because I think it would be nice to have different lane views depending on the type of editing I want to do. I should probably make a different thread for this next question, but what do you think about this other weird thing that happens when we make automation lanes where there are a bunch of duplications of the original track for every lane even when we leave automation mode? Why are those necessary or useful? I haven't been able to figure that out. Those extra lanes don't appear to do anything outside of automation mode. They just clutter things up and get in the way. Thanks again @polanoid for taking the time to check this stuff out!
  10. Hmm. You're right. I actually got it to work once on a fresh project, but only once. Here's what I did: 1. Open fresh project, add instrument, make a region and add 4 controllers in the piano roll. 2. Go to main window, turn on automation mode, select instrument track and change automation to region automation. Setup lanes so that only two of the four automation lanes are showing. (In the case of this first track, hitting the disclosure triangle at the bottom left of the track header only reveals one more lane. I have to keep adding lanes to see all four lanes. Odd. This is different than what happens on the other tracks I'm going to add later.) 3. Pressing A to open and close automation mode correctly shows the two lanes I last had visible. But... 4. I setup a second instrument track and option-dragged the region I made in the first track to the second track. Again, I set the second track to region automation and arranged the same two automation lanes for viewing. (But, as I mentioned, this time when I hit the disclosure triangle, all of the controllers showed and I had to delete two of the lanes in order to have the two I wanted to view.) 5. Now, pressing A to open and close automation mode collapses the view to one lane and I lose the two lane view I had previously set up. I added more tracks to see if that changed anything, but this new behavior where the lane setup is always collapsed seems to be permanent on my computer. Could you try this on your computer and see if adding tracks and regions makes the automation misbehave? Thanks for looking into this!
  11. I was hoping that maybe I missed something, but when I did a search and found this well-researched post, I had a bad feeling that this might be the way Logic actually handles multiple automation lanes. Since I'm using this multiple lane technique as a workaround for the fact that we can only have one controller showing in the piano roll at a time, I really want it to work. In fact, it does work, as long as I don't accidentally trigger automation mode in a different screenset and then try to exit automation mode. As long as I just leave one screenset with all the lanes arranged how I want them to be and leave automation alone everywhere else, the arrangement stays consistent, so it works pretty well as long as I stay away from that A key! I just submitted a feature request over at Apple for user automation lane views. I'm even alright with letting them be part of a screenset, just as long as we can lock in an automation lane arrangement and keep it. I also requested that opening, closing and then re-opening the automation view keeps the lane arrangement as it was the last time I used automation mode.
  12. So, I'm not imagining this? There's no way to setup a particular view where I see just a few of the lanes of CC data - in my case, modulation and expression - and leave the rest of the controllers collapsed and then leave the automation view and come back and have this setup still in place? Instead, Logic starts from scratch and I have to set up my custom view again, and again and again? This seems silly. I even tried to make a screenset that had my preferred view and then lock the screenset to preserve that view. But, as soon as I use automation in another screenset and then go back to the regular view, the locked screenset also collapses everything and I have to start over. Is there a workaround for this or something I'm missing? An automation lane custom view seems like something a lot of users would want and I certainly expect the automation to open in the condition it was in when I last used it.
  13. If you're running the latest Mini with the onboard graphics, make sure your monitor resolution in the system preferences is set to the native resolution of your monitor. If that makes things too small, try 1/2 of the native resolution. The idea here is that you don't want the Mac to have to scale the video. I find that the CPU hit is significantly lower when I run at my monitor's native resolution (3840 x 2160, in my case). It's especially noticeable in Live Mode with heavier virtual instruments.
  14. I just checked and it looks like all of my AU plug-ins have this permission set, so I don't know if this is your problem. I seem to have all the same settings, but everything works over here. I hate problems like this. They're so frustrating! I'll keep thinking about it and if I come up with anything, I'll let you know...
  15. Hi Peter, I'm on 10.5.1 and I've got Halion 6 running pretty much all the time and I just checked and I also have the Steinberg folder in my AU Instruments drop down. The only obvious thing I see that's different in our setups is that I'm still on Mojave. Have you tried creating a custom folder in the Plug In Manager? For instance, I have a folder called Sample Players that includes all of my sample based plug ins. I'm just curious if Halion will show up in Logic if you drag it to a custom folder since that's where I normally access it on my system.
×
×
  • Create New...