You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a great admirer of your work. I'm curious about the limitations of processing large videos with certain algorithms like POS, G, and Chrom. It seems that these algorithms might not be optimized to handle videos exceeding a certain frame count. Given that publicly available datasets often contain longer and larger videos, it's challenging to achieve accurate heart rate measurements using these methods.
PS: Could you please explain the reason behind replacing parse_video_input funt with parse_image_inputs funct and are there any other significant changes in the updated repo/library.
The text was updated successfully, but these errors were encountered:
I'm a great admirer of your work. I'm curious about the limitations of processing large videos with certain algorithms like POS, G, and Chrom. It seems that these algorithms might not be optimized to handle videos exceeding a certain frame count. Given that publicly available datasets often contain longer and larger videos, it's challenging to achieve accurate heart rate measurements using these methods.
PS: Could you please explain the reason behind replacing parse_video_input funt with parse_image_inputs funct and are there any other significant changes in the updated repo/library.
The text was updated successfully, but these errors were encountered: