-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clock values #40
Comments
Agree we should formalize what we allow as clock values. I had, for now, punted on that, hence the Media Overlays reference. I think though that conceptually we are a valid subset of SMIL, which says "If no metric specifier is given, then a default of "npt=" is presumed.". I wonder if it would be beneficial to leave this unrestricted and accept (1) ? Since SyncMedia supports video, there might be some content creators who would want to use SMPTE frame-level references, whereas we didn't have to accommodate this in Media Overlays. |
Ah! I did not realize this (I am not really an expert in SMIL in spite of the fact that I still belong, formally, to the CWI department that has many of the SMIL editors on board:-). But sounds then good.
I cannot really comment on that, not being an expert on using these... |
At the moment, the definition of
clipBegin
andclipEnd
refer to §B which lists a number of examples.However...
clipBegin
andclipEnd
are not prefixed assync
, which means that these are the SMIL attributes as defined in the SMIL Spec forclipBegin
andclipEnd
, respectively. In SMIL, the value of these attributes refer to SMPTE or NPT and there is a "metric specifier" as part of the value. Looking at the examples in the SMIL spec, we have things likeclipBegin="smpte=10:12:33"
orclipBegin="npt=123.45s"
.I am not an expert in clock values, but there are questions here:
clipBegin
andclipEnd
as clock values.If the choice is (2) (which sounds find to me) then what we have is not the SMIL attribute anymore; we should not create an incompatibility (see also my comment in #35). Which would mean, in practice, to put both those attributes into the
sync
namespace.The text was updated successfully, but these errors were encountered: