Hi there,

Tried asking this question on the original thread, but got no response. It's here:

http://community.avid.com/forums/t/72886.aspx

I'm running v3.5.9 on Classic Symphony Nitris.

BLKDOG reported that the anchor point bug in SubCap had been resolved and would be rolled out in a future release. This was on 23rd. July, 2009.

It doesn't appear to be fixed in v3.5.9. Is this correct?

Regards,

Ian

EyeBee:

Hi there,

Tried asking this question on the original thread, but got no response. It's here:

http://community.avid.com/forums/t/72886.aspx

I'm running v3.5.9 on Classic Symphony Nitris.

BLKDOG reported that the anchor point bug in SubCap had been resolved and would be rolled out in a future release. This was on 23rd. July, 2009.

It doesn't appear to be fixed in v3.5.9. Is this correct?

Regards,

Ian

Bump! Anyone at Avid listening?

Bump. Anyone  .... even anyone at Avid listening?

Patient regards,

Ian

For my part, I have never used the Subcap effect so I can't answer. Just wanted you to know at least 1 person is listening, just no answer for you.

Thank you, Terence.

A gentleman, as always.

Now Avid, why the silence?

Regards,

Ian

Hi EyeBee!

I'm thoroughly convinced that someone at Avid is listening, but not at all surprised that you haven't got an answer yet.

I hope I'm wrong, but the problem here could be that the bug is said to have been fixed way back in July, but since it isn't mentioned at all in the readme file from any of the last *FIVE* releases, chances are that it hasn't been implemented (or fixed?) yet and that some people at Avid are a bit embarassed to admit it.

Can I assume that you've already asked for the bug fix via the proper support channels, and wasn't satisfied with the answers you got?

If you want to take this further, write a polite email to Marianna or BLKDOG and let them know your thoughts.

It goes without saying that this bug should have been fixed in 3.6, but since that release was renamed 4.0, you'll most probably have to pay a couple of hundred bucks to be able to make use of the SubCrap tool, oops... SubCap is the correct name. Sorry! :-)  

Sincerely

So we're going to start another thread about this now and claim that Avid isn't listening because we're responding in the original thread and not this one? LEt's stick to the original thread please?

Guys, did you read my response in that thread? The problem is on the list to go into an upcoming release but it is sort of in the middle of the pack right now.

Speaking strictly as an editor now and not as an Avid employee (I try to make at least one career limiting comment a day on the forums, here comes todays ), there are som many more serious problems to be jumping up and down about, to me and my workflow, this one is an annoyance but in no way is it a show stopper.  Believe me, Avid knows that this needs to be fixed but personnaly, there are much bigger fish to fry before this.

I'm going to lock this thread so let's continue this in the original one. I missed this one yesterday and I'd hate to be accused of not listening to a dozen threads on the same topic.