foreststone

Hello, The anchor point is set to the very beginning of the audio file.

Wow thanks for verifying this, I knew something wasn't quite right, but I can't always replicate it. Sometimes when I bounce in place everything works as expected.

Hi Erik, The scissors tool wouldn't cut at that point. I also tried doing the alt cut and logic ended up creating 16 1 bar regions with the dreaded dot on the end. I don't get it. For now I'll just pack the regions in a folder which does allow me to size exactly to the bar. Thanks for your suggestions, much appreciated.

Hi thank you for the suggestion. Sadly it did not help. It seems related to just these files that I bounced in place in this particular Logic project. I have snap set to bar and snap regions to absolute value but logic will still not let me size these regions exactly on the bar. When I zoom in I can see that the region is slightly off (see attached screen shot). I'm not sure what to do other than pack it in a folder and then size the folder.

I discovered that this is only occurring with .wav files that are timestamped. files that don't have a timestamp can be resized to an absolute value. The files that are time stamped in my project are the ones where I did a bounce in place. Does anyone know how I can remove the time stamp so that I can resize these regions to an absolute value?

Hi, To help troubleshoot the issue can you try running the session on a non ssd hd? Perhaps an external firewire drive? Maybe it has something to do with the ssd drivers? Just a hunch.

Thanks for your response Erik, I do have my snap set to division and the absolute flag turned on. I'll try it again with a different zoom setting and see if that helps.

Hello, When resizing a region in the main window, with snap set to absolute division, I am getting a period at the end of the length field in the Event Float. I noticed when the period is displayed, looping the region will not indicate an exact number of repetitions but something like 1+. On regions that don't have that period displayed I can get looping to be exact for example repetitions would indicate 2 instead of 1+. Does anyone have any insight as to what that period means and why it seems to throw the looping off? I attached a screen grab of the event float for reference...

It's not available on audio tracks. J. Thanks Jordi, I was afraid of that. For me it's more useful to view delay in ms for audio tracks than on instrument tracks.

You just set it to Milliseconds! No trial and error here: [attachment=0]Screen Shot 2013-11-03 at 16.45.24.png[/attachment] [attachment=1]Screen Shot 2013-11-03 at 16.44.37.png[/attachment] J. Hi Jordi, I don't see the delay option on audio tracks. I see it for audio regions but the only option is to display in ticks. How can I set the delay in milliseconds of an audio track?

Hi, Can you confirm your audio settings on the General tab? For sample accurate automation, volume, pan, sends and plugin parameters should be set. Also the Plug in latency/compensation setting should be set to All and low latency unchecked. see screen shot. I tried a simple test with Battery 4 on an instrument track and a kick and a snare on separate outs with the waves hcomp on the snare track both summed to an aux. I also put a fabfilter pro q on the summed aux and set it to use max latency. Programmed a basic beat and added another bass track with an arpeggiator pattern and the timing was all good.

Hi Mike, It doesn't look like you have delay compensation set for plugin parameters. There's a separate setting for them. See screen shot.

Great to hear, foreststone! Thanks for the update! J. Hi Jordi, Your welcome

Updating to 10.0.7 has resolved this issue for me.