razzzzz

Awesome! It's like a UI upgrade from logic 7 to logic X in one go.

I'm making a diagram which aims to illustrate the concept of round-trip latency in digital applications. This diagram is for a personal project I'm working on; It's not specific to Logic Pro. That said, I'm sure it will certainly apply. Here's what I have for the input latency section of my diagram: - Latency is introduced when audio travels through air, from the instrument to the microphone - Latency is introduced in the AD conversion phase - Latency is introduced when the audio is delivered to the system/application (DAW or otherwise) via the driver Question 1: Can the microphone itself also cause non-negligible latency, or are all microphones created equal in this regard? For example, would the microphone on an iPad introduce any more latency than a professional studio mic? For the output latency section of my diagram: - Latency is introduced when the audio is delivered to the sound card via the driver - Latency is introduced in the DA conversion phase - Latency is introduced when audio travels through air, from the speaker to the listeners ears Question 2: Similar to the microphone, can the speaker itself also cause non-negligable latency? .R

I previously wrote feedback to apple about this and suggested they use a "compact" display for the slider when the track header is narrow. Not the worst issue in the world, but would be nice to have the slider available at all times. Feel free to write feedback to Apple as well.

"Adds support for Force Touch trackpad" I was curious as to what support the logic team added. Started force-clicking around and found a few goodies. - Force click on an empty section of a software instrument track to create a 1 bar region (works with any tool selected) - Force click on an empty section of an audio track to launch the Open File dialogue box - Force click on any region to rename it - Force click on the ruler to create a marker - Force click in the piano roll window to create AND delete midi notes (works with any tool selected) - Force click on any track header to toggle zoom on focused track - Force click on an empty area of the track list to launch the 'create new track' window Anybody else?

I'll leave any discussion about 'what happens behind the curtains' to those who are more experienced, but in terms of work-flow, I think there's an alternate way to get what you want without using the event list. 1. Open the automation track 2. On the automation track, use the marquee tool to highlight the section you would like to pitch bend 3. Click and drag up (or down) on the portion of the automation line that is located within the boundries of your newly created marquee selection If I remember, this should 'visually' create an instantaneous value jump, or square-shaped automation line (although, as David said, it actually isn't instantaneous) From there, you can simply delete any points you don't need to create any ramp shapes that you want. .R

Ah shoot. Maybe it's part of my old video-game testing days... I get excited when I find reproducible issues/bugs. I'll keep working at trying to get it to happen again on my system and report back. Would love to hear any tips/tricks you have for a more transparent approach to recording vinyl. Should I start a different post then?

Sorry, meant ADC above, not DAC.

Looks like it's a problem with the project file then. I'll try starting from a new empty project to see if I can get it to happen again. Regarding the use of the limiter: I used to simply record my vinyl by trying to get it as near to 0dbfs with no clipping and leave it at that. When I compare them to .wav tracks I purchased, I noticed my recordings sounded very quiet. After examining the tracks I recorded, I noticed they all had very uneven peaks (some due to vinyl pops, others probably due to intentional dynamic range choices, and others that I just have no idea why they are happening... Probably DAC?) When I use an adlimiter to even some of this out, the result sounds much better. Since I have a boatload of vinyl, I thought it would be convenient to do this at record time (via the input channel strip) so I don't need to go back and process each recording one by one.

Hi Eric, Please find the attached zip file containing the template I used in my original post. And thanks for the heads up about the peaks. I've since updated my template to use an AdLimiter followed by a Gain utility. I'm new to ripping vinyl, but what I've been doing is: 1) Make sure I'm not peaking on the sound cards input, aiming for a peak of about -3db. 2) Using the gain parameter in the AdLimiter to ever so gently push the signal into the ceiling of about -1db 3) Using the Gain utility to bring it up the rest of the way Also, I changed the signal flow from Input Channel Strip -> Bus -> Audio Channel Strip to Aux Channel Strip -> Bus -> Audio Channel Strip. The bug went away after I made this change. Curious. Not sure if what I'm doing is anywhere close to a recommended best practice... but thought I'd experiment a bit. Any feedback on this is welcome .R Vinyl Ripping Template.zip

