- Jan 1, 1970
No, thats not real time rendering(well, its becoming that way). That is ray
tracing but games now days use ray casting. You cannot ray trace in real
time yet to any significant degree.
I'm not going to argue about it any more. You don't have to understand or
believe what I'm saying. Your ringing example is no counter example though
because you still cannot see the higher frequency components. There is
always a band limiting aspect after the conversion and your not taking that
into account. That or you act like I'm going to only display the such a
small portion of the total spectrum of the signal to make it useless. That
is not the case. I will display what is only necessary for real time and
leave the rest for non-real time purposes.
I guess we have two different approaches. My goal is not to see the complete
signal in real time but have a history of the whole signal so I can go look
back at it. For example, I could use a scope like this as a logic analyzer.
A digital signal is simply a signal. I would digitize it, go look at it and
see what happened. With a analog scope this is impossible because you have
no way to see the history. If you try to view it in real time then chances
are you'll not catch anything because it went by too fast. If you have the
whole signal stored in memory then you can easily go back and do processing
on it and view it. You can even view it for ringing and such and get all the
details you need up to the bandwidth/sample rate of the conversion. Ofcourse
even if its not in real time you don't need to display unnecessary
information that the user cannot process.
About the haystack. No, thats not true. You don't understand very well. You
can have triggers, intelligent searches, etc... I'd take that ability to be
able to go back and look at some instant of the signal that was momentary
than loose it for ever. Ofcourse if your dealing with several seconds of a
signal samples at about 1GS/s then it would probably take you several days
to find some random event that happened. Having some intelligent way to go
through the signal would move that down to a few mins. Similary to how a
word processing application works. If your looking for every instance of
some word you do not have to manually search through the whole document.
You could have something like "bookmarks" that set a bookmark when a search
"trigger" occured. This way you can very easily navigate to specific events.
That's the equivalent feature of Wave inspector from Tektronix: