> Interesting example because, in fact, that problem was in the
> audio MONITOR,
> not the audio itself. This is probably a good example for all since
> we need to make sure the person reporting the "bug" is correct before
> jumping to conclusions.
HEAR YE HEAR YE ONE AND ALL ..
I am the guy that after two days of serious testing believed the
problem in the monitor was also affecting transmitted audio. And I
made that post in good faith, and was not "jumping to conclusions".
And when I finally became convinced after multiple exchanges with
T-T engineering, even more testing, and a test version of new
firmware that this WAS NOT THE CASE I also posted THAT
information. But it seems very few people bothered to notice the
second post. Guess it wasn't something that interested any one,
especially the detractors or guys who just get up on the wrong side
of bed in the morning.
And to the persons who keep stating that no one posts PROBLEMS
with the radio (you know who you are) -- because we just believe it
has to be good because it's T-T or we're a cult, or whatever, then
you need to recalibrate your bias. History has confirmed over and
over that once the lore is formed, it's hard to get rid of it. There's a
lot of bad juju and grossly uninformed information being spread on
the various T-T/Orion reflectors. Heck, guy gets up in the morning
with the flu and blames it on his firmware. It's past the point of
being absurd. That's why it's better to have the discussion's
privately with T-T, and then if there is a problem it gets fixed. Now
do you understand? Do I need to spell anything for you?
So -- once and for all, write this down, and underline it ...
***THERE WAS NO PROBLEM WITH TRANSMIT AUDIO ***
Grant/NQ5T
_______________________________________________
TenTec mailing list
TenTec@contesting.com
http://lists.contesting.com/mailman/listinfo/tentec
|