webrtcsink: fix pipeline when input caps contain max-framerate
GstVideoInfo uses max-framerate to compute its fps, but this leads to issues in videorate when framerate is actually 0/1.
Fix this by stripping away max-framerate from input caps
Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
GstVideoInfo uses max-framerate to compute its fps, but this leads to issues in videorate when framerate is actually 0/1.
Fix this by stripping away max-framerate from input caps