mithro: sounds good, I'm around that week you're intending on doing the hardware stuff and could join you after work most days
mithro
juliusb: you fill out the form?
juliusb: did you see the spreadsheet where I took a look at the resource usage of the different mor1kx configs?
juliusb: We should also do dinner Sunday evening
hyadez joined the channel
tumbleweed
1/3 opsis boards worked on day 2
yay
mithro
?
tumbleweed
now they're cooling off during the first session
one just wouldn't POST
another one isn't able to capture more than a frame or two
and the atlys is still running the broken firmware I was showing you. Oops
the one that wouldn't boot
I tried about 5 times, in the room
with a good 20 seconds off between power attempts
power it off, take it away
powers up perfectly in another room
grrr
maybe we have an atlys udev rule that was causing trouble, I must look
(these opsises were set up for atlyss)
paddatrapper
s/opsis/odroid/
tumbleweed
yes, that
rohitksingh_work joined the channel
rohitksingh_wor1 has quit
rohitksingh_work has quit
rohitksingh_work joined the channel
had to reboot projectors too. #WTF
tsglove2 has quit
rohitksingh_wor1 joined the channel
rohitksingh_work has quit
sb0 joined the channel
tsglove2 joined the channel
tsglove3 joined the channel
tsglove2 has quit
tsglove3 has quit
tsglove3 joined the channel
rohitksingh_wor1 has quit
CarlFK[m]
tumbleweed is not having a good day
xfxf
tumbleweed: if this was easy, they wouldn't need you :P
tumbleweed
CarlFK[m]: this is the problmem with using an existinginstall on the odroid, that's used to atlys
it mostly works
if you get the boot order right :P
also that noise issue
we got some interesting noise on green backgrounds too
CarlFK[m]
tumbleweed (IRC): im surprised you didn't re-whatever them
tumbleweed
I think it was an HDMI cable way out of spec
(length wise)
CarlFK[m]: i did ansible them. But that doesn't delete things...
CarlFK[m]
reimage?
right
ah right. that makes soup.
tumbleweed
and now our NOC has been given to a sponsor for VR demos
and we had to clear out during the last talk
fun :(
this happened last year too. And somebody must have said "that worked well, let's do it again"
CarlFK[m]
lol
tumbleweed
CarlFK[m]: if odroids didn't require a shity kernel (and weird fs) I'd totally have re-imaged
CarlFK[m]
has anyone used the mino? tidbit? board for 'this' ?
tumbleweed
only at a minidebconf, I think
or maybe that was just at the sprint? I can't really remember
CarlFK
meh, I don't have enough shows coming up to swap the c2's out
rohitksingh joined the channel
tumbleweed
our audio was also pretty nasty
had to use camera audio for a few talks because the desk feed was clipping
not enough volunteers to be monitoring it properly
paddatrapper
tumbleweed: it was at the sprint
CarlFK
paddatrapper: do you think they will become the standard thing to pair with the Opsis ?
tumbleweed
that was the plan
(at least for debconf)
paddatrapper
CarlFK: by the sounds of it. They're what RattusRattus wants and he's building the boxes
tumbleweed
but maybe ethernet will be working first :P
paddatrapper
At this rate, quite possibly
tumbleweed
paddatrapper: I think doing audio for recording is significantly different to doing it for the PA system, and that's possible something worth doing some training with the techs about, next time
same goes for buzz @ debconf
paddatrapper
tumbleweed: good point. I also need to look at finding a way of splitting off earlier/making what we get to the cameras more independent. I wonder what the TV/news industry does...
tumbleweed
usually a post-fader send is all that we need
paddatrapper
When we work the audio, yes
tumbleweed
but they must not mute the only source, during what would be recorded
paddatrapper
That's why the ambient, but they didn't use them properly/we didn't train them how to use them properly
tumbleweed
yeah
without them having headphones on that send, they won't get it right
and those ambient mics weren't sensitive enough
paddatrapper
Well they're actually too sensitive, except all they get is the aircon...