What steps will reproduce the problem?
1. Try to encode H.264 with number of B-frames ("bf" property) greater than
zero
What is the expected output? What do you see instead?
This was from Xuggler 3.3, but I got the same issue on Xuggler 3.2
2009-10-26 16:44:34,771 [pool-1-thread-1] WARN org.ffmpeg - [libx264 @
0x81e38d0] MB rate (1825032704) > level limit (983040)
2009-10-26 16:44:34,783 [pool-1-thread-1] INFO org.ffmpeg - [libx264 @
0x81e38d0] using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
2009-10-26 16:44:34,806 [pool-1-thread-1] INFO org.ffmpeg - [libx264 @
0x81e38d0] profile High, level 5.1
2009-10-26 16:44:39,653 [pool-1-thread-1] ERROR org.ffmpeg - [libx264 @
0x81e38d0] error, non monotone timestamps 208542 >= 83417
Exception in thread "pool-1-thread-1" java.lang.RuntimeException: failed to
write packet:
com.xuggle.xuggler.IPacket@139316968[complete:true;dts:83417;pts:83417;size
:328;key:false;flags:0;stream index:0;duration:-1;position:-1;time
base:1/1000000;]
at
com.xuggle.mediatool.MediaWriter.writePacket(MediaWriter.java:1222)
at
com.xuggle.mediatool.MediaWriter.encodeVideo(MediaWriter.java:774)
at
com.xuggle.mediatool.MediaWriter.encodeVideo(MediaWriter.java:790)
at
com.xuggle.mediatool.MediaWriter.onVideoPicture(MediaWriter.java:1441)
at
com.xuggle.mediatool.AMediaToolMixin.onVideoPicture(AMediaToolMixin.java:16
6)
at
com.xuggle.mediatool.MediaReader.dispatchVideoPicture(MediaReader.java:610)
at
com.xuggle.mediatool.MediaReader.decodeVideo(MediaReader.java:519)
at
com.xuggle.mediatool.MediaReader.readPacket(MediaReader.java:475)
at MultiClipVideoCreator.run(MultiClipVideoCreator.java:182)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.j
ava:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
675)
at java.lang.Thread.run(Thread.java:595)
What operating system and JVM version are you using.
I'm using Ubuntu Linux 9.04 Hardy Heron LTS, with Java 1.5
Attach relevant log/output files.
Original issue reported on code.google.com by thou...@gmail.com on 26 Oct 2009 at 9:48
Original issue reported on code.google.com by
thou...@gmail.com
on 26 Oct 2009 at 9:48