Qualitative analysis software for video and audio data  
Developed at the University of Wisconsin-Madison Center for Education Research  

Download ::
  Latest Version
  Archived Versions

 
What's New in Transana 2.11?
  • To make a selection in the Visualization Window, you can now click on the starting point of your selection and hold down the Shift key while clicking to select the ending point. This allows easier modification of a selection in the waveform. Click once a the start, and use repeated shift-clicks until you find the correct ending point.

  • There are new ways to control the video position from the Visualization Window.

    • When the Visualization Window has the program focus, you can use cursor left and cursor right to move the visualization cursor one pixel. (The amount of time this movement represents depends on the length of the current video, the width of the visualization window on screen, and the level of zoom of the visualization window.) If one pixel would be less than a single frame of the video, the video position will shift by one full frame.

    • If you hold down the Shift key while pressing the cursor keys, you move the video in one second increments.

    • If you hold down the Alt key, the video moves in 1/2 second increments.

    • If you hold down the Ctrl key, the video moves by 1/30th of a second, or one frame under the NTSC standard.

  • You can now create clips using an open coding approach. That is, there is now a mechanism for creating simple clips quickly and easily in the early parts of an analysis. See the "Quick Clips" page in the Transana tutorial for more information about this feature.

  • A number of enhancements for the keyword map have been implemented:

    • As you move your mouse over a colored band in the keyword map, the name and duration of the clip(s) represented by that band are displayed in a hint popup.

    • Left-click a band to load the appropriate clip and close the keyword map.

    • Right-click a band to load the appropriate clip and leave the keyword map open.

    • If multiple clips overlap on the keyword map, this is now indicated by a multi-colored band.

    • You can select what keywords are included or excluded from the report (keyword filtering).

    • You can alter the order that keywords appear in the report (keyword ordering).

    • You can alter what clips are included in the keyword map (clip filtering).

    • You can specify a time range within the Episode for display. This makes short Clips in long Episodes much easier to see and interpret.

    • You can save and re-load "Filter Configurations" for the keyword map, allowing you to create reusable report templates.

    • The keyword map now displays bands in 23 colors, up from 12. (A couple of the greens can be a bit difficult to distinguish on a poorly adjusted monitor. Sorry about that.)

  • When loading a clip through the Episode Clips tab and the Selected Clips tab in the Data Window, the appropriate clip record is highlighted in the Database Tree tab, making the manipulation of the identified clips more convenient.

  • During Transcription, you can now save your transcript by pressing F12.

  • Database loading has been optimized. One multi-user database used for testing showed a decrease in loading time from 35 seconds to 0.33 seconds.

  • A few new colors have been added to the Transcript Font options.

  • Norwegian Bokmål and Norwegian Ny-norsk translations have been added. (We offer our sincere thanks to Dan Jacobsen for this.)

  • Numerous bugs, most of them obscure and unreported, have been fixed. Some of these were never public, but occurred when we upgraded wxPython. Others can be observed in the 2.10 release series.

    • Field length limits are now enforced on all Properties forms. (If you had multiple clips that had the same first 100 characters in the Clip ID, bad things could happen.)

    • If the user clicked on the time code symbol when making a selection for a clip, the transcript cursor could get "caught" between the time code symbol and the time code data. If you see a clip that starts with time code data (the "<" and ">" characters with numbers in between), it is likely that the clip has the wrong clip start time.

    • Creating a clip from within another clip was fixed.

    • Problems detecting Time Codes on the Mac during RTF and Transana XML import were fixed.

    • There was a problem with some style creation on the Mac, making it difficult to select some font colors.

    • There was a problem updating the Video Root directory with some legacy databases.

    • The Chat Window now reflects changes in interface language.

    • Database Export now works in languages other than English.

    • Editing or removing Clip Keywords via the Keywords Tab caused ugly error messages if the Clip Transcript was in Edit Mode. The error messages are much clearer now.

    • Keyword Group error checking has been improved. Case differences are now ignored. Illegal characters such as parentheses and colons are now prevented better.

    • Keywords with colons (":") embedded in them could not be removed from Episodes or Clips. This has been fixed.

    • Occasionally, a Clip would be prematurely terminated following Pause in the Play All Clips routine. This has been fixed.

    • In Transana-MU, Clip Transcripts would not re-load properly following Multi-user edit conflicts.

    • In Transana-MU, changes in Episode and Clip Keywords by one user were not being reflected on the Keywords tab of other users. If user 1 was viewing the Keywords tab when user 2 made changes, then user 1 made changes, user 2's changes would be lost.

    • In Transana-MU, drag-and-drop keyword assignment was not reporting keyword assignment failures due to record locks. Thus, a user could believe a keyword had been assigned when in fact it hadn't because of a record lock problem. Cut-and-paste keyword assignment reported the error awkwardly.

    • In Transana-MU, if one user is editing an object's properties, including the object's ID, when another user saves an object properties edit that changes the selection in the database tree for the first user, the wrong tree node on screen will be updated when the first user saves for all users. (The actual data objects will be saved correctly in the database. Only the database tree on screen will be incorrect. Restarting Transana-MU resolves the problem.) This problem has been corrected by ensuring that the current selection in the database tree is not altered when other users make changes that affect the tree.