Blog

Sound clearer by recording with 6dB less noise

The quest for the ‘quiet PC’ is always a challenge for any audio engineer.  A standard PC has several fans, each of which contributes background noise that a sensitive microphone will pick-up.  It is easy enough to remove the background noise in post-production but the ideal situation is to keep your source signal as clean as possible.

My sE2200a is a wonderful mic and annoyingly my case fan has been showing its age, over the last few months it has noticeably become louder.  My quest for the best solution took me to Noctua.at, they produce high-end fans.  My choice was the NF-R8, reviews are always positive.

Using my sE2200a and Audacity I recorded the original case noise-level (-30dB) and the improved noise-level (-36dB), for this I ran Audacity on my MacBook with the mic placed at the back of the PC.  The PC and mic were kept in exactly the same position between the tests.

The 6dB noise reduction comes with the use of the Low Noise Adapter (L.N.A.), the earlier review suggested that this was the most effective to reduce noise (the Ultra L.N.A. is too wimpy).  The L.N.A. is just a resistor that sits in-line with the power-supply.

This fan is the first I’ve mounted using rubber screw-replacing ‘vibration compensators’.  These are the same shape as screws but are long rubber fixers that you pull through the case – they cut down the vibrations that the fan could transmit into the case.

All in I’m very happy with the NF-R8, the reduction in noise is quiet evident and this means even clearer recordings for me than I’d achieved before.


Ian is a professional screencaster (ProCasts, twitter) and blogger (IanOzsvald.com).

Choosing your screencast software

We’ve already covered why you should be screencasting, now let’s look at your software choices.  For each platform you have a choice of a few pieces of software.  Each of the choices will give you crystal-clear recordings so you have great raw-footage to edit down.

I’ll cover editing in the next of these screencast tutorial posts.  You really should put time aside to edit the recording down otherwise you have to take a perfect recording (and that’s hard!).

You can use desktop software or web-based tools, these are your main choices:

My preferred tool on Windows is CamTasia (all our commercial productions are recorded with it).  I’ve used HyperCam in the past, it is simple, cheap and stable.  CamStudio is equally as simple as HyperCam and comes with a free lossless codec, but the codec suffers from audio/video synch problems on some machines (all of mine!) and doesn’t work so well on XP.

TechSmith offer a First Walkthrough pdf (12 pages) on the fundamentals of making your first recording using CamTasia.  Even if you’re not using CT you should take a look, they highlight a lot of points that will probably help you out.

Both HyperCam and CamStudio lack an editor (see the next post) whereas CamTasia has everything built-in.

On a Mac I use ScreenFlow.  I’m told that iShowU and SnapzPro are each very good.

For Linux you have RecordMyDesktop, it exports .ogg vorbis files (which makes editing a pain as few editors work well with .ogg) but is a stable tool.  You might have to fight to get your mic to work, that’s a perennial problem with Linux annoyingly.

The three web-based tools are easy to use, they run straight from the browser.  I believe that they each lack an editor though it looks as though you can export a .mov or .avi from each for off-line editing.  I believe that Jing watermarks the videos (unless you buy Jing Pro) and that ScreenToaster and Screencast-o-matic are unmarked.

Next you’ll want to edit your screencast to remove glitches, cut down sections when things are loaded and generally make the screencast as snappy as possible.  After editing of course you’ll want to add music to improve the viewer’s perception of quality.

Would you like a free eBook that covers all of this information (and more)? Our Little Book of Screencasting is in the works, to receive a notification when we release it send an email to: ebook_notify@procasts.co.uk


Ian is a professional screencaster (ProCasts, twitter) and blogger (IanOzsvald.com).

Open-source advocacy with Adblock Plus

Over Christmas I’d spoken to Wladimir Palant of the Adblock Plus project, Adblock (you guessed it…) strips ads from within Firefox.   Some of his users had trouble understanding how the plug-in worked and how to get it installed.  We offered to do some open-source advocacy where we’d explain how to get started and find help for Adblock Plus in just over a minute.

Richard and I put time into developing a brief, scripting, storyboarding, animating and screencasting this short tutorial and we’re really rather happy with the result.  A higher quality version is listed on our usual Examples page, we decided to go with YouTube since it makes it easy for a viewer to embed it in their blog for advocacy.

Wladimir has a nice entry about our work, I’ve also covered it as has Richard.  This screencast is our 3rd for open-source advocacy after Django in Under a Minute and IE8 vs Firefox 3.  The open-source advocacy effort builds upon the fact that I’m a co-founder of ShowMeDo and have created over 130 tutorial screencasts about open-source.


Ian is a professional screencaster (ProCasts, twitter) and blogger (IanOzsvald.com).

Converting screencasts to Ogg Theora (.ogv)

For the Adblock Plus video Wladimir wanted a freely licensed .ogv video to accompany the YouTube format.  At first I turned to my trusty ffmpeg but it seems that theora/vorbis output isn’t as good as it could be using ffmpeg.  [If you want tips on ffmpeg, see my earlier converting screencasts with ffmpeg post]

A good comment on the post Fast and reliable ways to encode Theora Ogg videos pointed me at ffmpeg2theora which Just Works.  I’m using v0.21 on Ubuntu, and v0.24 looks to be the most current, but v0.21 did the job fine.

At first I tried using the defaults:

ffmpeg2theora AdBlockPlus_iPhoneFinished.mov -o out.ogv

which converted the 35mb .mov to an 8mb .ogv but the video stream had some artefacts.  The audio stream was far superior compared to ffmpeg’s attempts.  To solve the video artefacts I asked it to use ‘quality level 8′ rather than the default 5:

ffmpeg2theora AdBlockPlus_iPhoneFinished.mov -v 8 -o out.ogv

and the 13mb output is great.  I also created a 10mb .m4v iPhone version so I can demo it when on the move.


Ian is a professional screencaster (ProCasts, twitter) and blogger (IanOzsvald.com).

8 Tips to Make Screencasts That Grab Eyeballs (part 1)

Are you making your own screencasts?  Frustrated that they’re not generating the actions you want?  Here we present 8 tips borne of 4 years screencasting experience from teaching 100,000 users a month at ShowMeDo and explaining client’s products inside ProCasts.

  1. Avoid built-in and 3.5mm (analogue) microphones – built-in and analogue mics introduce background hum.  Often built-in mics pick-up fans and the heavy thump of fingers on keys and mics with 3.5mm plugs introduce background hum which is hard to remove
  2. Use a USB mic – digital microphone connections bypass the built-in analogue circuitry and so avoid the introduction of background noise, this makes your final audio sound much more professional.  More expensive mics and equipment give superior results.
  3. Edit out the dull bits – nobody likes watching a spinning hourglass, wiggling mouse or slowly-painting window.  Use a video editor to remove all the deadwood, your viewers will thank you!
  4. Know your audience – think about your audience and their needs.  What’s the shortest message you can give that covers most of their questions?
  5. Have a plan – you’ve thought about your audience, now question what they need to know and how you’ll teach them.
  6. Storyboard – sketch the scenes to clarify what you’re making.  First sketch what you want to achieve, then plan each scene.  We often sketch what we’ll see (especially for animations) and write comments telling us what is happening and what is being communicated
  7. Use annotations to give supporting information – extra text on-screen in call-outs can give useful background information that’s secondary to the narration.  Plan them when story-boarding to help reduce the narration.
  8. Keep it short – the shorter it is, the more will watch it.  30 seconds to 1 minute is easily watched, 5 minutes often feels like a chore.  Shorter is better, aim to get across 90% of the information in 1-2 minutes compared to 100% in 5 minutes and you’ll be on the right track.

Would you like a free eBook that covers all of this information (and more)? Our Little Book of Screencasting is in the works, to receive a notification when we release it send an email to: ebook_notify@procasts.co.uk


Ian is a professional screencaster (ProCasts, twitter) and blogger (IanOzsvald.com).

Introducing – Richard Mitchelson (Deisign, Animation, Creative)

My name is Richard Mitchelson and I am a creative designer/animator with 5 years commercial experience working with clients such as the BBC, Toyota, Nokia, Vodafone, Philips and Christian Aid.

I have skills in 2d animation and illustration using flash. Also experience as a Creative on successful Mobile campaigns for Vodafone and user interface design skills working with Nokia S40 and S60 handset themes.

Over the past 5 years I have gained a wealth of experience working for many different studios producing varied styles and adopting versatile techniques. I am an animator/illustrator by training with the imagination and concepting skills of an agency creative.

I joined the ProCasts team as I see it as a forward thinking use of technology and a great way to work hands on with brands to get the most out of the services they offer.  With the experience I have in advertising and digital media, adapting each ProCasts screencast to fit any brand or company identity is second nature.

