In the SubCap tool, the positioning anchor point doesn't follow the text alignment setting.

Align Center should naturally have the anchor point at the center of the text lines, and Align Right should have the anchor point at the right edge of the text lines.

Various users have been reporting this BUG at least since september last year, but this anomaly hasn't been fixed yet. 

Also, the text border feature can only be used to fatten the text. Dark border erodes the characters and is totally unusable. Better antialiasing or at least a subtle softening would be nice too...

Seconded, same problem in the new RT timecode tool.

I agree.  So Moderators - this is the third report of this problem.  Will it get escalated?

Cheers,

Jef

While this is sort of a bump, I must say that this bug kills this tool for us.  To bad - lots of potential.

Thank heavens we have DS!!!

Cheers,

Jef

jef:

I agree.  So Moderators - this is the third report of this problem.  Will it get escalated?

Cheers,

Jef

Nope, this BUG will not be dealt with anytime soon.

The moderators of this forum conveniently moved this thread to the "feature request" section, hoping that noone would take notice of the fact that this is an actual MAJOR BUG !!!

This is the kind of behavior we've learned to expect from the moderators of Apple's user forums, and even those guys have since learned that it pisses off their customers. Avid unfortunately hasn't learned this lesson yet.

In Avid lingo, this is what's known as "New Thinking"...

Not sure why this was moved but " editdude" the moderators did NOT conveniently move this hoping Avid wouldnt notice.   First Jef pinged me and I have sent this to QA for repro and then Larry Rubin escalated it officially. 

All the mod's work hard on their OWN time to moderate these forums.  The forums are NOT a support forum so what these folks do it huge for the members of the community and I for one appreciate them tremendously.  They advocate for the custoemr day and night.  So think about that before you post next time. 

I'll report back as soon as I have verification on this issue. 

Marianna

Thanks for stepping in Marianna.  I too wondered why it moved, but did not think to hard about it.

I am glad it is being looked at.  As I said, this one, seemingly minor problem really kills this tool for us.  Mainly because it could fill in a feature set that the DS tool does not cover.

I think that this does point out an oportunity for Avid:  A bug forum.

Someone posts a bug with REPEATABLE reproduction steps.  Other users with approved specs confirm that the repro steps in fact trigger the bug and respond accordingly to the thread.

When X numbers can repeat it, off it goes to higher powers.  Just an idea.  The fact that one currently has to be on maintanence to report a bug misses out on a lot of users.

Thanks for helping out.

Cheers,

Jef

Marianna:

Not sure why this was moved but " editdude" the moderators did NOT conveniently move this hoping Avid wouldnt notice.   First Jef pinged me and I have sent this to QA for repro and then Larry Rubin escalated it officially. 

All the mod's work hard on their OWN time to moderate these forums.  The forums are NOT a support forum so what these folks do it huge for the members of the community and I for one appreciate them tremendously.  They advocate for the custoemr day and night.  So think about that before you post next time. 

I'll report back as soon as I have verification on this issue. 

Marianna

Marianna, noone has suggested that this thread was moved hoping Avid wouldn't notice the topic.

Most users don't frequent the Feature Requests forum that much, and if a moderator in error chooses to move a bug report to that section, please inform them that this is wrong and move the topic back!

If anyone was offended by my posting, I humbly apologize, but there is one thing that we need to set straight about these forums: 

● These forums *ARE* in fact support forums, whether you or the Avid executives choose to acknowledge this fact or not.

Most users come here to solve their problems with Avid products. First by searching for postings regarding experiences similar to their own, and secondly by reporting anomalies and possible bugs, hoping for a quick response from fellow forum users, moderators or Avid employees. 

This site is the best way for many users to get a quick response to their support issues, and it is absolutely essential that Avid acknowledges the need for an official and public platform for bug reports on these forums.

We appreciate your efforts Marianna. Keep up the good work!

This forum is a place where Users get support from one another. However, Marianna is correct that this forum, in itself, is not an Avid support channel. This is a USER community.

Volunteer moderators advocate for their fellow users by bringing your needs to Marianna and to me and we do our best to move customer concerns to the appropriate Avid personnel. Personnel in our support channels do not participate here so the moderators, Marianna and I do our best to fill the gaps. Other than Marianna, the rest of us do it on our own time and with the interests of getting User issues like this into the right hands. If the expectation is for a problem to be solved within a certain time frame, this is not the place to address the issue. If you have problems that need immediate addressing, please call support at 1-800-800-AVID.

Impolite and/or abusive attitudes and language will usually ensure a much slower response here than a genuine, respectful request for help. We are, after all, volunteers here and with the volume of users needing assistance, I would much rather move on to someone with whom I can work professionally.

This forum is a place where Users get support from one another. However, Marianna is correct that this forum, in itself, is not an Avid support channel. This is a USER community.

Correct. This is not Avid's OFFICIAL support channel.

Most users however regard these forums as their best source of information regarding poblems with your products. You can call it whatever you like, but the users of these forums still consider it their best source for support. It's time for Avid to acknowledge this fact and make the most of it.

If the expectation is for a problem to be solved within a certain time frame, this is not the place to address the issue. If you have problems that need immediate addressing, please call support at 1-800-800-AVID.

Correct. If your system is toast, call tech support. If you believe you have found a bug, call tech support.

