• Skip to primary navigation
  • Skip to main content

site logo
The Electronic Journal for English as a Second Language
search
  • Home
  • About TESL-EJ
  • Vols. 1-15 (1994-2012)
    • Volume 1
      • Volume 1, Number 1
      • Volume 1, Number 2
      • Volume 1, Number 3
      • Volume 1, Number 4
    • Volume 2
      • Volume 2, Number 1 — March 1996
      • Volume 2, Number 2 — September 1996
      • Volume 2, Number 3 — January 1997
      • Volume 2, Number 4 — June 1997
    • Volume 3
      • Volume 3, Number 1 — November 1997
      • Volume 3, Number 2 — March 1998
      • Volume 3, Number 3 — September 1998
      • Volume 3, Number 4 — January 1999
    • Volume 4
      • Volume 4, Number 1 — July 1999
      • Volume 4, Number 2 — November 1999
      • Volume 4, Number 3 — May 2000
      • Volume 4, Number 4 — December 2000
    • Volume 5
      • Volume 5, Number 1 — April 2001
      • Volume 5, Number 2 — September 2001
      • Volume 5, Number 3 — December 2001
      • Volume 5, Number 4 — March 2002
    • Volume 6
      • Volume 6, Number 1 — June 2002
      • Volume 6, Number 2 — September 2002
      • Volume 6, Number 3 — December 2002
      • Volume 6, Number 4 — March 2003
    • Volume 7
      • Volume 7, Number 1 — June 2003
      • Volume 7, Number 2 — September 2003
      • Volume 7, Number 3 — December 2003
      • Volume 7, Number 4 — March 2004
    • Volume 8
      • Volume 8, Number 1 — June 2004
      • Volume 8, Number 2 — September 2004
      • Volume 8, Number 3 — December 2004
      • Volume 8, Number 4 — March 2005
    • Volume 9
      • Volume 9, Number 1 — June 2005
      • Volume 9, Number 2 — September 2005
      • Volume 9, Number 3 — December 2005
      • Volume 9, Number 4 — March 2006
    • Volume 10
      • Volume 10, Number 1 — June 2006
      • Volume 10, Number 2 — September 2006
      • Volume 10, Number 3 — December 2006
      • Volume 10, Number 4 — March 2007
    • Volume 11
      • Volume 11, Number 1 — June 2007
      • Volume 11, Number 2 — September 2007
      • Volume 11, Number 3 — December 2007
      • Volume 11, Number 4 — March 2008
    • Volume 12
      • Volume 12, Number 1 — June 2008
      • Volume 12, Number 2 — September 2008
      • Volume 12, Number 3 — December 2008
      • Volume 12, Number 4 — March 2009
    • Volume 13
      • Volume 13, Number 1 — June 2009
      • Volume 13, Number 2 — September 2009
      • Volume 13, Number 3 — December 2009
      • Volume 13, Number 4 — March 2010
    • Volume 14
      • Volume 14, Number 1 — June 2010
      • Volume 14, Number 2 – September 2010
      • Volume 14, Number 3 – December 2010
      • Volume 14, Number 4 – March 2011
    • Volume 15
      • Volume 15, Number 1 — June 2011
      • Volume 15, Number 2 — September 2011
      • Volume 15, Number 3 — December 2011
      • Volume 15, Number 4 — March 2012
  • Vols. 16-Current
    • Volume 16
      • Volume 16, Number 1 — June 2012
      • Volume 16, Number 2 — September 2012
      • Volume 16, Number 3 — December 2012
      • Volume 16, Number 4 – March 2013
    • Volume 17
      • Volume 17, Number 1 – May 2013
      • Volume 17, Number 2 – August 2013
      • Volume 17, Number 3 – November 2013
      • Volume 17, Number 4 – February 2014
    • Volume 18
      • Volume 18, Number 1 – May 2014
      • Volume 18, Number 2 – August 2014
      • Volume 18, Number 3 – November 2014
      • Volume 18, Number 4 – February 2015
    • Volume 19
      • Volume 19, Number 1 – May 2015
      • Volume 19, Number 2 – August 2015
      • Volume 19, Number 3 – November 2015
      • Volume 19, Number 4 – February 2016
    • Volume 20
      • Volume 20, Number 1 – May 2016
      • Volume 20, Number 2 – August 2016
      • Volume 20, Number 3 – November 2016
      • Volume 20, Number 4 – February 2017
    • Volume 21
      • Volume 21, Number 1 – May 2017
      • Volume 21, Number 2 – August 2017
      • Volume 21, Number 3 – November 2017
      • Volume 21, Number 4 – February 2018
    • Volume 22
      • Volume 22, Number 1 – May 2018
      • Volume 22, Number 2 – August 2018
      • Volume 22, Number 3 – November 2018
      • Volume 22, Number 4 – February 2019
    • Volume 23
      • Volume 23, Number 1 – May 2019
      • Volume 23, Number 2 – August 2019
      • Volume 23, Number 3 – November 2019
      • Volume 23, Number 4 – February 2020
    • Volume 24
      • Volume 24, Number 1 – May 2020
      • Volume 24, Number 2 – August 2020
      • Volume 24, Number 3 – November 2020
      • Volume 24, Number 4 – February 2021
    • Volume 25
      • Volume 25, Number 1 – May 2021
      • Volume 25, Number 2 – August 2021
      • Volume 25, Number 3 – November 2021
      • Volume 25, Number 4 – February 2022
    • Volume 26
      • Volume 26, Number 1 – May 2022
      • Volume 26, Number 2 – August 2022
      • Volume 26, Number 3 – November 2022
  • Books
  • How to Submit
    • Submission Procedures
    • Ethical Standards for Authors and Reviewers
    • TESL-EJ Style Sheet for Authors
    • TESL-EJ Tips for Authors
    • Book Review Policy
    • Media Review Policy
    • APA Style Guide
  • TESL-EJ Editorial Board

