Showing posts with label Pixels. Show all posts
Showing posts with label Pixels. Show all posts

Friday, September 18, 2015

Nerds Unite - Standing with Ahmed, for Tech and for Passion

This week's social media storm (there always seems to be one) was about the saga of one Ahmed Mohammed, 14 year old student in Texas. As I'm sure you're aware, Ahmed was taken from his class, questioned by the principle, and arrested by the police because school administrators were too racist to think that a Muslim boy could have electronics for any reason on than a bomb scare and the cops were too stupid to see that the thing he had was just a clock. Yes, I do have a slight bias towards the young student and against the administrators and teachers and police. What brought joy to my heart was the outpouring of support Ahmed received from the tech world including Mark Zuckerberg,



Commander Hadfield) and the political world - all the way up the President of the United States.


That said, there are things that make me quite sad. First, there's the reminder that we still have a long way to go in terms of diversity in the tech sector; when I attend industry events, I see an awful lot of white men. This kind of anti-encouragement isn't going to help. For every Ahmed whose story resonates across the world, I'm sure there are scores of hidden Ahmed's we don't see: the ones whose passions are quietly discouraged or quietly ignored until they stop caring and stop loving the things they love. That's the element of this about which I want to talk today: about passion and about the element of the all-too-predictable backlash against Ahmed about which I'm the most disappointed.

Fred Shen (the Shen of Shen, Milsom and Wilke) has said that one thing he's learned in his decades of business is that a positive attitude is more important than knowledge, experience, or most anything else. I'll add passion as one of those elements of attitude; people will do their best, learn the most, and accomplish the most in endeavours about which they care. This is why I adore my friends in the #AVTweeps community; someone who goes to work, does his job, and then logs onto twitter to talk about his industry is someone really interested who really cares. It's someone who will go the extra kilometer because they feel the joy in a thing well done, because they want to learn, perhaps even to show off a bit for their peers. It's the spirit of a kid who wants to learn more about electronics so he assembles a clock from spare parts to bring to his teachers, to show them "look what I'm doing. I want to do more of this." This is the call that nerd-twitter was answering - that we have our passions as well and do not wish to stand by and see the joy in learning, in doing snuffed out. Who doesn't understand this? The police. They've been soundly mocked (justifiably so) for not knowing what a clock is. What bothered me most was the statement from police spokesperson James McLennan that Ahmed maintained that it was a clock but was unable to give a "broader explanation" as to what it would be used for. Setting aside the obvious answer that clocks are used to tell the time, the broader implication to me is this: the police don't understand what all of us do. They don't understand doing a thing simply to find joy in doing, and further joy in sharing. They have no passion. They walk, yet they are dead inside.

This brings me to the people who should know better: the nerdier-than-thou techdude gatekeepers who want to dismiss Ahmed as "not a real maker" because what he did is, to them, not all that impressive. They've see pictures of the infamous clock and pointed out, perhaps accurately, that the clockish parts which make it work appear to be repurposed rather than created from individual components. It's a cake from a mix, it's a shortcut. It is, to some "not real nerdery". My answer to that is twofold. First, we all start somewhere with the tools and guidance available to us. Remember what Fred Shen said last paragraph: the kids who disassembles and reassembles devices because they loves to tinker with them will, in the end, likely travel farther than the ones who solders at the component level because they are forced to. Ahmed as the passion, he has the attitude. The rest of is is just stuff. He'll learn the stuff - if the love isn't beaten out of him first.

The second thing is that I'm an AV System designer.  There are some on the AV contracting side who will implement the systems which I design. We've all read the technical musings and heard podcast  appearances, for example, from Crestron programmer Hope Roth. Does she get fewer "techie points" because she doesn't design the hardware and didn't create her programming tools from raw assembly language, or can we honor the art in what she does and the passion for the task she has?

I, of course, design systems at the component level; I have some idea of how the parts work, but I don't build them. Over the past years I've spent literally hours talking to people like, for example, Paul Harris of Aurora Multimedia about potential new products and new product categories. My advice if you stop by the Aurora booth at a trade show? Make sure you have plenty of time, because Harris can talk about his products, the challenges in creating them, and their potential with the enthusiasm of a true fanatic. So... does he and his ilk get all the nerd points, or do we want to shrug and point out that they're just implenting FPGAs which do the heavy lifting of video encoding and packetization. Or point out that the FPGA makers are using already-invented video codecs and network topologies?