I've set up a logic x template for recording my vinyl with some very basic signal routing. I'm using an Input channel strip in the environment so I can record using a limiter. - Audio comes in on Input 1/2 - Created an Input Channel Strip in the environment - Set the Input Channel Strip to Input 1/2 - Slapped a limiter on the Input Channel Strip so I can tame any peaks during recording - Input Channel Strip sends audio to Bus 1 - Deleted the auto-created Aux Channel Strip when instantiating bus 1 as it's not needed - Audio Channel Strip receives audio from Bus 1 - Audio Channel Strip sends to Output 1/2 Whats strange is that the right channel on the Audio channel strip is MUCH louder when the audio passes through the Bus, as if the Bus is doubling the right channel. I can't for the life of me figure out why this is happening. Check out the screen cap below: - At first audio is coming through the Input Channel Strip - If you check out the levels on the Audio Channel Strip you can see the right channel is much louder - I change the Audio Channel Strip to record directly from Input 1/2 and you see the issue goes away - I change the Audio Channel Strip to record from Bus 1 again and you see the issue come back - I disable the limiter on the Input Channel Strip to rule it out as the culprit What's up with this? .R

Hi Simon, Can you post your system info in your signature? See the forum rules here for more information: rules.php I just tried the steps you outlined as best as I could and everything works fine for me. I'm wondering if this is a graphic display bug that is specific to your system. In other words, maybe the data is still there and 'selected' but it just visibly disappears due to the specific graphic card you have in your mac, OS version, or combination of both. Posting your info might help others with the same system specs as you try to reproduce the issue and get to the bottom of it. EDIT: Sorry I just saw you have some info already posted. Can you post your os version and logic version to your signature as well? .r

Excited about the idea of an update coming soon. Actually, I'm really happy with the latest version, and I have more than everything I need to make music... but Alchemy would definitely be a great addition! That said, I REALLY wish they would have chosen to update the EXS24 first.

Thanks Eric. I'll give that a shot later tonight when I'm in my studio. Question: Is it fair to say that what I'm experiencing is a bug? I would think so, especially as turning Software Monitoring on BEFORE pressing play works from a fresh boot, but ceases to work after time. Would like to know others opinions before I send this off to Apple as a "bug"

Thanks for the reply, Atlas. I checked the device preferences and everything seems to be in order. Both the "Input monitoring only for focused track" and "Input monitoring level for record-enabled channel strips" are disabled. (by the way, I believe the linked manual to be outdated here as the text for this second option in the latest version of Logic now reads "Independent monitoring levels for record-enabled channel strips"). I can see how having the first option on might cause the behavior I am seeing IF it was turned on and IF I happened to have a different track selected, but in my case it is turned off and I did have the track selected (and record enabled and input monitor enabled), so I don't think this could have been the issue. I don't think the second option is related to my issue at all as 1) it was turned off to begin with and 2) even if it was on, I'm not sure how it would produce the behavior I am seeing. I also ran through the checklist you linked (thanks for that, it's always nice to be reminded of the details), and everything seems to be in order. Wish I could say the advice helped, but I'm still stuck here

Hi, Apologies if this is a re-post. I've had this issue for a while now which is KILLING my productivity, but I can't remember if I posted anything to this forum or if it was a different forum. (tried searching my previous posts) Issue: In LPX, software monitoring only works for me if I start playback FIRST, then turn software monitoring on AFTER playback has started. Check out the video attached. Details: 1. "SubPhatty" External Instrument track sends MIDI to my Moog Sub Phatty 2. "Moog" Audio Track receives audio from my Moog Sub Phatty and is input monitor and record enabled 3. I turn software monitoring ON 4. I press space to START playback 5. Result: No audio. I see audio coming in to the "Moog" Audio Track, but it is not being passed to stereo out. 6. I press space to STOP playback 7. I turn software monitoring OFF 8. I press space to START playback 9. I turn software monitoring ON 10. Result: Audio is heard as soon as I turn software monitoring ON. Occasionally the issue will go away if I restart logic, but the solution is only temporary; the issue almost always comes back if I stop and start playback a second time. KILLING me here. I know I can direct monitor via my focusrite but A) I like using effects during jam sessions so I prefer software monitoring and B) shouldn't it just be working anyway? I mean, the only difference is WHEN software monitoring was turned on, so I think it should work regardless... or am I crazy? Super frustrated. .R SoftMonitoringBug.mp4.zip