You can see more of my personal and previous work on my blog or check me out on LinkedIn.

Richard Mitchelson


Introducing – Ian Ozsvald (founder, producer, screencaster, open-src advocate)

We figured introducing our team makes sense so you know who you’re dealing with.  I’m the founder of ProCasts.  The idea of professionally producing screencasts came to fruition during August 2008  after 3 years co-running ShowMeDo.  I bring the right team together to explain your stuff using video, I also create the screencast and voice-over elements.

ShowMeDo is a rather large screencast-based open-source tution site, we get 100,000 users a month watching over 1,000 open-source screencasts.  Users would ask if we could make screencasts to explain their products, from there I spun-out ProCasts to make these videos.

On my author-page inside ShowMeDo you’ll see that I’ve created over 140 videos, on the statistics page you’ll see that I’m ranked first for most categories (in fairness, it helps that I co-founded the site and spent 3 years working on it!).

My background is somewhat technical, in reverse order:

  • Founder of ProCasts to help explain software products via video
  • Co-founder of ShowMeDo in 2005, teaching open-source via screencasts
  • Founder of Mor Consulting Ltd. in 2004, an Artificial Intelligence consultancy
  • Senior programmer in MASA 1999-2004, an Artificial Intelligence start-up between the UK and France

My background makes me very much a geek problem solver – give me a hard problem and a team and I’ll successfully build you a solution.  Along the way (circa 2003) I learned that creating a solution was only half the challenge, explaining it and helping new users learn the necessary skills was just as important.  From there my interest in teaching people via the web and video grew to where we are today.

You can find out more about me on my personal blog (ianozsvald.com), at LinkedIn and you can follow ProCasts on twitter.


Ian is a professional screencaster (ProCasts, twitter) and blogger (IanOzsvald.com).

Interview: Remy Sharp, founder of jQueryForDesigners.com

Remy Sharp runs jQuery For Designers, a screencast education site for jQuery users.  He screencasts using iShowU on a Mac with a pro microphone and is a local here in Brighton.

Please tell us about your background

My name is Remy Sharp (@rem on Twitter).  I’ve been working on the web for over 10 years and have been coding for a lot longer. I have always been obsessed with the problem-solving aspect of the developer role.

I was the second man in to a company called Digital Look back in 1999, and learnt pretty much every aspect of running web sites over the following years.  My background is in server-side programming  but scratching my own itch I got (back) in to JavaScript around 2005 and I’ve made this the focus of many of my projects today.

As I learnt the tools of my trade, the company started taking on employees, people that I would come to mentor and manage. This where I first got a real taste for teaching other people how to go about solving problems.

Today I run my own freelance consultancy called Left Logic working with JavaScript and the LAMP stack.

In my spare time I run my screencasting web site called jQuery for Designers.

Why do you use screencasts on jQuery for Designers?

The initial reason for using screencasts was quite simply that I could convey more information than typing out an article.  It was my way of taking a slightly lazy approach to blog posting.

However my feelings quickly changed as I realised I had a responsibility to my readers. Screencasting was more important than it just being a tool for me to get my ideas out faster.  It is a powerful education tool.

Today, after running jQuery for Designers for over a year, I’m a huge fan of using screencasts to educate.

One side effect I never anticipated also convinced me that screencasting is a great method for teaching: the mistakes I make.  As I’m recording, depending on the degree of mistake I make, I’ll work out the problem and continue with the screencast.

Many viewers have commented on this as though I’ve dived right in to the session and included all my mistakes, and how this is one of the most valuable aspects of the screencasts.  They get to see how someone else would approach debugging a completely unrelated bug during development.

Why do you think screencasts work?

The real killer aspect of screencasts is that you can convey two methods of education: audibly and visually, and as such there’s very little effort and commitment required from the viewer.

The comparison is easy: I could read the newspaper and it would take me 15 minutes.  Alternatively I watch the news on the TV which would take me 5 minutes but I’ve taken in even more information in a much shorter time.

It is simple to see the benefits given how busy people are in today’s world.

This is only for education screencasts.  Screencasts as sales tool are powerful mediums to demonstrate a product and win a customer.  The visitor to your site has to give very little, i.e. a simple click on an image to start the video, before they’re given an introduction to using the product.  Without a screencast, the sales tool would be a feature list and some screenshots.

Text and images certainly have their value, but to me, the screencast is the extra value, the icing on the cake if you will.