A bit of personal history: my most fondly remembered High School tech project was a digital voice recorder. It lived in a home-made plexiglass box about a foot and a half wide by three feet long, contained a mess of hand-soldered circuit boards including a timing circuit (which I had some help designing) and a whole mess of hard-wired logic gates to control start/stop functions, to set variable sample rates, and to handle the refresh cycle on the dynamic RAM chips I used. It helped, of course, that as the son of an electrical engineer I had access to not only a mentor but a basement full of tools, supplies, and test equipment. Today, of course, none of the nuts-and-bolts lessons make all that much sense; logic which was hard-wired in 1988 would live on a microprocessor now. It's the experience - taking a thing and turning into another thing, seeing and feeling a creation come to life - which shines the brightest in my memory. That's the experience for which Ahmed and so many others are reaching.

Hipster-nerd gatekeeping, at its worst.
This is why I'm upset to see fellow tech geeks shrug him off as not really one of us, his clock as a "mere" case-mod not worthy of respect. The worst comment I was was from Chris Putnam, a  former Facebook engineer who should know better. From his social media post and general bitch-fest about the topic:


For those who don't know, Putnam famously hacked Facebook to make people's profiles take on the appearance of MySpace pages. Perhaps because he was a young, white male college student the college-educated young, white, males running the place ended up offering him a job where he was instrumental in some major improvements to the platform. He didn't, of course, invent his own facebook from the ground up. I'm angry at his sad, cruel, belittling commentary because it does the same thing Ahmed's teachers are doing: discourage a young man from further participation by sending the message that he doesn't belong. It's gatekeeping, it's exclusionary, and it's counterproductive. In some ways it's worse than the teachers because, coming from inside the tech community  it could carry extra weight with not only Ahmed but with any other kids just starting to tinker.

Watch below as Putnam goes from nasty attacks to mean-spirited mockery on his Facebook page. It's not pretty watching a successful adult bullying a 14 year old just starting out in his field.

I don't know what Ahmed will grow up to be; if he'll create new generations of hardware, find new ways to implement existing tech, or even if his passions turn a different route and he becomes an artist or a poet or something. I'd like to think that, professionally or not, he'll carry his love for things tech throughout his life, even if only as a hobby. Whether he does or not, he'll always remember the joy of taking apart and rebuilding, and he'll always have this moment in which the larger community told him that we see his passion and in it recognize a reflection of our own. That we love him, that we honor him, that he belongs with us.


So Ahmed and all of you other Ahemd's out there, keep doing what you're doing. Don't ever let anyone tell you that it isn't enough. If you have the chance and want to, learn more and go farther. In any event, find your niche.

And you gatekeepers out there, the Chris Putnam's of the world, remember your roots. Learn empathy, learn humility. Welcome the next generation with open arms and open minds, even if their path does not match your.s



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.

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.

Friday, June 12, 2015

Infocomm 2015 - for what YOU will be looking!

We're setting aside Flash Fiction Friday this week for my annual look-ahead towards Infocomm. I'll not be attending this time around; with Karine not quite six-months post surgery this is an excellent time for me to not travel and continue to take care of things at home. Fear not; I'll still have my eyes on the show from afar, and have some thoughts on what I expect to hear and at what those of you who are journeying to Orlando should be looking.

Display Technology
Displays and loudspeakers are nice to see (and hear!) in person. We can be honest and admit that processing, capture, and transport gear looks like nothing more than a collection of black, greyish, or other-colored boxes; what resolution a matrix switch handles can be just as easily viewed on a spec sheet. Detailed evaluation requires the kind of time, controlled conditions, and freedom to experiment you'll not likely find at a trade show. We should, to a large extent, be looking at the things which we'd see and hear in the real world.


4K is obviously a big trend, with almost every display manufacturer on board. With OLED having finally arrived as a technology, this is a great chance to experience the difference between transmissive and emissive display technologies; I still have concerns about burn-in on OLED displays, but I'd expect them to look terrific.

Another thing which looks terrific, and of which I've spoken here before, is direct-view LED displays Christie, Barco, and Planar have all been showcasing direct-view LEDs with a 1.6mm pixel pitch. Silicon Core Lavender is an even more impressive 1.2mm.  I saw a demo of this at the Sapphire Marketting New York roadshow; it's jaw-droppingly beautiful with an equally jaw-dropping price tag. Drop by the Silicon Core booth and be amazed. Just don't ask what it costs.

