Showing posts with label AV. Show all posts
Showing posts with label AV. Show all posts

Friday, July 3, 2015

Does Sex Sell? On Appropriate Demo Material

I'm not doing much in terms of post-Infcomm wrap-up this year; like some of you, I watched from afar. There might be something to say about that process and how it developed over the years, especially with new tools like Periscope available for live-streaming of booth-tours and even parties. Today I'd like to revisit the depressingly common theme of casual sexism in the tech industry and why we all need to grow up a little bit.

If one is displaying a video product, one needs to think carefully about what test media to use. It need to be the right format. It needs to have a wide enough range of colors to highlight the display technology. Video streaming products need to have enough motion to prove that they can handle it without too many distracting artifacts. And, in something which should go without saying but sadly doesn't, the material needs to be appropriate for the situation and the audience. When we are at a business event - and trade shows, demo facilities, and showrooms ARE business settings - we need to conduct ourselves in a businesslike manner. If you want to be taken seriously, this is not the time to try to attract the (straight) male gaze with "sexy" content.
I discussed this very issue with a video transport manufacturer two years ago; in that case I expressed discomfort to the national sales manager manning the booth and was answered with a shrug, a smirk, and an "I like it." That is what I remembered. This year the only impression I got of the ClearOne booth was this photograph, semi-anonymously shared with me. Yes, ClearOne chose to demo their network streaming solution with a loop of a lingerie show.

Why do I have an issue with this kind of media? First, and most obviously, is the point that it is demeaning to women. It sends a message to the female clients, contractors, consultants, and other professionals that they are in a "boys club" with a culture that sees women as decoration. It doesn't tell women "keep out", but it reminds them that they are in a place where they are seen to not belong. Enough of that kind of message and they'll feel that they don't belong; Clear One (and others who use this strategy) certainly aren't trying to talk to them.

Secondly, and equally important, it sends a message about their judgement. If I can't trust you to not display a six-foot tall image of a woman's derriere at a tradeshow, then why should I specify your product and risk having to expose contractors, clients, or other subcontractors to you and your team? What confidence can I have that the careless attitude about subtexts is not part of a corporate culture? One factor at which I look when specifying equipment is support; does a manufacturer have track record of standing behind their product, would they bring a team to site if needed, and would that team act like professional adults? The choice to screen a lingerie show on ones demo wall gives me zero confidence, especially non the last point.

AV systems once relied more on physical media than they do today; when I worked for AV integration firms I'd sometimes have ot provide media for testing. I remember grabbing a VHS tape from my personal collection when the office's stock of "official" media was elsewhere, and apologizing for the choice: Barney the Dinosaur. The tech on site laughed and said that he always used Thomas the Train Engine. Why? Because it was as aggressively harmless and inoffensive as media can be. No risk of salty language, no risk of anything suggestive or otherwise inappropriate, just video content mild enough for a toddler. I'm not saying that demo media need to be all purple dinosaurs and anthropomorphic trains. I AM saying that we need to be mindful of our potential audience, of the messages we might be sending.

Let your product speak for itself. Next time you arrange a demo, do so in such a way that it is brought ot my attention for the quality of your product and your work, not for your poor judgement.

Wednesday, June 17, 2015

Witches and Wizards and Women in Tech

I promised more on women in technology, but I'll set that aside for a moment to broaden the discussion. Is female representation still an issue? Of course it is.  Do I have anything more to say to my fellow AV professionals who complain that groups for advancement of women in the industry is somehow sexist? Only that I long for the day that we no longer need them - and on the day when an all-female panel addresses a gender-balanced audience on technology I'll know that that time has come. I feel that it is still a long way away. For more on representation, I'll direct you to programmer Hope Roth, who I quoted earlier this week. This is more her story than mine, so you should read her words.

No, today I'm going to talk about an old critique of the first Harry Potter books and how they apply to the discussion at hand.

Way back in 2000, Christine Shoeffer wrote a critique of Harry Potter from a feminist perspective, with which I not quite all agree. One part that does resonate with me is the idea that traditionally "female" forms of magic - divination, for example - are given less respect and attention than more typically "male" forms. 

Sybill Trelawney is the other female professor we encounter. She teaches divination, a subject that includes tea-leaf reading, palmistry, crystal gazing — all the intuitive arts commonly associated with female practitioners. Trelawney is a misty, dreamy, dewy charlatan, whose “clairvoyant vibrations” are the subject of constant scorn and ridicule. The only time she makes an accurate prediction, she doesn’t even know it because she goes into a stupor. Because most of her students and all of her colleagues dismiss her, the entire intuitive tradition of fortune-telling, a female domain, is discredited.

This is a valid criticism. In fact, the very symbol of wizardry is the phallic wand, while the cup, a feminine tool, is pretty much ignored. Women, though assigned the needlessly gendered-name "witches"  do get to wield wands and perform "wizardly"  magic aside their male peers.

