Bug #744
create timestamps are wrong
| Status: | Resolved | Start date: | 12/02/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | J. Moringen | % Done: | 100% | |
| Category: | - | |||
| Target version: | - |
Description
For the 0.5 branch they are of by 3 missing zeros... Did I miss a commit while merging that back to the branch?
Associated revisions
refs #744
- src/gst_rsb_sink_base.cpp: handle integers representing microsecond
time more carefully with respect to overflows; there may have been a
problem on 32-bit systems
History
#1 Updated by J. Moringen over 12 years ago
- Status changed from New to Feedback
Which element (i.e. rsbaudiosink, rsbvideosink, ...) creates the incorrect timestamps? Where can these be observed? In the GStreamer pipeline or in RSB events? Please provide additional information. If possible, include a recipe for reproducing the observed problem.
#2 Updated by J. Wienke over 12 years ago
rsbvideosink was the problem running on a Nao with the new SDK 1.12. I just tried to reproduce the problem on my local machine and wasn't successful. One difference I see is that Nao is a 32 bit system. Could this problem be a result of an overflow while handling with the quite high microseconds numbers?
#3 Updated by J. Wienke over 12 years ago
I could observe the wrong timestamps in the RSB logger.
#4 Updated by J. Moringen over 12 years ago
Any new insights for this issue? Supposing the problem was fixed by r52, do we have to backport the fix to the 0.5 branch?
#5 Updated by J. Wienke over 12 years ago
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
Looks fixed. Right now we used trunk. No idea if it is worth backporting this?
#6 Updated by J. Moringen over 12 years ago
Probably not, if you use trunk anyway.
#7 Updated by S. Wrede about 12 years ago
- Target version deleted (
0.5)