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
Depending on how someone is skimming the transcript, it can be more useful for speech elements to have either the clock time or the relative timecode in a recording.
Could we add a display format selector for choosing absolute or relative?
This would seem to require:
Allowing something like an optional recordingStartTime attribute to each debateSection element.
If a debateSection has this attribute, then show a dropdown on the end-user view page, allowing preference for absolute clocktime vs relative timecode
For debateSections with recordingStartTime, use preferred selection, falling back to absolute if a section has no recordingStartTime. (Perhaps add a little tooltip question mark on fallback to explain to end-user?)
For this to work: Is there a section-level AN attribute in the spec that corresponds to the absolute time that the event (ie. debateSection) started?* If not, could we supplement this?
Possible caveats:
If the recording is not real-time (but instead has cuts), and the adminstrator doesn't understand the above behaviour, then the display of a timecode might be misleading. It would look like a video timecode, but it wouldn't align with any recording timecodes after the first cut.
Thoughts on whether this is a worthwhile train of discussion? As it stands, our workaround will be to try to put a timestamp in the corner of our livestreams, so they can be matched with SayIt transcripts. But for existing videos or third-party videos where we can't realistically get them to add timestamp watermarking, all users will have is the YouTube timecode.
* (I'll admit that I feel like I don't understand how they've documented the spec, because I don't even see startTime/endTime in the spec I can find...!)
The text was updated successfully, but these errors were encountered:
Depending on how someone is skimming the transcript, it can be more useful for speech elements to have either the clock time or the relative timecode in a recording.
Could we add a display format selector for choosing absolute or relative?
This would seem to require:
recordingStartTime
attribute to eachdebateSection
element.debateSection
has this attribute, then show a dropdown on the end-user view page, allowing preference for absolute clocktime vs relative timecodedebateSection
s withrecordingStartTime
, use preferred selection, falling back to absolute if a section has norecordingStartTime
. (Perhaps add a little tooltip question mark on fallback to explain to end-user?)For this to work: Is there a section-level AN attribute in the spec that corresponds to the absolute time that the event (ie.
debateSection
) started?* If not, could we supplement this?Possible caveats:
Thoughts on whether this is a worthwhile train of discussion? As it stands, our workaround will be to try to put a timestamp in the corner of our livestreams, so they can be matched with SayIt transcripts. But for existing videos or third-party videos where we can't realistically get them to add timestamp watermarking, all users will have is the YouTube timecode.
* (I'll admit that I feel like I don't understand how they've documented the spec, because I don't even see startTime/endTime in the spec I can find...!)
The text was updated successfully, but these errors were encountered: