Xuggle 5.4 is available

[hyakki]

Could someone check if the 64-bit stability issues are now fixed in a newer Xuggle release?
The old Xuggle has problems with latest sceMp3 implementation...

I tested it the other day and it works for me, but then again it has always worked for me, I could never reproduce the crash problem.
I wonder if committing a build with it would just be the best way to test since alot of users would try it.
(or I could probably throw a jpcsp together /w xuggle 5.4 and u/l it to mediafire for people to test)

[legend80]

Could someone check if the 64-bit stability issues are now fixed in a newer Xuggle release?
The old Xuggle has problems with latest sceMp3 implementation...

I tested it the other day and it works for me, but then again it has always worked for me, I could never reproduce the crash problem.
I wonder if committing a build with it would just be the best way to test since alot of users would try it.
(or I could probably throw a jpcsp together /w xuggle 5.4 and u/l it to mediafire for people to test)

I can check it out if a build is provided.

[hyakki]

Could someone check if the 64-bit stability issues are now fixed in a newer Xuggle release?
The old Xuggle has problems with latest sceMp3 implementation...

I can check it out if a build is provided.

build based off vanilla r2793
http://www.mediafire.com/download.php?ca5ia45vn808qh4

( you probably want to extract to a new folder since its for testing, and not overwrite your current build )
Just to confirm I tested a few in-game videos and it's working on my end.

[nash67]

just tested the version hyakki built

all these games that have problems with the normal 64 bit build
Harry Potter and the Order of the Phoenix
Infected
Jungle Party
OMG-Z
Ronnie O'Sullivan's Snooker
Speedball 2 - Evolution
work on this version with Xuggle 5.4

[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..

[digiadventures]

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 ?

[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.

[digiadventures]

Any type of video ??
I have i5 2400 I will test my games and report back

---

Well I tested about ten games and two of them do crash : tactics ogre and crimson gem saga.
This issue doesnt seem related to video playback,but to specific games. I have tested each game a couple of times,and only those 2 crashed.
Also,they crash when there is no video to be played-for example when trying to load a game

[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.

Any type of video ??
I have i5 2400 I will test my games and report back

---

Well I tested about ten games and two of them do crash : tactics ogre and crimson gem saga.
This issue doesnt seem related to video playback,but to specific games. I have tested each game a couple of times,and only those 2 crashed.
Also,they crash when there is no video to be played-for example when trying to load a game

Thanks for testing.
Xuggle is used for the media engine, so video playback is the simplest way to test, but xuggle does also process certain types of audio too like normal at3, mp3 ..etc, so its possible crash on other areas.
Does the crimson gem saga and tatic ogre crash happen with the normal builds? I tried to load Crimson gem saga and tactic ogre in r2806 and but both loaded ok on my end with xuggle 5, so I'm curious if it's xuggle 5 or just some other bug. (since the 10 other games worked ok )

btw:
when you said crash do you mean the 'windows error reporting' kind of crashes where the windows dialog pops up ?
for example
   
(not invalid memory or pause type errors in the emulator.)

[legend80]

Could someone check if the 64-bit stability issues are now fixed in a newer Xuggle release?
The old Xuggle has problems with latest sceMp3 implementation...

I can check it out if a build is provided.

build based off vanilla r2793
http://www.mediafire.com/download.php?ca5ia45vn808qh4

( you probably want to extract to a new folder since its for testing, and not overwrite your current build )
Just to confirm I tested a few in-game videos and it's working on my end.

Their stuff is still broken. I replaced the jar file, deleted the previous lib dir, copied one from archive and started JPCSP. It crashed on me as soon as I clicked on MegaManX in the UMD browser. The second time I had to switch between another title and MMX a couple times, but it still crashed....just as unstable as before. Sorry.