You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose that ZZZ mode (i.e. milliseconds) be removed from Tero Subtitler. [Note: users would, of course, still be able to import and export millisecond-based formats (SubRip; WebVTT, etc).]
Millisecond-based formats are historic, accessible, frame-agnostic, and supported by most media players, hence enthusiasts have tended to use them. Until the advent of TTML and derivative formats (containing support for frames and/or milliseconds), frame-based formats tended to be the preserve of studios (e.g. Spruce Technologies/DVD Studio Pro).
However, videos (which we typically synchronise to) are naturally frame-based (or indeed interlaced), as are video editors, so I believe the GUI of Tero Subtitler should only be frame-based, following in the footsteps of other subtitling solutions that tend to be favoured by high-end users/production environments (Annotation Edit, CaptionMaker, Cavena, EZTitles, Fab Subtitler, Ooona, SoftNI, Spot, Subtitle Horse, SubtitleNEXT, and Wincaps).
Ultimately, millisecond-based formats are intended for delivery; and unless I miss something, I cannot see an advantage in editing the numbers of milliseconds directly (i.e. without the frame infrastructure), so I think there should be a general discouragement of this in software because it has the potential to cause hassle which has to be fixed (diverting time and resources).
Tedious and imprecise.
The different calculations between ZZZ and FF (particularly in regards to gapping) cause discrepancies internally (including false errors about gapping and CPS) and, potentially, between colleagues.
Eliminates the need for Round times... (would be done automatically, correcting mistakes).
Convolutes Conventions.
It might seem controversial to those long used to editing in milliseconds (here and in other applications), but I think a move towards FF-only is inevitable and would be a positive one: encouraging uptake by professionals and enabling higher-quality output from others in training (minimising the learning curve; encouraging better practices, etc.).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I propose that ZZZ mode (i.e. milliseconds) be removed from Tero Subtitler. [Note: users would, of course, still be able to import and export millisecond-based formats (SubRip; WebVTT, etc).]
Millisecond-based formats are historic, accessible, frame-agnostic, and supported by most media players, hence enthusiasts have tended to use them. Until the advent of TTML and derivative formats (containing support for frames and/or milliseconds), frame-based formats tended to be the preserve of studios (e.g. Spruce Technologies/DVD Studio Pro).
However, videos (which we typically synchronise to) are naturally frame-based (or indeed interlaced), as are video editors, so I believe the GUI of Tero Subtitler should only be frame-based, following in the footsteps of other subtitling solutions that tend to be favoured by high-end users/production environments (Annotation Edit, CaptionMaker, Cavena, EZTitles, Fab Subtitler, Ooona, SoftNI, Spot, Subtitle Horse, SubtitleNEXT, and Wincaps).
Ultimately, millisecond-based formats are intended for delivery; and unless I miss something, I cannot see an advantage in editing the numbers of milliseconds directly (i.e. without the frame infrastructure), so I think there should be a general discouragement of this in software because it has the potential to cause hassle which has to be fixed (diverting time and resources).
Round times...
(would be done automatically, correcting mistakes).It might seem controversial to those long used to editing in milliseconds (here and in other applications), but I think a move towards FF-only is inevitable and would be a positive one: encouraging uptake by professionals and enabling higher-quality output from others in training (minimising the learning curve; encouraging better practices, etc.).
Beta Was this translation helpful? Give feedback.
All reactions