Inaccurate loop length

Report bugs to the developers. Detail conditions under which bugs happen, and discuss suggested workarounds.

Inaccurate loop length

Postby darudevil » Mon Aug 15, 2011 12:51 pm

Could someone please explain to me why does this happen, or if I'm doing something wrong, so I can fix it?

1) I take 5 kick samples, put them on 1,2,3,4 on the first bar, then 1 on the second bar.
2) I merge them.
3) I cut the loop at the second bar first beat, to make a 4 kick loop (to be used as sidechain trigger in this case; and yeah, I know I can use sampler etc, but that's beside my point). Logic shows it's cutting exactly on bar 2 first beat and the length is 1 bar.
4) I loop this over the whole track, say 200-300 bars.
5) I zoom in on bar 310 and I see that the kick is not accurately on the beat anymore. The difference is small, sure, but it IS off, which bugs the sh!t out of me!! And it does trigger the sidechain early.
6) I've tried to tweak the loop/region length in arrangement and sample editor to make it accurately EXACTLY one bar, but the loop is pretty much always off by some fraction. What the hell am I missing here? I'm using Smart Snapping, but I've tried other options too, to no avail.
7) When I Convert Loops To Real Copies, the ones later in the arrangement, after 200 bars start being of by one, two, three, even 5 ticks the further the time goes. (So it's not just a visual thing, but actual timing issue)
You do not have the required permissions to view the files attached to this post.
Last edited by darudevil on Mon Aug 15, 2011 12:55 pm, edited 1 time in total.
Ville

LP 9.1.8, MP Octo 2,93GHz, 12Gb, 10.6.8, MOTU UltraLite, Novation ReMOTE 49SL Compact, MBP 17" Quad 2.3GHz
Darude.com - SoundCloud - YouTube
User avatar
darudevil
 
Posts: 274
Joined: Thu Jan 05, 2006 10:49 am
Location: Turku, Finland

 

Postby ski » Mon Aug 15, 2011 12:54 pm

MacPro 8 Core 2.4 Xeon | 32G RAM | OSX 10.6.8 | Logic 9.1.7 | RME FF800 | 3 monitors | Toys for days
User avatar
ski
Site Contributor
 
Posts: 15673
Joined: Thu Dec 15, 2005 5:12 pm
Location: Los Angeles

Re: Inaccurate loop length

Postby David » Mon Aug 15, 2011 1:00 pm

darudevil wrote:Logic shows it's cutting exactly on bar 2 first beat and the length is 1 bar.


Make sure there's not a dot after the length numbers. You can click-hold the region to see if it's 1 0 0 0 (exactly one bar) or 1 0 0 0. (not exactly one bar).

I use the Marquee tool to quickly cut regions to an exact number of bars.
 Certified Logic Studio Master Trainer
Author of Logic Express 9 and Logic Pro 9, Apple Pro Training Series
Logic Pro 9.1.8 - Mac OS 10.7.4 - Mac Pro 8 core 2.8 GHz Intel Xeon - 6GB RAM - Metric Halo ULN2
User avatar
David
Site Admin
Site Admin
 
Posts: 45825
Joined: Sat Mar 05, 2005 12:16 am
Location: Valley Village, CA

 

Postby EricBradley » Mon Aug 15, 2011 1:01 pm

This is ski and fader 8 beating around the bush:

http://www.logicprohelp.com/viewtopic.php?t=61977
Eric Bradley Cardenas
EC Making Sound
Mac mini 2.6 GHz 16GB RAM Areca⚡RAID | MacBook Pro 2.2 GHz 16GB RAM | Os 10.8.3
Logic Pro 9.1.8 | RME Fireface UFX | Adam A7 + Sub8 | Spectrasonics | Softube
User avatar
EricBradley
Moderator
Moderator
 
Posts: 6645
Joined: Sat May 07, 2005 12:47 pm
Location: Uppsala, Sweden

 

Postby darudevil » Mon Aug 15, 2011 1:02 pm

Ski to the rescue!

Thanks for the info, and to let you know, I did search for "loop length not accurate" and a couple of others, but didn't come across this.

Aggrevating. I call it a bug, I don't care. Using scissors should be accurate "smartly". What does Logic (developer) think I want to do when I'm not zoomed in and I snip at 1st beat (or 16th for eg)? Duh.
Ville

LP 9.1.8, MP Octo 2,93GHz, 12Gb, 10.6.8, MOTU UltraLite, Novation ReMOTE 49SL Compact, MBP 17" Quad 2.3GHz
Darude.com - SoundCloud - YouTube
User avatar
darudevil
 
Posts: 274
Joined: Thu Jan 05, 2006 10:49 am
Location: Turku, Finland

 

Postby darudevil » Mon Aug 15, 2011 1:06 pm

Same result with Marquee tool.
And while cutting with scissors there's no . in the end. And neither is with Marquee tool. And, David, I understand that you like Marquee tool, and I'm glad it works for you, but it's a workaround which shouldn't be needed, the scissors should "just work". Sillyness this is, tiny little thing that has now been around for several updates.

Regardless of me probably sounding grrrrrrr-ey, which I am, thanks all for chiming in, I know it's not your fault! :)
Ville

LP 9.1.8, MP Octo 2,93GHz, 12Gb, 10.6.8, MOTU UltraLite, Novation ReMOTE 49SL Compact, MBP 17" Quad 2.3GHz
Darude.com - SoundCloud - YouTube
User avatar
darudevil
 
Posts: 274
Joined: Thu Jan 05, 2006 10:49 am
Location: Turku, Finland

 

Postby Rev. Juda$ Sleaze » Mon Aug 15, 2011 1:12 pm

Have they changed the behaviour of the scissors in L9?

They always snip exactly to the bar for me.
Zappa is not dead, he just smells funny.

LS8.0.2, OS 10.6.8, iMac 3.06GHz dual, 12GB RAM, Zoom H4n, M-Audio KeyRig 49, MOTU Fastlane USB/midi, Sonuus G2M
User avatar
Rev. Juda$ Sleaze
 
Posts: 4136
Joined: Tue Jan 26, 2010 4:57 pm
Location: Ciderland, UK

 

Postby David » Mon Aug 15, 2011 2:13 pm

darudevil wrote:David, I understand that you like Marquee tool, and I'm glad it works for you, but it's a workaround which shouldn't be needed

I know, and I agree with you, I was just trying to provide a workaround.
 Certified Logic Studio Master Trainer
Author of Logic Express 9 and Logic Pro 9, Apple Pro Training Series
Logic Pro 9.1.8 - Mac OS 10.7.4 - Mac Pro 8 core 2.8 GHz Intel Xeon - 6GB RAM - Metric Halo ULN2
User avatar
David
Site Admin
Site Admin
 
Posts: 45825
Joined: Sat Mar 05, 2005 12:16 am
Location: Valley Village, CA

 

Postby ski » Mon Aug 15, 2011 3:05 pm

To the OP, you're welcome!

To the right Rev., if I recall correctly, this problem first cropped up in Logic 8. The thing is, this problem won't happen to you until it does. One day. Out of the blue. When you least expect it. It's inconsistent behavior.

Looking at the date of my own post on this topic in this thread, I'm not sure if I was referring to L8 or L9.

EricBradley wrote:This is ski and fader 8 beating around the bush:

http://www.logicprohelp.com/viewtopic.php?t=61977


LOL!
MacPro 8 Core 2.4 Xeon | 32G RAM | OSX 10.6.8 | Logic 9.1.7 | RME FF800 | 3 monitors | Toys for days
User avatar
ski
Site Contributor
 
Posts: 15673
Joined: Thu Dec 15, 2005 5:12 pm
Location: Los Angeles

 

Postby Rev. Juda$ Sleaze » Mon Aug 15, 2011 5:16 pm

ski wrote:To the right Rev., if I recall correctly, this problem first cropped up in Logic 8. The thing is, this problem won't happen to you until it does. One day. Out of the blue. When you least expect it.


Oh man, now I'm scared... :shock:
Zappa is not dead, he just smells funny.

LS8.0.2, OS 10.6.8, iMac 3.06GHz dual, 12GB RAM, Zoom H4n, M-Audio KeyRig 49, MOTU Fastlane USB/midi, Sonuus G2M
User avatar
Rev. Juda$ Sleaze
 
Posts: 4136
Joined: Tue Jan 26, 2010 4:57 pm
Location: Ciderland, UK

Re:  

Postby ruari » Sun Feb 12, 2012 7:37 am

ski wrote:The thing is, this problem won't happen to you until it does. One day. Out of the blue. When you least expect it. It's inconsistent behavior.


It's happening to me on a drum loop I've just made, it's a frustrating little bugger for sure :evil:

David wrote:I use the Marquee tool to quickly cut regions to an exact number of bars.


Usually that works fine for me too but not this time, the marquee method is cutting ever so slightly after the bar & either the split region by locators or the scissors are cutting ever so slightly too early. I can't get an accurate 1 bar loop no matter what I'm trying here, even after I've made the edits & tried time stretch to nearest bar I still can't get it.

In the screenshots I've placed the region on 1.1.1.1 & zoomed in at bar 128.

Marquee method
Screen shot 2012-02-12 at 15.14.13.png


Scissors method
Screen shot 2012-02-12 at 15.16.01.png
You do not have the required permissions to view the files attached to this post.
Logic Master Pro

iMac3.2GHz i3|8GB RAM|10.6.8|9.1.7|SaffirePro40

We are not in a position to give out medical advice.If you want to create wobble-bass on the ES2,this is the right place to ask,otherwise seek professional advice - Rev. Juda$ Sleaze
User avatar
ruari
 
Posts: 1436
Joined: Sun Jun 21, 2009 10:30 am

Re: Inaccurate loop length

Postby redlogic » Mon Feb 13, 2012 1:39 am

Open the file in the Sample Editor.
Make sure Edit > Snap Edits to Zero Crossings is NOT checked.
Zoom all the way in on the region end and set it to exactly one bar.
Go to Edit > Selection -> Region.
You may need to add a small fade out to the region in the Arrange window, if it pops or clicks due to Snap Edits to Zero Crossings being disabled.
Manual...WTF is that!

Logic Pro 9.1.8, 8.0.2 & 7.2.3, MacPro 2 x 2.66 GHz Dual-Core Intel, 9 GB ram, OS X 10.6.8, RME Fireface 400, UAD-2 Quad
redlogic
 
Posts: 2359
Joined: Wed May 28, 2008 12:28 pm

Re: Inaccurate loop length

Postby fader8 » Mon Feb 13, 2012 3:53 am

redlogic wrote:Open the file in the Sample Editor.
Make sure Edit > Snap Edits to Zero Crossings is NOT checked.
Zoom all the way in on the region end and set it to exactly one bar.
Go to Edit > Selection -> Region.

While that works, it's a long version of trimming the region by locator in the Arrange.

I've said it before and I still stand by it. Using the locator edit functions is the best way to work in a loop oriented workflow.
Music helps not the toothache.--George Herbert

G5Quad2.5, LP9.0.2,OSX.5.8,RME Digi&Multiface,002r, 4xUAD-1,Duende PCIe,Unitor8-AMT8,Logic Control+4 LCXT's,Capybara320,Kurz...
User avatar
fader8
Moderator
Moderator
 
Posts: 11330
Joined: Tue Dec 13, 2005 3:46 am
Location: Lewisburg, West Virginia

Re: Inaccurate loop length

Postby ruari » Mon Feb 13, 2012 6:40 am

Thanks for the suggestions guys, but neither of those is working on this loop either. I had already tried the split region by locators & the crop button yesterday but I tried them again to see if it was going to work today.

Even when I zoom in as far as I can go in the sample editor I can only get either 3.3.239. or 1.0.0.0. it's never an exact measure.

I've tried it in a couple of empty projects to see if that helps but nothing I try has worked so far, I've attached the loop here in case anyone here would like to try.

It's not the end of the world for me, more of a mild annoyance.
You do not have the required permissions to view the files attached to this post.
Logic Master Pro

iMac3.2GHz i3|8GB RAM|10.6.8|9.1.7|SaffirePro40

We are not in a position to give out medical advice.If you want to create wobble-bass on the ES2,this is the right place to ask,otherwise seek professional advice - Rev. Juda$ Sleaze
User avatar
ruari
 
Posts: 1436
Joined: Sun Jun 21, 2009 10:30 am

Re: Inaccurate loop length

Postby Rev. Juda$ Sleaze » Mon Feb 13, 2012 9:01 am

What's the bpm?
Zappa is not dead, he just smells funny.

LS8.0.2, OS 10.6.8, iMac 3.06GHz dual, 12GB RAM, Zoom H4n, M-Audio KeyRig 49, MOTU Fastlane USB/midi, Sonuus G2M
User avatar
Rev. Juda$ Sleaze
 
Posts: 4136
Joined: Tue Jan 26, 2010 4:57 pm
Location: Ciderland, UK

Re: Inaccurate loop length

Postby ruari » Mon Feb 13, 2012 9:09 am

128
Logic Master Pro

iMac3.2GHz i3|8GB RAM|10.6.8|9.1.7|SaffirePro40

We are not in a position to give out medical advice.If you want to create wobble-bass on the ES2,this is the right place to ask,otherwise seek professional advice - Rev. Juda$ Sleaze
User avatar
ruari
 
Posts: 1436
Joined: Sun Jun 21, 2009 10:30 am

Re: Inaccurate loop length

Postby fader8 » Mon Feb 13, 2012 9:30 am

Sample rate?
Music helps not the toothache.--George Herbert

G5Quad2.5, LP9.0.2,OSX.5.8,RME Digi&Multiface,002r, 4xUAD-1,Duende PCIe,Unitor8-AMT8,Logic Control+4 LCXT's,Capybara320,Kurz...
User avatar
fader8
Moderator
Moderator
 
Posts: 11330
Joined: Tue Dec 13, 2005 3:46 am
Location: Lewisburg, West Virginia

Re: Inaccurate loop length

Postby Rev. Juda$ Sleaze » Mon Feb 13, 2012 9:46 am

Works fine for me with "cut by playhead" and scissor tool on Logic 8. Looped it for 101 bars, no problems.
You do not have the required permissions to view the files attached to this post.
Last edited by Rev. Juda$ Sleaze on Mon Feb 13, 2012 9:58 am, edited 1 time in total.
Zappa is not dead, he just smells funny.

LS8.0.2, OS 10.6.8, iMac 3.06GHz dual, 12GB RAM, Zoom H4n, M-Audio KeyRig 49, MOTU Fastlane USB/midi, Sonuus G2M
User avatar
Rev. Juda$ Sleaze
 
Posts: 4136
Joined: Tue Jan 26, 2010 4:57 pm
Location: Ciderland, UK

Re: Inaccurate loop length

Postby ruari » Mon Feb 13, 2012 9:55 am

fader8 wrote:Sample rate?


44.1

@Rev - I've tried cut by playhead too & it's just not playing ball, I'm on 9.1.6 though :cry:
Logic Master Pro

iMac3.2GHz i3|8GB RAM|10.6.8|9.1.7|SaffirePro40

We are not in a position to give out medical advice.If you want to create wobble-bass on the ES2,this is the right place to ask,otherwise seek professional advice - Rev. Juda$ Sleaze
User avatar
ruari
 
Posts: 1436
Joined: Sun Jun 21, 2009 10:30 am

Re: Inaccurate loop length

Postby Rev. Juda$ Sleaze » Mon Feb 13, 2012 10:00 am

Weird :?

Oh, and have you read the forum guidelines? You should put your Logic version in your signature :P :lol:
Zappa is not dead, he just smells funny.

LS8.0.2, OS 10.6.8, iMac 3.06GHz dual, 12GB RAM, Zoom H4n, M-Audio KeyRig 49, MOTU Fastlane USB/midi, Sonuus G2M
User avatar
Rev. Juda$ Sleaze
 
Posts: 4136
Joined: Tue Jan 26, 2010 4:57 pm
Location: Ciderland, UK

Next

Return to Logic Studio Bugs & Workarounds

Who is online

Users browsing this forum: No registered users and 0 guests