Do screencasts ever replace text+pictures for explaining certain topics?

I wouldn’t say that screencasts should entirely replace text & pictures – or certainly not for tutorials.  Indeed all the screencasts on jQuery for Designers also comes with a complementing article.  Some articles go in to more detail than others but I still feel it’s important to explain the topic in some written form, even if it’s briefly.

The primary reason that I provide the full article is for both the visitors that would prefer to only read the tutorial but also for accessibility and for SEO.  If I were to only post a screencast, search engines would only have the title to index.  Whereas posting a written tutorial it is fully indexed, and new visitors could enter my site via Google searching for a specific answer.

There’s other issues with replacing text & pictures with just a screencast, often relating to now the content is accessed.  For example, screencasts can be many megs to download, if there was a written article summarising what the visitor will learn, they can make that decision before downloading.

If a screencast is available for a tool that you’re interested in – would you watch it?

Always. When a screencast is used to promote a product, or to give a preview of how something is used, it’s much more telling than screenshots.  With a product or a tool, as a user I already have an idea of what I should be able to do.  By watching a screencast, it will nearly always finalise my decision as to whether I want to download or purchase a tool.

I think this works particularly well for software.  There’s no better sales tool, than to show a potential user how to interact with the software.  The Apple web site use this tool for all of their key products and include demos of how to use the software as a sales tool to get people interested in all the things they could do with their software.

What hardware and software do you use to screencast?

My very first screencasts were run on a MacBook Pro via the internal microphone.  This works fine if you’re doing quick and dirty screencasts.  However the biggest problem, aside from bad sound, was that after a while of recording, the fan would kick in and it could be heard in the audio.

Today I record on an iMac, 2.8Mhz 2Gb machine.

I also have a separate user account set up that I can switch to record the screencast.  That way I can prepare a specific wallpaper – which includes brand, Creative Commons information and URLs, a specific screen resolution (800×600) and desktop icons for the session.  This allows me to record the full screen to include everything I do during a session.

I use a Samson CO1U mic, which I set to record in AAC mono 22.050 kHz.

The video is compressed using H.264 at 12fps.  These settings keep the size down for the visitor but maintains a good end quality screencast.

The software I use for recording the session is iShowU.

Once the session is completed (for my posts I don’t edit the video, I try to get a single uncut take – but this is because of the nature of the subject I’m screencasting) I will convert to iTunes compatible MP4 and to raw FLV.

This way I can make both Flash and QuickTime versions available on from my web site, and the MP4 version available on iTunes (which has to be 640×480 – so some video compression takes place).

Are there any other screencasting sites that web-developers should know about?

Other than jQuery for Designers the biggest screencasting site I would recommend is CSS-Tricks run by Chris Coyier.  He publishes screencasts primarily covering CSS but also other web topics, such as Photoshop and jQuery.


Ian is a professional screencaster (ProCasts, twitter) and blogger (IanOzsvald.com).

Interview: Horst Jens, open-source screencaster at ShowMeDo.com

Here Horst Jens, another long-time author in ShowMeDo, tells us about his background working with kids and open-source and how he spreads knowledge via screencasts.  He takes charge of the interview later on and sets his own questions that he has to answer.  Horst mainly uses Linux with RecordMyDesktop.  Note – I’m a co-founder of ShowMeDo.

What’s your background?

I work and live in Vienna, Austria as an programmer/computer teacher and have founded my own company spielend-programmieren.at (“programming while playing”) with the focus on teaching young students the joy of open-source game-programming.

What sort of screencasts do you make?

Usually screencasts about themes of the Linux/Open-Source world. I like to work with  students and kids. See my ShowMeDo page.

Why do you think screencasts work?

I think there is no better way of learning than having to explain a topic to someone else. Producing screencasts force the students to learn a topic to be able to explain it.  I see it as a learning tool for the screencast-maker first, for the screencast-watcher second.

showmedo.com (where I publish almost exclusively) has a good feedback function and I get emails nearly each day, encouraging me to make more and better screencasts.

So, the motivation aspect  works for me :-)

I suspect that most of the watchers of “my” screencasts don’t learn so much from the video itself; more get the feeling like: “hey, it’s that simple, even those kid on the video could do it” and the watcher does the little required actual learning by looking up the documentation.

However I noticed that many people learn not by watching what the teacher says but instead by watching what their neighbor does.

Maybe screencasts support this way of learning.

