LibCasting

I wish I noticed this earlier today, but for another couple of hours, you can get DemoCreator free at Giveaway of the Day (GOTD). Scroll down to the “Download Democreator now” link and be sure to install it and activate it before the deadline to get it for free. It apparently retails for $129.95, although it is on special now for $99 on the DemoCreator site (in case you don’t read this until after the special is over). Do note the terms and conditions of “Strictly non-commercial usage” on the free GOTD version. Also note all the quick reviews available on GOTD under the comments section.

I have not tried this software before. I’m downloading it, installing, and activating it as I type this, so I hope to have some type of review of it up in the future. If you happen to read this in time (deadline is June 14 at midnight PST), download the file, unzip it, run setup, then run activate. To check if you got it registered in time, click the small “order” icon (shopping cart) in the upper right and make sure it says that “DemoCreator has been registered.”

So after posting about Demofuse yesterday, I thought I’d post a screencast of what it is like to use. My Quick View of Demofuse (3.3 MB, 3:50) does not show all the features and is only based on my rather limited experience with Demofuse. Oh, and if anyone is interested in trying Demofuse, you need an invitation code. They gave me one to share — invitation code 731125. Enjoy!

Well this is not exactly screencasting, but Demofuse is a fascinating technology anyway. You can use it to create a special link that gives a tour of a Web page. I’ve only played around with it a bit, but it seems to be limited to a one page tour at a time, and you have to have edit access to the page so you can add a two lines of Javascript to the bottom. The process is fairly simple — I should do a screencast of it. But for now, take a look at a quick Demofuse tour on the home page of LibCasting (or click the button below which is the code they offer. The link to the tour of the page just adds a single variable to the end of the URL which quickly disappears once the tour starts. But the tour does not show when readers go straight to the page. In other words, a link to
http://www.notess.com/screencasting/
will not start the tour but one to
http://www.notess.com/screencasting/?dftid=1427413
will.

ACRL had a Getting Started with Screencasting Webcast back in April and it is scheduled again for July 26. Echoing Paul’s post, I am not exactly sure how “delivering screen captures via RSS” connects with screencasting, but see the comment to that post for an attendee of the earlier Webcast to see if it sounds interesting to you.

Paul “Distant Librarian” Pival has posted a YouTube video and a better quality screencast on how to find the RSS feeds now available on Ebscohost. The problem with posting a screencast on YouTube is that it is hard to read the text on the screens due to the YouTube resolution. I need to blog the details of how I’ve done it to try and get the highest quality possible. The advantage of YouTube is that it makes it very easy to embed the screencast in a blog post of on most any Web page. Note that Paul has to link to the “nicer-quality version” of the screencast.

This Camtasia-produced screencast is hosted on TechSmith’s Screencast.com, which is a fee-based system. It does not have an embed option like YouTube, and only provides HTML code for a fairly standard link. It would be nice if Camtasia provided a way to embed a screencast as easily as YouTube does, but with the higher quality.

Want to get an idea of what features might be available in the next version of Camtasia? See the “What’s coming in Camtasia Studio 5?” interview with  Camtasia Studio Product Manager, Troy Stein. I was intrigued that the interview is presented as an audio-only podcast rather than a screencast. It makes sense since the interview took place by phone (well, Skype anyway). Maybe Camtasia 5 would make it easy to produce a podcast like this without the need to use the Flash MP3 player used on this site.

One other use I’ve been making of screencasting is for communication with technical support and systems departments. Ever call in a technical issue and have the tech person not understand the problem? As a reference librarian, I know that I get calls where I am trying to guess the problem based on a verbal description. It is much easier when I can look over the person’s should and see the problem when it occurs.

So, this evening on the reference desk, I came across a strange problem with subject headings in our catalog. After describing it an an email, I decided to use Wink again to do a quick screencast to document the problem. In between answering reference questions, I was able to reproduce the problem, add a few call-out text boxes, and upload the screencast. As I mentioned in an earlier post, I have Wink at the reference desk since I can’t see recording audio there while I’m staffing the desk. Yet Wink lets me take a quick screencast for purposes like this one. Another benefit to creating screencasts for tech support issues is just that it provides another opportunity to practice making screencasts quickly. It is not (nor does it need to be) a highly polished production. Take a look if you would like.

For the more technically minded Web designers, A List Apart has an article, Flash Embedding Cage Match, that looks at various methods in which Flash can be embedded on a Web page. A List Apart always aims for standards-compliance, and sometimes their approaches will not work in all browsers, but it might be useful to compare with the default embedding that screencasting software produces.

While I’m catching up, I thought I’d follow up on my process post from November. I still haven’t finished (or even worked on) the screencast I talked about in that post, primarily because our site was going to be changing and the steps I wanted to show would be changing as well. That change is not yet complete, so I’ll be waiting awhile to try that screencast. However, later on the same day that I posted, I was working at the reference desk and received a reference question on voice mail. The person left an email address, but the process to get to the wanted information had many steps — a perfect candidate for a screencast. Unfortunately, not only did I not have Camtasia available at the reference desk, but there is also no microphone. Nor could I see putting on a headset-microphone combination while I was supposed to be approachable at the desk.

So, I thought I might try Wink instead. I fairly quickly downloaded and installed Wink. Then I just recorded the steps as I wrote them up in a draft email as well. Then I produced the screencast and uploaded it to a Web server (fortunately, I did have access to my work Web server from the reference desk). Then I sent the email along with a link to the screencast (0.8MB, 1:10). I could have taken more time to add call-outs, but I thought it better to respond more quickly. I tried to make sure that each step was clear and had a couple seconds between. It seemed to work, at least based on the email thank-you response I received. I wonder if other situations like this will crop up. If so, that’s another reason to learn to be able to produce screencasts quickly.

Now that the new semester is underway and both our library Web site and catalog have changed their design, it is time to get moving on updating some of my screencasts. It is also a good reminder to update this blog. I’ve just published a number of entries that had remained as drafts for the past month or so. If you’re interested, see the Linux Guide, OpenID, Meredith Muses, and PowerPoint Screencasts posts.

For my library screencasts, I started the update process with What Floor is this Book on?. Using Camtasia Studio 4, I found that on Windows 2000, it sometimes would freeze after I cut a section of the video clip. I also had a strange situation where the produced video had black bars on the top and bottom, no matter how I changed the output dimensions. I ended up having to re-edit the video which somehow avoided whatever caused that problem.
If you’re interested, you can compare the new screencast (1.4MB, 1:52) to the old one (1MB, 2:32). I ended up increasing the size, but I decreased the length. Some of the changes include getting rid of the keyboard sounds and reducing the dimensions. I found that the update process was more time consuming that I had hoped, mostly due to the problems mentioned above. However, now that I’ve worked out some of the problems, I plan on updating the others over the next week or so.

I also created a few screencasts for Search Engine Showdown over the last month or so. See my Overlap Showdown and my News Search Showdown posts. Both of those screencasts are hosted on YouTube. I host them on YouTube so that I do not have to worry about paying extra for the bandwidth on that account, but it also is nice to have the YouTube statistics, comments, and ability for others to embed the video themselves if they wish. Both of those videos were recorded and edited with Camtasia. I tried to record using a 320×240 window since that is the maximum YouTube dimensions. I then “produced” them as Quicktime .mov files which were uploaded to YouTube. In the Overlap Showdown, I used several blur call-outs to mask the personal information of the person for whom I was searching. This seemed to work well, but it was a bit tricky to make sure that the blur call-outs lasted for exactly the right amount of time to obscure the search term.