Jeremy Spencer
Senior Member
I didn’t hear anything
Nor did I
I didn’t hear anything
Nor did I
I know the basic functions of Logic. The issue is that Logic only snaps automation to fractions of beats, and does not allow snapping to other types of data. If you read the accompanying article this would perhaps be more clear.
Sorry, but no, you obviously don't know Logic very well and i think you should spend more time on it before making videos speaking about it. Or focus on making videos about things you understand.
A little hint for the problem you're facing at 0:56 ->>
click while pressing Shift control alt starting at the point where you want your volume drop and then select the range. Logic will create two points at the start and end each. You can - without snap - move the points in pairs. And you can set the volume inside the range as you want it.
It's really easy and nothing to worry about.
Welcome to VI control.I knew this video would get some flack, but I didn't predict this strange turn.
Did you try it?
Thank you for the information, but that is exactly how I setup the automation for the test "off screen". I suspect you're taking a bit of injected humour too far (though, placing automation breakpoints is annoying). The issue for the test had to do with placement of automation points, and this was an orthogonal issue that I thought was funny.
As i've written, you can change the placement by selecting both points (the higher and the lower; see the white portion in my second image), then move both by grabbing the higher one.
However, Logic indeed applies a 4-5 ms ramp.
(In earlier versions, the automation even was flawed in some situations, but that one get fixed.)
That is a great tip, I didn’t know that, thank you.Sorry, but no, you obviously don't know Logic very well and i think you should spend more time on it before making videos speaking about it. Or focus on making videos about things you understand.
A little hint for the problem you're facing at 0:56 ->>
click while pressing Shift control alt starting at the point where you want your volume drop and then select the range. Logic will create two points at the start and end each. You can - without snap - move the points in pairs. And you can set the volume inside the range as you want it.
It's really easy and nothing to worry about.
When moving the points, is it possible to move an automation point to a specific frame/millisecond/sample quickly?
Its not at all straight forward, but if you set up key commands its a two step process
1. "Track Automation Event List…"
2. "Show Event Position and Length as Time or Bars/Beats"
Then select whatever automation you want to move and double click the first value to enter exactly where you want the shape to move
Set the transport to where you want the automation point. Select "Create Two Automation Points for Visible Parameter". You can create a keyboard shortcut for this too.If there's an easier way to precisely get automation points to a specific sample, then I definitely missed it, and I would love to be corrected.
Set the transport to where you want the automation point. Select "Create Two Automation Points for Visible Parameter". You can create a keyboard shortcut for this too.
Wow, I just checked, that's right. And the same for the Shift control alt clicking method. I wonder why they do it like that? Maybe some people prefer a short fade like this as it's not going to create and audible pop on a bassy sound for example.The problem with this method is that it's not exactly precise. It sets a 0.5 millisecond offset in both directions. Of course it depends on the situation if this is enough precision or not....
Wow, I just checked, that's right. And the same for the Shift control alt clicking method. I wonder why do do it like that? Maybe some people prefer a short fade like this as it's not going to create and audible pop on a bassy sound for example.
Agree totally.I.e. they should offer the option to do it precisely, and also without the 4ms fade.