jimdilian Posted January 27, 2018 Share Posted January 27, 2018 I can't really see what you're doing or what result is wrong in the video... why ? just using commands to move the "playhead" selectting all inside loop duplicate -- move and SPLIT and it stars happening_ Quote Link to comment Share on other sites More sharing options...
jimdilian Posted January 27, 2018 Share Posted January 27, 2018 I can't really see what you're doing or what result is wrong in the video... I ain't doing anything wrong man_ really you can' see it ? wow_ ok. min 2:50 when you select all tracks and split by play head-- the shift positions_ Quote Link to comment Share on other sites More sharing options...
jimdilian Posted January 27, 2018 Share Posted January 27, 2018 I have a new_ way to reproduce this very STRANGE_ bug, steps_ 1_ create a new "empty project from logic templates" 2_ enable cycle mode_ and set the tempo to 199. and add a audio track and record audio 3_ duplicate the track 4_ record on the second track_ 5_ select all in the main windows with command duplicate selectiion 6_ zoom a lot and see the end zones recorded_ how they start to shift position the more you duplicate them_ in the end of the zones the more they start "shifting". video showing the BUG Quote Link to comment Share on other sites More sharing options...
TelecasterTubes Posted January 27, 2018 Share Posted January 27, 2018 Don't know if this is only a graphical bug, but easily reproduced here.... Strangely only at 199 198 does not show this behaviour (or 129 etc.) Quote Link to comment Share on other sites More sharing options...
jimdilian Posted February 10, 2018 Share Posted February 10, 2018 if you want to split by playhead - while playing the audio it does shift the audio file too---- arggg... apple apple. 5 years with this BUG, argg. Quote Link to comment Share on other sites More sharing options...
loopsinner Posted February 13, 2018 Share Posted February 13, 2018 Have you reported this to Apple? If it's a bug you can easily reproduce, just send your feedback at https://www.apple.com/feedback/logic-pro.html I have had some luck with Apple engineer contacting me back regarding a bug that i could easily reproduce. It took him less than 48 hours to contact me back after i reported using the support form. Quote Link to comment Share on other sites More sharing options...
jimdilian Posted February 14, 2018 Share Posted February 14, 2018 Have you reported this to Apple? If it's a bug you can easily reproduce, just send your feedback at https://www.apple.com/feedback/logic-pro.html I have had some luck with Apple engineer contacting me back regarding a bug that i could easily reproduce. It took him less than 48 hours to contact me back after i reported using the support form. yes like 30 times I had reported_ and 3 times they ask me for everything and send everything no further response after that. for this bug. Quote Link to comment Share on other sites More sharing options...
jimdilian Posted December 20, 2018 Share Posted December 20, 2018 not fixed in 10.4.3 Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted December 20, 2018 Share Posted December 20, 2018 I can't really see what you're doing or what result is wrong in the video... I ain't doing anything wrong man_ really you can' see it ? No, in your first video and without further explanations I cannot see what you're doing, or what result is wrong. For example, for all I know, you keep pasting a little region at the playhead position. I'll have a look at the more recent video you've posted. Quote Link to comment Share on other sites More sharing options...
jimdilian Posted January 11, 2019 Share Posted January 11, 2019 I ain't doing anything wrong man_ really you can' see it ? No, in your first video and without further explanations I cannot see what you're doing, or what result is wrong. For example, for all I know, you keep pasting a little region at the playhead position. I'll have a look at the more recent video you've posted. I am doing the same as the Instructions of this BUG tells how to replicate the BUG.. you can do it your self if you follow the instruccion at the begining of the Post. Quote Link to comment Share on other sites More sharing options...
vanhaze Posted January 11, 2019 Share Posted January 11, 2019 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... fisherking Posted January 11, 2019 Share Posted January 11, 2019 No, in your first video and without further explanations I cannot see what you're doing, or what result is wrong. For example, for all I know, you keep pasting a little region at the playhead position. I'll have a look at the more recent video you've posted. I am doing the same as the Instructions of this BUG tells how to replicate the BUG.. you can do it your self if you follow the instruccion at the begining of the Post. it's not a bug unless everyone (or even, almost everyone) has it; it's a problem you're having. go easy on the people here, this is a good forum. perhaps someone can help sort it out. good luck with it! Quote Link to comment Share on other sites More sharing options... Eriksimon Posted January 11, 2019 Share Posted January 11, 2019 4 bars at 199 BPM at 44.1 kHz is exactly 212743,718592964824121 samples long. I believe 1 sample is the lowest quantisation unit in Logic. So there's a rounding error. When I cut my recorded region the audio bin tells me it is 212744 samples long, so (about) 0.281 samples longer. Copy that eleven times and there's a difference of roughly 3 samples. Hundred times, 28 samples - which is less than one millisecond. I'd say, snip off one sample every three or four bars - or use a different BPM. At 200 BPM there is no rounding error: 4 bars at 200 BPM at 44.1 kHz is exactly 211680 samples long (I suspect that all BPM's that are a prime numbers may suffer from this not-really-a-bug-but-a-matter-of-math - but I'm not a mathematician, I just know how to use a calculator). Quote Link to comment Share on other sites More sharing options... jimdilian Posted January 12, 2019 Share Posted January 12, 2019 I am doing the same as the Instructions of this BUG tells how to replicate the BUG.. you can do it your self if you follow the instruccion at the begining of the Post. it's not a bug unless everyone (or even, almost everyone) has it; it's a problem you're having. go easy on the people here, this is a good forum. perhaps someone can help sort it out. good luck with it! noup.. you are wrong. it is a bug and a lot of users have it.. depending of your workflow.. you will have it more or less.. maybe not have it.. just follow the instruccions.. it is easy.. go easy on the people here, ??? what?? ha.. come on. how is raising the voice..??????????.. go easy? hahaha.. what do you mean?? maybe because in my original language we speak more directly.. and when I write in english.. you get miss undertood.. or some one.. Quote Link to comment Share on other sites More sharing options... fisherking Posted January 12, 2019 Share Posted January 12, 2019 it's not a bug unless everyone (or even, almost everyone) has it; it's a problem you're having. go easy on the people here, this is a good forum. perhaps someone can help sort it out. good luck with it! noup.. you are wrong. it is a bug and a lot of users have it.. depending of your workflow.. you will have it more or less.. maybe not have it.. just follow the instruccions.. it is easy.. go easy on the people here, ??? what?? ha.. come on. how is raising the voice..??????????.. go easy? hahaha.. what do you mean?? maybe because in my original language we speak more directly.. and when I write in english.. you get miss undertood.. or some one.. i've been using logic for over a decade, and don't have that 'bug'. so, i will go back to work, and you can go back to posting the same thing over and over. hopefully, you will catch your breath, see that smart people here are trying to help... and get past this, so you too can go back to making music. good luck! Quote Link to comment Share on other sites More sharing options... Eriksimon Posted January 12, 2019 Share Posted January 12, 2019 4 bars at 199 BPM at 44.1 kHz is exactly 212743,718592964824121 samples long. I believe 1 sample is the lowest quantisation unit in Logic. So there's a rounding error. When I cut my recorded region the audio bin tells me it is 212744 samples long, so (about) 0.281 samples longer. Copy that eleven times and there's a difference of roughly 3 samples. Hundred times, 28 samples - which is less than one millisecond. I'd say, snip off one sample every three or four bars - or use a different BPM. At 200 BPM there is no rounding error: 4 bars at 200 BPM at 44.1 kHz is exactly 211680 samples long (I suspect that all BPM's that are a prime numbers may suffer from this not-really-a-bug-but-a-matter-of-math - but I'm not a mathematician, I just know how to use a calculator). please respond. Quote Link to comment Share on other sites More sharing options... TelecasterTubes Posted January 12, 2019 Share Posted January 12, 2019 viewtopic.php?f=1&t=135969 Quote Link to comment Share on other sites More sharing options... fisherking Posted January 12, 2019 Share Posted January 12, 2019 https://www.logicprohelp.com/viewtopic.php?f=1&t=135969 ha, also explains my deja vu... Quote Link to comment Share on other sites More sharing options... TelecasterTubes Posted January 12, 2019 Share Posted January 12, 2019 People in the know: "It’s an ugly bug for sure" (Eric C.) It bothers some people more than others and there is a workaround, but it probably would be better if this got fixed one of these days.... Quote Link to comment Share on other sites More sharing options... jimdilian Posted January 13, 2019 Share Posted January 13, 2019 noup.. you are wrong. it is a bug and a lot of users have it.. depending of your workflow.. you will have it more or less.. maybe not have it.. just follow the instruccions.. it is easy.. go easy on the people here, ??? what?? ha.. come on. how is raising the voice..??????????.. go easy? hahaha.. what do you mean?? maybe because in my original language we speak more directly.. and when I write in english.. you get miss undertood.. or some one.. i've been using logic for over a decade, and don't have that 'bug'. so, i will go back to work, and you can go back to posting the same thing over and over. hopefully, you will catch your breath, see that smart people here are trying to help... and get past this, so you too can go back to making music. good luck! I am working too.... hahaha.. what's your point ? .. that does not stop me.. and here I've been using logic for 10 years too.. so?? what's your point there too ? what does that has to do with the BUG ??... just because you have not experience that BUG yet.. does not mean other users are experiencing that BUG.. ? anyway.. I will not reply you .. your mm... attitude.. it is very.. mm.. like.. m.. "apple YES it is perfect.. there are no bugs here.. " I am just reporting a BUG.. that affects me.. and many others too.. for several years NOW. and apple don't fix this BUG.. simple.. what is wrong with complaining? so we cannot TALK about it ?.. say a word about that BUG ?.. why not ?... we have to posted.. and let apple finally FIX that bug. reported.. etc etc.. and yes --- this place it is great .. logicprohelp.. that is why I am here... here we talk about BUGS too. anyway. Quote Link to comment Share on other sites More sharing options... 2 years later... jimdilian Posted April 28, 2021 Share Posted April 28, 2021 10.6.2 update BUG not fixed Quote Link to comment Share on other sites More sharing options... 8 months later... Bk2 Posted January 2, 2022 Share Posted January 2, 2022 I found a work around Turn on flexi time. Set a marker and then cut in that marker the sample wave form won't shift led or right. Quote Link to comment Share on other sites More sharing options... Prev 1 2 Next Page 2 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 All Activity Home Forums Music Software Logic Pro Audio region wave form shifting to the right after split
fisherking Posted January 11, 2019 Share Posted January 11, 2019 No, in your first video and without further explanations I cannot see what you're doing, or what result is wrong. For example, for all I know, you keep pasting a little region at the playhead position. I'll have a look at the more recent video you've posted. I am doing the same as the Instructions of this BUG tells how to replicate the BUG.. you can do it your self if you follow the instruccion at the begining of the Post. it's not a bug unless everyone (or even, almost everyone) has it; it's a problem you're having. go easy on the people here, this is a good forum. perhaps someone can help sort it out. good luck with it! Quote Link to comment Share on other sites More sharing options...
Eriksimon Posted January 11, 2019 Share Posted January 11, 2019 4 bars at 199 BPM at 44.1 kHz is exactly 212743,718592964824121 samples long. I believe 1 sample is the lowest quantisation unit in Logic. So there's a rounding error. When I cut my recorded region the audio bin tells me it is 212744 samples long, so (about) 0.281 samples longer. Copy that eleven times and there's a difference of roughly 3 samples. Hundred times, 28 samples - which is less than one millisecond. I'd say, snip off one sample every three or four bars - or use a different BPM. At 200 BPM there is no rounding error: 4 bars at 200 BPM at 44.1 kHz is exactly 211680 samples long (I suspect that all BPM's that are a prime numbers may suffer from this not-really-a-bug-but-a-matter-of-math - but I'm not a mathematician, I just know how to use a calculator). Quote Link to comment Share on other sites More sharing options...
jimdilian Posted January 12, 2019 Share Posted January 12, 2019 I am doing the same as the Instructions of this BUG tells how to replicate the BUG.. you can do it your self if you follow the instruccion at the begining of the Post. it's not a bug unless everyone (or even, almost everyone) has it; it's a problem you're having. go easy on the people here, this is a good forum. perhaps someone can help sort it out. good luck with it! noup.. you are wrong. it is a bug and a lot of users have it.. depending of your workflow.. you will have it more or less.. maybe not have it.. just follow the instruccions.. it is easy.. go easy on the people here, ??? what?? ha.. come on. how is raising the voice..??????????.. go easy? hahaha.. what do you mean?? maybe because in my original language we speak more directly.. and when I write in english.. you get miss undertood.. or some one.. Quote Link to comment Share on other sites More sharing options...
fisherking Posted January 12, 2019 Share Posted January 12, 2019 it's not a bug unless everyone (or even, almost everyone) has it; it's a problem you're having. go easy on the people here, this is a good forum. perhaps someone can help sort it out. good luck with it! noup.. you are wrong. it is a bug and a lot of users have it.. depending of your workflow.. you will have it more or less.. maybe not have it.. just follow the instruccions.. it is easy.. go easy on the people here, ??? what?? ha.. come on. how is raising the voice..??????????.. go easy? hahaha.. what do you mean?? maybe because in my original language we speak more directly.. and when I write in english.. you get miss undertood.. or some one.. i've been using logic for over a decade, and don't have that 'bug'. so, i will go back to work, and you can go back to posting the same thing over and over. hopefully, you will catch your breath, see that smart people here are trying to help... and get past this, so you too can go back to making music. good luck! Quote Link to comment Share on other sites More sharing options...
Eriksimon Posted January 12, 2019 Share Posted January 12, 2019 4 bars at 199 BPM at 44.1 kHz is exactly 212743,718592964824121 samples long. I believe 1 sample is the lowest quantisation unit in Logic. So there's a rounding error. When I cut my recorded region the audio bin tells me it is 212744 samples long, so (about) 0.281 samples longer. Copy that eleven times and there's a difference of roughly 3 samples. Hundred times, 28 samples - which is less than one millisecond. I'd say, snip off one sample every three or four bars - or use a different BPM. At 200 BPM there is no rounding error: 4 bars at 200 BPM at 44.1 kHz is exactly 211680 samples long (I suspect that all BPM's that are a prime numbers may suffer from this not-really-a-bug-but-a-matter-of-math - but I'm not a mathematician, I just know how to use a calculator). please respond. Quote Link to comment Share on other sites More sharing options...
TelecasterTubes Posted January 12, 2019 Share Posted January 12, 2019 viewtopic.php?f=1&t=135969 Quote Link to comment Share on other sites More sharing options...
fisherking Posted January 12, 2019 Share Posted January 12, 2019 https://www.logicprohelp.com/viewtopic.php?f=1&t=135969 ha, also explains my deja vu... Quote Link to comment Share on other sites More sharing options...
TelecasterTubes Posted January 12, 2019 Share Posted January 12, 2019 People in the know: "It’s an ugly bug for sure" (Eric C.) It bothers some people more than others and there is a workaround, but it probably would be better if this got fixed one of these days.... Quote Link to comment Share on other sites More sharing options...
jimdilian Posted January 13, 2019 Share Posted January 13, 2019 noup.. you are wrong. it is a bug and a lot of users have it.. depending of your workflow.. you will have it more or less.. maybe not have it.. just follow the instruccions.. it is easy.. go easy on the people here, ??? what?? ha.. come on. how is raising the voice..??????????.. go easy? hahaha.. what do you mean?? maybe because in my original language we speak more directly.. and when I write in english.. you get miss undertood.. or some one.. i've been using logic for over a decade, and don't have that 'bug'. so, i will go back to work, and you can go back to posting the same thing over and over. hopefully, you will catch your breath, see that smart people here are trying to help... and get past this, so you too can go back to making music. good luck! I am working too.... hahaha.. what's your point ? .. that does not stop me.. and here I've been using logic for 10 years too.. so?? what's your point there too ? what does that has to do with the BUG ??... just because you have not experience that BUG yet.. does not mean other users are experiencing that BUG.. ? anyway.. I will not reply you .. your mm... attitude.. it is very.. mm.. like.. m.. "apple YES it is perfect.. there are no bugs here.. " I am just reporting a BUG.. that affects me.. and many others too.. for several years NOW. and apple don't fix this BUG.. simple.. what is wrong with complaining? so we cannot TALK about it ?.. say a word about that BUG ?.. why not ?... we have to posted.. and let apple finally FIX that bug. reported.. etc etc.. and yes --- this place it is great .. logicprohelp.. that is why I am here... here we talk about BUGS too. anyway. Quote Link to comment Share on other sites More sharing options...
jimdilian Posted April 28, 2021 Share Posted April 28, 2021 10.6.2 update BUG not fixed Quote Link to comment Share on other sites More sharing options...
Bk2 Posted January 2, 2022 Share Posted January 2, 2022 I found a work around Turn on flexi time. Set a marker and then cut in that marker the sample wave form won't shift led or right. Quote Link to comment Share on other sites More sharing options...
Recommended Posts