Xuggle 5.4 is available

[hyakki]

Has anyone else tested? I'm sure gid15 would like to know if the crash issue is still present for some users.
Another very quick way to test is on the buildbot get both the 32bit and 64bit builds (luckily the 64bit build still has the latest xuggle 5 64bit dll bundled)
1. First extract the 64bit build to the harddrive somewhere.
2. Then from the 32bit build just extract 'bin/jpcsp.jar' from the archive and replace the 64bit 'bin/jpcsp.jar' that you extracted on your hard drive (do not replace any other files), this should auto enable the use of xuggle 5 under 64bit.
3. run start-windows-amd64.bat or the launcher under 64bit and play your games like normal and check if videos are working or if you are getting any crashes.

(if you want you can also remove the these files from the lib\ directory
xuggle-xuggler-3.4,jar
xuggle-xuggler-test-3.4.jar

And from lib\windows-amd64
avcodec-52.dll
libxuggle-ferry-3.dll
libxuggle-xuggler-3.dll
libxuggle-xuggler-io-3.dll
)
this way you can be certain its relying on libxuggle-5, though in my tests its not necessary, just using the 32bit jar under 64bit seems to be enough to switch xuggle versions..

Yeah but wasn't the problem only related to few games such as megamen, 3rd birthday and kingdom hearts if I understood correctly what I read in this thread ?
Or can we test any game,does that have any sort of relavance ?

I think the problem was related to AVX instructions for people with second gen I7/5/3 processors (or so was guessed , only a few users could re-produce the error, this was the best idea we could come up with), when playing any type of video it would cause java to crash with xuggle-5.dll exception error, but people with older first gen I cpu's or other brand processors xuggle 5.4 appeared to work fine, so this is what caused jpcsp to revert to xuggle 3.4 on the 64bit builds, the bug didn't seem to effect 32bit so it got to stay in the 32bit builds.