No Empty Couches
Last year in Vegas one of the world's largest and most recognizable software companies purchased what felt like a square mile of show floor space which they populated with moderately comfortable couches, charging stations, and a handful of TVs showing the soccer tournament. It was the biggest expenditure for the least effect I've seen in a trade show.


This past year I'm expecting things to be different; with the announcement of the Surface Hub, Microsoft is taking a big step into the increasingly important and increasingly crowded huddle-space/small collaboration room field. The all-in-one arge touch display with a camera and microphone isn't a revolutionary concept, but but given that they own the operating system, I would expect Microsoft to have tighter software integration than many of their competitors. David Danto has sometimes extolled the value of off-the-shelf AV solutions rather than bespoke systems; I'd be curious to see the Surface Hub to evaluate what size room it can support as a standalone device. We've already been discussing possible use-cases for this in the office, including some non-traditional workflow options. It's definitely worth looking at and discussing with the Microsoft team.

Software eats Hardware - So Lets Accessorize!
I've made no secret of my growing interest in software-based solutions. One can use 
software for capture and playback, for control,  for video routing, for conferencing. This creates an increasing need for tools which can allow computers to access professional quality input and output devices. If you missed it last year, I'd suggest you see the demo of Audinate's soon-to-be-released Dante Via, which allows each application on a PC to be a separate input and output to a Dante network. It's quite nifty, and opens up many possibilities.
Also look for tools to move video and audio via USB. Yesterday I saw this press release from Phoenix Audio; it's a soundbar/microphone/SIP speakerphone with USB connectivity. This plus a flatpanel, webcam, and small form-factor PC can make a neat soft-codec based system. It's the kind of solution of which I'd love to see more. 

Look also for lower-cost camera options. The Vaddio Zoomshot/Wideshot fixed cameras were an early entry to this field, but their cost is still a bit high for the kinds of systems in which they'd be used. HuddleVu  and Logitech have low-cost PTZ cameras for these applications; I'd be on the lookout for other options as well.

On the same topic, I'd look for software, hardware, and hybrid hardware/software bridging solutions at the UCC pavilion. Vidyo had a nice demo last year of multi-site call involving Lync, a hardware Codec, and another software option. We'll need more options for bridging various technologies and platforms.

On the Network
IP-based systems are another exciting frontier. This year we're promised the long-awaited debut of Aurora Multimedia's "IPBaseT" system. This is an uncompressed video over 10G ethernet system, with a slew of interesting features (image tiling, Dante integration, etc). It's a system which promises a great deal. I know some of my colleagues are going to check it out to see if it delivers.

We need to talk about 10G copper vs Fiber. That's another post
There are also network-based video solutions from a variety of other players, both traditional and not. I'm especially curious to see how different players in this space handle the bandwidth demands of 4K video AND to chat with them to see if they can envision a path to 8K or higher. On the audio side, I'd interested in developments from the aforementioned Audinate as well as promised updates to QSC's QSYS platform.

I'm also quite curious to see who is taking advantage of the suite of the time synchonization protocols in the TSN/AVB standard. This is one for which many (including myself) have sounded a death knell before, but it appears to be alive and kicking. There are real issues which CAN be solved with these protocols if we are to use them. Time will tell.

Finally, Some Fun! (and not)
There are some things which I consider fun and would recommend: The Drunk Unkles concert is a great time and a chance for the industry to raise money for charity. AVNation and WAVE are co-hosting a "Tweetup" - largely a gathering of professionals who use the "AVTweeps" hashtag on Twitter, but all are welcome. 

What I'm not a fan of is in-booth raffles, giveaways, and other associated games. If that's what you like, enjoy. I suspect you'd get more out of the experience as a technology professional if you choose to NOT show up at the same time as a half-hundred other people looking to win a free iWatch and instead drop in when you can actually speak to a product expert. 

Last thought for anyone who is going:

As I said, I'm holding down the fort this year. That means that I need to count on YOU to be my eyes and ears on the floor, in training classes, around Orlando. That's right, you. So... look around. Tell me what you see. Hashtag it on twitter (and if you see sexist displays in any booths, do us all a favor and tag those #NotBuyingIt. You can tell the people there that I'd disapprove). 

Then come back, reflect on what you've learned, and see how you can use it to make your projects - and our industry - just a little bit better.

Enjoy.

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.