'Pro' vs. 'Pro-GRADE'

JimT wrote on 8/6/2000, 9:58 AM
After reading tons of posts with the word 'Pro' used, I
feel that many people meant 'Pro-Grade' instead. There's a
difference. If you get paid for what you do as a
profession, the word 'Pro' is used. If something is
considered amongst the highest of quality ,whether it's an
object or level of work, the term 'Pro-Grade' should be
used. Keeping this in mind, we can now say that
professionals (or serious hobbyists) typically use what's
considered pro-grade equipment to help ensure pro-grade
results. Though it is still highly possible to get less
than pro-grade results even if the person uses pro-grade
equpment.

Then the controversey turns to WHICH audio softwares are
considered pro-grade...

Comments

JimT wrote on 8/6/2000, 12:43 PM
Actually, ALL of them are 'Pro'. They make money doing what they do,
so they are technically correct when they label their products as
Pro. Whether their products are pro-grade or not is the question.
Just like all those nifty products that you see in those cheesy
catalogs and commercials trying to impress the consumers with the
term 'Space Age'. OF course it's space age...DUH!

Anyway, I think that some very valid points have been made regarding
Vegas' shortfalls. I just question the context in which these points
have been made. I must admit that even though some people are making
every effort to let the 'truth' be known, the way they present their
opinions is offensive to many...including myself sometimes. The best
way to get things to change is to INCLUDE people in the changing
process...by working WITH them while avoiding fingerpointing,
hostility, provoking etc.

I honestly think Sonic Foundry has a great starting point with the
Vegas line. I like most of it's features very much. The only thing
that really bothers me is the the latency issue. Yeah, there are ways
to correct this problem, but it's an unnecessary pain in the neck. I
only hope that SF will get over it's stubborness about implementing
ASIO support just because it was developed by a competitor. Unless
they have another way to correct the latency problems, they ought to
just bite the bullet and use something that is widely acceptable and
desirable until they can develop their own (possibly BETTER) solution.

My message to Sonic Foundry: Keep the momentum going! I can see Vegas
rising to the top with some more tweaks and added features. But
PLEASE find a solution for the latency problem.


The Coroner wrote:
>>Very well put, Jim.
>>This brings my point home: It is every musician's responsibility to
>>learn the demands of his occupation, so that NOBODY can take
him/her
>>for a ride...
>>While on this subject: The label "PRO' on pro...ducts has been so
>>abused, that you have to be weary of anything sporting it. Similar
to
>>what happened to the word "Quality". This problem is most pervasive
in
>>recording where you have products like MasterTracks PRO,
CoolEditPRO,
>>VegasPRO, SawPRO, CakewalkPRO, AcidPRO, StudioPRO, MidiTraxPRO,
>>WaveConverPRO, GoldWavePRO, SoundLaundryPRO, DartPRO, etc. How many
of
>>them are really PRO? your decision...
>>
>>
>>Victor.
>>
>>
>>
>>
>>Jim wrote:
>>>>After reading tons of posts with the word 'Pro' used, I
>>>>feel that many people meant 'Pro-Grade' instead. There's a
>>>>difference. If you get paid for what you do as a
>>>>profession, the word 'Pro' is used. If something is
>>>>considered amongst the highest of quality ,whether it's an
>>>>object or level of work, the term 'Pro-Grade' should be
>>>>used. Keeping this in mind, we can now say that
>>>>professionals (or serious hobbyists) typically use what's
>>>>considered pro-grade equipment to help ensure pro-grade
>>>>results. Though it is still highly possible to get less
>>>>than pro-grade results even if the person uses pro-grade
>>>>equpment.
>>>>
>>>>Then the controversey turns to WHICH audio softwares are
>>>>considered pro-grade...
>>>>
JohanAlthoff wrote on 8/6/2000, 1:25 PM
Good point. I really hope they continue to develop their own audio
engine rather than dance to other people's pipes, but if the demand
for ASIO is high, I suppose SF would be doing the right thing in
following the customers' needs. As long as the customers really need
what they think they need, which is not always the case.

>>ASIO support just because it was developed by a competitor. Unless
>>they have another way to correct the latency problems, they ought
to
>>just bite the bullet and use something that is widely acceptable
and
>>desirable until they can develop their own (possibly BETTER)
solution.
>>