05-01-2012, 07:38 PM
(05-01-2012, 03:42 AM)Itaru Wrote: Unfortunately I have confirmed that there is indeed a nasty bug in Xuggle 5.x which breaks AT3 playback. Games affected are those which use AT3 for music such as Disgaea Afternoon of Darkness and Prinny Can I Really Be a Hero since ffmpeg is used to decode those AT3 files. The title music in Patapon is also affected since it's in AT3 format, so it's not just Nippon Ichi titles. Disgaea 2 has no problems with bgm since it uses AT3+ format. AT3+ files which are decoded externally either through SonicStage or SoundForge are not affected at all.Hmm, could you post a log file while inserting the following in LogSettings.xml:
In the previous Xuggle 3.4, AT3 playback works fine. However in Xuggle 5.x, the IContainer.readNextPacket() method in Xuggle returns an error after around 8 seconds of AT3 playback. The return code is a very large negative number which Xuggle categorizes as IError.Type.ERROR_UNKNOWN. Both 32-bit and 64-bit versions are affected. I think it's a bug in the ffmpeg that is embedded in the libxuggle-5.dll file since the return code in the readNextPacket() method just returns whatever code that ffmpeg returns when it exits. Xuggle 5.2 and 5.3 also have the same problem.
Looks like we'll have to revert r2538 until the problem is hopefully fixed in the next Xuggle 5 release.
Code:
<logger name='hle.sceAtrac3plus'> <level value='debug' /> </logger>
<logger name='PacketChannel'> <level value='debug' /> </logger>
See jpcsp.connector.AtracCodec.java, Line 365.
Maybe the new one requires even more... the DEBUG logging of PacketChannel will show if Xuggle/ffmpeg tries to read more data than available at the start of an Atrac3 decoding (log of "PacketChannel: End of data").
Always include a complete log file at INFO level in your reports. Thanks! How to post a log