Develop span command #3
Conversation
…ameters in addition to the default parameter list. Those two are a starting and ending point for the playback just like KinectStudio has.
…ommand. * Also to avoid problems of relative vs absolute paths when it comes to file paths, added conversions to FileInfo to any variable that resembles filePath, prior to giving it to the function that will consume it.
|
A neat addition to this might be a span that also takes Metadata entries which are of type TimeSpan, saved on the clip by KinectStudio manipulation. Easier to use in automated testing to store and also debug metadata keys instead of TimeSpan strings. |
* Updated help with the new commands as well as usage examples.
…fies the file to be used and only trough the filePath can we query properly.
|
Added support for playback of time portion given Metadata keys that correspond to TimeSpan values, saved on the recording itself. For now it only works with Personal Metadata. where SomeEdgeCaseStart and SomeEdgeCaseEnd correspond to metadata keys attached to the recording(Personal Metadata) when opened for Edit in KinectStudio , choosing value type to be TimeSpan and entering the values given by the time region anchors above the timeline. PS: Renamed the assembly to KSUtilExtended to avoid conflicts when saving directories into the PATH system variable for usage without the full path of the application. Was isolated in one commit so reversal is very easy. |
…tart/End points , therefore the recorded ended immediately.
A new command that provides a way to playback a portion of a file akin to the way KinectStudio provides.
Starting and Ending points are TimeSpans so we have to provide the string format of the TimeSpan that KinectStudio displays when hovering on top of the equivalent handles.