FRC Video Splitter (Beta)

[Alex_Miller]

Originally Posted by Ty Tremblay

This is a tough call. You want to show the final score, but sometimes there's that 5-10 minute delay while the refs talk confer. You could cut that out, but that's a lot of manual labor and would be a great target for automation.

Yes, cutting out the time when the refs/scorekeepers are doing their thing would be better. You could then automate it by saying match start = 10 seconds before noise, match end =2 minutes after noise (or whatever the correct timings are) and then if the difference between that and the scoreboard screen is larger than 20 seconds or so flag it for manual review or even automate it more to delete that time inbetween...

[cbale2000]

So I've finally had some time to play around with this and I must say I'm very impressed with the speed and simplicity of using this program. I'm even more happy (and a bit surprised) that it's compatible with .flv files (the native output of our stream software).


One idea on the whole scoreboard discussion; can ffmpeg merge video clips? If it can, you could just add another (optional) timestamp column to the match list for scoreboard appearance times, then take like a 10 second video clip (or for that matter just a still image would work) from that point and tack it on to the end of the match video.

Just a thought.

[artdutra04]

Originally Posted by cbale2000

One idea on the whole scoreboard discussion; can ffmpeg merge video clips? If it can, you could just add another (optional) timestamp column to the match list for scoreboard appearance times, then take like a 10 second video clip (or for that matter just a still image would work) from that point and tack it on to the end of the match video.

Just a thought.

Instead of getting crazy with sound or video recognition you could add in FRC or TBA API calls to get the match score, then generate a PNG or JPG image with all the info, then append that to the end of the match video as a still image slide for a few seconds.

[plnyyanks]

Originally Posted by artdutra04

Instead of getting crazy with sound or video recognition you could add in FRC or TBA API calls to get the match score, then generate a PNG or JPG image with all the info, then append that to the end of the match video as a still image slide for a few seconds.

This is a pretty great idea. The FRC API includes actual match start time in its Results endpoint (we'll add it into TBA if this ever happens).

I bet you could manually sync the video with the actual times by entering them both for the first match, then have a script calculate the rest of match start times using the API, then cut out the next ~2:30.

This actually seems really feasible. If I get the chance today, I'll try and integrate that into my python scripts

[Ty Tremblay]

Originally Posted by plnyyanks

This is a pretty great idea. The FRC API includes actual match start time in its Results endpoint (we'll add it into TBA if this ever happens).

I bet you could manually sync the video with the actual times by entering them both for the first match, then have a script calculate the rest of match start times using the API, then cut out the next ~2:30.

This actually seems really feasible. If I get the chance today, I'll try and integrate that into my python scripts

Is autoStartTime accurate to seconds?

[plnyyanks]

Originally Posted by Ty Tremblay

Is autoStartTime accurate to seconds?

And more!

➜  phil@fedora ~ frc-api https://frc-api.usfirst.org/api/v1.0/matches/2015/onto2\?tournamentLevel\=qual\&matchNumber\=1
{"Matches":[{"autoStartTime":"2015-03-06T04:19:49.573","description":"Qualification 1","level":"Qualification","matchNumber":1,"scoreRedFinal":63,"scoreRedFoul":0,"scoreRedAuto":6,"scoreBlueFinal":122,"scoreBlueFoul":0,"scoreBlueAuto":6,"Teams":[{"teamNumber":3949,"station":"Red1","dq":false},{"teamNumber":4001,"station":"Red2","dq":false},{"teamNumber":3360,"station":"Red3","dq":false},{"teamNumber":5580,"station":"Blue1","dq":false},{"teamNumber":4069,"station":"Blue2","dq":false},{"teamNumber":1114,"station":"Blue3","dq":false}]}]}%

[MikeE]

Originally Posted by plnyyanks

And more!

"autoStartTime":"2015-03-06T04:19:49.573"

+1 for the new API

It also looks like it was a very early start for our friends in Canada.

[Eugene Fang]

Originally Posted by MikeE

+1 for the new API

It also looks like it was a very early start for our friends in Canada.

Looking at the start times, they all seem pretty off.
For example 2015CAMA's QF 1 has a start time of "2015-03-08T09:25:33.04" which doesn't make sense in local time (Pacific) or UTC.

[Ty Tremblay]

Originally Posted by Eugene Fang

Looking at the start times, they all seem pretty off.
For example 2015CAMA's QF 1 has a start time of "2015-03-08T09:25:33.04" which doesn't make sense in local time (Pacific) or UTC.

I guess it wouldn't really matter for this application, all we really care about is the time span between matches.

[Eugene Fang]

Originally Posted by Ty Tremblay

I guess it wouldn't really matter for this application, all we really care about is the time span between matches.

Ah, you are correct.

[MikeE]

Originally Posted by Ty Tremblay

I guess it wouldn't really matter for this application, all we really care about is the time span between matches.

Correct. It's only the autoStartTime deltas that matter for this application, but it would be comforting to know the source of the time reference. I'd have expected it was a timestamp from the FMS server, but that's usually set to event local time.

[plnyyanks]

I wrote up a quick script that will hit the FMS API for an event of your choosing an make a CSV file of {tbaMatchKey, autoStartTime} for use elsewhere.

You need to have your API secrets in a file to be read

https://github.com/phil-lopreiato/ma...timing-data.py

[cbale2000]

The only potential issue I see with relying on the API is that not every event will have API data (IE, most off-season events).

[Eugene Fang]

Originally Posted by Ty Tremblay

Is autoStartTime accurate to seconds?

Precise, yes. Accurate, who knows.