Skip to content
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

Open
jmrunge opened this issue Mar 26, 2013 · 8 comments
Open

Playlists validation #13

jmrunge opened this issue Mar 26, 2013 · 8 comments
Assignees
Milestone

Comments

@jmrunge
Copy link
Member

jmrunge commented Mar 26, 2013

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.

@ghost ghost assigned fabriciocosta Mar 28, 2013
@fabriciocosta
Copy link
Contributor

I'm ok with that, we need fps and frame length to be able to make the comparison.

@Lacrymology
Copy link
Contributor

what's the difference between fps and frame length?

oh, you mean the length of the video in frames?

@fabriciocosta
Copy link
Contributor

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?

@xaiki
Copy link
Member

xaiki commented Apr 24, 2013

Forma now get it from melted
On Apr 23, 2013 4:01 PM, "Fabricio Costa Alisedo" [email protected]
wrote:

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?


Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-16879123
.

@Lacrymology
Copy link
Contributor

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?

@xaiki
Copy link
Member

xaiki commented Sep 17, 2013

yep, if we need to hack melt/melted, that's not an issue for me, we already
know that it makes heavy processing on load (cpu).

On 17 September 2013 17:06, Tomas Neme [email protected] wrote:

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?


Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-24617921
.

Niv Sardi

@Lacrymology
Copy link
Contributor

DTISC

I just checked, and whatever you mark as the length of the clip in the XML, the result of list u0 says the actual length of the clip

I just created an XML that reports that the clip out should be 35474 (len + 10) and list u0 reports

0 "/test/foooo.xml" 0 35464 35265 35265 25.00

@xaiki
Copy link
Member

xaiki commented Sep 18, 2013

Great, so we can actually test.

Niv Sardi, mobile.
On Sep 17, 2013 5:53 PM, "Tomas Neme" [email protected] wrote:

DTISC

I just checked, and whatever you mark as the length of the clip in the
XML, the result of list u0 says the actual length of the clip

I just created an XML that reports that the clip out should be 35474 (len

    1. and list u0 reports

0 "/test/foooo.xml" 0 35464 35265 35265 25.00


Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-24621520
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants