juanmooreraps Posted January 13, 2016 Share Posted January 13, 2016 Very simple, every time I split an audio region, the region to the right of the split shifts over to the right and sometimes the left a bunch of samples. Now I read to change my drag mode to overlap, but for some reason that hasn't helped. This has made my audio editing nearly impossible because everything is falling out of sync so easily. Is there a fix for this? Im pretty sure I have a bug going on. Im running Logic x 10.2 on yosemite. Still have logic 9 installed. Going crazy, been trying to fix this for weeks, about to burn my computer. Thanks. Quote Link to comment Share on other sites More sharing options...
Eric Cardenas Posted January 13, 2016 Share Posted January 13, 2016 It sounds to me like you are experiencing this bug: Audio Regions moving when cutting [bUG] Quote Link to comment Share on other sites More sharing options...
juanmooreraps Posted January 13, 2016 Author Share Posted January 13, 2016 It sounds to me like you are experiencing this bug: Audio Regions moving when cutting [bUG] You know I just saw your post and hoped that there was a fix but it just seems we gotta wait for the next update then? Any workarounds? Im thinking of going back to 9 but logic x just sounds so much better. Quote Link to comment Share on other sites More sharing options...
Eric Cardenas Posted January 13, 2016 Share Posted January 13, 2016 Let Apple know about this issue, they are the ones that can make it happen: Apple - Logic Pro - Feedback Quote Link to comment Share on other sites More sharing options...
juanmooreraps Posted January 13, 2016 Author Share Posted January 13, 2016 yep will do, I actually talked to a guy the other day so im gonna give him a call back and report it. The only workaround ive seen is to copy and paste, and use the trim function to edit that one specific audio piece... Quote Link to comment Share on other sites More sharing options...
jimdilian Posted September 3, 2017 Share Posted September 3, 2017 Logic Pro X 10.3.2 .. and this BUG stills there.. almost impossible to work this way.. everything is out of synchronization ... I won't if they will ever fix this.. or maybe in Logic Pro X 11 . Quote Link to comment Share on other sites More sharing options...
triplets Posted September 3, 2017 Share Posted September 3, 2017 Logic Pro X 10.3.2 .. and this BUG stills there.. almost impossible to work this way.. everything is out of synchronization ... I won't if they will ever fix this.. or maybe in Logic Pro X 11 . Not happening here. Quote Link to comment Share on other sites More sharing options...
jimdilian Posted September 6, 2017 Share Posted September 6, 2017 Logic Pro X 10.3.2 .. and this BUG stills there.. almost impossible to work this way.. everything is out of synchronization ... I won't if they will ever fix this.. or maybe in Logic Pro X 11 . Not happening here. all logic users have that bug.. no matter if it appears in your song or not.. you have it. this is a bug. that exists in every logic version. Quote Link to comment Share on other sites More sharing options...
Kim Olesen Posted September 6, 2017 Share Posted September 6, 2017 Isn't it only the display of the waveform that changes? I haven't noticed anything going out of phase. Quote Link to comment Share on other sites More sharing options...
kerochan Posted September 6, 2017 Share Posted September 6, 2017 Logic Pro X 10.3.2 .. and this BUG stills there.. almost impossible to work this way.. everything is out of synchronization ... I won't if they will ever fix this.. or maybe in Logic Pro X 11 . Not happening here. Not happening here either! Quote Link to comment Share on other sites More sharing options...
Kim Olesen Posted September 6, 2017 Share Posted September 6, 2017 Easily testable: Take a full mix wav file. Place it on two tracks starting on the first bar. . Split onlLy one of them on bar number two. If it still sounds in ohase after the split, then it is only a graphical bug. Remember to turn the master volume down. Two tracks of the exact same volume will sound twice as loud. Quote Link to comment Share on other sites More sharing options...
jimdilian Posted January 11, 2018 Share Posted January 11, 2018 Quote Link to comment Share on other sites More sharing options...
TelecasterTubes Posted January 11, 2018 Share Posted January 11, 2018 Is snap edits to zero crossing on? (snap drop down menu) Quote Link to comment Share on other sites More sharing options...
jimdilian Posted January 14, 2018 Share Posted January 14, 2018 Is snap edits to zero crossing on? (snap drop down menu) no matter what snap you have selected.. it will happen.. I had try with all. and all setting I can imagine. I had report this BUG like 20 times.. in 2 years.. or 3.. or 4.. please somebody else report this BUG too in.. Logic Feedback. Please.. Quote Link to comment Share on other sites More sharing options...
maceasy Posted January 14, 2018 Share Posted January 14, 2018 Are you sure you don't have snap to relative value on? It should be set to snap to absolute values. And it should be set to ticks or samples. Quote Link to comment Share on other sites More sharing options...
jimdilian Posted January 14, 2018 Share Posted January 14, 2018 Are you sure you don't have snap to relative value on? It should be set to snap to absolute values. And it should be set to ticks or samples. yeap tried both ways.. it happens both ways. all ways.. Quote Link to comment Share on other sites More sharing options...
maceasy Posted January 15, 2018 Share Posted January 15, 2018 Well I can’t replicate your video Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted January 15, 2018 Share Posted January 15, 2018 I can't replicate here either, even with a tempo of 151 and sample rate of 48kHz, Snap set to Smart. Out of curiosity, what happens if you turn Snap off? Quote Link to comment Share on other sites More sharing options...
jimdilian Posted January 15, 2018 Share Posted January 15, 2018 I can't replicate here either, even with a tempo of 151 and sample rate of 48kHz, Snap set to Smart. Out of curiosity, what happens if you turn Snap off? can you replicate this one ? Quote Link to comment Share on other sites More sharing options... David Nahmani Posted January 15, 2018 Share Posted January 15, 2018 I can't really see what you're doing or what result is wrong in the video... Quote Link to comment Share on other sites More sharing options... jimdilian Posted January 15, 2018 Share Posted January 15, 2018 I can't really see what you're doing or what result is wrong in the video... ok, just follow the steps from the instructions of the header of this post, and you will see the bug. this bug is there.. not fixed yet. I wonder if they will ever fix it. Quote Link to comment Share on other sites More sharing options... David Nahmani Posted January 15, 2018 Share Posted January 15, 2018 ok, just follow the steps from the instructions of the header of this post, and you will see the bug.this bug is there.. not fixed yet. I wonder if they will ever fix it. Oh ok I was finally able to replicate. It seems like a region needs to be at least 4 ticks long, so if you try to create a cut that would result in a smaller region, Logic lengthens the second region so it's at least 4 tick long. Quote Link to comment Share on other sites More sharing options... Kim Olesen Posted January 16, 2018 Share Posted January 16, 2018 Easily testable:Take a full mix wav file. Place it on two tracks starting on the first bar. . Split onlLy one of them on bar number two. If it still sounds in ohase after the split, then it is only a graphical bug. Remember to turn the master volume down. Two tracks of the exact same volume will sound twice as loud. Just reminding everyone. Quote Link to comment Share on other sites More sharing options... JakobP Posted January 16, 2018 Share Posted January 16, 2018 Maybe the title of this thread should be changed, or maybe split it, since it seems to address two different issues ? Quote Link to comment Share on other sites More sharing options... 2 weeks later... jimdilian Posted January 26, 2018 Share Posted January 26, 2018 Not Fixed in 10.4 =( Quote Link to comment Share on other sites More sharing options... maceasy Posted January 26, 2018 Share Posted January 26, 2018 If it only applies to regions 4 ticks long it isn’t a problem, maybe not a bug, but a limitation. Either way, not an issue really. Quote Link to comment Share on other sites More sharing options... jimdilian Posted January 26, 2018 Share Posted January 26, 2018 If it only applies to regions 4 ticks long it isn’t a problem, maybe not a bug, but a limitation. Either way, not an issue really. No it does not happen only with " 4 ticks long " Quote Link to comment Share on other sites More sharing options... maceasy Posted January 26, 2018 Share Posted January 26, 2018 See David’s post above. Quote Link to comment Share on other sites More sharing options... David Nahmani Posted January 26, 2018 Share Posted January 26, 2018 No it does not happen only with " 4 ticks long " Then can you give one specific set of steps to reproduce? For example stating exactly at what position the playhead is when you cut etc...? I've tried but cannot reproduce what I see in your videos. Quote Link to comment Share on other sites More sharing options... jimdilian Posted January 27, 2018 Share Posted January 27, 2018 No it does not happen only with " 4 ticks long " Then can you give one specific set of steps to reproduce? For example stating exactly at what position the playhead is when you cut etc...? I've tried but cannot reproduce what I see in your videos. Shure I'm on 24bits / 48 khz always, strange__ this bug drives me nuts the Bug starts at min 2:50 Quote Link to comment Share on other sites More sharing options... Prev 1 2 Next Page 1 of 2 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 0 Go to topic listing
David Nahmani Posted January 15, 2018 Share Posted January 15, 2018 I can't really see what you're doing or what result is wrong in the video... Quote Link to comment Share on other sites More sharing options...
jimdilian Posted January 15, 2018 Share Posted January 15, 2018 I can't really see what you're doing or what result is wrong in the video... ok, just follow the steps from the instructions of the header of this post, and you will see the bug. this bug is there.. not fixed yet. I wonder if they will ever fix it. Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted January 15, 2018 Share Posted January 15, 2018 ok, just follow the steps from the instructions of the header of this post, and you will see the bug.this bug is there.. not fixed yet. I wonder if they will ever fix it. Oh ok I was finally able to replicate. It seems like a region needs to be at least 4 ticks long, so if you try to create a cut that would result in a smaller region, Logic lengthens the second region so it's at least 4 tick long. Quote Link to comment Share on other sites More sharing options...
Kim Olesen Posted January 16, 2018 Share Posted January 16, 2018 Easily testable:Take a full mix wav file. Place it on two tracks starting on the first bar. . Split onlLy one of them on bar number two. If it still sounds in ohase after the split, then it is only a graphical bug. Remember to turn the master volume down. Two tracks of the exact same volume will sound twice as loud. Just reminding everyone. Quote Link to comment Share on other sites More sharing options...
JakobP Posted January 16, 2018 Share Posted January 16, 2018 Maybe the title of this thread should be changed, or maybe split it, since it seems to address two different issues ? Quote Link to comment Share on other sites More sharing options...
jimdilian Posted January 26, 2018 Share Posted January 26, 2018 Not Fixed in 10.4 =( Quote Link to comment Share on other sites More sharing options...
maceasy Posted January 26, 2018 Share Posted January 26, 2018 If it only applies to regions 4 ticks long it isn’t a problem, maybe not a bug, but a limitation. Either way, not an issue really. Quote Link to comment Share on other sites More sharing options...
jimdilian Posted January 26, 2018 Share Posted January 26, 2018 If it only applies to regions 4 ticks long it isn’t a problem, maybe not a bug, but a limitation. Either way, not an issue really. No it does not happen only with " 4 ticks long " Quote Link to comment Share on other sites More sharing options...
maceasy Posted January 26, 2018 Share Posted January 26, 2018 See David’s post above. Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted January 26, 2018 Share Posted January 26, 2018 No it does not happen only with " 4 ticks long " Then can you give one specific set of steps to reproduce? For example stating exactly at what position the playhead is when you cut etc...? I've tried but cannot reproduce what I see in your videos. Quote Link to comment Share on other sites More sharing options...
jimdilian Posted January 27, 2018 Share Posted January 27, 2018 No it does not happen only with " 4 ticks long " Then can you give one specific set of steps to reproduce? For example stating exactly at what position the playhead is when you cut etc...? I've tried but cannot reproduce what I see in your videos. Shure I'm on 24bits / 48 khz always, strange__ this bug drives me nuts the Bug starts at min 2:50 Quote Link to comment Share on other sites More sharing options...
Recommended Posts