|
VideoMatch looks for the likelihood of coherence between the sequence of pertinent image hashes obtained after preparing the comparison between video Motion vector.
● Data Source:
CranContrib
● Keywords: NoSQL, Video Motion Curve
● Alias: VideoMatch
●
0 images
|
|
Video hashes have been stored in differnt chuncks. Main chunk includes the container data. Then, a second chunk named _video.json stores the motion vector and later on, under the ev_father entry different chunks have been stored with key image hashes. Those hashes implements different pHash hashes ( DCT, MW, RD, STRADA).
● Data Source:
CranContrib
● Keywords: Video List
● Alias: VideoSearch
●
0 images
|
|
A R function allowing to ask to a REST/Json server for the video frame descriptions stored there. It will return it as a vector of strings making clear the positions inside the video for those frames.
● Data Source:
CranContrib
● Keywords: JSON, NoSQL, Video Motion Curve
● Alias: ExtractImgPos
●
0 images
|
|
For two video segments represented by their own video motion vector it is interesting to look for their matching in order to verify potential coherence between them happens.
● Data Source:
CranContrib
● Keywords: Video Motion
● Alias: VideoComparison
●
0 images
|
|
Comparison between videos by their descritors (motion curves and image hashes for transitions)
● Data Source:
CranContrib
● Keywords: package
● Alias: VideoCompare-package, VideoComparison-package
●
0 images
|
|
A R function allowing to ask to a REST/Json server for the motion vector of a video stored there. It will return it as a vector of integers.
● Data Source:
CranContrib
● Keywords: JSON, NoSQL, Video Motion Curve
● Alias: ExtractMotion
●
0 images
|
|
Each image es represented by a list of hashes (in current implementation DCT, MW, RD, STRADA) and appropriate metrics is measured, per hash, to both images.
● Data Source:
CranContrib
● Keywords: Image Hash
● Alias: VideoDistance
●
0 images
|
|
A R function allowing to ask to a REST/Json server for the video frame hashes stored there. It will return it a list with the hashes related to the requested image inside the video for those frames.
● Data Source:
CranContrib
● Keywords: Image Hash, JSON, NoSQL
● Alias: ExtractImgHash
●
0 images
|
|
Compare two videos from their names by retrieving their data from the database. A likelihood estimation will be returned, as well as basic parameters for motion matching (correlation, pos on each video and length of the matching).
● Data Source:
CranContrib
● Keywords: NoSQL, Video Likelihood
● Alias: Compare2Videos
●
0 images
|
providing 
.