<div dir="ltr"><div>Splitting into a separate thread so we can discuss further.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra" style>I've mostly ignored audio as you guys seem to have it under control and it looks complicated :P</div>
<div class="gmail_extra" style><br></div><div class="gmail_extra" style>Tim</div><div class="gmail_extra" style><br></div><div class="gmail_extra"><div class="gmail_quote">On 17 June 2013 23:50, Carl Karsten <span dir="ltr"><<a href="mailto:carl@personnelware.com" target="_blank">carl@personnelware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Mon, Jun 17, 2013 at 2:50 AM, Tim Ansell <<a href="mailto:mithro@mithis.com">mithro@mithis.com</a>> wrote:<br>
> Hey guys,<br>
><br>
> So I thought I'd quickly document what the current state is;<br>
><br>
> TwinPac for VGA capture to DV,<br>
><br>
> Firewire based camera for presenter using DV,<br>
><br>
> Going into DVSwitch (pretty much as described by<br>
> <a href="http://dvswitch.alioth.debian.org/wiki/large_meeting/" target="_blank">http://dvswitch.alioth.debian.org/wiki/large_meeting/</a>)<br>
><br>
> veypar is used for conferences to allow quick processing of the large amount<br>
> of video, splitting into talks and uploading to YouTube/pyvideo/other.<br>
><br>
> Going into Flumotion or Icecast for Live Streaming (least tested)<br>
><br>
><br>
> The current setup has been well tested and I believe well understood.<br>
><br>
> However, the current setup has some limitations;<br>
><br>
> Currently only SD resolution<br>
><br>
> Getting features into DVSwitch is painful<br>
><br>
> TwinPac is End-Of-Life and impossible to purchase new anymore<br>
><br>
> Laptop's no longer have Firewire ports so ExpressCards must be used and have<br>
> a tendency to pop-out<br>
><br>
> Firewire Cameras are becoming impossible to find<br>
><br>
> Poor ability to integrate with other online systems such as HangOuts, etc<br>
><br>
> Requires significant expert knowledge to run smoothly<br>
><br>
> Requires 2 people per room.<br>
><br>
><br>
> Have I missed anything? What do you guys think?<br>
><br>
<br>
</div></div>Audio - which maybe is out of scope, but I think it should be mentioned.<br>
<br>
Requires 2 people - I think that should be better defined. 1 person<br>
can do it all, so I would not say "requires."<br>
"recommended" maybe? I think what is a requirement is having a 2nd<br>
person for redundancy to being fault tolerant, and that will be the<br>
case regardless of what the people are doing.<br>
<br>
And then once I have the 2 people in a room, I load them both up with<br>
work, and I keep finding more things for them to do. I need to make<br>
sure I don't over commit so if one person drops the remaining person<br>
won't be able to handle everything.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Carl K<br>
</font></span></blockquote></div><br></div></div>