One thing I must ask the more experienced people here on this forum - please do not use acronynms or abbreviations. If you do, then please include the full meaning. For example the use of the term AME - YOU know what this means, the new users of PR CS4 more than likely don't!
I agree very annoying, the same goes for tipical American abbreciations, this for being non-American.
In CS3 and earlier the way I make freeze frame: cut the avi from where you want freeze frame. Then framehold inpoint. You have the first frame as still. If your avi is not long enough for the duration, just slow down the segment. The first frame will show through the length of the clip as a freeze frame. Easy. I guess it will work in CS4 as well.
please do not use acronynms or abbreviations.
You ask a lot of folks who write this stuff day in and day out. The concept of abbreviations is there for a reason. The better request would be for a sticky Glossary that the uninformed may refer to.
I agree that abbreviations and acronyms that resemble SMS and other shorthands are disturbing and make for very unpleasant reading, often leading to misinterpretation and confusion. OTOH (On the other hand) some basic abbreviations like IMHO, AFAIK, IIRC and the like are so common, that everybody ought to know these terms and if they do not recognize these, there is always the help of http://www.netlingo.com/
You have already fallen into the trap of using abbreviations by talking about PR instead of Premiere Pro. It may take some time to get used to it, but with the proper terms and commonly recognized abbreviations, it makes posting and replying a lot easier. If you have to spell out AME for each and every post it would quickly become extremely cumbersome.
There is always a middle road. If I started talking in terms of: "You better use teamed NIC's over iSCSI for the NAS" I would not be surprised you find that geek talk. If I were to enlarge on this with a full explanation, to be understood by every newbie on the block, you would think: "Jeez, can't you get to the point. I don't want to read 8 pages of dull text."
Just my 0.02
Yes you're quite right. I used abbreviations too, and writing posts it's hard not to do the same. Looking back on how I described my system spec - jeez too!
I think what Jim suggests is quite a useful idea - provide a glossary. That would certainly help newbies like me. And thanks to AsianOcean.com for the freeze frame suggestion.
I see both points. Spending some time on the PE (Premiere Elements) forum, where many users have never touched any form of NLE, I try to give the "translation" to my abbreviations, when first used. Often, it works fine, but too often the reader skips over the "NLE (Non Linear Editor)" reference and question "what the heck does 'NLE' mean?"
OTHO (we all know this one, don't we?), the info IS contained, if one just wants to read it.
It can make things a bit difficult, but with just a little help along the way, they should be able to translate it.
PS, what I hate is the "text messaging-speak," that one sees too often nowadays.
I agree on the glossary concept. I'd love to see it expanded to "common terms," as well as the abbreviations. Pursuant to a simiar comment in another thread, it would be great to have a chart with columns for Adobe, Avid, FCP, etc., as some of the terms common to one program will be different in another.
However, I shudder to think of compiling such a glossary, and how long it would be.