Do kids like making and watching screencasts?

Until the kids find out how much hard work it is to produce even a very small video: yes.

Having to be silent while one kid tries to speak a single sentence over-and-over again is sometimes hard for the other kids.

The good thing is that kids become experienced fast and it pays to make several screencast with the same group of kids at different times.

Do screencasts ever replace text+pictures for explaining certain topics?

I hope not, (functional) illiteracy is a big enough problem that I see while teaching in a rich, developed country like Austria.

The biggest problem for me with screencasts is that you are stuck with the creators speed. In a book, I can turn some pages forward if I’m bored or read a chapter slower if it’s difficult. While technically I can fast-forward and rewind on a video, it is less practicable (streaming) and more difficult to find the next “chapter”.

Ian Ozsvald encourages authors to do series of smaller videos instead of one big video, that is a good idea.

To answer the question: hopefully not replace but complete.

What software do you use to screencast?

Getting a kick out of being 100% open source I work with xvidcap on linux. My newest version of Ubuntu Linux don’t like xvidcap so I work with RecordMyDesktop at the moment.

I never found a good video-editor on Linux (there exist several but are all too complicated for me) so I work in a very arcane way with mplayer command-lines to include subtitles and logos, cut pauses etc. See Ubuntu video editing for notes. For editing sound I use Audacity.

What hardware do you use?

Different laptops, and a Logitech webcam. I found out that the microphone built-in to the webcam is better than the cheap external microphones I have used in the past.

How long does it take to get a new person making a screencast?

As a rule of thumb you need 10 times the “film” time to record a screencast. So to produce a 6-minute clip you need a full hour (with no post-production). If you have experience this time decreases dramatically.

Does watching a screencast about a commercial tool help you decide whether that tool is the one you need?

“About a commercial tool” ? Could not say, I prefer open-source tools :-)

I experimented with the idea of making a screencast about a “close-sourced”-computer game (YouTube) but I doubt that anyone will buy the game because of my video :-) I see screencasts more in a support role, for users that already bought a software rather than an marketing tool.

From a customer perspective, I would prefer a product that inspire users to produce lots of  screencasts over a product that provide only company-made screencasts. So I could use number and quality of user-made screencasts as an popularity-indicator of a product as well as an indicator of the quality of support I could expect from the product’s community.

What useful sites have you found that teach screencasting?

showmedo.com has all that you need.

And at this point Horst decided to write his own questions and answers to express further thoughts, mostly about ShowMeDo (note – I’m a co-founder) that he felt needed airing :-)

What don’t you like about ShowMeDo?

….(long pause)…this is a very difficult question! Well, the ShowMeDo wiki is not very popular, that’s sad because I like Wiki. Also I don’t see the sense of anonymous comments. I want to answer everyone who writes me a comment. If you really need anonymous feedback, a simple rating or flag system is enough.

What do you like about showmedo.com?

  • The founders, Ian and Kyran, these are great guys
  • The focus, about open-source
  • The policy: the videos are free, and authors are encourage to license under a creative-commons license. Lot of video sites look for the quick dollar; be it with banner-ads, be it with pay-per-view models etc. Most videos on showmedo are free from the start, and I think the subscription model is very fair.

What was your worst moment with showmedo?

Working 2 weekends and visiting my own elemtary school twice to produce a single video with elementary school kids…just to realize the video is crappy because of my visual concept. I haven’t published the video yet.  Poor kids, they put much work into it :-(

On a German OpenOffice forum I got criticised for a series of German open-office video tutorials. I do not mind the critique (some of the videos were bad) nor the style (produce nothing, criticise  others) but i don’t like to get criticised  for the idea of showing the speaker’s face using a webcam. I had seen this concept on ShowMeDo first (on a video about Django) and have never created a screencast without a webcam since.

What was your best moment with showmedo?

  • Getting good feedback right from the start for my first (crappy) video
  • Getting good feedback still feels good every time
  • Doing something for free education
  • Winning a price at the ars-electronica competition because I made a ShowMeDo screencast with kids – this felt very good
  • Seeing my name published in the Python Papers because of Ian’s work
  • Too many ‘best moments’ to select one and they still are coming :-)
  • Producing a video with students in Chinese and Russian language  even though I speak no word of each language
  • Reading comments below a video about Python in Russian language:

“Thank God I understand Python.” – gasto

“Clear and simple even if I don’t understand either Russian nor German.” – richard1956

“Very nice introduction to Python! I enjoyed the video very much! I was surprised to find how anyone can easily follow along no matter what language you speak! I feel stupid now, I guess that’s why Python is called a programming language : )” – anonymous

Where do you want to see ShowMeDo.com in the future?

In a world where bad news and pessimistic prognoses are produced by the hour I make an optimistic forecast: ShowMeDo will be there in the future, it will be somewhat bigger and
still great.

Along with the One-Laptop-per-Child project, I think that the best way to improve this planet and it’s residents is to spread access to knowledge and education. ShowMeDo can be a part of it; providing the tools, the knowledge and the community for everyone to share his bit of wisdom and giving access to this wisdom to everyone.

I also think that video-platforms like ShowMeDo will inherit the role that currently big publisher houses hold for the book market: Providing for the audience the service of filtering only the most interesting of all the those possible authors and providing for the authors the service of helping to reach the audience.

I feel  that those companies that provide the best all around (learning) service  will rise while those that hold on to the concept of physical learning products will fail.

In ShowMeDo’s financial humble beginnings, Ian and Kyran have already proved  to always put the user’s needs before their own needs. This attitude makes me certain to see a bright future for ShowMeDo in the long run.


Ian is a professional screencaster (ProCasts, twitter) and blogger (IanOzsvald.com).

Interview: Gabrial Hasbun, open-source screencaster at ShowMeDo.com

Gabriel Hasbun (gasto) is another long-time screencaster at ShowMeDo.com where he has created over 20 tutorial screencasts.

What sort of screencasts do you make?

Educational screencasts for programming (C and Python) and software usage (GIMP, and in the future Blender).

How long does it take you to make each screencast?

It depends. There are 2 types of screencast (if one wants to show discrimination) :

  1. Straight forward screencasting. One simply records one’s voice and screen while showing the educational material on-screen. A 20 minutes screencast takes about 1 hour, and 4 if I went through a rehearsal script before. So it will depend also on the familiarity of the subject to me.
  2. Edited screencasting. These are the most time consuming. Only recommended if what one wants is to emphasize on concepts rather than sole “clicking here creates X” screencasts. One needs video editing software. A 20 minutes screencast might take 3 days (if I really want it polished)

What software do you use to screencast?

  • CamStudio for screencasting
  • VirtualDub and the GIMP/GAP for video editing
  • Audacity and Cubase LE for sound/music editing

What hardware do you use?

An old Pentium Celeron 2.6 Ghz, 2 GB RAM, 255 MB GeForce 6200 AGP graphics card, with a Lexicon Labmda mini audio studio, a Dexun Pro-58 microphone, a Casio music keyboard, SoldSound headphones and a lot of patience.

What does a new screencaster need to get started?

  • Patience, like everything worth one’s time.
  • A lot of knowledge and a lot of research.
  • The will to help people.
  • Love of computers
  • Didactics knowledge
  • Creativity
  • A computer with minimum performance (to 2009 mainstream standards), unless one wants advanced video editing, in which case I would recommend a fast processor and a mid-profile graphics card. Integrated audio is OK unless one is interested in composing music, in which case I’d recommend a cheap audio interface from Lexicon (Alpha is OK).
  • Articulated speech

What useful sites have you found that teach screencasting?

Do you recommend screencasts as a good technique to teach new users about software?

Yes. Multimedia in general will always be better than plain boring text. It enhances the learning experience:

  • Provides immediate confidence with software/programming because of the I-am-at-your-side-teaching feeling the screencaster gives with the voice
  • The visual feedback inherent in screencasts of what needs to be done on screen with the input device replaces the need of a distracting textual explanation
  • Text is boring. Writing 5000 characters to explain how one’s software/library/website works is a good way of scaring away your potential users
  • Watching a screencast is fun, easy-going, and easy to the eyes;
  • Following a screencast and mimicking is straightforward, no need for translations of text to action

In my opinion all computer documentation should use screencasting and leave text for medieval transcripts.

You see, in my previous paragraph, it is not clear whether I am referring to a computer booklet which explains the motherboard specifications, or documentation written digitally. I could’ve used more refined terms or add extra lines for the clarification. In screencasting, that is not necessary at all. Language issues are resolved visually immediately.


Ian is a professional screencaster (ProCasts, twitter) and blogger (IanOzsvald.com).


  • Subscribe2

  • Pages

  • Recent Posts

  • Archives

  • Categories