(01-10-2011, 12:32 PM)NaturalViolence Wrote: [ -> ]The problem does not exist in 2.0? And are you using jit dynarec?
Disabling Jit Dynarec remains the same.
I will test the 2.0 and see if it happens.
In the dolphin 2.0,the music stops too.
Ok then it's not a regression. This thread is for regressions only, not general problems.
(01-11-2011, 04:12 AM)NaturalViolence Wrote: [ -> ]Ok then it's not a regression. This thread is for regressions only, not general problems.
Yeah, I'm sorry if I put it in the wrong place, but "told" that the LLE was emulating 100% sound in every game, from within the r6569.
I think that I misunderstood.
I know of an "issue" with DSP,This is fixed in older revs(last is I think 4638)
.
http://code.google.com/p/dolphin-emu/issues/detail?id=2190
And it seems the problem happens also with LLE.
I tested RE Darkside, and LLE has the same problem of HLE.
I've just noticed that in RE4, all music stops after a few minutes in the LLE, if this is a core issue,, when fixed,i hope, it will work for both (HLE and LLE).
This thread is for things that were broken between 5350 (2.0) and current revisions.
NaturalViolence: just a great project for making dolphin perfect
But it seems also that we have to make it as simple and user-friendly as possible for the testers. So my idea:
What about a "separating system" of the main source code part of Dolphin (like the kernel system), between which the user can switch? So there is one folder with the different R-versions (easily addable after download), which can be changed per drop-down list.
Of course that wouldn't be easy, but uprade the possibility of testing enormous - wouldn't it!?
.... is that in some way realistic to implement?
I don't even get what you mean lol
Okay, new try:
Imagine you have your Dolphin started. But you won't see a SVN build number in the window top, because it's a universal version now. The only place where you can read a SVN build number is in the new drop-down list - and there you can even find every damn Dolphin version from which you put the "kernel system code" in your "unvisersal-build-folder".
Now an idea from what I mean?
I think you are suggesting that a revision selection feature be added to the Dolphin menu. I'm not sure how difficult this would be for the developers to do, but wouldn't it be just as easy to have a Dolphin folder on your computer with all of the different revisions you've downloaded inside of it?
This thread is a great way to let the developers know of a problem with a new revision. I use Ubuntu, and get new revisions of Dolphin through the Glennric PPA. I don't have that many games yet, but if any of them stop working properly after an update, I'll post about it here.
Yes, that's what I mean. The pro of this "feature" is that - in contrast of the way you told (and which seems to be the only option for testing like NaturalViolence appeal for with this thread) - you don't have to synchronize configs and save data every time you test the game with another revision.