millerme

Hello! I've explained the issue in-depth in the linked video below. Having Auto-Input Monitoring checked or unchecked does not have any effect on being able to have playback on a recorded track while the track is record armed, unfortunately. https://www.dropbox.com/s/nv9s78tw2zc87t4/20230227_141817.mp4?dl=0

Hello, we're having the same issue over here. All playback of existing audio and instrument tracks ceases to play for about 1 second after punching in. The only audio that can be heard during this 1 second gap is the monitored audio from a microphone on the selected track, but from UAD's Console since we use that for software monitoring. Software monitoring within Logic is turned off. After this 1 second gap, all audio continues to playback normally. The playhead continues smoothly during this 1 second gap. MIDI instruments do not have to "catch" after this 1 second gap, which is extremely strange to me. It's like all software instruments and audio tracks are playing back normally, but a momentary mute is occurring on all tracks. I've tried assigning hotkeys for the various record modes, like "Record Toggle." This doesn't fix the issue unfortunately. The behavior is the same regardless if cycle is on or off. It doesn't matter if Auto Input Monitoring is turned on or off. This is occurring on both a Mac Studio and Macbook Pro, so I'm assuming this is a setting somewhere that I'm missing. There is a single fix for this so far, but unfortunately, it isn't acceptable. By record arming the track manually, it eliminates this issue. However, we are unable to hear recorded audio during playback, since the track is record armed. Obviously de-activating the record arm on this track will fix this, but it's too clunky of a workflow. I believe there is an issue with the process of record arming a track, if the track is not manually armed. "If no track is Record-enabled, when you press record, the selected track is automatically Record-enabled." This seems to be the issue that is causing the delay. If there is a way to hear recorded audio on a track that is record armed, that would fix this issue. Thank you for the help!

I'll get you a version number next time I'm in the studio this has been an issue in, thanks! We have an older machine with that version of Logic, which this bug isn't occurring in.

Yep! And as for the VCA faders, I probably missed it due to Cubase being my main DAW and reacting like this to VCA fader movements. 158a08ba92b10e604543b238231b0cf9.mp4

I believe it's control or command click on a solo button in your mixer(don't have Logic in front of me this second). Will put a red line through the solo button in your mixer. It makes it so that the track is ALWAYS soloed if any region or track is soloed, so that signal may pass through complex signal routing without running into a muted track since you soloed a region or track.

Yikes. Completely my bad. You have no idea how long I troubleshooted this, only to not see that VCA at +0.4dB. Very embarrassed by this to say the least, and I'll own up to this mistake! As for the other Logic issue that you asked about, let me go ahead and put the steps below, to at least show I'm not completely crazy! This has at least been verified by other users, and was reported a week or two ago.

Hello, I've reported a confirmed bug regarding Auxes being routed into Audio Tracks. Logic hasn't released a maintenance update regarding this yet, but the bug is confirmed and is being worked on. I'm running into a separate issue that is incredibly frustrating. Pretty simple signal routing that Logic seems to be inconsistent with. I have an audio track region soloed with no sends, its output being my Mix A (Mix Aux) track. Mix A gets routed to Mix P (Mix Print), which then goes to my Stereo Out. Ignore the rest of the Auxes and Print tracks in the screenshot, they aren't being used for this test. The levels between Mix A and Mix P are different even though there are no inserts (yes, I see Ozone disabled on Mix P, but I have the same result with it completely removed). Both faders are at unity. This is absolutely ridiculous that bugs like this make it through beta testing before going public. The previous bug I reported and is confirmed now is just as simple, and ridiculous that Logic has issues with. If someone has a fix for this, please recommend, thank you!

Perfect, this is exactly what I needed. Will just have that splitter as part of the template. Thank you!

Hello, Is there a way to block Logic from receiving a specific MIDI channel, but not the entire device? I would like to avoid having to set every individual channel from MIDI In Port "All" to "1" if possible. I use Ableton and Logic side by side, synced together. I would like Logic to receive MIDI channel 1 from my keyboard, but not MIDI channel 2, which is what Ableton will respond to. Thanks!

Hi all, I'm experiencing an issue with Logic where you cannot play notes through your midi controller for several seconds after selecting the track. This happens more often than not when in playback. After selecting a MIDI/Instrument track, it takes several seconds for any MIDI information sent from a keyboard or controller to be registered by that track, and output audio. This also happens occasionally during punch in/out. Makes it impossible to punch in and out, and the timing of the punches is always off as well. This seems like some sort of functionality in Logic to conserve CPU or something, but it's more destructive than anything. Any ideas on how to fix this? Also may help to point out that we're using an Avid HD Native card, with 2 Digidesign 192 I/O. We've ran into issues with these before with functionality with Logic. Logic 10.4.8 OSX High Sierra 10.13.6 64GB RAM 2 x 3.46 GHz 6-Core Intel Xeon

Inside of logic. Let's say Keyscape for example.

I understand that. The instruments we use responds to that though. For a particular software instrument and the disklavier, I need to do the following. MIDI Input -> Transform CC64 to CC63 -> Sequencer Input -> Sequencer Output -> Transform CC63 to CC64 -> Input of Software Instrument or Disklavier. How can I set this up in the MIDI Environment?

Trying to find the best way to tackle this. Usually the MIDI is recorded from a software instrument, and then regions are moved to the external MIDI track. So when on the software instrument track the sustain also needs to be recorded as CC63 for half pedaling (the sustain pedal on the keyboard sends information based on how much it is pressed, so half pedaling is enabled), but transferred to CC64 before being sent to whatever virtual instrument. Hopefully we can get this setup so that it can transition well between the software instrument, then being moved to the external MIDI track. Could you run me through how to convert incoming MIDI sustain data to the sequencer to CC63, then out of the sequencer as CC64? I'm not super familiar with the MIDI Environment.

Thank you! Trying to make a more permanent solution for this setup though. Any incoming MIDI sustain info should be recorded as CC63 for editing, then sent as CC64 to the disklavier.

Thanks for the answer. I'd love to be able to use the automation curve tool, but it's disabled for cc64 due to logic. I'll try to get the MIDI environment to transform in real time CC63 to CC64. What I really need to get setup is so that any incoming MIDI sustain data is recorded as CC63, then sent as CC64 if routed to the disklavier. Thanks for the help.