Then post your findings on these forums and chances are you'll find that others have experienced the anomaly long before you did, and might even have developed a workaround.

Avid's response to serious reporting of bugs is often condescending and followed by silence.

We've reported bugs through the official channels on numerous occasions the last fifteen years or so, but have never gotten any useful feedback or status report. (DS support is a totally different story. Those guys do great work!) Some bugs never gets fixed, and it has happened that our local Avid dealer called us a year later asking for help finding a workaround. We found one, but never billed Avid for our time.  :-)

Impolite and/or abusive attitudes and language will usually ensure a much slower response here than a genuine, respectful request for help. We are, after all, volunteers here and with the volume of users needing assistance, I would much rather move on to someone with whom I can work professionally.

I totally understand your position, but professionalism means something totally different to me. Solve the client's problem, no matter what. Arguing is fine, but tend to the problem first!

What Avid doesn't understand is that many or most of the users on these forums make their living using your products, and are paying top dollar to get the best and most reliable editing and finishing systems available today. When bug reports seems to be ignored, customers get annoyed.

We can't charge our clients extra for the time we spend finding workarounds for bugs in Avid's products. Need I say more?

This thread has now been moved to an even more obscure part of these forums. Who did that?

Please move the bug report in this thread back to the relevant section!

Thanks!

This forum is the correct place to post issues that affect both the Mac and the PC. In the future, should you have an issue to be seen by users of both platforms, post it here.

I'll say it once again so that you've heard it clearly. It doesn't matter what you think this forum should be or what it may be in the future, currently, it is a completely free resource hosted by Avid on their servers for users to help one another in a community setting. Marianna and I jump in here to offer yet another free service to help customer resolve their issues a little more quickly. There is no offer or expectation of free support services from Avid here.

However, if you are using it to get any problems solved in any specific time period, you are in the wrong place. The best avenue to get bugs reported and prioritized is by calling support and opening up a ticket. What has happened in the past is irrelevant as the company has spent the last two years attempting to improve it's response to customer issues and has done a spectacular job of it. Evidenced by the crippling AMA bug that was reported here last week and fixed with a patch within seven days.

No system is perfect and everyone has an idea of how they think processes should work. I just hope you understand now how they actually do work and can work within the structure to get your problems resolved. Marianna and I will always be here to help where we can and you are welcome to contact either of us directly if you should ever have an issue that we might resolve.

Hi,

BLKDOG:

Impolite and/or abusive attitudes and language will usually ensure a much slower response here than a genuine, respectful request for help. We are, after all, volunteers here and with the volume of users needing assistance, I would much rather move on to someone with whom I can work with professionally.

I agree with this completely.

editdudes:

I totally understand your position, but professionalism means something totally different to me. Solve the client's problem, no matter what. Arguing is fine, but tend to the problem first!

Editdudes, you're not my client; you're a fellow editor with a problem, and you're coming here asking me to spend my time to help you for free.  If you ask in a professional manner, I'll do the best I can to help you.  If you write posts like the one you wrote on the 21st, I'm going to ignore you and help somebody else, because to me, professionalism means dealing with colleagues respectfully.

good luck,
Carl

Just checked on this bug and it had been reported through proper channels and is fixed. It is due to be rolled into an upcoming release.

Man ....  Blkdog..... you beat me to it :)

FWIW.....   BlkDog and Carls comments are spot on.  This is a user community first where peers and moderators assist each other as best they can.  I monitor all of the forums both inside and outside of Avid along with a bunch of other responsbilities like launching products, etc....  and when I see a trend here like the Mojo DX connectivity issue or this sub cap one, I jump on it as does Todd. You have at least 2 advocates here as well as 30+ moderators working for you.

Most often a moderator has already escalated an issue when you folks bump a topic or cry out that we arent listening. This sub cap one is a perfect example.  Larry did his job.  The moderators have a formal escalation process to come directly into me and a team of peeps to work issues - some of the best escalation and engineering folks at Avid are on this email address.   As I said, many times we get wind of an issue here first so this is a hugely valuable place for Avid AND the community.  But this is not a free support forum.    If you get your issue resolved here thats great but sometimes you wont and need to call and speak with a tech to deep drill an issue. 

The intent is to provide you with enough self help options so you have a better Avid experience.  We are working to that goal. 

You don't like something that is happening like Jef did with this bug, or you have a suggestion or a comment, ping me directly instead of bumping on the forum.  I take a direct email to my email address as a sign of your true interst in resolving something.  Just in case you misplaced my email........

marianna.montague@avid,com

Only an email away....

Marianna

Thanks to Blkdog for the info on the bug fix.  Good news on that.

I agree with Carl's comment about this being a User forum.  Users helping Users - the Golden Rule in action.

I also know these forum ar a valuable resource for Avid to communicate with their clients and potential clients.  And there lies my one concern here.  Yes I know this is not free support.  No problem there.  But is seems shortsighted to have an official policy where you must be on paid support to officially log a bug.  That is what I have been told is the policy.  I also read here that moderators can escalate issues.  A bit of confusion there but a step in the right direction. 

Better would be a Bug report forum as I noted above.  Keep it all in one place.  Let people follow the developments.  Currently discussion of bugs is mixed in with all other topics.  There is a dedicated Feature Request forum.  Why not a Bug report one?

Thanks for helping.

Jef