SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : The *NEW* Frank Coluccio Technology Forum -- Ignore unavailable to you. Want to Upgrade?


To: axial who wrote (35695)9/15/2010 8:55:28 AM
From: Frank A. Coluccio  Read Replies (1) | Respond to of 46821
 
Hi Jim.

In my previous post in this thread I took some off the top of my head liberties by SWAG-ing numbers out of the blue and now realize I overstated the delays of an optimal link earlier, since

[1] I probably doubled the time for DSP processing times, and

[2] the latency demands on the codecs used in wireless-mic applications are generally under 5 ms, while some devices are capable of under 2 ms.

As for the physics you asked about, see Table 6 .1: Single Hop Delay Calculation at this Cisco White Paper: bit.ly and subtract the receiv buffering and dejittering processes I mentioned earlier. I stand corrected on the 'send-side' buffer I mentioned earlier. As you can see in Table 6.1 referenced above, it was the packetization delay that I should have cited, instead.

As for my mentioning automobile insurance and mobile telephony applications as a couple of examples of emerging, dynamic, algorithmic-based transaction processing applications (over in the HFT thread), it was merely an attempt on my part to steer the discussion back to its technology-oriented aspects, and in no way was it an attempt at minimizing the risks associated with HFT. You may recall, in fact, that I posted similar concerns earlier on, although not to the same depth that you've apparently examined the subject over the years.

As for your posting a longer treatment on the topic of risks presented by the current HFT paradigm, I suggest that you devote a little time to creating a treatise-like writing on the subject, if it is your intention to be comprehensive about it, and post it in one or only a few longer messages for expository and reference purposes. So yes, I'd be interested in seeing the breadth of the threats as you perceive them. Also, I'd gladly entertain using the old FCTF thread for a longer discussion on the topic, or even engaging you, or following your views on the topic, if you were to post them to a new thread named after the subject, if such a thread on SI doesn't already exist, but that is your call to make.

FAC

------



To: axial who wrote (35695)9/15/2010 1:04:33 PM
From: Win-Lose-Draw  Read Replies (3) | Respond to of 46821
 
Musicians don't want any lag between what they play or sing, and what they hear.

Being the drummer, I often use more mics than the rest of the band combined. :P

Look, if we accept that there should be dedicated bandwidth reserved for any given particular special use, then we accept that *any* special use may have a legitimate claim for their own swath of "interference free" spectrum. They also may not, but we can't reject on a fundamental principle that they don't.

Before you know it, we end up - well - we end up exactly where we are. And I don't think too many of us are all that impressed with where we currently are, spectrum-use-wise.

"We have to do it this way" sounds an awful lot like the claims made by the TV guys and radio guys and every other set of guys who had/have legacy spectrum. Audio is fundamentally low-bandwidth - as an engineer I do not accept we can't find a better way with proper motivation.

(I'm just using you as a jumping off point, J)