FireWire and Creating Web-Based Video Content

November 1999 — Volume 4, Number 2

FireWire and Creating Web-Based Video Content


Jim Duber
UC Berkeley
<jim@duber.com>

If you haven’t already heard about FireWire (also known as IEEE 1394 and iLink)[1], the new standard for high-speed connections between computers and peripheral devices, then chances are you will very soon as all sorts of new devices that take advantage of FireWire technology are quickly coming to market. The benefits of FireWire for digital video creation have made it the current interface of choice among professional multimedia developers. Now that same technology is appearing in consumer-level computers, video camcorders, disk drives, and more. As a result, the goal of producing quality desktop video is within reach of the masses, and that includes TESL teachers and students.


FireWire: The Benefits

The advantages of FireWire all derive from its speed–at 400Mbps, it has 30 times more bandwidth than USB. At this rate, there’s a lossless transfer of digital video data from a FireWire equipped camcorder, for example, to the computer. Before FireWire, developers had to invest in far more expensive hardware and software setups and then struggle with the technology in order to convert videotape to a digital format. This process, known as digitizing, can be awfully time-consuming, and frequently results in dropped frames where video segments aren’t captured simply because the hardware just isn’t fast enough to keep up. With the new breed of FireWire-equipped digital camcorders, the video is actually digitized as it’s shot, and the speed of the transfer to and from a computer via FireWire is such that there is no loss of quality and no dropped frames when going from camera to computer and back again. Simply revolutionary.

Some additional benefits of FireWire are that it supports up to 63 interconnected devices using cables up to 14 feet in length; it is "hot-pluggable," i.e., you don’t have to turn your computer off before connecting or disconnecting a FireWire equipped camera, scanner, Zip drive, etc.; you don’t have to set device IDs, jumpers, DIP switches or terminators. Truly "plug and play."

The Creation Process

Many classroom instructors are accustomed to using video cameras for student analysis, simulations, role plays and class projects. By going the digital route, they can now easily edit, customize and publish these videos to the web or private intranets. Creating digital video content has truly never been easier. Here are the basics:

The Shoot

With the camera on a tripod to keep it steady, shoot close-ups as much as possible. Small background details tend to get lost when sizing clips for the web (typically 320 X 240 pixels). It’s best to keep movement at a minimum–scenes with pans and zoom effects can pose a problem in the compression stages. Because the audio portion is probably of utmost importance, a good microphone is generally advisable.

Log and Edit

Digital video (DV) files require about 3.8Mb/second (approximately 230Mb/minute) of storage space. For that reason alone it’s usually best to make a quick inventory of all the available shots on a tape so that you can transfer only the data that you need to work with. You’ll need to make sure you have at least 2GB of available space on your hard drive for every 9 minutes of DV. There are several software products that are specifically intended for digital video production. The latest version of Adobe Premiere (Win/Mac) and Apple’s Final Cut Pro (Mac only) are two outstanding examples, both of which make the logging process very easy. With a FireWire cable connecting the camcorder to the computer, these software products can control the camera, prompt you to create a detailed log of your video data and automatically capture only the clips that you mark when the time comes.



Final Cut Pro’s "browser"–the icons on the left represent clips, the red lines indicate that they have yet to be captured.

After logging the video, you decide which clips to transfer from the camera to your computer in the capture stage. Once again, the computer can control the camera via the FireWire connection and it will very quickly locate only the sections that you’ve marked as "good" to transfer. Now that the video is on your computer, you can use the same software to edit it further–it’s very easy to trim unwanted sections, add transitions between scenes, and overlay titles, soundtracks, effects and more.



Final Cut Pro’s main interface windows.

Final Output and Delivery

After applying the final edits to the project be sure to save and archive all your hard work. Most video software will allow you to print a copy to video tape for playing on a standard VCR or back out to the video camera for archiving to tape.



Adobe Premiere’s Print to Video dialogue box.

In order to make your video viewable on the web, however, you’ll need to compress your work using one or more of the standard web video formats–QuickTime, RealVideo, or Windows Media. Again, the editing software will help, though to achieve the best results with any of the formats, it’s often necessary to experiment while learning the art of video compression. The best description of compression I’ve ever read is contained in a manual that comes with the Sorenson Video Developer’s Edition:

Compression is like making orange juice concentrate. Fresh oranges go in one end and concentrate comes out the other. The concentrated orange juice takes up less space, is easier to distribute, and can easily be reconstituted by the consumer.

Video compression takes a large file and makes it smaller. The smaller files require less hard disk space, less memory to run, and less bandwidth to play over networks or the internet. Many compression schemes exist and all have their specific strengths and weaknesses. (p. 12)

After this stage, the job is nearly complete and your files are ready to be added to a web page and uploaded to a web server so they can be accessed by your students and the world at large.

Additional Resources

More details on digital video and FireWire are available at these websites:

http://www.DVCentral.org/Firewire.html

http://amazing.freelink.net/dv/dv-faq.html

http://www.CodecCentral.com


Note

1. Originally created by Apple and called FireWire, the same standard as adopted by Microsoft is called IEEE 1394 and by Sony as iLink.

[return to reading]





© Copyright rests with authors. Please cite TESL-EJ appropriately.

Editor’s Note: Dashed numbers in square brackets indicate the end of each page for purposes of citation.

© 1994–2023 TESL-EJ, ISSN 1072-4303
Copyright of articles rests with the authors.