7.4 Hiccup...

[MrDibS]

Soooooo... The question I had for the guy at AES: What if, when analyzing loops in the browser window, Pro Tools doesn't correctly identify the loop (number of bars etc). He said, "As long as I've been using it (which was since that morning) I haven't run into that issue."

Well, I'm here to tell you.... It's an issue. I just went down an old loop CD (aiff files) and many didn't come back right. A four bar loop would come up as being 7/2/448 so it would play slow and out of time. All things considered, this is a pretty amazing feat, but the fact remains that the incorrect ones are now useless and there is no way to correct it that I can find. I've tried the different "analysis plugins" and none seem to fair better.

I analyzed a folder of 276 loops and 26 of them came back presumably erroneous... Anyone else notice this?

[SessionKat]

Soooooo... The question I had for the guy at AES: What if, when analyzing loops in the browser window, Pro Tools doesn't correctly identify the loop (number of bars etc). He said, "As long as I've been using it (which was since that morning) I haven't run into that issue."

Well, I'm here to tell you.... It's an issue. I just went down an old loop CD (aiff files) and many didn't come back right. A four bar loop would come up as being 7/2/448 so it would play slow and out of time. All things considered, this is a pretty amazing feat, but the fact remains that the incorrect ones are now useless and there is no way to correct it that I can find. I've tried the different "analysis plugins" and none seem to fair better.

I analyzed a folder of 276 loops and 26 of them came back presumably erroneous... Anyone else notice this?

Hi Dibs,

There's a couple of thoughts and solutions for you here.

1. In our comparative tests with over 500 files, (from short/clean to long and 'sloppy'), we've determined that we hit an accurate detection mark of approx 90%. So your 26 out 276 seems about the expected result.
2. What can "fool" the detection? Odd meters (signature), too-much silence at start of file, too much silence at end of file can.
3. Tips for correcting (yes you can!) erroneous files:
Drag them in t EA tick-based track. Select it and open the EA Properties window. From your stated example above, type over the "7/2/448" (in the 'Source Length' field), with "8/0/000" and you'll see the region stretch to proper length making it usable.

Hope this helps,

-tv

[MrDibS]

It does help, and like I said, 10% error rate is pretty darned good. What would be nice is some mention of this in the manual. I know that you don't want to officially print shortcomings on a 1.0 product, but with an entirely new technology being introduced into your software, these are the kinds of "real world" instructions we users need.

That being said, thank you for your eerily fast response. I know you are all probably working overtime right now and we appreciate it. Overall I'm quite impressed with 7.4.