It would make a lot of sense to add subforms to the "Avid Product Features Request" forum.
Requests for Symphony don't necessarily relate to MC, and most likely will not relate to DS. These products are different enough that they should each have their own subform for new features requests.
Thanks much for considering this suggestion.
Then again, Symph and MC share 98% of their features and interface. Requests are likely to be relevant to both products.
Okay, but DS shares no code base with either, so it should have its own requests subform.
As for MC/Symphony feature requests, how about separate subforms based on topic, similar to how help is organized? Something like:
1) Installation
2) Capturing
3) Timeline
4) Importing and Exporting
5) Audio
6) Color Correction
7) Effects
... and so on.
As it stands now, "Avid Product Features Request" contains 750 threads spanning thirty-eight pages. That is unwieldy.
How many of these requests are no longer necessary or have been implemented? And how many repeat or are minor variations on previous requests? I have no idea.
I have to agree with Bobby on this one. A cross reference by specific system would be extremely helpful, especially for searching to see if your suggestion has already been made for your particular model system. This would especially make sense between the DS Nitris line and the Symphony/Media Composer Nitris, which are totally different. Also, there are enough sizable differences in the color correction tool between Symphony and Media Composer to warrant separate listings.
Larry Rubin
Senior Editor
The Pentagon Channel
www.pentagonchannel.mil
Hi,
If I were a product designer at Avid, I'd rather just check the one Feature Request forum once or twice a week and see what's new. Having to dig through a number of subforums to see the latest posts in each one would be a pain.
adios,Carl
There is no such thing as a video emergency. My Demo Website
Carl,
I imagine that if I were a programmer working on the latest CC upgrade, I wouldn't want to have to sift/search through seven hundred posts to see all the requests that apply to color correction. And I'd be annoyed when posts are duplicated and bumped b/c their originals have moved to the back.
Presently, suggestions get pushed to the back, duplicated, implememted, etc and no one knows because Features Request is a thirty-eight page flat file.
As for DS, the forum is essentially unworkable for suggesters or designers, b/c DS post are lumped together with all the ones for MC and Sympony. That makes no sense whatsoever.
I imagine that designers of all platforms would like to have a more organized and cogent way of understanding the features users want. Having one, long, FIFO list doesn't do that.
To each their own. I'd be annoyed at having to click on a bunch of different subforums to see what had been posted in each one. If I wanted to see what had been suggested regarding a particular feature, I'd just search the forum.
DS could use its own forum, though.
I'm just annoyed that the requests don't come true!
http://www.whydocumentaries.com.au
What do you mean they don't come true?
What about the time they... uh... I mean... Yeah, the time they... uuuhh... hmmmm. Oh I remember, it was the... (Yeah, feature request forums for any product or any company exist solely to exist.)
Yet we all know this! What the heck are we doing? Renders take 2 minutes nowadays, not 20. Editors can't type fast to save their lives, so you know we're just lollygagging by posting anything to this place. We drone on and on logorrhoeically* expecting some mysterious dark room in Avid, run by some manically diligent, rule-breaking Tony Almeida type guy to fix all our little daily annoyances and then to list us individually on the Download CPR in the README as the architects of all worldly efficiency.
I know. I'm as guilty as anyone. DOH!
*http://en.wikipedia.org/wiki/Logorrhoea
Pixel Monkey
www.alwaysediting.com
Pixel Monkey: What about the time they... uh... I mean... Yeah, the time they... uuuhh... hmmmm. Oh I remember, it was the... (Yeah, feature request forums for any product or any company exist solely to exist.)
Hey, we got the scrolling timeline back, didn't we!!!
Michael.
Pixel Monkey: What do you mean they don't come true? What about the time they... uh... I mean... Yeah, the time they... uuuhh... hmmmm. Oh I remember, it was the... (Yeah, feature request forums for any product or any company exist solely to exist.) Yet we all know this! What the heck are we doing? Renders take 2 minutes nowadays, not 20. Editors can't type fast to save their lives, so you know we're just lollygagging by posting anything to this place. We drone on and on logorrhoeically* expecting some mysterious dark room in Avid, run by some manically diligent, rule-breaking Tony Almeida type guy to fix all our little daily annoyances and then to list us individually on the Download CPR in the README as the architects of all worldly efficiency. I know. I'm as guilty as anyone. DOH! *http://en.wikipedia.org/wiki/Logorrhoea
I know it's August, and we've got a way to go yet, but this gets my vote for 2008 Post of the Year.
camoscato:I know it's August, and we've got a way to go yet, but this gets my vote for 2008 Post of the Year.
I'll second that, if for no other reason, "logorrheically". Yeah, it's a real word even if your spellcheck doesn't think so!
Avid Technology, Inc. brands: Digidesign | M-Audio | Sibelius | Pinnacle Systems | Sundance Digital | Softimage
© Copyright 2000-2008 Avid Technology, Inc. All Rights Reserved — Legal Notices | Terms of Use | Privacy Policy | RSS Feeds | Site Map