<?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"
	>
<channel>
	<title>Comments on: How to Produce a Good Video Tutorial</title>
	<atom:link href="http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/</link>
	<description>Fresh Blender News, Every Day</description>
	<pubDate>Thu, 28 Aug 2008 15:37:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Tom</title>
		<link>http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-235401</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Thu, 17 Jan 2008 17:30:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-235401</guid>
		<description>I found a free video tutorial recorder that records to FLV files... this alows me to stream the tutorial with a FLV web player... so the users dont have to wait for the download.

&lt;a href="http://www.vtute.com/create.php" rel="nofollow"&gt;http://www.vtute.com/create.php&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I found a free video tutorial recorder that records to FLV files&#8230; this alows me to stream the tutorial with a FLV web player&#8230; so the users dont have to wait for the download.</p>
<p><a href="http://www.vtute.com/create.php" rel="nofollow">http://www.vtute.com/create.php</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: indiworks</title>
		<link>http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-49993</link>
		<dc:creator>indiworks</dc:creator>
		<pubDate>Thu, 08 Feb 2007 01:55:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-49993</guid>
		<description>"Find a good fast hosting service to host your file."

while it might not be the fastest, it is very reliable and best of all it is free: the internet archive (www.archive.org) offers free hosting (indie media, non commercial projects etc.) e.g. via the open source movies section:

http://www.archive.org/details/opensource_movies

upload is via ftp (click "contribute your video") and follow the instructions. alternatively you can use the ccpublisher (uploading tool) http://wiki.creativecommons.org/CcPublisher. a good and free os x ftp client is cyberduck http://cyberduck.ch/.

make sure to tag your uploads (can also be done later on) so that others find your work when looking for "blender" or "tutorial"...</description>
		<content:encoded><![CDATA[<p>&#034;Find a good fast hosting service to host your file.&#034;</p>
<p>while it might not be the fastest, it is very reliable and best of all it is free: the internet archive (www.archive.org) offers free hosting (indie media, non commercial projects etc.) e.g. via the open source movies section:</p>
<p><a href="http://www.archive.org/details/opensource_movies" rel="nofollow">http://www.archive.org/details/opensource_movies</a></p>
<p>upload is via ftp (click &#034;contribute your video&#034;) and follow the instructions. alternatively you can use the ccpublisher (uploading tool) <a href="http://wiki.creativecommons.org/CcPublisher" rel="nofollow">http://wiki.creativecommons.org/CcPublisher</a>. a good and free os x ftp client is cyberduck <a href="http://cyberduck.ch/" rel="nofollow">http://cyberduck.ch/</a>.</p>
<p>make sure to tag your uploads (can also be done later on) so that others find your work when looking for &#034;blender&#034; or &#034;tutorial&#034;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander Ewering</title>
		<link>http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-49882</link>
		<dc:creator>Alexander Ewering</dc:creator>
		<pubDate>Wed, 07 Feb 2007 22:09:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-49882</guid>
		<description>Nice writeup, however, there are a few mistakes in the audio part:

    * Use a good microphone and a quiet room to record. If possible, use a quiet computer. Record on the highest level that you can without oversampling.

What's meant here is "clipping", not "oversampling". If the audio will be post-processed, though, this step is essentially not necessary. (Yes, yes, I know there's a worse S/N ratio anyway when not recording "hot" enough, but that doesn't matter for a videotutorial)

    * Normalize the audio level afterwards. Don’t surprise your audience with loud passages after a soft one. Also, maximize the audio level without clipping it. This will ensure the best possible audio quality.

"Normalize" is exactly equivalent to "maximize the audio level without clipping it" ;) Also, normalizing won't do anything to the "loud after soft passage" problem.

    * This tip was posted by jcarney: “Get a De Esser for your microphone (one of those round thin screens placed between you and the mic.) It softens the consonants, so they don’t POP when spoken. (B and P are the worst). You can do it in post, but getting right before it’s recorded is still the best.”

Now, this is total bullshit. A de-esser is an electronic device which selectively softens the signal when certain high-frequency components are encountered, and is used to soften the sound of "hiss" phonems when lots of EQ in the high range is used as well. What jcarney means is a "Poppschutz", though I have no idea what the English word for that would be. And essentially, you can't do it in post. Cutting the low frequencies hard enough, especially with a male voice, will remove the bottom end and the voice will sound like the speaker had a flu :)

Anyway, random rant time over ;)</description>
		<content:encoded><![CDATA[<p>Nice writeup, however, there are a few mistakes in the audio part:</p>
<p>    * Use a good microphone and a quiet room to record. If possible, use a quiet computer. Record on the highest level that you can without oversampling.</p>
<p>What&#039;s meant here is &#034;clipping&#034;, not &#034;oversampling&#034;. If the audio will be post-processed, though, this step is essentially not necessary. (Yes, yes, I know there&#039;s a worse S/N ratio anyway when not recording &#034;hot&#034; enough, but that doesn&#039;t matter for a videotutorial)</p>
<p>    * Normalize the audio level afterwards. Don’t surprise your audience with loud passages after a soft one. Also, maximize the audio level without clipping it. This will ensure the best possible audio quality.</p>
<p>&#034;Normalize&#034; is exactly equivalent to &#034;maximize the audio level without clipping it&#034; ;) Also, normalizing won&#039;t do anything to the &#034;loud after soft passage&#034; problem.</p>
<p>    * This tip was posted by jcarney: “Get a De Esser for your microphone (one of those round thin screens placed between you and the mic.) It softens the consonants, so they don’t POP when spoken. (B and P are the worst). You can do it in post, but getting right before it’s recorded is still the best.”</p>
<p>Now, this is total bullshit. A de-esser is an electronic device which selectively softens the signal when certain high-frequency components are encountered, and is used to soften the sound of &#034;hiss&#034; phonems when lots of EQ in the high range is used as well. What jcarney means is a &#034;Poppschutz&#034;, though I have no idea what the English word for that would be. And essentially, you can&#039;t do it in post. Cutting the low frequencies hard enough, especially with a male voice, will remove the bottom end and the voice will sound like the speaker had a flu :)</p>
<p>Anyway, random rant time over ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bart</title>
		<link>http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-46131</link>
		<dc:creator>Bart</dc:creator>
		<pubDate>Thu, 01 Feb 2007 08:58:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-46131</guid>
		<description>@Chris Stones: For OXS, Snapz X Pro seems to be the tool of choice:

http://www.ambrosiasw.com/utilities/snapzprox/

It costs $69 which isn't too bad I think.</description>
		<content:encoded><![CDATA[<p>@Chris Stones: For OXS, Snapz X Pro seems to be the tool of choice:</p>
<p><a href="http://www.ambrosiasw.com/utilities/snapzprox/" rel="nofollow">http://www.ambrosiasw.com/utilities/snapzprox/</a></p>
<p>It costs $69 which isn&#039;t too bad I think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Stones</title>
		<link>http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-46129</link>
		<dc:creator>Chris Stones</dc:creator>
		<pubDate>Thu, 01 Feb 2007 08:57:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-46129</guid>
		<description>Whoa lots of people have stuff to say about this topic. Mac OS X really really needs something like CamStudio for it. I spent a very very long time looking and realized that I was just going to have to program something myself. And if or when I do I'd make it GPL too.</description>
		<content:encoded><![CDATA[<p>Whoa lots of people have stuff to say about this topic. Mac OS X really really needs something like CamStudio for it. I spent a very very long time looking and realized that I was just going to have to program something myself. And if or when I do I&#039;d make it GPL too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RedSharky</title>
		<link>http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-46100</link>
		<dc:creator>RedSharky</dc:creator>
		<pubDate>Thu, 01 Feb 2007 08:09:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-46100</guid>
		<description>Another important thing is imho the technical quality of a video tutorial. This is often underrated unfortunately. 
This means that the video should offer good visual quality at a small file size. Sometimes we see video tutorials that use 25 fps or something. Totally useless in most cases. 5 fps are sufficient for almost everything you want to show in a VT. It’s fast enough so that nothing is omitted.
Before one wants to start a VT it’s always good to think about the later resolution of the video. Imho there is no good reason to capture in HD when distributing it over the net. So you ought choose a TV or DVD resolution. Also some standard PC resolutions like 800x600 or 640x480 are are fine. I like the last one best because it’s large enough. And if so you should start Blender in a window with exact these dimensions. Blender command line arguments will do that for you (-p    ). If you capture just this window and make it your video nothing will be blurred. This is good for the viewer and of course for file size. 

When it comes to encoding it is always good to really know your codec. Try to experiment with bit rates, key frames and other settings. Tons of mb could be saved with nearly no quality loss. And then there is really no need for using the latest proprietary non widely used codecs to keep the file size small. A common codec will do fine too. I personally like avi container with divx and mp3. Not because it’s a technical pleasure, but because everybody can instantly play it. 
And just a word to audio: Please don’t use stereo when there is no need for it, for example when you just recorded in mono. And please use low bit rates. And normalize your stuff. 

Keeping with those simple guide lines you will have perfect quality at small size (fun to download and to store). You will end up with less than 1 mb per minute. That’s really cool! So if your VT is about 20, 30 mb or so there is mostlikely much space for improvements. Absolutely no need for large files with blurry and blocky video with crappy sound. 
(If you like you can try my attempts of making good VTs, http://mitglied.lycos.de/redsharky/. They were made for the german community). 

And just one last thing: Name your VT-files properly. Give it the authors name plus a good title. This prevents guessing in forums: “ Hi, I’m searching a specificVT. Does anybody know it? It’s name is tutorial1 …”</description>
		<content:encoded><![CDATA[<p>Another important thing is imho the technical quality of a video tutorial. This is often underrated unfortunately.<br />
This means that the video should offer good visual quality at a small file size. Sometimes we see video tutorials that use 25 fps or something. Totally useless in most cases. 5 fps are sufficient for almost everything you want to show in a VT. It’s fast enough so that nothing is omitted.<br />
Before one wants to start a VT it’s always good to think about the later resolution of the video. Imho there is no good reason to capture in HD when distributing it over the net. So you ought choose a TV or DVD resolution. Also some standard PC resolutions like 800&#215;600 or 640&#215;480 are are fine. I like the last one best because it’s large enough. And if so you should start Blender in a window with exact these dimensions. Blender command line arguments will do that for you (-p    ). If you capture just this window and make it your video nothing will be blurred. This is good for the viewer and of course for file size. </p>
<p>When it comes to encoding it is always good to really know your codec. Try to experiment with bit rates, key frames and other settings. Tons of mb could be saved with nearly no quality loss. And then there is really no need for using the latest proprietary non widely used codecs to keep the file size small. A common codec will do fine too. I personally like avi container with divx and mp3. Not because it’s a technical pleasure, but because everybody can instantly play it.<br />
And just a word to audio: Please don’t use stereo when there is no need for it, for example when you just recorded in mono. And please use low bit rates. And normalize your stuff. </p>
<p>Keeping with those simple guide lines you will have perfect quality at small size (fun to download and to store). You will end up with less than 1 mb per minute. That’s really cool! So if your VT is about 20, 30 mb or so there is mostlikely much space for improvements. Absolutely no need for large files with blurry and blocky video with crappy sound.<br />
(If you like you can try my attempts of making good VTs, <a href="http://mitglied.lycos.de/redsharky/" rel="nofollow">http://mitglied.lycos.de/redsharky/</a>. They were made for the german community). </p>
<p>And just one last thing: Name your VT-files properly. Give it the authors name plus a good title. This prevents guessing in forums: “ Hi, I’m searching a specificVT. Does anybody know it? It’s name is tutorial1 …”</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: [t0rc]</title>
		<link>http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-46036</link>
		<dc:creator>[t0rc]</dc:creator>
		<pubDate>Thu, 01 Feb 2007 04:26:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-46036</guid>
		<description>If you're on Windows try CamStudio ( http://www.camstudio.org/ ). It's free and outputs AVI/Flash. I would suggest using their codec as it does encode quickly, is lossless, and seems to be less CPU intensive. Of course you don't want to keep it in that format so make sure to download VirtualDub and convert it to something more common (XviD, DivX). It doesn't ad banners or watermarks to the videos either.

There's also a good How-To ( http://www.blender3d.org/cms/Miscellaneous.477.0.html ) on the Blender website; it's from Metsys. Kind of dated and I wouldn't use the demonstrated application but there is some good advice in it.

Good post though; definitely something to think about. Two more things you might want to add to the list: First, making sure your theme is compression and viewer friendly (or at least make sure it is easily discernible in the final) and second, creating a table of contents that highlights the times for different, important parts (really only applies to longer tutorials and those that cover multiple things. i.e., "Time Saving Tips", et cetera) and such makes navigation a lot easier - especially if you're viewers are pressed for time and of differing skill levels.</description>
		<content:encoded><![CDATA[<p>If you&#039;re on Windows try CamStudio ( <a href="http://www.camstudio.org/" rel="nofollow">http://www.camstudio.org/</a> ). It&#039;s free and outputs AVI/Flash. I would suggest using their codec as it does encode quickly, is lossless, and seems to be less CPU intensive. Of course you don&#039;t want to keep it in that format so make sure to download VirtualDub and convert it to something more common (XviD, DivX). It doesn&#039;t ad banners or watermarks to the videos either.</p>
<p>There&#039;s also a good How-To ( <a href="http://www.blender3d.org/cms/Miscellaneous.477.0.html" rel="nofollow">http://www.blender3d.org/cms/Miscellaneous.477.0.html</a> ) on the Blender website; it&#039;s from Metsys. Kind of dated and I wouldn&#039;t use the demonstrated application but there is some good advice in it.</p>
<p>Good post though; definitely something to think about. Two more things you might want to add to the list: First, making sure your theme is compression and viewer friendly (or at least make sure it is easily discernible in the final) and second, creating a table of contents that highlights the times for different, important parts (really only applies to longer tutorials and those that cover multiple things. i.e., &#034;Time Saving Tips&#034;, et cetera) and such makes navigation a lot easier - especially if you&#039;re viewers are pressed for time and of differing skill levels.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JJ</title>
		<link>http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-45917</link>
		<dc:creator>JJ</dc:creator>
		<pubDate>Wed, 31 Jan 2007 20:59:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-45917</guid>
		<description>It's not free, but there's an inexpensive Mac screen-to-movie capture app called iShowU - you can find it at &lt;a&gt;http://shinywhitebox.com/home/home.html&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>It&#039;s not free, but there&#039;s an inexpensive Mac screen-to-movie capture app called iShowU - you can find it at <a>http://shinywhitebox.com/home/home.html</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Holmes</title>
		<link>http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-45916</link>
		<dc:creator>Paul Holmes</dc:creator>
		<pubDate>Wed, 31 Jan 2007 20:57:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-45916</guid>
		<description>I take inspiration form this guys style of video tutorial making. Andrew Kramer.  Some of the most enjoyable tutorials I have ever watched, plus they teach cool stuff, and thats a must when making a tutorial.  
Here: http://www.videocopilot.net/tutorials.html</description>
		<content:encoded><![CDATA[<p>I take inspiration form this guys style of video tutorial making. Andrew Kramer.  Some of the most enjoyable tutorials I have ever watched, plus they teach cool stuff, and thats a must when making a tutorial.<br />
Here: <a href="http://www.videocopilot.net/tutorials.html" rel="nofollow">http://www.videocopilot.net/tutorials.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pedro</title>
		<link>http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-45854</link>
		<dc:creator>Pedro</dc:creator>
		<pubDate>Wed, 31 Jan 2007 17:57:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.blendernation.com/2007/01/31/how-to-produce-a-good-video-tutorial/#comment-45854</guid>
		<description>Bart, you wrote about something I always wanted to. I really liked it, thanks. One thing I believe missed in the article is the fact that people should avoid recording fullscreen because it makes hard to see the interface and what´s been done once the image is reduced or the copression is set too high in order to get small files.

I believe that resizing Blender window with just what´s needed for the tutorial is the best to do. In most cases it´s possible to create small files without having to reduce the image size.

+++++++++++++++++++++++++++++++++++
Alex, I know that it´s not free, however I believe Quicktime Pro is a very good option. It offers great image quality, small files and has options to record just parts of the screen.</description>
		<content:encoded><![CDATA[<p>Bart, you wrote about something I always wanted to. I really liked it, thanks. One thing I believe missed in the article is the fact that people should avoid recording fullscreen because it makes hard to see the interface and what´s been done once the image is reduced or the copression is set too high in order to get small files.</p>
<p>I believe that resizing Blender window with just what´s needed for the tutorial is the best to do. In most cases it´s possible to create small files without having to reduce the image size.</p>
<p>+++++++++++++++++++++++++++++++++++<br />
Alex, I know that it´s not free, however I believe Quicktime Pro is a very good option. It offers great image quality, small files and has options to record just parts of the screen.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.121 seconds -->
