<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: iPads, Kindles, Netflix, and Video Collaboration</title>
	<atom:link href="http://vsee.com/blog/ipads-kindles-netflix-and-video-collaboration/feed/" rel="self" type="application/rss+xml" />
	<link>http://vsee.com/blog/ipads-kindles-netflix-and-video-collaboration/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ipads-kindles-netflix-and-video-collaboration</link>
	<description>Simple Video Conference and Screen Share</description>
	<lastBuildDate>Wed, 08 May 2013 05:54:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Rich Griffin</title>
		<link>http://vsee.com/blog/ipads-kindles-netflix-and-video-collaboration/#comment-1534</link>
		<dc:creator>Rich Griffin</dc:creator>
		<pubDate>Wed, 04 Aug 2010 16:15:09 +0000</pubDate>
		<guid isPermaLink="false">http://vsee.com/blog/?p=878#comment-1534</guid>
		<description><![CDATA[Yeah, the post on room setups is great. I used only one camera because it would require too much switching of video windows and I was using fullscreen (on an older version of VSee that still offered that layout option.) When we had 4-way calls, I&#039;d instruct folks to scale the various windows during pre-meeting setup.

The weakest part of that setup is the camera. I couldn&#039;t justify the cost of the HD Sony - but that would have been ideal then. Adding continuous presence screen layout pre-sets would be helpful along with the newer Ctrl-T window positioning arrangement. (hint, hint :)]]></description>
		<content:encoded><![CDATA[<p>Yeah, the post on room setups is great. I used only one camera because it would require too much switching of video windows and I was using fullscreen (on an older version of VSee that still offered that layout option.) When we had 4-way calls, I&#8217;d instruct folks to scale the various windows during pre-meeting setup.</p>
<p>The weakest part of that setup is the camera. I couldn&#8217;t justify the cost of the HD Sony &#8211; but that would have been ideal then. Adding continuous presence screen layout pre-sets would be helpful along with the newer Ctrl-T window positioning arrangement. (hint, hint <img src='http://vsee.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: john</title>
		<link>http://vsee.com/blog/ipads-kindles-netflix-and-video-collaboration/#comment-1531</link>
		<dc:creator>john</dc:creator>
		<pubDate>Wed, 04 Aug 2010 14:53:22 +0000</pubDate>
		<guid isPermaLink="false">http://vsee.com/blog/?p=878#comment-1531</guid>
		<description><![CDATA[Great set up, btw.  I like using the bluetooth devices.  I hope I didn&#039;t imply we avoid rooms.  I very much endorse VSee for rooms!  In fact, we have a meeting every week where we use a room set up!  And, of course, &lt;a href=&quot;http://vsee.com/blog/?p=832&quot; rel=&quot;nofollow&quot;&gt;there&#039;s this recent post&lt;/a&gt;...]]></description>
		<content:encoded><![CDATA[<p>Great set up, btw.  I like using the bluetooth devices.  I hope I didn&#8217;t imply we avoid rooms.  I very much endorse VSee for rooms!  In fact, we have a meeting every week where we use a room set up!  And, of course, <a href="http://vsee.com/blog/?p=832" rel="nofollow">there&#8217;s this recent post</a>&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Grifin</title>
		<link>http://vsee.com/blog/ipads-kindles-netflix-and-video-collaboration/#comment-1529</link>
		<dc:creator>Rich Grifin</dc:creator>
		<pubDate>Wed, 04 Aug 2010 12:24:53 +0000</pubDate>
		<guid isPermaLink="false">http://vsee.com/blog/?p=878#comment-1529</guid>
		<description><![CDATA[Which isn&#039;t to say that VSee cannot be used in a room setting. At my last gig, I had set up a room system with a 54&quot; LCD, Logitech, WebCam 9000 and a Phoenix Audio Quattro running on a fast PC with an Ethernet connection in our main conference room. I had to set the zoom to capture the room participants better; but it worked great. As we had great connectivity, I was able to set it to high res with 30fps and wideband audio.

A bluetooth mouse and keyboard allowed the PC to be out of the way. When we weren&#039;t showing files or webpages we would set the peripherals out of the way for a clean, professional view on the room.

The best part was when I used nearly the same setup to compare LifeSize Express. The user experience was about the same for audio and video but LifeSize&#039;s doc sharing is flakey. When I showed the CFO the price sheets for both he nearly fell out of his chair at what LifeSize cost. (The caveat is that LifeSize connects to *most* H.323 Gatekeepers/MCUs/Endpoints; whereas VSee [at the time] connected only to other VSee clients.)]]></description>
		<content:encoded><![CDATA[<p>Which isn&#8217;t to say that VSee cannot be used in a room setting. At my last gig, I had set up a room system with a 54&#8243; LCD, Logitech, WebCam 9000 and a Phoenix Audio Quattro running on a fast PC with an Ethernet connection in our main conference room. I had to set the zoom to capture the room participants better; but it worked great. As we had great connectivity, I was able to set it to high res with 30fps and wideband audio.</p>
<p>A bluetooth mouse and keyboard allowed the PC to be out of the way. When we weren&#8217;t showing files or webpages we would set the peripherals out of the way for a clean, professional view on the room.</p>
<p>The best part was when I used nearly the same setup to compare LifeSize Express. The user experience was about the same for audio and video but LifeSize&#8217;s doc sharing is flakey. When I showed the CFO the price sheets for both he nearly fell out of his chair at what LifeSize cost. (The caveat is that LifeSize connects to *most* H.323 Gatekeepers/MCUs/Endpoints; whereas VSee [at the time] connected only to other VSee clients.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

 Served from: vsee.com @ 2013-05-18 09:26:44 by W3 Total Cache -->