iCaption 2.4.2 Released

iCaption 2.4.2 has been released today, to address the following issue:

– Fixed a bug from iCaption 2.4.0 where loading subtitles previously made would result in bad times on systems with region settings using ‘.’ as a number separator and ‘,’ as a decimal separator.

 

iCaption 2.4.1 Released

iCaption 2.4.1 has recently arrived, as a bug fix release. See changes below.

– Fixed a bug from iCaption 2.4.0 where the video playback and seeking started from the markers with a timing tolerance (in some cases a few seconds).
– Fixed a crash from iCaption 2.4.0 where the playback to the very end of the video crashed the application.
– Fixed a crash when loading another video while still playing a first video would crash the application.
– Fixed a rendering artifact in the waveform visualization when jumping between sections in the video and playing them out of sequence.

 

iCaption 2.4.0 Released

iCaption 2.4.0 has recently been released, adding new features requested by the users.

The audio and video core of iCaption has been re-written to take advantage of OSX 10.9 Mavericks’ AVFoundation (the QuickTime API is deprecated in 10.9). Warning: All OSX versions prior to 10.9 are now unsupported. Support for non-Apple-friendly media formats will be affected as a consequence. For Snow Leopard, Lion or Mountain Lion support please continue to use iCaption 2.3.0.

  • Added the ability to instantly edit the subtitle’s start and end times in the timeline by dragging them (without pressing the Apply to Subtitle button afterwards). Apply is still used to move the entire subtitle.
  • Added the ability “Add Next Subtitle”, which starts at the end of the currently selected subtitle, with the same duration.
  • Added drag and drop for opening supported media formats.
  • Added drag and drop for opening supported subtitle formats.
  • Fixed search for subtitle translations to use the new search API by AllSubs.org.

 

iCaption 2.3.0 Released

iCaption 2.3.0 has recently been released, adding new features requested by the users.

  • The Preview is now combined with Play/Pause, which is toggled with the Command + P shortcut.
  • Added the ability to add subtitles on the fly while the video is playing, using the ‘[‘ and ‘]‘ keys in combination with Command for the new subtitle’s start and end times respectively.
  • Added trackpad support for the changing the timeline scope.
  • Two-finger horizontal swipe while the pointer is in the time line will move the scope one minute forward or backward.
  • The pinch/stretch gesture while the pointer is in the time line will zoom in and out of the scope.
  • Updated the documentation.

iCaption 2.2.0 Released

Another follow-up on the 2.x series includes mostly bug fixes, a more flexible timeline size and online translation search capabilities from allsubs.org.

  • Added the ability to adjust the height of the subtitle timeline, taking further advantage of the multi-resolution waveform visualization algorithm, and allowing for finer-grained study of the audio track.
  • Added a feature to search for translations of the currently loaded media.
  • Fixed a sandbox connection denied issue after selecting a video, which may have occurred for users who have dictation input enabled in Mountain Lion, causing iCaption to not be able to load reference videos.
  • Fixed a bug (from 2.0.0) with Adjust All Subtitles where the durations were incorrect.
  • Fixed a bug (from 2.0.0) with automatic subtitle duration was not automatically setting the same duration that it was reporting.
  • Fixed a bug when the subtitles list is filtered by a search, and clicking on a subtitle will show a preview from the unfiltered list.

iBodyFat 1.2.0 Released

What’s New in Version 1.2.0

– Added an average (mean) percentage column to the data table
– Added a line graph showing relative drops in body fat percentage, weight and BMI.
– Added the ability to modify the date that a measurement was taken in the data table (after the fact), in case you are adding backlogged information.
– Improved number formatting, alignment and spacing in the user interface.
– Updated multi resolution application icon for hi-res displays.
– Updated graphics and documentation.

 

iKeepActive Lite 1.1.2 Released

Added a new mechanism for tracking when scheduled activities are due in Mountain Lion.
– For earlier versions of OS X, the Applescript system is still used for tracking due activities.
– Rearranged the flow of information on the Summary View for ease of the new user.
– Added 4 more available activities.
– Quite possibly one of the last versions to support Snow Leopard and Lion, so get it while you can.
– Dropped support for 32-bit.

iKeepActive 1.2.2 Released

The latest version of iKeepActive (1.2.2) is now available in the Mac App Store now. The release focus is on Mountain Lion Fixes, but other features and improvements have also been added so updating is recommended for everyone on 64-bit Intel Macs.

– Added a new mechanism for tracking when scheduled activities are due in Mountain Lion.
– For earlier versions of OS X, the Applescript system is still used for tracking due activities.
– Added support for retiring scheduled activities. This allows you to remove an activity from your calendar while still keeping the history for tracking purposes. Retired activities can be re-scheduled.
– Rearranged the flow of information on the Summary View for ease of the new user.
– Added 4 more available activities.
– Quite possibly one of the last versions to support Snow Leopard and Lion, so get it while you can.
– Dropped support for 32-bit.

iBodyFat

About

iBodyFat is an application which calculates your body fat percentage and keeps a log of your results. Two different calculations are presented for each measurement made. The body fat percentage formulas used by iBodyFat are girth body fat calculations invented by the U.S. Navy, and professional body builder and writer Hugo Rivera.

For taking girth body fat measurements, no special equipment is needed; all that is required is a vinyl tape measure. Girth is not as accurate as skin fold techniques using body fat calipers, but there has been claim of +/- 3% accuracy. However there is chance it can be wrong because you can only tell so much by circumference.

Features

– Get two body fat percentage ratings for each measurement.
– Tracks all of your measurements by date.
– Also tracks your Body Mass Index.
– Multi-user support.
– Fully documented.
– Designed so future versions of the application may have more formulas and body fat measurement methods.

Screens

Requirements

In order to run iBodyFat, your Mac computer must meet the following requirements:

  • Intel-based Mac with OSX 10.7 Lion or greater
  • 1 GB Memory
  • 5 MB Free hard disk space

iCaption

About

iCaption is a simple-to-use soft subtitle editor, utilizing timeline based editing. The file formats currently supported are SubRip and YouTube.

What are soft subtitles? Soft subs are external files stored separately from the video file. They are called soft, because they are not hard-encoded into each video frame; they are rendered in real-time. Most modern video players support soft subs and can manage multiple files for quick and easy swapping of languages.

Features and Capabilities

  • A robust, elegant user interface.
  • Powerful timeline editing, with or without a reference video loaded.
  • Waveform visualization in the timeline, overlaying onto subtitle time time visualization.
  • Transfer subtitle times from the reference video or the timeline selection.
  • Automatically determine the subtitle duration.
  • Real-time checking and visualization for overlapping subtitle times.
  • Easily adjust all subtitle times with one edit.
  • Search subtitles allows you to filter the subtitle list.
  • Previewing allows you to test subtitles without an external viewer.
  • Create, edit, open and save YouTube (.sbv) files.
  • Create, edit, open and save SubRip (.srt) files.
  • Convert SubRip to YouTube format and vice versa.
  • Complete abstraction from the subtitle file formats.

Screens

Requirements

In order to run iCaption, your Mac computer must meet the following requirements:

  • Intel-based Mac with OSX 10.6.7 (Snow Leopard) or greater
  • 1 GB Memory
  • 4 MB Free hard disk space

 

Frequently Asked Questions

You should be able find all you need to know about iCaption in the in-app help; just click the Help button on the toolbar. For all issues/concerns not answered in the FAQ below, nor in the in-app help, email jeffrey@seatoskyware.com and include your hardware info and version of Mac OSX.

Where can I get iCaption Editor? ^top
It is available in the Mac App Store.

I am trying to make subtitles for an .mkv video and I can’t load it as a reference in iCaption Editor. ^top
iCaption Editor uses an embedded QuickTime movie view and therefore supports only the formats supported by QuickTime. If you are the creator of the video, it is more than likely that QuickTime supports your source format. If are not the creator of the video file, be aware that creating subtitles for certain videos you do not own the rights to may be considered as copyright infringement. It is possible to get QuickTime add-ons for more file formats, here orhere, but that is not directly supported neither by iCaption Editor nor QuickTime.

Which reference video formats does iCaption Editor support? ^top
As mentioned above, iCaption Editor supports the media formats supported by QuickTime, as well as the formats supported by any QuickTime add-ons you have installed.

The miliseconds for my subtitle times don’t look right (in version 1.x only). ^top
There is nothing wrong with your subtitle times. When iCaption transfers the times from the movie, the miliseconds are shown as a timescale. This is because QuickTime understands time scales instead of miliseconds, where the number is displayed as frames/timescale, where timescale can be different between videos and frame rates. Don’t worry; upon saving the subtitle iCaption Editor will properly convert the timescale to 1000, its equivalent in miliseconds. Another thing to note is that timescales have no leading zero’s, so 62 milliseconds would be displayed in the table as .62/1000, not .062/1000.