-
Notifications
You must be signed in to change notification settings - Fork 5
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
Playlists validation #13
Comments
I'm ok with that, we need fps and frame length to be able to make the comparison. |
what's the difference between fps and frame length? oh, you mean the length of the video in frames? |
Yes. I can calculate frames length with a length formatted like that "01:35:58.33" with his "fps" as "25,001" for example. I can also do a validation or check in mosto as the server_playlist returned by getServerPlaylist give me this information. It will be nice to have it from Caspa, and make Mosto just check it. Is it possible? |
Forma now get it from melted
|
I've been thinking about this, and I'm not sure if it can be done. Melted gets the clip length from the XMLs, and the XMLs are built from the DB data. The bottom line is, we don't have a way to double-check this from melted. So is this issue valid? |
yep, if we need to hack melt/melted, that's not an issue for me, we already On 17 September 2013 17:06, Tomas Neme [email protected] wrote:
Niv Sardi |
DTISC I just checked, and whatever you mark as the length of the clip in the XML, the result of I just created an XML that reports that the clip out should be 35474 (len + 10) and
|
Great, so we can actually test. Niv Sardi, mobile.
|
Mosto should validate every playlist it loads against the playlists already loaded using a library defined by Caspa in order to emit warning and error messages via pub/sub.
The text was updated successfully, but these errors were encountered: