Wrong timestamps in IVideoPicture

67 views
Skip to first unread message

Wim Deblauwe

unread,
Jul 6, 2010, 5:24:59 AM7/6/10
to xuggler-users
Hi,

I am using

IContainer#readNextPacket(packet)

and most of the time this is ok. However, quite frequently the
timestamp in the IVideoPicture gets a completely wrong value.

This is a correct sequence:


2010-07-06 11:09:24,358 [FeedService-1] TRACE RTSPFeed Created new
frame: com.xuggle.xuggler.IVideoPicture@2004634504[pixel
type:YUV420P;width:352;height:288;time
stamp:-9223372036854775808;complete:false;size:152064;key:true;time
base:1/1000000;]
2010-07-06 11:09:24,362 [FeedService-1] TRACE RTSPFeed Decoding video
with offset 0: com.xuggle.xuggler.IPacket@2010456304[complete:true;dts:
79200;pts:79200;size:3629;key:false;flags:0;stream index:0;duration:
3600;position:-1;time base:1/90000;]
2010-07-06 11:09:24,363 [FeedService-1] TRACE RTSPFeed Decoding video
done. Frame: com.xuggle.xuggler.IVideoPicture@2004634504[pixel
type:YUV420P;width:352;height:288;time stamp:880000;complete:true;size:
152064;key:false;time base:1/1000000;]
2010-07-06 11:09:24,372 [ProcessorService-1] TRACE RTSPProcessor
[415e6d7bff179ad8e663c6a2b21c26d9_232_202_512] Writing event to output
stream: Video - ts: 680 length: 513

This is an incorrect sequence:

2010-07-06 11:09:24,398 [FeedService-1] TRACE RTSPFeed Created new
frame: com.xuggle.xuggler.IVideoPicture@1984380216[pixel
type:YUV420P;width:352;height:288;time
stamp:-9223372036854775808;complete:false;size:152064;key:true;time
base:1/1000000;]
2010-07-06 11:09:24,399 [FeedService-1] TRACE RTSPFeed Decoding video
with offset 0: com.xuggle.xuggler.IPacket@2017241216[complete:true;dts:
115057310750820;pts:115057310750820;size:3631;key:false;flags:0;stream
index:0;duration:3600;position:-1;time base:1/90000;]
2010-07-06 11:09:24,400 [FeedService-1] TRACE RTSPFeed Decoding video
done. Frame: com.xuggle.xuggler.IVideoPicture@1984380216[pixel
type:YUV420P;width:352;height:288;time stamp:
1278414563898000;complete:true;size:152064;key:false;time base:
1/1000000;]
2010-07-06 11:09:24,491 [ProcessorService-1] TRACE RTSPProcessor
[415e6d7bff179ad8e663c6a2b21c26d9_232_202_512] Writing event to output
stream: Video - ts: 661793250 length: 3617

Notice that the dts and pts values in the IPacket are also very high
in the incorrect sequence. What are those dts and pts values? Any clue
on what might be wrong?

regards,

Wim


Wim Deblauwe

unread,
Jan 24, 2011, 10:41:04 AM1/24/11
to xuggle...@googlegroups.com
Anybody who has a clue? I updated to use Xuggle 4.0 and it seems to be more frequent. This is some output with Xuggle 4.0:

2011-01-24 16:35:07,947 [ProcessorService-5] [INFO ] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Skipping blank notify message
2011-01-24 16:35:08,452 [ProcessorService-5] [INFO ] Processor [75a6be3e61d421a0c77149e7db212893_505_407_512] Video frame dimensions - feed: 352x288 output: 505x407
2011-01-24 16:35:08,453 [ProcessorService-5] [DEBUG] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Running
2011-01-24 16:35:08,453 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Key frame: true
2011-01-24 16:35:08,459 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Writing event to output stream: Video - ts: 0 length: 26210
2011-01-24 16:35:08,530 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Queue size 2
2011-01-24 16:35:08,530 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Key frame: true
2011-01-24 16:35:08,536 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Writing event to output stream: Video - ts: 40 length: 2108
2011-01-24 16:35:08,536 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Processor stream has 1 consumers
2011-01-24 16:35:08,536 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Queue size 1
2011-01-24 16:35:08,537 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Key frame: true
2011-01-24 16:35:08,542 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Writing event to output stream: Video - ts: 80 length: 1668
2011-01-24 16:35:08,594 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Queue size 1
2011-01-24 16:35:08,594 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Key frame: true
2011-01-24 16:35:08,599 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Writing event to output stream: Video - ts: 120 length: 809
2011-01-24 16:35:08,652 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Queue size 2
2011-01-24 16:35:08,652 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Key frame: true
2011-01-24 16:35:08,657 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Writing event to output stream: Video - ts: 160 length: 684
2011-01-24 16:35:08,658 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Processor stream has 1 consumers
2011-01-24 16:35:08,658 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Queue size 1
2011-01-24 16:35:08,658 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Key frame: true
2011-01-24 16:35:08,663 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Writing event to output stream: Video - ts: 200 length: 613
2011-01-24 16:35:08,715 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Queue size 1
2011-01-24 16:35:08,715 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Key frame: true
2011-01-24 16:35:08,720 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Writing event to output stream: Video - ts: 240 length: 557
2011-01-24 16:35:08,773 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Queue size 2
2011-01-24 16:35:08,773 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Key frame: true
2011-01-24 16:35:08,778 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Writing event to output stream: Video - ts: 280 length: 532
2011-01-24 16:35:08,779 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Processor stream has 1 consumers
2011-01-24 16:35:08,779 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Queue size 1
2011-01-24 16:35:08,779 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Key frame: true
2011-01-24 16:35:08,783 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Writing event to output stream: Video - ts: 320 length: 491
2011-01-24 16:35:08,836 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Queue size 1
2011-01-24 16:35:08,836 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Key frame: true
2011-01-24 16:35:08,841 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Writing event to output stream: Video - ts: 954267556 length: 468
2011-01-24 16:35:08,893 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Queue size 2
2011-01-24 16:35:08,893 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Key frame: true
2011-01-24 16:35:08,898 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Writing event to output stream: Video - ts: 954267596 length: 549
2011-01-24 16:35:08,899 [ProcessorService-5] [DEBUG] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Reached FPS or max awake time
2011-01-24 16:35:08,899 [ProcessorService-5] [DEBUG] RTSPProcessor Sent frames: 11  -  FPS: 10
2011-01-24 16:35:08,899 [ProcessorService-5] [DEBUG] RTSPProcessor Awake for 445.859 ms 
2011-01-24 16:35:08,899 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Queue size 1
2011-01-24 16:35:08,899 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Key frame: true
2011-01-24 16:35:08,904 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Writing event to output stream: Video - ts: 954267636 length: 716
2011-01-24 16:35:08,956 [ProcessorService-5] [TRACE] RTSPProcessor [75a6be3e61d421a0c77149e7db212893_505_407_512] Queue size 1

regards,

Wim
Reply all
Reply to author
Forward
0 new messages