Bug #756
Scheduling strategy for the video-only case produces too fast results
| Status: | Resolved | Start date: | 12/09/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | J. Moringen | % Done: | 100% | |
| Category: | - | |||
| Target version: | - |
Description
When you use a pipeline that is just configured to convert timestamped RSB video data (e.g. from Nao) to a video (file) with a constant framerate (i.e. when you use record_?.sh with just a video source), the resulting video has a much too high framerate. Or rather, the action in the video looks much to fast.
Associated revisions
Added new scheduler to allow proper scheduling for single scope case
fixes #756
fixes #756
- scripts/record_mp4.sh: use rsb-timestamp scheduler for video-only
case - scripts/record_ogv.sh: likewise
- src/gst_rsb_src_base.{h,cpp}: added rsb-timestamp scheduling
strategy
History
#1 Updated by D. Klotz over 12 years ago
For example results, you could take a look at /vol/nao/scratch/test3.ogv and test4.ogv, produced from the same data (/vol/humavips/studies/Y2_preStudy/corpus_merged/vernissage/Test8SittingComplete.tide), once with audio and once without.
#2 Updated by J. Moringen over 12 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset r55.