Putting a want in a witch's hand and giving her access to the male form of magic is an improvement in some ways, but a furthering of harm in others. It's sets the male-dominated hermetic magic tradition as the only valid one, casts aside women working in female traditions. Women can earn respect, but only by becoming more like men.

Contrast the depiction of witches and wizards in the late Terry Pratchett's Discworld novels. Pratchett's wizards were, at their best,  studious, and intellectual. At their worst, they were prone to petty squabbles, professional maneuvering and backstabbing at their "Unseen University", and as often as not cause trouble by experimenting first and thinking about the possible repercussions second. Pratchett also writes about witches. They have many traditional witchly trappings: the broomstick, the cottage in the woods, knowledge of herbs and such. At their worst, witches can be meddlesome busybodies. What's more interesting is that at their best, witches become part of the glue that hold communities together and empower those around them. Some of the most sympathetic heroes in the books - including Tiffany Aching of the young-adult subset of the Discworld novels - are witches. It's an aspect of Pratchett's writing which shows great respect for and elevates that status of traditional female roles.

Yes, I know. You're wondering what this has to do with women in technology. Fighting for a women's role in STEM fields is a bit like letting women into Hogwarts to wield wands and mix potions. It's vitally important for the women with desires and aptitude for that work AND for those of us who will benefit from their skills, but it isn't the entire story. There's a whole world outside of traditional STEM which doesn't always get the respect it deserves. Physicians are highly respected and highly paid, but mental health practitioners aren't. Schoolteachers receive minimal respect and even more minimal money. Big budget films are created from traditional boys' toys and cartoons created for the young males of yesteryear.

I mentioned Hope Roth at the opening of this piece. Her role is important, and it's important for her to be allowed it. She's a talented programmer; she's Hermione Granger, wielding her wand alongside the boys. We need to respect and honor her efforts, but we also need to find the Tiffany Achings, the Esmerelda Weatherwaxes, and to honor them equally.

Monday, June 15, 2015

All-Male Panels - on Representation

The is an AV post but also a feminist post; it seems that this is the time of year for me to discuss such things. Last year, if we'll recall, I wrote about the use of female models to attract attention at trade-shows - so called "booth babes". What got my attention this year? I had an interesting and sometimes frustrating set of discussions on Twitter regarding the upcoming Infocomm keynote speech to kick off the show in Orlando. The keynote is something different and sounds legitimately interesting: New York Times lead technology writer Nick Bilton is moderating a panel discussion/debate on the Internet of Things, including implications for privacy and security as well as growth potential and open specifications for this segment of the industry. Panelists include Fred Bargetzi, CTO of Crestron Electronics, Ron Gazzola, VP of marketing for Samsung, Kevin Hague of Harman, and Mike Walker of Cisco. It's a smart, accomplished group of men representing some of the largest and most influential manufacturers in the industry. 

So what's the problem? Heather Sidorowicz, owner of residential AV contractor Southtown AV, pointed it out:



Yes, five out of the five speakers are men. I seconded my discomfort with this (coupled by honest embarrassment that I'd not noticed it myself), and was immediately greeted with fairly tense skepticism about the idea of seeking diversity for its own sake. The concern was that seeking to include women on a panel would potentially pass over more qualified candidates if all of the best choices were men. I'll agree that he idea that one should select the most qualified candidates for any position - be that on a discussion panel, as new hires, or as bullpen arms for a major league baseball team - is an appealing one. It's also one with which I fundamentally disagree. 

The first question we can ask ourselves is what one means by "most qualified". How does one measure qualifications to sit on a panel and discuss technology? For something like the Infocomm keynote, speakers should have a firm grasp of the subject matter, an engaging public speaking style, and a position in the industry giving them access to information about not only current trends but short- and long-term roadmaps. The last qualification - place in the industry and access to information - is measurable. The other ones, interestingly, are not. This means that any move to choose "the best people" are, almost by definition, subjective. This is not akin to choosing, for example, the fastest person to run a leg of a relay race. There's no stopwatch, no scale, no yardstick against which to measure the "best" speaker. I'd make exactly the same argument on a broader level for choosing the "best" new hire to be the "best" employee. There are scores of factors, only the most superficial of which are easily measurable. Our biases - even if only subconciously - will affect our choices.

I gave "bullpen arm for a baseball team" as one hiring example. This may seem to be a case in which you CAN make objective measurements, but let's look at this as an analogy: you're looking to find the best pitcher to add to the team. You measure by strikeouts, walks and hits per innings pitched, and a dizzying array of advanced statistical metrics. Say that the best four choices for two available roster positions are all hard-throwing right-handers. Do you sign all four of them, or do you select a soft-tossing lefty who might not be in some ways as "qualified", but adds something the others don't.

This is one reason why all-male panels are problematic. Seeing a group of middle-aged white men presented as the topic experts they are reinforces the subconcious idea that this is what a technology thought-leader looks like: a middle-aged white man. As a middle-aged white man myself, I benefit from this. I was not only always encouraged to pursue math and science education, I was pushed to try again and harder if I struggled with something. Professionally, I was offered the chances to take more technical roles and responded quite favorably when I asked to. Would it have been the same if I were from a different group? Perhaps and perhaps not. What I do know - and know that I can take for granted  - is that experts, presenters, speakers, and executives will very often be people who look like me. I'll never have the experience that AV control system programmer Hope Roth described on Twitter:



Roth shouldn't be an outsider. I've spoken with her about technology and the industry and found her to be not only very smart, but also very heavily engaged with the industry in a way that not enough people are. I want more women to engage, and I want more to see examples of how they CAN engage. An all-male panel sends a message to Roth and those like her that their voices aren't the ones that we want to hear.

We should want to hear those voices. While we don't have any women in a technical capacity at SMW's office here in New York, my cubicle-neighbor is an African-American millenial. Sharing a workplace with someone much younger than I am with a different background gives me different ways of looking at not only projects and various corporate cultures, but the the world at large. I'd argue that his presence makes me not only a better AV designer by giving me different ways to look at corporate cultures, but also a better person by pulling me out of my comfort zone.

The Infocomm keynote panel looks terrific, but like so many other all-male panels it runs the risk of keeping us too far within our comfort zones and of NOT reaching out to those who aren't already part of the tribe. We can do better. And, I hope, we will.

Expect more on this topic in posts to come. I will close with one note of caution: while we need to listen to the thoughts of our sisters in the industry on this, we need to approach respectfully. It's tempting to ask a woman in the field what she thinks of representation, how it feels to be a woman in the field, etc. Doing so runs the risk of making her the Ambassador of Femininity at best, and the Travelling Female Museum Show at worst. Remember that all of us - men and women alike - are first and foremost humans. That doesn't mean that representation isn't important, but it does mean that we all need to remember that no group marches in lockstep, and to ask that one speak for all is another form of unfairness.

Tuesday, June 9, 2015

AV Control, Automation, and Expectations in a Consumer-drive World

Control and automation can be the most fun part of AV design; from the blank canvas of a user interface one can create anything. Preview windows? Live tiles? A photo of the room which reacts as conditions change? Imagination is the limit, but there are many pitfalls. Today we'll talk about why some users fear control systems and why some manufacturers fear their own potential resellers.

There's no question that the control interface is a major component in determining user experience; if controls are too simple, users will feel that the system is limited in capability. Too complex and it will be overwhelming and difficult to use. Poorly laid out controls make the experience uncomfortable and unpleasant, if not confusing.  How do people outside the industry see this aspect of AV design? I see a few trends.

To the User, The System IS the Program
This is an obvious point, and one on which we need to educate the public. I discussed the possibility of control systems with a family member when he was moving. He initially considered the idea but, after speaking to some of his friends, decided against it. One of the biggest factors was the number of people who said that they didn't like the system interface,that it was confusing to use or not flexible enough. This was a fully programmable system in which the interface would be whatever the programmer created. It's a bit like saying that you don't like your computer because the menu structure on your spreadsheet program is  difficult to use. It doesn't matter: the association had been made that Brand X (I'll not name them here) = bad experience. While not the only factor, this was one factor in his decision to not get a control system.

This came to mind yesterday during a Twitter discussion about how a certain manufacturer doesn't always make it easy for smaller AV contractors to buy their  control products. From the contractor's  point of view, I see this as not only frustrating, but as pushing them away from a brand which they'd otherwise be interested in supporting. Looking at the above discussion with the public, it makes perfect sense. If you let one poorly trained individual muddle through control system programming, their sloppy work creates the impression that your hardware is not very good. 

Configurable, rather than programmable, systems mitigate this a bit; a configurable system allows the manufacturer to carefully craft an interface which will fit the majority of simple configurations. This is, perhaps, a greater part of the configurable systems' value than the significant savings on programming labor. It is a way in which a manufacturer can control the experience while still allowing wide access to their devices. 

Consumerization Creates Familiarity - For Good and Ill
Not too many years ago, the initial part of training for an integrated AV system in a corporate environment dealt with convincing users that they don't need the "TV remote" and that they should control everything via the nice custom GUI on the touchpanel. Today most of us have touch panels in our pockets, and many of us have the ability to control something in the outside world with them. This means that a touchpanel is no longer foreign, but also that it's no longer special. An eye opening moment came when I was discussing device layout in the final stages of construction for a new fairly high-technology facility. One of the users pointed at a table and said "We don't want the iPad there. The people at that position only need a microphone."

The "iPad" in this context was a desktop-mounted touchpanel, complete with the control manufacturer's logo. It was over a thousand dollars in hardware with countless hours of custom programming and GUI design. It didn't matter. To the user it was a ten-inch touchpanel;  the same thing they use to watch Netflix. Turning on the big video wall with the touchpanel is no more special than streaming a YouTube video to the TV in your living room.
A day at programming class

We're Being Spoiled by Off the Shelf Tools
A few years ago I took introductory Crestron training and learned, amongst other things, how to build a rudimentary control GUI. One class exercise was creating a transport control page for a DVD player. We had to draw buttons, map them the appropriate commands, and set up feedback to buttons remained in the engaged state if appropriate. It took some time and some knowledge. This past year, as some of you know, I moved. We unpacked the DVD player long before we unpacked its handheld remote - a remote which I'm still not certain I found. This was no problem; in just a few minutes I was able to download a free remote app on my phone which just so happens to have an IR emitter. I can now use my phone as a remote for anything I own.

Automation and No-Touch Control Will become expected
"Wow moments"  are becoming few and far between. During an excellent webinar on modern control system design, Sumanth Rayancha of Pepperdash listed "no-touch" fully automated control as one future trend. An example was the "smart meeting room". Once a meeting is booked, everythign becomes automatic. Lights come on to the appropriate level when the presenter enters, the correct technology activates itself, complete with display of a presentation. An email or text message can even be sent to the food service team to deliver lunch. It's am amazing growth in the potential of control and automation.

This is amazing, but still well within reach of consumers; just this morning my wife was lamenting that if she forgets to turn off phone notifications on her phone before bedtime she'll often get woken up by something or other; I pointed out that it is now fairly easy to use a web-service such as If This Then That to automatically silence and unsilence your phone at certain times of day. One can also turn on the porch light, off the hall light, etc. As more people come aware of these things, they will become more expected.

Not many years ago there was a bit of a "wow" moment when you hit the "VideoConference" button on a touchpanel and the shades closed, lights adjusted themselves, cameras swung into position, and displays lit up. That is quickly becoming just as familiar as the "iPad" on the table.


What does this mean? It means that the expectations have never been higher. It's not enough anymore to have control or even automation - we need to have it and present it in a manner which is thoughtful, pleasant to use, and fills all of the users' needs. Otherwise we're back to users seeing AV systems - and hardware - as "terrible" because someone didn't make it do what they expected of it.

Wednesday, June 3, 2015

Onward - Towards the Future!

I'll open with a personal note: this marks the 200th published post on this blog! Over the past years we've talked about commercial AV, speculative fiction, and even enjoyed some original writing. I'd like to thank all of you for joining me on this journey, and hope to continue to share my words with you for a long time to come.

Thanks for listening. And now onward -- towards the future!

As those outside of the industry don't always know what they should be looking for in terms of AV solutions, requirements often incorporate broad concepts at best, buzzwords at worst. Some of the most common are scalability, accessibility, and today's topic, future-proofing. It makes AV design like a science-fiction story in that it reaches from the present towards an imagined future. Like good SF, a "future proof" technological solution must make sense today even as it builds towards our best guess at tomorrow. How does one future proof? Is it even possible in so rapidly a changing world? Let's consider some opportunities and some potential pitfalls in building for the future.

When is the Future?
The first point to discuss is what you mean by "future": is it next decade, next year, or next week? From the perspective of AV design, next week is still "today" while next decade - at least from an equipment and systems point of view - may very well be the end of time.



Conceptual Design - What does the future mean to you?
Before pen goes to paper to create actual designs, there need be a discussion on not only current uses but on future plans. Are we looking at a corporate environment in which real time collaboration and document sharing will be the focus? Real-time collaboration between branch offices of an expanding firm?

If it's an educational institution, are plans being made for new pedagogies, including "flipped classrooms", distance learning, or creation of on-demand content?

Some of the above are user-focused discussions, based on their business models and future plans. It's also important to have AV industry-focused discussions centered on the things about which we know. Will the spaces discussed someday be a good fit for 4K resolution and beyond? Will a converged network topology allow greater flexibility? Will there be appropriate uses for emerging technologies such as virtual or augmented reality? In these cases industry trends and client needs go hand-in-hand; as professionals, we cannot simply ask "where do you see yourself in five years?" We need to tell the client "in five years, the technology will likely be available to do this, which can fit your operation in this way. Let's explore the possibilities together."

We need to think boldly, and we need to remember that the future may not look like today. I'm reminded of Isaac Asimov's science fiction. He got many things right, but there were so many either near- or complete-misses. The first of his classic Foundation novels centered around a project to create a "galactic enclopedia" to save human knowledge in the face of an upcoming galactic collapse. He couldn't imagine that such an encylopedia would not only exist, but be created by a loose network of volunteers. Early computers were big, so he posited bigger and bigger centralized automated computers, rather than the distributed networks of smaller computers we see today. The point is that the future is the future; don't expect it to be the exactly like the present only moreso.

Infrastructure
The first - and least sexy - part of AV design is infrastructure. This is the part in which we discuss floor boxes, wall-boxes, conduit, electrical power, and data requirements. It's not what people think of when they think "technology", but good infrastructure design can be the difference between an easy, pleasant project and a tangled mess of work-arounds and improvisation.

Infrastrucre can also be a bit of a tightrope. On one side, it is absolutely imperative to have enough infrastructure in place to be able to build the system. On the other hand, somebody has to pay for all of the pipes, boxes, and power for which we ask. It can be a delicate balancing act.

I'm reminded of Isaac Asimov's science fiction. He got many things right, but there were so many either near- or complete-misses. The first of his classic Foundation novels centered around a project to create a "galactic enclopedia" to save human knowledge in the face of an upcoming galactic collapse. He couldn't imagine that such an encylopedia would not only exist, but be created by a loose network of volunteers.

At this point we start talking about not only raceways, but the physical plant, as we bleed into system design.

There's been plenty of talk about 4K video recently, and plenty of confusion about what is, at this point, present technology. See fellow AV blogger try to make sense of the spec sheets on various digital video switching systems. One thing has become clear: 4K uses a great deal of bandwidth, 8K - when it comes - will use even more. Is it time to step away from our old friend copper and start using single-mode fiber? Is the cost of fiber too great to be reasonable for the modest gain it will give us today? As usual, the answer is that it depends. As one nears the distance limitations of current technology, there can at least be a concern that higher-bandwidth future applications may fail using current wiring standards.

Software vs Hardware, modular vs all-in-one
Finally, we reach questions of design topolgy. Are elements replacable and upgradable, or is the only upgrade path a complete system redesign? This is where reliance on "all-in-one" presentation systems including a video matrix switch, audio and control processors, and audio amplifers in a single box can be a scary proposition. They are useful in that they afford a simple, cost-effective solution. A "room in a box" if you will. The drawback is that an upgrade to the video transport system, for example, means replacing everything: control, audio, and local switching. The upgrade path becomes a matter of throwing it away andstarting anew.

This is one intriguing positive for software solutions; software grows, software is supported software is updated, software can be replaced by client's own IT department. When we say that software eats hardware, this is one reason; replacing software rarely means replacing actual infrastructure or equipment.

Follow the trends, gaze into the crystal ball
The concept of future-proofing and of designing for the future is one reason I spent so much time last week on possible HDBaseT and TSN-based solutions which are years out from being actual product; the project which starts today might not be completely built until next year or later. Sometimes future-proofing means creating a solution which can grow with changing technologies and requirements, but sometimes it can mean creating a solution which is current the day it is completed.
Ask the next question


I'll close with words from another science fiction writer: the great Theodore Sturgeon. "Ask the next question.

"Ask the next question." Ask the next question, and the one that follows that, and the one that follows that. It's the symbol of everything humanity has ever created, and is the reason it has been created. This guy is sitting in a cave and he says, "Why can't man fly?" Well, that's the question. The answer may not help him, but the question now has been asked.
The next question is what? How? And so all through the ages, people have been trying to find out the answer to that question. We've found the answer, and we do fly. This is true of every accomplishment, whether it's technology or literature, poetry, political systems or anything else. That is it. Ask the next question. And the one after that."

This, perhaps, is what future-proofing really is. It's asking questions, then asking the next question and seeing where it leads. 

Thursday, May 28, 2015

Pixels and Erasable Ink - Could I be wrong?

Those of you who follow my musings on the world of professional AV know that I can be skeptical at times. I'm skeptical about AVB. I was skeptical about video over IP. I'm skeptical about the continued value of HDBaseT. What I try not to be is cynical; it's good to start off questioning new assumptions, but it's equally important to balance those questions with an open mind. Technology, after all, is not a static thing. What made sense yesterday might be pure folly tomorrow. With that in mind, I'd like to tell you about two points on which I might be wrong.

AVB - Is it dead yet?
This is a question one of my colleagues asked me last year at the Infocomm trade show. The question had a pleading tone, as if wishing for what increasingly looks like a zombie technology to be put out of its misery. We'd all seen the same proof-of-concept video-over-AVB streaming demo two years running at that point. We saw one major DSP manufacturer choose an audio transport system based on AVB while nearly everyone else chose Audinate's Dante protocol. We saw the major manufacturers of network switches decline to support AVB year after year. In short, we saw a very promising technology losing a format war.

Or did we?

After years wandering down the same dead-end path, the AVNu alliance (the people behind the creation of the AVB standard) finally realized their biggest problem. It's a problem unrelated to bandwidth requirements of low-latency AV transport, unrelated to network traffic shaping, unrelated to questions of layer 2 or layer 3 protocols. It's so simple a problem that we can all understand it, and we all should have seen it sooner.

The problem is the name.

The problem is that the name leads to comparisons like the one I just made with Dante which is, to be honest, a poor comparison.

We've all known for years that AVB is not a streaming technology; it is a suite of IEEE 802.1xx standards for bandwidth reservation and time synchonization over networks. Solving the "lip sync" problem for separate audio and video streams is one application of this technology. It is also of vital importance, for example, in syncing control and sensor signals for electronically controlled manufacturing processes. Whatever transport technologies we use today can be enhanced by access to the tools within AVB, not replaced by them. The debate between AVB and Dante is a bit like saying that you don't believe that a series of new high-speed carpool lanes  would make a difference because you're driving a Prius. It's a non-comparison.

The problem is that the name "AVB" for "Audio Video Bridging" sounds like a transport technology and has been, to a very large extent, marketed as one. What does AVB do? It creates a bridge over which one sends audio and video signals.  Audio manufacturers with AVB compliant products don't help this when they describe "audio over AVB" not "network audio taking advantage of AVB's timing protocols".  I know that AVB is a suite of 802.1xx standards, but when I hear the words "Audio Video Bridging" my brain sees a transport protocol. As is often the case, language informs thought.

To solve this problem, AVB has picked up a new name; TSN or "Time Synchronized Networking". This divorces AVB from the "A" and the "V", aligning the language with what the standard actually is.

So will our future AV over IP systems take advantage of these new protocols? Perhaps - if those are the systems we build. Or perhaps there won't be a large enough volume of networks requiring time synchronization for these tools ever to be widely adopted. Time will tell.

For AV transport, there is another option.

HDBaseT - A Bridge to Itself?
I, and many others, have described HDBaseT as a "bridge technology" between yesterday's point-to-point systems and tomorrow's video over IP systems. In an earlier post I spoke about the value of HDBaseT and what advantages and disadvantages it has over IP video. Most of that is absolutely correct today. It might be the opposite of correct tomorrow.
The bridge is a metaphor

I had the pleasure of a terrific conversation with Micha Risling, marketting director of the HDBaseT alliance. Mr. Risling pointed me to part of the HDBaseT 2.0 specifation I'd admittedly payed too little attention to at the time. Take a moment to look at this image from the HDBaseT alliance website, comparing 1.0 to 2.0.

Does that look familiar to you? It should; it's quite similar to the OSI stack. For years we've thought of HDBaseT as something that looks like an IP network but isn't; it's a point to point transport technology using the same physical topology - but no the same logical topology - as IP.

Or is it?
This layercake looks familiar
(image from HDBaseT.org)

There is, as of the release of the 2.0 spec, no reason that HDBaseT cannot exist in a packet-switched environment similar to any other network, using "HDBaseT switches" more akin to the network switches we know and love than the AV matrix switches of today. Such switches would use an internal addressing scheme, signals would be routable between switches, and the overall scalability problems of current HDBaseT systems would be a thing of the past. The HDBaseT alliance sees their dedicated video network as a better solution than a "converged" network for AV transport. Bandwidth requirements for uncompressed video - especially at resolutions of 4K or beyond - could be, at the very least, challenging to implement on a larger network. HDBaseT is purpose-built for video transport with, they claim, better cross-network optimization than the IP we know and love.

Will all of this come to fruition? I don't know; what I DO know is that the chipset for such an "HDBaseT switch" is in development today, and that we might not be that far from seeing HDBaseT as a packet-switched technology rather than point-to-point as is currently the case.


If HDBaseT has a "language problem", it's the opposite of the problem AVB has; as HDBaseT sounds enough like "100BaseT" (fast ethernet) and "1000BaseT" (gigabit ethernet) to cause confusion, we've all worked very hard to remind ourselves that it is a very different thing with a different logical topology. That it might not be so different after all is, to say the least, jarring.

Will the benefits of HDBaseT switching balance the challenges of deploying and maintaining parallel but separate networks? Will the demands of video on converged networks push us to separate networks anyway? Many questions remain and the devils are, as always, in the details.

Whatever may come, we'll talk about it when it gets here. You can expect to hear me question it, but with an open mind and open eyes.
Time will tell if my initial guesses are proven right or wrong.

Friday, May 22, 2015

Flash Fiction Friday - Community, Hashtags, and The Future of AV!

This will be one of two upcoming Flash Fiction Fridays dealing with the moon, and more science-fictional than my usual fare. As readers of this blog know, I not only work in the audiovisual field, but also have a somewhat active presence in the AV online community, including occasional appearance on AV-related podcasts, this blog, and the AV twitterati. AV twitter peeps (referring to ourselves with the hashtag #AVTweeps).

A massive #AVSelfie
One thing at which some AVTweeps have done an excellent job is the creation of community through shared experiences - often trivial ones. Last year at Infocomm (the annual AV tradeshow) Chris Neto came up with the idea for the "#AVSelfie" hashtag; people were encouraged to take selfies either at the show or with AV equipment. There was even, believe it or not, a music video. If you don't blink you'll see your favorite pixel-and-inkstained wretch, taking a selfie at the moment the song premiered (on the AVWeek podcast).

More recently, there's a weekly #AVHashtags game; a weekly joke hashtag with which we AVTweeps play. We've had AVTVshows, we've ReplacedAVWithFruit, and other silliness.

This year's game was #Infocomm2099 - imagining the AV industry through a trade show nearly 75 years in the future. I love the future, and like the idea of using small details from press-releases, foot-notes, and what would be other "found" writing to sketch a picture of future worlds. This is too much to cram into 140 characters on Twitter, so I give to you the following Two Excerpts from the Infocomm2099 Program.

Enjoy.


-----------------------------------------------------------------------------------------------

"Two Excerpts from the Infocomm2099 program"

Training, Day 1
Tuesday, 9AM
Vid127 (Video, Intermediate), Instructor: Glenn Yorreazz. Use of standing tachyon waves to achieve lip-sync in non-deterministic video systems
    • For as long as video streaming has been with us, so too have lip-sync issues. Explore the use of time itself to solve the conumdrum!
Net103 (Network, Basic), Instructor: Jarash Gosou. Mystifying Time-Aware Networks.
    • Explore the metaphysics behind this newest incarnation of the soon-to-be-adopted TAW suite of IEEE protocols. Originally introduced as audiovideo bridging, this is a technology whose time has come. Learn why you'll expect to start seeing TAW products next year.
Aud322 (Audio, Advanced), Instructor Glenn Yorreazz. Catching the retro "wave" - the use of air pressure waves as an audio transport tool
    • Discuss the opportunities and challenges inherent in this age-old alternative to subcutaneous speaker implants or direct neural transmission.
Vid127 (Video, Basic): Instructor Marco Knox. Quantum Entanglement and HDCP7.2
    • Understand the physics behind the newest digital content protection standard, including a discussion of the continuing issues we have with the HDMI9.7 standard which still lacks a locking connector.
Gen133 (General, intermediate): Instructor, Glenn Yorreazz: Time Management Techniques
    • Learn how the instructor is using temporal fugue to teach three simultaneous courses while walking the show-floor and visiting the nearby theme park.

---------------------------------------------------------------------------------------------------
Special Event: Lunar Projection Mapping
Congratulations to the Infocomm member known as AVSunrise, of NewBoston. In a first, her winning design will be projected onto the moon itself using multiple banks  Sircthie Digital's new advanced TurboLaser projectors, placed throughout the hemisphere. See the following Q&A with Sirchtie spokesman Dick Bowlerton.

Q: Tell us about this project
A: The TurboLASER projector is a first in its class. Centuries-out-of-date regulations limit use of LASER light in earth-based projection, but sending light to the moon is safe and effective.

Q: Tell us a bit about the technology
A: Light engines are located at various generation hubs (ie, Pacific tidal generators, Hoover Dam), with light pumped to transmission units via fiber optics. We'd planned a field-trip to the Southwest Windfarms, but the prototype wasn't read last year and this, as you know, is an Orlando year.

Q: How do you answe concerns that the focused energy would be any danger to the newly active Lunar tectonics, and the lawsuits threatening to shut the project down?
A: This is very, very highly unlikely. Our engineers are confident that the moon will survive! If it doesn't survive, out multi-body algorithm will be quite well suited for projecting images on the ensuing dust cloud. Just kidding about that last part. But it really would work.

Q: What else is new from Sirchtie?  

A: Inerplanetary mapping is a big thing. More of this will be detailed in the free interactive neural upload "Book of Explorations", including a new plan to "paint" canals on the surface of Mars, several major advertising initiatives, and a few surprises. At last, we can see the world as we see it in our imaginations. Expect new wonders, new miracles. The world is our canvas.

Wednesday, May 20, 2015

On Wire Management, Flyball pitchers, and an awkward-looking shortstop

I recall a mathematics professor using an HL Mencken quote to describe a particularly intractable physics puzzle:

"Explanations exist. They have existed for all time; there is always a well-known solution to every human problem - neat, plausible, and wrong."

(I'm certain that the abovementioned professor paraphrased Mencken, but thanks to the power of the internet we can get the quote right).

Three discussions I had over the past week brought this idea to mind, and have me reflecting on the limits of intuition and of statistics, both professionally and recreationally:
  1. A discussion of the defensive ability of New York Mets shortstop Wilmer Flores
  2. Predictions on future success of Mets pitcher Carlos Torres
  3. A discussion on the AV Installation Nightmares Facebook group on the merits of plastic cable ties as opposed to hook-and-loop straps to bundle category cable.

What do the above have in common? All are, to some of us, important questions. None are within our ability to intuitively answer. What it comes down to, in the end, is almost a question of epistemology: how does one know that an assertion is true?

A Data Driven World - When Statistics are the Answer
We know things today. Gathering data is a skill at which we have become quite adept. One high-profile example of this is in election predictions: there has always been a great deal of polling and data gathering before elections. In recent years it's become possible - even easy - to gather data from wide areas over years, make comparisons, and see which correlations appear stable over time. This lead, for example, to several statistics-based analysts (ie, Nate Silver of "538" and Wang of the Princeton Election Consortium) to predict the last Presidential and midterm election with nearly frightening accuracy. More traditional pundits relying on fewer numbers but more experience and intuition ran into one of Mencken's neat, plausible, and wrong explanations.
Warmups at CitiField, Queens NY

The key is in knowing what one knows and how to leverage that knowledge. This brings us to the discussion of Carlos Torres, relief pitcher for the New York Mets. In a discussion on the Amazing Avenue blog, one commenter asserted that based on statistical analysis, Torres' early success was based largely on luck. A more "traditional" view would be to look at simple statitics such as "earned run average" - the number of runs allowed per nine innings - or "batting average against" - how often opposing batters hit safely. Looking more deeply, Torres had a greater number of walks per nine innings pitched than expected, and possibly a lower "batting average for balls in play"; looking at these statistics, it appears more apparent that his success is a bit of a statistical anomaly.

What fascinated me is that that didn't end the discussion. Another poster - a young man going by the handle "noahmets" who is about to begin an internship with baseball analysis website Harball Times. Noah's contention is that one can look at a set of statistics called  "Pitch f(x)" which give details of the exact location, result (ie, swing and miss, put in play, pitch taken) and even spin-rate of each thrown ball. This data is available via sensors which have been installed in every major league ballpark since 2006. Having this extra data lets us see more and, hopefully, derive stats which are more stable over time. He was able to add a dizzying alphabet soup of pitching statistics which control for ballpark and other variables. What was once conjecture can now become predictive.

A similar discussion about shortstop Wilmer Flores eventually went nowhere; to the more "visually oriented" fans he looks awkward and appears to have limited range. To the statistically-oriented fans his numbers look just fine. The problem with the statistical argument is that he's played very few games at shortstop thus far, and those numbers have fluctuated wildly over this time. Statistics can only give an answer with a workable statistical model and sufficient data; in the case of defensive range, I'm not convinced that we have either.

How does any of this relate to AV? In the abovementioned install nightmares group, somebody posted a picture of an AV rack mid-wiring. In what was meant to be playful teasing, I "tsk tsk'd" him for using plastic cable ties on category cable. What followed was a discussion on why one should use hook-and-eye (ie, velcro) straps instead of cable ties, IF one should do so, if it even makes a difference. My arguments against plastic ties:
  1. Ties fastened too tightly can deform the precisely-manufactured cable, increasing crosstalk between pairs
  2. It's very easy to accidentally overtighten, especially if fastening many of them
  3. BICCSI standards recomment against using nylon or plastic cable ties
  4. A white paper from Valens Semiconductor (maker of the chipset at the heart of HDBaseT transport systems) recommends hook-and-eye straps.

AV professional William Bloomquist had what looked like a data-driven argument against. His point:
  1. Many people use nylon ties without a problem.
  2. There are no failure statistics detailing how many failures are caused by compression caused by overtightened cable ties.

Do you see the key difference between this analysis and the above discussion on relief pitchers? We can very precisely analyze pitching because we have very precise data; Pitch f(x) is in all major league ballparks and measures every single pitch in every major league game. THis is not so for cable failures; if video doesn't pass on one cable it gets re-terminated, re-re-terminated, and perhaps replaced without anybody performing a post-mortem or a root-cause analysis on the failure. There's no pitch f(x) database listing all of the cable failures  across the industry on which we can perform analysis, no decades of polling.
Hook-and-eye cable straps, detail.

What we're left with are best practices designed to minimize failure. When I write  a bid specification, I'll include hook-and-eye fasteners for category cable because I know that that will eliminate one potential source of technician error and, ultimately, failure. Absent statistical proof, we're with the scouts evaluating shortstops based on experience and hands-on analysis. In short, with no real-world statistics and without my own laboratory, I'm left with what other experts have measured and presented. Whitepaper from Valens. Whitepapers from cable manufacturers. Best practices from those organizations in the IT industry whose job it is to know what they're talking about. 


I applaud people like Bloomquist for being prudent and insisting on statistics to back up our choices. Sometimes one needs to take a step back to understand which data is available and the limits of real-world statistical analysis. This has given me food for thought, but at the end of the day I'll still be requesting hook-and-eye straps to bundle category cable