ansolas Posted October 4, 2021 Share Posted October 4, 2021 My Logic keeps breaking my control surface setup (three X-touches). It randomly assigns port to teh wrong devices or double map. Quote Link to comment Share on other sites More sharing options...
sunbrother Posted October 11, 2021 Share Posted October 11, 2021 My Logic keeps breaking my control surface setup (three X-touches). It randomly assigns port to teh wrong devices or double map. You can turn that behavior off. Quote Link to comment Share on other sites More sharing options...
ansolas Posted October 12, 2021 Share Posted October 12, 2021 My Logic keeps breaking my control surface setup (three X-touches). It randomly assigns port to teh wrong devices or double map. You can turn that behavior off. Not Controller,I am talking about theses : Quote Link to comment Share on other sites More sharing options...
sunbrother Posted October 12, 2021 Share Posted October 12, 2021 I understand. You can turn that behavior off. I turned it off myself, as Logic was constantly re-assigning my Faderport and making duplicates. Quote Link to comment Share on other sites More sharing options...
ansolas Posted October 12, 2021 Share Posted October 12, 2021 I understand. You can turn that behavior off. I turned it off myself, as Logic was constantly re-assigning my Faderport and making duplicates. How ? please?! Just checked it right now and it was broken again: Quote Link to comment Share on other sites More sharing options...
sunbrother Posted October 12, 2021 Share Posted October 12, 2021 In that window, toggle New > Automatic Installation Quote Link to comment Share on other sites More sharing options...
ansolas Posted October 12, 2021 Share Posted October 12, 2021 In that window, toggle New > Automatic Installation It is disabled here. Quote Link to comment Share on other sites More sharing options...
JakobP Posted October 15, 2021 Share Posted October 15, 2021 In that window, toggle New > Automatic Installation It is disabled here. Not sure why control surface issues are discussed here ? Your problem seems worthy its own thread... Quote Link to comment Share on other sites More sharing options...
ansolas Posted October 16, 2021 Share Posted October 16, 2021 It is disabled here. Not sure why control surface issues are discussed here ? Your problem seems worthy its own thread... I apologise, you are correct. This is another topic. Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted October 16, 2021 Share Posted October 16, 2021 I apologise, you are correct. This is another topic. Don't hesitate to start a new thread for that topic, so that we can help further troubleshoot it there. Quote Link to comment Share on other sites More sharing options...
rfpm Posted October 19, 2021 Share Posted October 19, 2021 I'm very hands off with Logic these days, moved to Reaper last year but I still check in now and then. From what I'm reading 10.6.3 sounds nearly like a step backwards. Anyone tried out the 10.7 update? Quote Link to comment Share on other sites More sharing options...
en5ca Posted October 19, 2021 Share Posted October 19, 2021 I'm very hands off with Logic these days, moved to Reaper last year but I still check in now and then. From what I'm reading 10.6.3 sounds nearly like a step backwards. Anyone tried out the 10.7 update? According to release notes, nothing has been done. Quote Link to comment Share on other sites More sharing options...
rfpm Posted October 19, 2021 Share Posted October 19, 2021 I'm very hands off with Logic these days, moved to Reaper last year but I still check in now and then. From what I'm reading 10.6.3 sounds nearly like a step backwards. Anyone tried out the 10.7 update? According to release notes, nothing has been done. Very disappointing to hear, oh well. Quote Link to comment Share on other sites More sharing options...
ansolas Posted October 19, 2021 Share Posted October 19, 2021 Just checked it, it is still broken ! Quote Link to comment Share on other sites More sharing options...
ansolas Posted October 19, 2021 Share Posted October 19, 2021 PDC seams to be broken even without sidechain now: Here Just 2 channels of Alchemy. One Panned to hard right the othet hard left. On one I added adaptive Limiter with 200ms Lookahead, to make tging obvious: Quote Link to comment Share on other sites More sharing options...
ansolas Posted October 19, 2021 Share Posted October 19, 2021 Playback seams to be compensated, live is just broken, yes i have enable all Quote Link to comment Share on other sites More sharing options...
en5ca Posted October 19, 2021 Share Posted October 19, 2021 PDC seams to be broken even without sidechain now: Here Just 2 channels of Alchemy. One Panned to hard right the othet hard left. On one I added adaptive Limiter with 200ms Lookahead, to make tging obvious: Unfortunately that seems to be the desired behaviour of Logic when monitoring live inputs through software. Basically making 'record what you hear' impossible with mixed latency input sources. viewtopic.php?f=42&t=152855 Quote Link to comment Share on other sites More sharing options...
ansolas Posted October 19, 2021 Share Posted October 19, 2021 For Virtual Instruments either ? And how do you play a track stack instrument which contains effects which introduce latency ... I doubt that this is intended Quote Link to comment Share on other sites More sharing options...
en5ca Posted October 19, 2021 Share Posted October 19, 2021 For Virtual Instruments either ? And how do you play a track stack instrument which contains effects which introduce latency ... I doubt that this is intended Simple. You don't, at least in sync. But agreed, that probably isn't what they intended, but it's what has been accepted. That's been an issue since early versions of Logic Pro X. Quote Link to comment Share on other sites More sharing options...
ansolas Posted October 20, 2021 Share Posted October 20, 2021 Here another Example. Essentially it is the same example as the previous, but this time I wanted to check how sidechain 'meanwhile' behaves. The result is quite 'funky' to formulate it in a political way. So I added one Alchemy playing a pad sound On thet Track there is a Compressor. Its Sidechaininput is set to another channel with the kick drumsynth on it. Playback sound Ok to me. But here come the funkines. Live playback of all other tracks are now behave as expected! Once I remove the Sidechain Input it get's broken as in the previous videos I showed. Quote Link to comment Share on other sites More sharing options... en5ca Posted October 20, 2021 Share Posted October 20, 2021 Here another Example. Essentially it is the same example as the previous, but this time I wanted to check how sidechain 'meanwhile' behaves.The result is quite 'funky' to formulate it in a political way. So I added one Alchemy playing a pad sound On thet Track there is a Compressor. Its Sidechaininput is set to another channel with the kick drumsynth on it. Playback sound Ok to me. But here come the funkines. Live playback of all other tracks are now behave as expected! Once I remove the Sidechain Input it get's broken as in the previous videos I showed. Quote Link to comment Share on other sites More sharing options... sunbrother Posted October 20, 2021 Share Posted October 20, 2021 For Virtual Instruments either ? And how do you play a track stack instrument which contains effects which introduce latency ... I doubt that this is intended Simple. You don't, at least in sync. But agreed, that probably isn't what they intended, but it's what has been accepted. That's been an issue since early versions of Logic Pro X. Isn't this an issue with a lot of DAWs though? In some DAWs I could have sworn they just deactivate some of the routing when you monitor to prevent this. Mainly asking because I'm trying to keep track of what to avoid in my mixes and most of the stuff earlier in the thread I would run into was fixed throughout 10.6. Also, doesn't Low Latency mode help one work around this by disabling the plugins that cause that latency? Quote Link to comment Share on other sites More sharing options... ansolas Posted October 20, 2021 Share Posted October 20, 2021 Also, doesn't Low Latency mode help one work around this by disabling the plugins that cause that latency? Yes it does. Anyways is the behavior quite unexpected. ?! PDC works for live played instruments when a compressor has a sidechain assiinged to it ?! ?! If we remove that sidechain input live played instruments are no longer compensated ?! Something like this is essential to know, especially when having a huge project. Thing like this can be tricky to find out and solve. Quote Link to comment Share on other sites More sharing options... en5ca Posted October 20, 2021 Share Posted October 20, 2021 Isn't this an issue with a lot of DAWs though? In some DAWs I could have sworn they just deactivate some of the routing when you monitor to prevent this. Mainly asking because I'm trying to keep track of what to avoid in my mixes and most of the stuff earlier in the thread I would run into was fixed throughout 10.6. Also, doesn't Low Latency mode help one work around this by disabling the plugins that cause that latency? That depends on the DAW, and it's 'Low Latency Mode' implementation. Cubase doesn't change the routing, but it bypasses latency inducing plugins from monitored input signal chain to minimize latency while maintaining sync. Ableton and REAPER don't change the routing, they offer the ability to disable PDC for monitored inputs to reduce latency. Studio One and AFAIK Pro Tools bypass plugins and further routing. Logic seems to do all three in Low Latency Mode: bypass plugins, bypass routing and disable PDC in some cases, as shown in ansolas' video. This is perhaps slightly off topic, but regarding to input monitoring the problem with Logic is it does not offer discreet control over PDC while monitoring inputs, and in any case, doesn't properly compensate the monitoring latency to software monitored inputs with or without Low Latency Mode when recording. As shown in ansolas' video, creating the sidechain connection seems to enable PDC on all input monitored tracks without informing the user, or informing that PDC was disabled for monitored inputs in the first place (when in fact it is enabled in the preferences); this should be a global or track preference option, and not depend on the routing. There are some examples on this thread where sidechain PDC isn't working during normal playback in Logic, even after the fix, and when input monitoring is not involved at all. At least Ableton, Cubase and REAPER are able to handle this correctly: maintain sync during playback and recording with software monitoring, compensate recording positions for monitoring latency, and offer user control over whether to use or constrain PDC or not (or bypass plugins/routing) to reduce monitoring latency. What I know to be fixed with Logic is that reordering plugins no longer affects sidechain PDC, and sidechain PDC should work between tracks inside same submix or directly routed to master. What (I think still) should be avoided is sidechaining between different 'layers' or 'depths' of tracks/submixes/buses/groups/stacks/etc when different plugin latencies are involved. Quote Link to comment Share on other sites More sharing options... ansolas Posted October 21, 2021 Share Posted October 21, 2021 [praise] This fader here turns out to be very useful: It lets me easily see in teh muxer which channels exceed the latency threshold. <3 [/praise] So once set to 0 ms you can easily determine the zero latenzy plugins And teh best, LowLatency mode excludes plugins on teh master That way Realphones or ARC3 kept unaffected Quote Link to comment Share on other sites More sharing options... en5ca Posted October 21, 2021 Share Posted October 21, 2021 In Logic Pro, you can choose to apply plug-in latency compensation either to all channel strip types, or to only audio and software instrument channel strips: Audio and software instrument channel strips only: If you insert latency-causing plug-ins only on audio and instrument channel strips, you can choose plug-in latency compensation for only audio and instrument tracks. Logic Pro achieves this by delaying audio and MIDI regions on audio and instrument tracks. This results in snappy playback performance. All channel strip types: If you insert latency-causing plug-ins on aux or output channel strips, you can choose plug-in latency compensation for all types of channel strips. When this setting is turned on, Logic Pro compensates for latency-causing plug-ins by calculating the amount of latency caused by all plug-ins, and then delaying audio streams by an appropriate amount. This type of plug-in latency compensation can result in a slight lag in playback performance, depending on how much latency is being compensated. This is quote from revised(?) Logic Pro 10.7 manual. Now the description of PDC compensation for all channel strip types seems to be correct; delaying individual audio streams between nodes (plugins, split points, etc), causing 'extra lag' to maintain sync. Haven't tested 10.7 yet to see if this has been implemented properly. Quote Link to comment Share on other sites More sharing options... sunbrother Posted October 22, 2021 Share Posted October 22, 2021 In Logic Pro, you can choose to apply plug-in latency compensation either to all channel strip types, or to only audio and software instrument channel strips: Audio and software instrument channel strips only: If you insert latency-causing plug-ins only on audio and instrument channel strips, you can choose plug-in latency compensation for only audio and instrument tracks. Logic Pro achieves this by delaying audio and MIDI regions on audio and instrument tracks. This results in snappy playback performance. All channel strip types: If you insert latency-causing plug-ins on aux or output channel strips, you can choose plug-in latency compensation for all types of channel strips. When this setting is turned on, Logic Pro compensates for latency-causing plug-ins by calculating the amount of latency caused by all plug-ins, and then delaying audio streams by an appropriate amount. This type of plug-in latency compensation can result in a slight lag in playback performance, depending on how much latency is being compensated. This is quote from revised(?) Logic Pro 10.7 manual. Now the description of PDC compensation for all channel strip types seems to be correct; delaying individual audio streams between nodes (plugins, split points, etc), causing 'extra lag' to maintain sync. Haven't tested 10.7 yet to see if this has been implemented properly. Interesting. With a thread this long, it’s getting hard to parse which issues were fixed, which weren’t, which routing configs to avoid. I almost wonder if after 3 years it should have a 10.7 thread for whatever’s left. Quote Link to comment Share on other sites More sharing options... AMD Posted October 24, 2021 Share Posted October 24, 2021 Here another Example. Essentially it is the same example as the previous, but this time I wanted to check how sidechain 'meanwhile' behaves.The result is quite 'funky' to formulate it in a political way. So I added one Alchemy playing a pad sound On thet Track there is a Compressor. Its Sidechaininput is set to another channel with the kick drumsynth on it. Playback sound Ok to me. But here come the funkines. Live playback of all other tracks are now behave as expected! Once I remove the Sidechain Input it get's broken as in the previous videos I showed. Quote Link to comment Share on other sites More sharing options... Martin Schmitt Posted October 24, 2021 Share Posted October 24, 2021 Simply still not working Quote Link to comment Share on other sites More sharing options... Appleeateryumyum Posted October 31, 2021 Share Posted October 31, 2021 i can't believe this issue is been continued 3years straight lol well in my music, side chain function is essential and so most of modern music does seeing this issue never fixed with 3years, i'm not sure staying as a user of LPX is a good choice lol Quote Link to comment Share on other sites More sharing options... Prev 4 5 6 7 8 9 10 11 12 Next Page 9 of 12 Join the conversation You can post now and register later. If you have an account, sign in now to post with your account. Note: Your post will require moderator approval before it will be visible. Reply to this topic... × Pasted as rich text. Restore formatting Only 75 emoji are allowed. × Your link has been automatically embedded. Display as a link instead × Your previous content has been restored. Clear editor × You cannot paste images directly. Upload or insert images from URL. Insert image from URL × Desktop Tablet Phone Submit Reply Share More sharing options... Followers 14 Go to topic listing Related Topics Quick Help - Inspector Pane View - and Plugin Latency Values By tmuzik, August 16, 2020 latency 4 replies 841 views exmachina April 4 Latency delay on armed track Mact Studio M2 Ultra/ UAD Apollo X4 By blvckneon, March 28 uad apollo mac studio (and 2 more) Tagged with: uad apollo mac studio m2 latency 3 replies 135 views JakobP March 29 Heavy Latency on Drummer Track in a session from last year! Help pls. By melodea, March 4 latency 12 replies 220 views Jordi Torres March 5 Latency on OH in Logic Drummer By Kanten, February 6 latency drummer 5 replies 270 views Atlas007 February 8 Sidechain Latency on a Bus Latency Problem still in 2022? By testdriver85, May 30, 2022 sidechain latency 13 replies 3,888 views musikmike January 24 All Activity Home Forums Music Software Bugs & Workarounds Plug-in Delay Compensation broken with external side-chain × Existing user? Sign In Sign Up Home Forums Back Forums Unanswered Topics All Activity Leaderboard Search Our Picks Articles Logic Pro Class Back Logic Pro Class Student Testimonials FAQ Book Back Book in English Livre en Français About Back About Privacy Policy Terms of Service × Create New...
en5ca Posted October 20, 2021 Share Posted October 20, 2021 Here another Example. Essentially it is the same example as the previous, but this time I wanted to check how sidechain 'meanwhile' behaves.The result is quite 'funky' to formulate it in a political way. So I added one Alchemy playing a pad sound On thet Track there is a Compressor. Its Sidechaininput is set to another channel with the kick drumsynth on it. Playback sound Ok to me. But here come the funkines. Live playback of all other tracks are now behave as expected! Once I remove the Sidechain Input it get's broken as in the previous videos I showed. Quote Link to comment Share on other sites More sharing options... sunbrother Posted October 20, 2021 Share Posted October 20, 2021 For Virtual Instruments either ? And how do you play a track stack instrument which contains effects which introduce latency ... I doubt that this is intended Simple. You don't, at least in sync. But agreed, that probably isn't what they intended, but it's what has been accepted. That's been an issue since early versions of Logic Pro X. Isn't this an issue with a lot of DAWs though? In some DAWs I could have sworn they just deactivate some of the routing when you monitor to prevent this. Mainly asking because I'm trying to keep track of what to avoid in my mixes and most of the stuff earlier in the thread I would run into was fixed throughout 10.6. Also, doesn't Low Latency mode help one work around this by disabling the plugins that cause that latency? Quote Link to comment Share on other sites More sharing options... ansolas Posted October 20, 2021 Share Posted October 20, 2021 Also, doesn't Low Latency mode help one work around this by disabling the plugins that cause that latency? Yes it does. Anyways is the behavior quite unexpected. ?! PDC works for live played instruments when a compressor has a sidechain assiinged to it ?! ?! If we remove that sidechain input live played instruments are no longer compensated ?! Something like this is essential to know, especially when having a huge project. Thing like this can be tricky to find out and solve. Quote Link to comment Share on other sites More sharing options... en5ca Posted October 20, 2021 Share Posted October 20, 2021 Isn't this an issue with a lot of DAWs though? In some DAWs I could have sworn they just deactivate some of the routing when you monitor to prevent this. Mainly asking because I'm trying to keep track of what to avoid in my mixes and most of the stuff earlier in the thread I would run into was fixed throughout 10.6. Also, doesn't Low Latency mode help one work around this by disabling the plugins that cause that latency? That depends on the DAW, and it's 'Low Latency Mode' implementation. Cubase doesn't change the routing, but it bypasses latency inducing plugins from monitored input signal chain to minimize latency while maintaining sync. Ableton and REAPER don't change the routing, they offer the ability to disable PDC for monitored inputs to reduce latency. Studio One and AFAIK Pro Tools bypass plugins and further routing. Logic seems to do all three in Low Latency Mode: bypass plugins, bypass routing and disable PDC in some cases, as shown in ansolas' video. This is perhaps slightly off topic, but regarding to input monitoring the problem with Logic is it does not offer discreet control over PDC while monitoring inputs, and in any case, doesn't properly compensate the monitoring latency to software monitored inputs with or without Low Latency Mode when recording. As shown in ansolas' video, creating the sidechain connection seems to enable PDC on all input monitored tracks without informing the user, or informing that PDC was disabled for monitored inputs in the first place (when in fact it is enabled in the preferences); this should be a global or track preference option, and not depend on the routing. There are some examples on this thread where sidechain PDC isn't working during normal playback in Logic, even after the fix, and when input monitoring is not involved at all. At least Ableton, Cubase and REAPER are able to handle this correctly: maintain sync during playback and recording with software monitoring, compensate recording positions for monitoring latency, and offer user control over whether to use or constrain PDC or not (or bypass plugins/routing) to reduce monitoring latency. What I know to be fixed with Logic is that reordering plugins no longer affects sidechain PDC, and sidechain PDC should work between tracks inside same submix or directly routed to master. What (I think still) should be avoided is sidechaining between different 'layers' or 'depths' of tracks/submixes/buses/groups/stacks/etc when different plugin latencies are involved. Quote Link to comment Share on other sites More sharing options... ansolas Posted October 21, 2021 Share Posted October 21, 2021 [praise] This fader here turns out to be very useful: It lets me easily see in teh muxer which channels exceed the latency threshold. <3 [/praise] So once set to 0 ms you can easily determine the zero latenzy plugins And teh best, LowLatency mode excludes plugins on teh master That way Realphones or ARC3 kept unaffected Quote Link to comment Share on other sites More sharing options... en5ca Posted October 21, 2021 Share Posted October 21, 2021 In Logic Pro, you can choose to apply plug-in latency compensation either to all channel strip types, or to only audio and software instrument channel strips: Audio and software instrument channel strips only: If you insert latency-causing plug-ins only on audio and instrument channel strips, you can choose plug-in latency compensation for only audio and instrument tracks. Logic Pro achieves this by delaying audio and MIDI regions on audio and instrument tracks. This results in snappy playback performance. All channel strip types: If you insert latency-causing plug-ins on aux or output channel strips, you can choose plug-in latency compensation for all types of channel strips. When this setting is turned on, Logic Pro compensates for latency-causing plug-ins by calculating the amount of latency caused by all plug-ins, and then delaying audio streams by an appropriate amount. This type of plug-in latency compensation can result in a slight lag in playback performance, depending on how much latency is being compensated. This is quote from revised(?) Logic Pro 10.7 manual. Now the description of PDC compensation for all channel strip types seems to be correct; delaying individual audio streams between nodes (plugins, split points, etc), causing 'extra lag' to maintain sync. Haven't tested 10.7 yet to see if this has been implemented properly. Quote Link to comment Share on other sites More sharing options... sunbrother Posted October 22, 2021 Share Posted October 22, 2021 In Logic Pro, you can choose to apply plug-in latency compensation either to all channel strip types, or to only audio and software instrument channel strips: Audio and software instrument channel strips only: If you insert latency-causing plug-ins only on audio and instrument channel strips, you can choose plug-in latency compensation for only audio and instrument tracks. Logic Pro achieves this by delaying audio and MIDI regions on audio and instrument tracks. This results in snappy playback performance. All channel strip types: If you insert latency-causing plug-ins on aux or output channel strips, you can choose plug-in latency compensation for all types of channel strips. When this setting is turned on, Logic Pro compensates for latency-causing plug-ins by calculating the amount of latency caused by all plug-ins, and then delaying audio streams by an appropriate amount. This type of plug-in latency compensation can result in a slight lag in playback performance, depending on how much latency is being compensated. This is quote from revised(?) Logic Pro 10.7 manual. Now the description of PDC compensation for all channel strip types seems to be correct; delaying individual audio streams between nodes (plugins, split points, etc), causing 'extra lag' to maintain sync. Haven't tested 10.7 yet to see if this has been implemented properly. Interesting. With a thread this long, it’s getting hard to parse which issues were fixed, which weren’t, which routing configs to avoid. I almost wonder if after 3 years it should have a 10.7 thread for whatever’s left. Quote Link to comment Share on other sites More sharing options... AMD Posted October 24, 2021 Share Posted October 24, 2021 Here another Example. Essentially it is the same example as the previous, but this time I wanted to check how sidechain 'meanwhile' behaves.The result is quite 'funky' to formulate it in a political way. So I added one Alchemy playing a pad sound On thet Track there is a Compressor. Its Sidechaininput is set to another channel with the kick drumsynth on it. Playback sound Ok to me. But here come the funkines. Live playback of all other tracks are now behave as expected! Once I remove the Sidechain Input it get's broken as in the previous videos I showed. Quote Link to comment Share on other sites More sharing options... Martin Schmitt Posted October 24, 2021 Share Posted October 24, 2021 Simply still not working Quote Link to comment Share on other sites More sharing options... Appleeateryumyum Posted October 31, 2021 Share Posted October 31, 2021 i can't believe this issue is been continued 3years straight lol well in my music, side chain function is essential and so most of modern music does seeing this issue never fixed with 3years, i'm not sure staying as a user of LPX is a good choice lol Quote Link to comment Share on other sites More sharing options... Prev 4 5 6 7 8 9 10 11 12 Next Page 9 of 12 Join the conversation You can post now and register later. If you have an account, sign in now to post with your account. Note: Your post will require moderator approval before it will be visible. Reply to this topic... × Pasted as rich text. Restore formatting Only 75 emoji are allowed. × Your link has been automatically embedded. Display as a link instead × Your previous content has been restored. Clear editor × You cannot paste images directly. Upload or insert images from URL. Insert image from URL × Desktop Tablet Phone Submit Reply Share More sharing options... Followers 14 Go to topic listing Related Topics Quick Help - Inspector Pane View - and Plugin Latency Values By tmuzik, August 16, 2020 latency 4 replies 841 views exmachina April 4 Latency delay on armed track Mact Studio M2 Ultra/ UAD Apollo X4 By blvckneon, March 28 uad apollo mac studio (and 2 more) Tagged with: uad apollo mac studio m2 latency 3 replies 135 views JakobP March 29 Heavy Latency on Drummer Track in a session from last year! Help pls. By melodea, March 4 latency 12 replies 220 views Jordi Torres March 5 Latency on OH in Logic Drummer By Kanten, February 6 latency drummer 5 replies 270 views Atlas007 February 8 Sidechain Latency on a Bus Latency Problem still in 2022? By testdriver85, May 30, 2022 sidechain latency 13 replies 3,888 views musikmike January 24 All Activity Home Forums Music Software Bugs & Workarounds Plug-in Delay Compensation broken with external side-chain × Existing user? Sign In Sign Up Home Forums Back Forums Unanswered Topics All Activity Leaderboard Search Our Picks Articles Logic Pro Class Back Logic Pro Class Student Testimonials FAQ Book Back Book in English Livre en Français About Back About Privacy Policy Terms of Service × Create New...
sunbrother Posted October 20, 2021 Share Posted October 20, 2021 For Virtual Instruments either ? And how do you play a track stack instrument which contains effects which introduce latency ... I doubt that this is intended Simple. You don't, at least in sync. But agreed, that probably isn't what they intended, but it's what has been accepted. That's been an issue since early versions of Logic Pro X. Isn't this an issue with a lot of DAWs though? In some DAWs I could have sworn they just deactivate some of the routing when you monitor to prevent this. Mainly asking because I'm trying to keep track of what to avoid in my mixes and most of the stuff earlier in the thread I would run into was fixed throughout 10.6. Also, doesn't Low Latency mode help one work around this by disabling the plugins that cause that latency? Quote Link to comment Share on other sites More sharing options...
ansolas Posted October 20, 2021 Share Posted October 20, 2021 Also, doesn't Low Latency mode help one work around this by disabling the plugins that cause that latency? Yes it does. Anyways is the behavior quite unexpected. ?! PDC works for live played instruments when a compressor has a sidechain assiinged to it ?! ?! If we remove that sidechain input live played instruments are no longer compensated ?! Something like this is essential to know, especially when having a huge project. Thing like this can be tricky to find out and solve. Quote Link to comment Share on other sites More sharing options...
en5ca Posted October 20, 2021 Share Posted October 20, 2021 Isn't this an issue with a lot of DAWs though? In some DAWs I could have sworn they just deactivate some of the routing when you monitor to prevent this. Mainly asking because I'm trying to keep track of what to avoid in my mixes and most of the stuff earlier in the thread I would run into was fixed throughout 10.6. Also, doesn't Low Latency mode help one work around this by disabling the plugins that cause that latency? That depends on the DAW, and it's 'Low Latency Mode' implementation. Cubase doesn't change the routing, but it bypasses latency inducing plugins from monitored input signal chain to minimize latency while maintaining sync. Ableton and REAPER don't change the routing, they offer the ability to disable PDC for monitored inputs to reduce latency. Studio One and AFAIK Pro Tools bypass plugins and further routing. Logic seems to do all three in Low Latency Mode: bypass plugins, bypass routing and disable PDC in some cases, as shown in ansolas' video. This is perhaps slightly off topic, but regarding to input monitoring the problem with Logic is it does not offer discreet control over PDC while monitoring inputs, and in any case, doesn't properly compensate the monitoring latency to software monitored inputs with or without Low Latency Mode when recording. As shown in ansolas' video, creating the sidechain connection seems to enable PDC on all input monitored tracks without informing the user, or informing that PDC was disabled for monitored inputs in the first place (when in fact it is enabled in the preferences); this should be a global or track preference option, and not depend on the routing. There are some examples on this thread where sidechain PDC isn't working during normal playback in Logic, even after the fix, and when input monitoring is not involved at all. At least Ableton, Cubase and REAPER are able to handle this correctly: maintain sync during playback and recording with software monitoring, compensate recording positions for monitoring latency, and offer user control over whether to use or constrain PDC or not (or bypass plugins/routing) to reduce monitoring latency. What I know to be fixed with Logic is that reordering plugins no longer affects sidechain PDC, and sidechain PDC should work between tracks inside same submix or directly routed to master. What (I think still) should be avoided is sidechaining between different 'layers' or 'depths' of tracks/submixes/buses/groups/stacks/etc when different plugin latencies are involved. Quote Link to comment Share on other sites More sharing options...
ansolas Posted October 21, 2021 Share Posted October 21, 2021 [praise] This fader here turns out to be very useful: It lets me easily see in teh muxer which channels exceed the latency threshold. <3 [/praise] So once set to 0 ms you can easily determine the zero latenzy plugins And teh best, LowLatency mode excludes plugins on teh master That way Realphones or ARC3 kept unaffected Quote Link to comment Share on other sites More sharing options...
en5ca Posted October 21, 2021 Share Posted October 21, 2021 In Logic Pro, you can choose to apply plug-in latency compensation either to all channel strip types, or to only audio and software instrument channel strips: Audio and software instrument channel strips only: If you insert latency-causing plug-ins only on audio and instrument channel strips, you can choose plug-in latency compensation for only audio and instrument tracks. Logic Pro achieves this by delaying audio and MIDI regions on audio and instrument tracks. This results in snappy playback performance. All channel strip types: If you insert latency-causing plug-ins on aux or output channel strips, you can choose plug-in latency compensation for all types of channel strips. When this setting is turned on, Logic Pro compensates for latency-causing plug-ins by calculating the amount of latency caused by all plug-ins, and then delaying audio streams by an appropriate amount. This type of plug-in latency compensation can result in a slight lag in playback performance, depending on how much latency is being compensated. This is quote from revised(?) Logic Pro 10.7 manual. Now the description of PDC compensation for all channel strip types seems to be correct; delaying individual audio streams between nodes (plugins, split points, etc), causing 'extra lag' to maintain sync. Haven't tested 10.7 yet to see if this has been implemented properly. Quote Link to comment Share on other sites More sharing options...
sunbrother Posted October 22, 2021 Share Posted October 22, 2021 In Logic Pro, you can choose to apply plug-in latency compensation either to all channel strip types, or to only audio and software instrument channel strips: Audio and software instrument channel strips only: If you insert latency-causing plug-ins only on audio and instrument channel strips, you can choose plug-in latency compensation for only audio and instrument tracks. Logic Pro achieves this by delaying audio and MIDI regions on audio and instrument tracks. This results in snappy playback performance. All channel strip types: If you insert latency-causing plug-ins on aux or output channel strips, you can choose plug-in latency compensation for all types of channel strips. When this setting is turned on, Logic Pro compensates for latency-causing plug-ins by calculating the amount of latency caused by all plug-ins, and then delaying audio streams by an appropriate amount. This type of plug-in latency compensation can result in a slight lag in playback performance, depending on how much latency is being compensated. This is quote from revised(?) Logic Pro 10.7 manual. Now the description of PDC compensation for all channel strip types seems to be correct; delaying individual audio streams between nodes (plugins, split points, etc), causing 'extra lag' to maintain sync. Haven't tested 10.7 yet to see if this has been implemented properly. Interesting. With a thread this long, it’s getting hard to parse which issues were fixed, which weren’t, which routing configs to avoid. I almost wonder if after 3 years it should have a 10.7 thread for whatever’s left. Quote Link to comment Share on other sites More sharing options...
AMD Posted October 24, 2021 Share Posted October 24, 2021 Here another Example. Essentially it is the same example as the previous, but this time I wanted to check how sidechain 'meanwhile' behaves.The result is quite 'funky' to formulate it in a political way. So I added one Alchemy playing a pad sound On thet Track there is a Compressor. Its Sidechaininput is set to another channel with the kick drumsynth on it. Playback sound Ok to me. But here come the funkines. Live playback of all other tracks are now behave as expected! Once I remove the Sidechain Input it get's broken as in the previous videos I showed. Quote Link to comment Share on other sites More sharing options... Martin Schmitt Posted October 24, 2021 Share Posted October 24, 2021 Simply still not working Quote Link to comment Share on other sites More sharing options... Appleeateryumyum Posted October 31, 2021 Share Posted October 31, 2021 i can't believe this issue is been continued 3years straight lol well in my music, side chain function is essential and so most of modern music does seeing this issue never fixed with 3years, i'm not sure staying as a user of LPX is a good choice lol Quote Link to comment Share on other sites More sharing options... Prev 4 5 6 7 8 9 10 11 12 Next Page 9 of 12 Join the conversation You can post now and register later. If you have an account, sign in now to post with your account. Note: Your post will require moderator approval before it will be visible. Reply to this topic... × Pasted as rich text. Restore formatting Only 75 emoji are allowed. × Your link has been automatically embedded. Display as a link instead × Your previous content has been restored. Clear editor × You cannot paste images directly. Upload or insert images from URL. Insert image from URL × Desktop Tablet Phone Submit Reply Share More sharing options... Followers 14 Go to topic listing Related Topics Quick Help - Inspector Pane View - and Plugin Latency Values By tmuzik, August 16, 2020 latency 4 replies 841 views exmachina April 4 Latency delay on armed track Mact Studio M2 Ultra/ UAD Apollo X4 By blvckneon, March 28 uad apollo mac studio (and 2 more) Tagged with: uad apollo mac studio m2 latency 3 replies 135 views JakobP March 29 Heavy Latency on Drummer Track in a session from last year! Help pls. By melodea, March 4 latency 12 replies 220 views Jordi Torres March 5 Latency on OH in Logic Drummer By Kanten, February 6 latency drummer 5 replies 270 views Atlas007 February 8 Sidechain Latency on a Bus Latency Problem still in 2022? By testdriver85, May 30, 2022 sidechain latency 13 replies 3,888 views musikmike January 24 All Activity Home Forums Music Software Bugs & Workarounds Plug-in Delay Compensation broken with external side-chain
Martin Schmitt Posted October 24, 2021 Share Posted October 24, 2021 Simply still not working Quote Link to comment Share on other sites More sharing options...
Appleeateryumyum Posted October 31, 2021 Share Posted October 31, 2021 i can't believe this issue is been continued 3years straight lol well in my music, side chain function is essential and so most of modern music does seeing this issue never fixed with 3years, i'm not sure staying as a user of LPX is a good choice lol Quote Link to comment Share on other sites More sharing options...
Recommended Posts