Delay Comp problems again, Delay comp is RED but way below limits.

[Bushpig]

Guys

Avid must be really under the kosh. No reply here (or to many of the threads like it used to be). I even used one of my ASC codes to contact them about this, and 4 days later......tumbleweed. 200 staff missing suddenly perhaps??

SB

[Craig F]

200 plus another round this week

anyway maybe DLY should turn Yellow/Amber when there is a routing loop?

[Bushpig]

Guys,

Just had an email back about my ASC request. The chap has pointed out that he checked this in 10, 9, and 8 and apparently PT9 and 10 behave this way, but 8 does not. I realised I'd neglected to mention here, that I never bothered with 9. I went straight from 8 to 10 and this was the first thing I noticed.

Can anyone else here who's still running a PT9 partition check if this is the case for me? Thanks.

Cheers

Steve Bush
www.music180.com/pros/5887

[Bushpig]

Guys,

Hi. I just posted this info in another thread started by Firechild. It appears this is a change in the software that got implemented in PT9 (and is very annoying). My Tech Support conversation reprinted below.

Dear Avid,

Hi. Just started running PT10HD and immediately noticed a change to the delay compensation reporting. Here's a thread on the DUC that highlights my situation (user name is Bushpig):

http://duc.avid.com/showthread.php?t=311140

Message back:

I have confirmed the issue described in Pro Tools 10.
I tested the same session in HD9.05 and for me, it still occurs.
I then went back to HD8.0 and the DLY indicator does not illuminate.
I have just tested again on HD9 and it's still occuring for me.

Are you absolutely sure this did not occur in HD9?
If so, I can't reproduce it currently.

For me, something has obviously changed in the coding between Pro Tools HD 8.0 and 9.0

Can you let me know, i'll continue to look at this in due course.

Me:

I never upgraded to 9 at all, so if it changed then, I wouldn't have noticed (sorry). If you remember, you and I jumped through hoops to maintain my 8 iLok licence, as I wanted to skip 9 and go straight to 10. I realise now I never mentioned I was hopping straight from 8 to 10 in either in my DUC post or my ASC message.
I couldn't work out if this was "fixed" to be more stringent for other user's reasons I wasn't aware of, but it certainly has me distracted all day every day so far working in 10 and it would be nice to either correct it if it was changed in error, or at least offer a pref for this behaviour. I can only assume not many people set up their echo's this way if it hasn't been commented on previously.
Thanks for your continued help.

Tech Support:

I'll get this logged and keep you posted of any developments.
Unfortunately, at this stage, I can't say when this will be fixed.
It needs to be fully investigated by our engineering team, i'll know more after they have had chance to look at it.
Issues that require fixes are rated and categorised into the following :

1) The amount of people affected by the issue, i.e. a small / large subset / all customers
2) How invasive the fix is.

So, please bear with us on this, i'll come back to you when I have more information.

Me:

Thanks for the info mate. I initially thought something had gone fishy with my PT10 install, but it turns out it's behaving correctly. I suspect when the boys and girls were re-programming PT9 for ADC in the native format, they either had this on their list as a necessary addition to the delay reporting from user reports, or thought it was a good way to tighten up the reporting environment. It's a shame to always have the red DLY light on, as this is not a genuine case of an ADC error. It's fairly standard practice in a pro studio set up to use bouncing delays feeding each other back and forth, but I just need to keep my wits about me with regards to real ADC errors (still, a pref setting for this would be nice though).

Tech Support:

We have delved a little deeper into this issue with development.
As you have experienced the illumination of the DLY light is fairly new.
It actually appeared for the first time in Pro Tools 9. Although, you would have missed this, going from version 8 - 10.

That said, ADC has always had to detect feedback loops as it is a recursive algorithm.
In Pro Tools 9.0 we added detection for non traversed (i.e. missed) parts of the mixer, and added status light for both cases.”
So we’ve always detected feedback loops but we didn’t start lighting the “Dly” indicator to inform the user until PT 9.0

In our discussions with engineering we mentioned the possibility (as you did) of having a switchable preference within Pro Tools to switch off feedback loop detection. At this stage it's too early to say if this will occur. But your suggestion has been well and truly noted.

So if anyone feels inspired, get onto Avid about a pref for this. Maybe we're the only ones who have come across this.

Cheers

Steve Bush
www.music180.com/pros/5887