AV Super Friends On Topic is an
independent production wholly owned and
operated by AV Super Friends, LLC.
For the highest quality recording of all
of our shows, visit AVSuperFriends.com.
This is AV Super Friends On Topic,
a thirty-minute monthly roundtable focused
on a single topic.
This discussion will be opinionated,
to the point,
and saturated with our well-known blend of
painfully won expertise and deeply
ingrained immaturity.
For March, twenty twenty six.
Yes, I said March.
Deal with it.
It's the best sounding and most regularly
scheduled podcast in higher ed.
This is the AV Super Friends on topic.
Episode number sixty eight.
That's over five and a half years of
this.
man broadcasting live across four time
zones no scratch that we dropped we lost
somebody today broadcasting live across
three time zones across that time zone
though wait a minute no it is four
me and jamie are on the same time
oh you are okay so jamie's a scofflock
it still applies
Broadcasting live across four time zones,
it's spring, because it's March, remember.
Theater of the mind,
where the snow is melting,
the budgets are tightening,
the classroom tickets are blooming faster
than the campus flower beds.
And it's time to shake off our winter
firmware and step boldly into spring
refresh season.
So from preventive maintenance to project
planning,
from frozen loading docks to fully booked
install calendars,
we're thawing out the technology and
turning up our springtime momentum.
I'm Chris Dector.
It's time for another Friday afternoon
podcast adventure with the AV Super
Friends.
And let's say hello to today's panel of
AV Super Friends, which is this one.
Oh,
got to delete this because it's not that,
Jamie's not here, sorry.
Our first panelist ensures that every new
AV over IP deployment blooms beautifully
in April before immediately being clogged
by multicast storms and metaphorical
ragweed.
He's a director of emerging technologies
and seasonal pollen mitigation from
Corvallis, Oregon.
Say hello to Mr. Mark Kolowczynski.
Yes, the colors are always blooming here.
So we have somebody doing shading on all
of our rooms all the time on every
system.
Just turn the gamma up a little bit.
Exactly.
Our next panelist champions the annual
rediscovery of rooms that, quote,
worked fine in the fall and now require
emergency irrigation in the form of new
DSP configs and a reboot ritual.
He's an assistant provost for strategic
sprouting and deferred maintenance
awakening from Greensboro, North Carolina.
Say hello to Mr. Larry Darling.
Yep, I reboot every room every spring,
just like clockwork.
Whether it needs it or not.
And our final panelist leads the annual
migration from we'll fix it in summer to
why is this still broken in March while
aligning capital requests with pollen
forecasts and fiscal optimism.
He's a vice president of Vernal Refresh
Cycles and Strategic Thawing from Bowling
Green, Kentucky.
Say hello to Mr. Justin Rexing.
It's not right.
It's really VP of run to fail.
What the hell is, what's Vernal mean?
Sounds like an uncle's name.
Like Uncle Vernal.
That's Vern.
Hey, Vernal.
Like Uncle Vernal drank too much.
You didn't like study Latin in school at
all?
So, okay.
I mean, a little bit.
I was Catholic for a little bit.
All right.
For a little bit.
I'm still Catholic.
I haven't read Latin since like third
grade, I guess.
I don't know.
Well, anyway, speaking of being Catholic,
let's lean into that.
On today's show,
we're going to discuss our top ten
commandments of AV.
But first, a little bit of housekeeping.
So, first of all,
if you're listening to this as a recorded
MP three,
while you're crawling through a ceiling,
replacing a failed HDMI extender,
just know that we do stream live on
Fridays at about three fifteen Eastern
twelve fifteen Pacific or whenever Mark's
seasonal allergies subside.
And of course,
we were all late today because we had
a meeting right before this and that ran
long and then we're in all sorts of
planning retreat.
For two hours.
It was a treat.
Yes, that's right.
You can catch us live on YouTube,
LinkedIn, and Twitter,
and when the pollen count is high,
the takes are hotter,
and occasionally we'll even take your
calls,
which I don't have set up right now.
Deal with it.
Spring is all about renewals, new growth,
fresh start,
so maybe this season's the season that you
finally follow us on the socials.
Go search for AV Super Friends on YouTube,
LinkedIn, Twitter, and Blue Sky,
and we see you out there posting stuff,
so give us a follow, too.
While you're out there decluttering your
office,
please consider planting the seeds of
chaos by sharing this podcast with your
coworkers, your local integrator,
your procurement office,
that one faculty member who still insists
that VGA is more reliable.
They're not wrong.
And anyone else who might need a little
sunlight in their signal chain.
If you'd like to help this show to
keep blooming,
you can support us by using the donation
link in the show notes or at the
top of the website there.
Your contributions help keep our mics hot,
our opinions honest,
and the snark organically sourced
sometimes.
And finally,
we are turning over new leaves,
but we're never crossing the stream,
so keep an eye on what we're doing
here.
Thank you for your support.
We couldn't do this without your support.
Yay.
All righty.
We did it.
What, do you want more clapping?
It's like four people clapping there.
That's about right.
All right,
so let's go to this month's topic,
which is...
So, Justin, this was your suggestion.
Yeah.
So just so everyone knows,
we have an editorial calendar for the
entire year except March.
It literally says TBD.
There is no plan for March.
We change it up every year.
And Justin, this was your suggestion.
You were like, well, Hey,
let's talk about this.
So Justin go, what are we talking about?
It's the vernal season, Justin.
So what do you have?
Use your vernal Catholic Latin.
So being on a campus with a hill,
sometimes you find yourself walking around
thinking a lot.
And I was thinking one day about all
the problems I had and I was,
you know,
we ought to do a show about the
ten commandments of AB.
So here we are.
So we talked about how to do it.
I'm curious,
why did that anecdote need to have a
hill?
Yeah,
because every campus I've been on has a
hill.
Because all religions need death.
We're the hill-toppers, thank you.
I just mean you're on top of the
hill.
You're just at the top of the hill.
We are known for our hills.
And I bet you there's a lot of
universities in Texas that are not on
hills.
Is that a thing?
But maybe some are.
The hill-toppers is like straight up
because you're known for hills?
Wyoming's not on a hill.
No, there's a mountain.
Mountains.
Baby hills.
Our campus is more like that.
Most camps are more like this.
Yes, because when they built the town,
they were like, hey,
there's a flat spot over there.
That's where we should build the town.
This guy from Kentucky was like,
top of the mountain!
Top of the hill.
Hill toppers.
Anyway, so everybody started debating,
well,
how are we going to get through the
show?
There's so much to talk about.
Ten Commandments, like
just listed Ten Commandments.
You just come up with ten items.
So I came up with quite a few
here.
Yeah, I just just in five minutes,
I came up with this.
So I know they're supposed to come up
with two or three.
You want me to read all of mine
and just go through your list?
What defines let's define a command?
What defines your top ten commandments?
These are things you know,
commandments are things that you shall or
shall not do in any circumstance at this
point in our AV careers.
It's just you shouldn't or should do these
things.
You should not or maybe should or
sometimes maybe you do.
It just explicitly... It depends.
If you should or should not in each
commandment.
So it's not always thou shall.
It's sometimes thou shall not.
Unless you shall.
Or shouldn't.
General AV words of wisdom.
These are just general words of wisdom.
General suggestions.
Suggestions, not commandments.
The most strongest beliefs that Justin has
as of today in line with AV.
Now, this is fluid.
It could change tomorrow.
I was going to say, it sounds fluid.
How many of these are based on today's
commandments or tomorrow's?
as follows today's commandments are
tomorrow's problems let's just let's
realize that possibly but not necessarily
so just because i clipped this i want
to run it anyway because it's funny and
it cracks me up would you clip what
i what i say go all pay heed
the lord the lord jehovah has given unto
you these fifteen ten ten commandments for
all to obey
Okay.
Sorry, you said Ten Commandments.
That's the first thing that came to mind
was the Mel Brooks classics.
So these are not in any specific weighted
order whatsoever,
but genuinely you have very strong beliefs
about these.
Yes.
Like I always try to follow these things.
except i know i see someone on your
list that you do not follow yeah i
can't yeah we just gotta get we're not
gonna have times and we gotta get in
here somewhere so i want to know what
those are larry how do you know we'll
get there i'm i'm curious if we could
this could go many different ways today we
might just do you want me to just
know do you want me to pause and
talk about each i would say pick pick
one and we'll go around one let's go
there and usb
I don't think any of us disagree with.
Okay,
that was the one that was when he
came down reading an order.
Mouse and keyboard are farther away from
your computer than move the computer.
It's called wireless keyboard and mouse.
That's an IT thing.
That's a nightmare.
Okay,
that's a different group on your campus.
Okay, so what's up?
I want to know we don't want to
rattle off.
We're talking about USB in the
the naughty list kind of not from cameras,
not from other high bandwidth USB sources,
correct?
Stop doing that.
Yeah,
you're saying don't use USB as a
replacement for the appropriate transport
by extending USB through some bootleg,
you know, IT nonsense.
If it's not an SDI or Cat.Six type
cable, you're in trouble.
That I agree with.
That's not extending USB.
Because it's not the cat six is the
problem.
It's the
TXRX sides that become issues.
Yeah.
All right.
So is it because it's going to go
wrong, just generally,
thou shalt not do it because you're not
going to have a good time?
It's been a pain.
It's been quite a bit of a pain.
Well, if a friend of the show,
Joe Cornwell, was here,
he'd tell us USB was not designed for
that.
USB was designed to talk to local
peripherals connected to a computer.
It's not made to go long distance.
And yes,
you can make it go long distance,
but there's all sorts of things.
Because now you're way outside the spec of
what that protocol is supposed to do.
You run into all sorts of nonsense support
issues.
I want to know what Larry thinks that
I do on this list because I'm shocked
at that.
We'll get there.
We're going to get there.
Can I just rattle these off real quick?
No, no, no.
Larry, go.
Thou shall not use two screens when one
will do.
And what that means is you simplify the
functionality for the end user even if
they don't want to.
You got to understand what they think they
want to do.
And then also understand the cognitive
load of what that's going to take them
to do.
And they're not going to be able to
do that in the middle of a class.
And so simplify the system in such a
way that they can actually accomplish
teaching.
And most of the time, Larry,
I'll back you up on this.
It breaks your viewing angle standards.
Yeah,
like there are lots of reasons to simplify
and not do stuff like what if I
add another screen?
Oh, yeah.
Like a third screen in the middle.
That's half the content here.
Well,
just look up to the side of one
of them.
Eight of them circling the room?
At an angle.
Yeah.
Mark eight screens.
What's going on there?
So I want to lean into the discomfort
of this a little bit.
Is there a correct environment where Val
can have two screens?
Yes.
Conference rooms can work,
depending on the shape of the furniture.
That was probably the least on my list,
but OK.
Because if I'm laying it out, they design.
Let me redact that statement.
Can thou do this in a typical learning
environment successfully, Larry?
Maybe,
depends on the shape of the room and
furniture.
But if two displays can cover the entire
audience in the same manner and everyone
can see the content.
Equally.
You can have two screens up there,
but it's very limited because most people
don't design classrooms that way.
I've come across a couple.
But Justin,
let me give you an alternative here.
I teach in the College of Business.
I need two screens because two is better
than one.
I have two monitors at my computer.
Therefore, I need two computer screens.
I think we all see that.
We see this a lot.
I think we'd all agree.
You need to change rooms.
I don't disagree.
I'm just saying this seems to be something
from the College of Business for whatever
reason.
They're like, we need two screens in here.
Why?
Well, because that'd be two.
no i was actually going to bring tease
this out how much time we have in
this there seems to be this like
disconnect between like screen real estate
and two pipes exactly and it's like
there's this modality people get and
they're like no i need two pipes worth
of real estate but what if i give
you the same thing no no i need
two things my response is it always gets
into that well what about powerpoint in my
notes that's usually the hill this falls
apart you don't want to show the class
your notes so it's okay
right so my point is always do you
want to disservice half the room you want
to i say that to the faculty i
was like you were doing this i don't
like them they can't see it and they're
like and they usually say oh i never
never thought of it that way of course
we'll keep one and like okay then that's
what we're gonna make a real small one
over in the corner i need all the
whiteboard space i'm not going to
sacrifice any of that second monitor
But that is for you to use and
not to be broadcasting that.
Can I turn it around so the students
can view it?
I'd love that.
They do that a lot.
I don't give a shit.
You can try.
Until they rip tables out of stuff.
Yeah, it ain't going to work very well.
So we're not doing two screens just
normally across the board.
Nothing that makes them route something
else from a separate touch.
I only do it if it makes sense
from a visual acuity perspective.
Okay.
There's a lot there, but okay.
Mark, what's coming off your list here?
Thou shall design for serviceability.
It is non negotiable.
Which means that's on my list to kind
of the same.
No,
I think it's important because it's a good
concept.
I'm not disagreeing with understand that
this this is not necessarily what am I
going to design my pin down?
I'm gonna read this thing.
But when you view options and
opportunities and manufacturers come to
you,
do you understand what that means to your
serviceability?
Does the impact of
your staff how does it tie into your
ecosystem all that just because it does
something on paper does not necessarily
make ensure that's going to translate to
what you need from a serviceability
standpoint we all have ecosystems pick
your whatever it is does this work well
outside of what just the specs say do
your people know how to do it are
they trained to do it under skill like
have that in the back of your mind
not just
Well, it says it can do it.
And it's got the right number of eyes
and the right amount.
Oh, so it should work.
That's kind of where we see a lot
of that friction with like consultants all
time.
Well, they're like, well,
just says it can do this, like,
but it doesn't fit my service ecosystem
doesn't fit my capacity of my students,
my technicians, all those things.
So I think it's imperative that all
designs be viewed through that
serviceability lens,
I think it's too critical and
It's too much risk if you don't.
So is that because you're talking
serviceability and standardization all in
one shot,
your standards should follow the same
suit, right?
They should become written in a way that
speaks to how you're servicing and
supporting the space,
not just because it has the whiz bang
thing.
Can you actually do this?
So if you say yes to this,
what does it mean for you?
Can you afford saying yes to this product
or this service?
yeah i i almost had the same thing
like i had like treat yourself as treat
your future you as the most important
client system that you put in has to
be serviceable and it also has to be
standardized like you don't put a piece of
equipment in until jamie has tested it on
his system for a year yes once jamie
has figured out how many times it's going
to fail and what the remediation path is
then you can use it yes now shall
not test equipment
no battle shall not test equipment on your
network tested on jamie's okay so that i
mean do you well let's i mean do
you agree disagree with this i mean i
agree it's just like i'm going through
mine you've stepped on like three of mine
with just one there so but that's that's
on brand for me yeah he's kind of
broad sweeping in his commandments
Well, I think, to me,
I would have started off with that.
I disagree with the way you,
and I think it's just your phrasing.
I disagree that we design,
that standards are based on serviceability
as a primary.
Standards should be based, in my opinion,
standards should be based on experience of
teaching and learning.
Is that not the service that we're trying
to deliver anyway?
I don't know.
I think it's both.
I think there's a happy medium here.
To me, that's a support ability,
and that's your staff's ability to
maintain.
But if the system goes down,
then teaching and learning gets
interrupted as well.
It's compromised.
So it's got to be both.
You have to do both.
Yeah, it's a balance.
And I think you're right to say, OK,
it looks like this from this perspective,
and I'll say that from that perspective.
I think just generally,
and I think this is probably more of
an issue for different universities and
schools that are relying more heavily
about outside integrators,
understanding the impact for a design that
is not your own on your abilities.
You're walking right all over knowledge
work to just swinging your arms around.
I've been singing.
Chris, what is one of yours, sir?
I got it.
So so far,
I've marked off like four on my list
that you just I'm just being efficient.
Apparently,
you just you want one commitment.
Do what I say.
This is one paragraph.
All right.
Damacy,
this one's what Larry talked about, too.
I guess I'm gonna delete
This one.
You can always steal one.
Go to Justin's list.
He has an infinite list there.
I got a good list.
I'm going for the one I know Mark
don't do.
I know.
It's sitting right in front of me.
It's one of my options,
and I'm bad at it, so go ahead.
Thou shalt document everything.
Exactly.
That's the one.
I'm looking right at it on my list.
I was like, oh, I couldn't say that.
Documentation loves uptime.
Always save final signal flows,
your IP schemes, your firmware versions,
your as-builts.
And so the note here,
the note that I like,
the way I phrased this was,
if your documentation is go ask Steve,
you're like one person leaving away from
just utter chaos.
Unless Steve is your AI bot,
that may work.
That's not what that means, and you know.
Now, you raise a good point.
If everything is properly documented,
you have that,
and the AI bot has access to it,
and you can say, oh,
go ask the Steve bot.
Maybe.
I think we're all...
guilty of not fully documenting i'm i'll
tell you where my weak point is is
as built going back and those tweaks you
make during installation of going back and
and updating my drawings for that it's
hard to find time to do that so
here's the weird part yes i'm guilty of
not having documents for a thing but
I also believe thou shall not waste time
over documenting common things that
everybody should be doing all the time
anyway.
I disagree with that.
Yeah.
I don't.
I agree with Mark on that one.
And so there are certain things of
standards.
What are common things that you didn't
know?
If I'm going to build the same type
of room over and over and over and
over again,
then it would be fully documented.
The argument for that is,
which I address in my class,
if you want to take a class on
this.
And when is this class, Justin?
first three days.
If I wanted to take this doc class,
where would I sign up?
You want to keep those things documented
to some degree as a standard because in
theory, you have new employees coming in,
new student workers,
and that information can transpose to
other people more easily versus, well,
I mean,
ninety percent of our department knows how
to do something.
So, eh, F it.
I'm not saying it doesn't exist in
documentation, but at the same time,
I'm not saying that
we know what our general things are,
right?
Saying we cannot move forward until we
have this exactly spelled out to be the
same thing we've done over and over and
over again.
Okay.
Yeah.
I don't agree with keeping that as a
gatekeeper for not doing something like an
excuse, but like,
like you should be working towards
documenting everything if you don't like,
I think the general consensus is we want
to document as much as we can.
And I'll just say, Mark hates schematics.
No, I don't.
Yes, you do.
With a passion.
No, come on.
You're talking about... I love to hate it.
That's not design.
That's not what that is.
No, no, no.
That's just documentation.
I know that you get to systems where
you have to and you're like,
I know this has to be done,
but man,
I really don't want to do this shit.
I don't think...
I don't necessarily hate them.
I hate the process of having to sit
down and commit gobs and gobs of hours
to doing things that
Is it part of the,
do we need them?
Yes.
Do I like to have that identity of
having to do them all?
No.
Yeah, I'm with Mark on that.
I mean, it's just like doing taxes.
Do you want to do taxes all the
time?
I love doing taxes.
You just don't.
Right.
All right, Justin,
what's next on your list?
Thou shall abide by all five X safety
factors.
So I'm tired of people hanging shit.
with stupid things.
The toggles on the box says two hundred
pounds.
Drywall screws are just fine.
And part of this is, you know,
and I guess I have nine commandments here,
but one of them is bow shall support
drop ceiling speakers independently of the
ceiling grid.
I'm sick and tired of looking at new
ceilings that are
concave like what the hell y'all doing
it's a good to reflect better my business
we bid on something and then i go
back and look at some asshole that didn't
do any safety factor stuff that i bid
in my job that increased cost that like
you can't get away with that like why
are you talking about the integrators who
did work on my campus before i got
here because that's me it's infuriating to
me it's it's it's a bad
Did you guys ever go into a room
and find a projector on the grid and
the whole ceiling's like leaning down
towards it?
Yeah.
It's like,
how did you get away with that?
How's the building inspector... Like,
how's the client not worried about killing
people?
I'm interested.
Is that in your scope to check?
It's... Hell yeah.
I mean, if you were designing it,
but if you were to like...
have something handed off.
This becomes like a whole project process.
If you walked into a space,
let's just assume that you found out that
a newly furnished building- Like College
of Business, for instance?
Whatever it is,
whatever new college building du jour,
if you walked in,
would you take ownership on remediating
that?
Or would you say, nope,
if you touch it legally- We're talking
about it.
I'm going to walk over to that building
with a ladder,
and my first thing I'm doing is popping
my head above that ceiling going,
this shit's got to get fixed,
all of it.
And that's part of us owning that system
and being accountable for that system.
If I'm not doing my due diligence,
if I take over a system and I
know the integrators are doing a subpar
job,
I'm going to have a commitment that I
want to go right after you on this
one when we're all said and done.
Okay.
But there's no way I'm trusting that
person to do their job right.
And so I've got to check off on
all that shit.
This might be a dovetailing on that one
or maybe the same thing.
But thou shall not let business process
get in the way of doing what is
correct.
example if your general identity for the
organization which you work for is av and
there's an av problem thou shalt remediate
that problem not wait for some legal
definition as to when you can or cannot
do it you're gonna have to i'm not
sure what's the scenario on this you all
know what's right and wrong something's
broken if you get to a point you
say oh well we didn't install it somebody
else did
and there's a class at risk because it's
not working,
go in there and try to fix it.
We can't do it.
Is that a thing?
Yeah, we're not doing it.
The project's not even done.
It's not even signed off on at all.
If there are classes in there on behalf
of the university and it is not generally
able to go in there and fix it,
it's still under contract.
It's been not done for a year.
Like at some point.
Who's signing off on it?
I wasn't going to do this one.
I had a note to it.
I was like,
I'm going to just say it anyway.
The university as a whole is not allowing
us to go in there to work on
anything.
I still believe in the best interest of
the organization that you go remediate
that.
Successful learning outcomes would dictate
that you go fix it.
With what time and what money.
And our schedule's already full.
When you win.
Right now.
Stop the documentation and go fix it.
get in there we didn't put it in
we don't have any schematics we don't have
any passwords we have no ip addresses we
have we haven't even set foot in the
building yet okay pause there would you
know what you need to do if you
were going to go in there yeah and
what the fuck are you waiting for go
get it done time time you know it's
gonna it's gonna take a week to fix
one room mark
I'm thinking about this.
When you do that,
when classes are going on, Mark,
a week to fix the breaks between classes.
We just had winter break, dude.
That was several weeks.
You can make substantial progress in ten
minutes.
We were already booked on other projects
over other EDU classes.
Okay.
I only wanted to get in there because
it was a good opportunity to do so.
It was a good opportunity.
I mean, I just don't understand.
Larry, what's another one for me?
Well,
you stole my last one on my list,
so I was going to steal one on
Chris's list that's really good,
but I'll let him keep it.
I misread yours here and thought it was
way more interesting, but okay, go ahead.
Wait, what?
That was insulting.
I'm going to just say I thought the
word was furniture when I was scrolling
past.
Oh, okay.
So rather than steal Chris's...
You can steal from my list.
I can steal from your list?
Because I really like the four K,
five K, eight K nonsense.
Okay, that's fine.
Okay, I'm going to steal that one then,
because I really like it.
Thou shall not chase resolution idols.
Nobody can see it anyway.
It doesn't matter.
Like do not put four K, five K,
eight K anywhere outside of very,
very unique applications.
Yes.
If you're in an igloo.
Yes.
If you're touching the wall.
Yes, yes, yes.
But outside of that,
ten ADP is the max everywhere.
Seven twenty all day.
Yeah.
Do I hear four eighty?
I'd go four ADP black burst rumors that
are four eighty.
Otherwise, you're just wasting money.
NTSC gets it done.
By the way, Larry,
I think that's the reason why they're not
done yet is for K.
It would not surprise me.
For K for K.
seat yeah i'm not what's that mean justin
they're not done yet because of four k
are they waiting are there support i'm
going to cost them four thousand dollars
per room they did not have a very
they did not have a very well thought
through edid plan with all the devices and
things they had to configure and so
they're forcing four k through a ten
eighty monitor and they're wondering why
it's not working where did you guys find
it if you know this why don't you
tell them and get it fixed
We have.
We told them.
They're asking us, and we told them,
and they're like,
we put in Crestron and fixed it.
I'm like, yeah, you put in scalers.
We don't put in scalers like that should
be the eleventh commandment.
Thou shall not actually,
that's a good point that putting,
putting a hardware scaler at the end of
your signal chain does not fix your
inability to set up an eat chain.
No.
And that's exactly what this integrator
did and said,
we should have used Crestron instead.
I'm like use their use Crestron's D ten
and E ten series.
And let's see what the hell happens until
you need to, you're not,
now you're not doing apples and apples
here.
So that's a whole other thing.
Now shall not use scalers is my limit.
That is a good one.
I like that one.
That one's better than... Chris,
what did you get?
By the way, so I,
as you all know, inherited a campus.
Many, many, many, many, many, many, many,
many, many RMC scalers out there.
I did find a room that had a
seven-twenty P and ten-eighty I capable
cameras, the older PTZ cameras,
ten-eighty I.
which is the one place so far you
could legitimately say I want a hardware
scaler there, and it didn't happen.
So, we'll see.
Thanks, guys.
Anyway, can I read one?
No, I haven't gotten mine yet.
It's going to get a bunch of extra
credit ones in here.
Let's see.
Where's the one I was trying to find?
Ah, thou shalt protect audio above all.
You can make do with bad video.
Video forgives.
I just have a heart attack right now.
Video forgives, audio does not.
Bad lighting can be annoying,
but bad audio is fatal.
uh if you have to choose you sound
over an awesome picture is this that's
primarily in like teaching and learning is
this like specifically geared towards like
collaboration and conferencing yes yes so
i i agree with that but come on
chris that's such a little hanging fruit
okay you want to know that's like saying
the a is relevant in a and b
Okay, wait, I got one for Mark.
Here's one for Mark.
How about this?
I'll sneak another one in here.
Go for it.
Because that last one was so bad it
didn't count.
It was good.
I liked it.
Thou shalt avoid over-automation.
Just because you can auto-switch,
auto-mix, auto-sense,
auto-track your cameras, auto-detect,
motion-sensor lights,
doesn't mean you should.
Complexity increases support.
Larry brought up complexity increases
cognitive load.
And sometimes, this is just for Mark,
sometimes the best control system is fewer
decisions.
That's exactly what I'm doing.
But I read all that, like,
continue to do my automated system.
But sometimes because of their screen on
the display, so like,
there's a happy medium there.
Yeah,
but it's only for certain types of spaces,
right?
Okay, Justin, now get us right.
You want me to do some more?
Yeah,
do one of them that you don't follow
track of where we are.
Let's like thou shalt remodel,
read manuals.
I know you don't do that.
Nobody reads the manuals.
What the hell do you think I'm...
I'll get number five, Justin.
Go there.
Thou shalt not use a touch panel when
a button panel will suffice.
Agreed.
And I kind of want to hit comma
and also say don't use a button panel
when nothing will suffice because I've
done a few rooms that don't have an
interface.
What if it was automated?
You walked in, plugged in,
and it just worked?
What if you walked in and you just
have to wave your arms and things just
happen?
Yeah.
Or say, monitor on.
What if you just stayed home and just
joined remotely?
Plug and play to tech stuff.
Pretty simple.
It's all wireless now.
Let's see.
Dallas will not use chassis-based matrix
switches.
Oh, there we go.
Except for if you're going to use stacked,
sixteen or above more.
It has to be matrix into matrix with
sixteen by.
But you're running four outputs in your
quad box and your quad boxes?
Yeah, yeah.
I want to see all of those.
If you're going to do it, go bold.
Thou shalt abide by audio coverage
uniformity standards.
It's an easy one.
Okay.
Read the next one.
Thou shall abide by discus.
Now I will say that sometimes I can't
abide by this.
Exactly.
Based upon skilling heights.
But it's well communicated.
But I always,
it's number two on my list right after
audio coverage uniformity in my designs.
So could we use all of these to
design the ultimate worst room?
Really quick here.
We got multi-display USB extension,
eight K three foot tall images.
Could we make the worst scenario room
ever?
That would, I got,
I got one of my list just for
Justin here.
What is it?
He's going to love this one.
Thou shalt not let vendors design nice
strategy.
I agree with that.
Because vendors will design and build
projects.
Those are big words.
Okay, well,
so vendors will design and build projects.
You're interested in systems and
standards.
So they'll come in and do their own
thing that's not aligned with either of
those,
and they get their check and they peace
out.
Yeah, I'm pretty sure I agree with that.
How many did we get?
I don't know.
We're like in the twenty-seven range.
Yeah, at this point.
Thou shalt use sixteen by nine.
I think that's just a legal requirement
these days.
Yeah.
There's not really any other options.
How shall we label cables?
I think I'm including all the eleven
commandments that I had.
Yeah.
I think you got it.
um yeah i have the label cables thing
on here as well um if you just
might note that like you don't know what
hdmi three is a year from now so
labeling that with a human readable but
i'm pretty sure it's not going to be
analog audio it's probably going to be
something to do with video so at least
you know my favorite is when you see
the handwritten labels with a question
mark
this is probably this question no it says
it says confidence monitor question mark
you're like what what's supposed to do you
feel confident about this no uh does
anybody else have one that they want to
bring up because otherwise we'll wrap up
and roll out here i have one i'm
going to mention here at the end but
it's it's a it's one i i violate
all the freaking time but what is it
thou shalt test with real content
a laptop your laptop with a default
windows background is not a test of an
appropriate test for your your video
systems no i don't know oh we're all
guilty of that one the whole nine thousand
spec check it off over document it yeah
every room forget this out what size it
is
Okay.
Well, any last minute things?
A network-based one,
but I don't know if it's really relevant
or not.
The network is part of your...
I have one about life cycle, but...
I have a life cycle one as well.
Design for life cycle.
Thou shalt.
Thou shalt appropriately commission before
declaring victory.
That's a good one.
All right, well,
I think we get the gist of it.
All right, well, there's your,
I don't know how many that was.
That's a lot.
There was probably like seventeen in
there.
Or eighteen commandments.
The things you got to do maybe most
of the time,
unless you knowingly violate them,
which we all do.
Yeah, if you want.
If you feel like it this week.
All right, any last thoughts?
nope maybe all right well safety is
important be safe out there good point
safety third safety third after lunch all
right okay well do this and we'll uh
we'll come back we'll be back next month
with more stuff uh head over to
avsuperfriends.com for uh more shows of
this type of discussion
with yet another episode of AV
Superfriends On Topic.
You can contact us with questions,
topic ideas,
or general complaints at
avsuperfriends.com.
Nice work, everyone.
Sharp broadcast.
Really good.
Everyone on the floor as well.
Really a lot of hustle.
I liked it.
The opinions expressed by the AV
Superfriends are solely those of the
individuals and do not represent their
respective institutions, organizations,
companies, or clients.