[Ty Tremblay]

Originally Posted by cbale2000

I'm loving version 2, much easier to use and the data pull feature actually works correctly. Honestly I wish I had this a few weeks ago when I ran the stream for our local district, it would have saved us a lot of time.

A few suggestions:

• It would be nice if there was an option to add a fixed amount of time to the end of a match, since it seems the post result time does not always sync with when the scores actually appear.
• The current system doesn't appear to handle multiple source files very well (for when recording software automatically breaks up recordings into like 4gb parts). It would be great if there was a way to have multiple sources or to have the splitter recognize the length of the source file and prompt for the next file when it gets to the end of the source instead of just looping back to the beginning and generating incorrect match videos.
• Not sure if it's a limitation of the splitter or how the FIRST API is utilized at events, but it would be great to have more support for off-season competitions.

• Great idea, I've added a setting for this.
• The current workflow for multiple source files is to add your first source, include only the matches on that source, split the videos, and then repeat for subsequent sources. When you're done, include all videos before uploading to YouTube.
• I think Emile answered this well.

Originally Posted by JohnFogarty

I like this application quite a bit.

I did notice a problem with the synchronization from the TBA match times to the actual competition video. It didn't work for me at all with the GADAL event.

I tried inputting the start time in the video of the first match I wanted and then only included matches that I wanted the program to spit from the main video file. 5632's matches were the only ones I was interested in spitting from the video file and I got wildly wrong generated time stamps.

Everything worked great if I manually input the match start time-stamp.

This wasn't one of the intended use cases for Splitter when it was conceived, but it shouldn't be too hard to implement. I'll work on this for the next release.