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
When using MMIF from the latest clams whisper app, the visualizer fails to generate VTT format because the timeUnit key used in the app is millisecond, while the timedelta class expects milliseconds.
We need to "normalize" the timeunit key names, and this can be done using SDK helper. However, current implementation of the normalization scheme is using singular millisecond (unfirtunately) and wonder what's the best way to address this bug.
Bug Description
When using MMIF from the latest clams whisper app, the visualizer fails to generate VTT format because the timeUnit key used in the app is
millisecond
, while thetimedelta
class expectsmilliseconds
.We need to "normalize" the timeunit key names, and this can be done using SDK helper. However, current implementation of the normalization scheme is using singular
millisecond
(unfirtunately) and wonder what's the best way to address this bug.https://github.com/clamsproject/mmif-python/blob/262015bca12bf82a49c50923946e392f8e66d710/mmif/utils/timeunit_helper.py#L5-L22
Reproduction steps
Input whisper output MMIF to the mmif-viz
Expected behavior
No response
Log output
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: