WinUAE 2.3.0 beta series (was 2.2.1)

[Toni Wilen]

winuae.zip now reverts previous audio.device hack (protracker issue)

[thomas]

Originally Posted by Toni Wilen

You should already know that problems that obviously does not happen here will get automatic "works fine here" reply without logs.

Still the same with new winuae.zip.

[Toni Wilen]

Originally Posted by thomas

Still the same with new winuae.zip.

Of course because it can't cause your problem, another reason why I wanted logs

You really sure it is b5? Does older version still work? Because there are no changes in that part of sound code at all.

[thomas]

Ok, the problem is caused by ASUS' power saving feature. Without JIT it is so slow that even Workbench games are not playable.

But there is definitely a difference between b4 and b5. With b4 sound is ok even if the CPU is slowed down but with b5 it crackles sooner or later. Seems like the sound buffer cannot be emptied fast enough. Sound LED quickly goes from 0 to -99 when sound starts. When sound ends the LED goes off. When a new sound starts, LED again starts at 0 and goes down to -99 quickly.

All that does not happen in b4, there sound LED stays between 0 and -10.

[Toni Wilen]

Originally Posted by thomas

Ok, the problem is caused by ASUS' power saving feature. Without JIT it is so slow that even Workbench games are not playable.

But there is definitely a difference between b4 and b5. With b4 sound is ok even if the CPU is slowed down but with b5 it crackles sooner or later. Seems like the sound buffer cannot be emptied fast enough. Sound LED quickly goes from 0 to -99 when sound starts. When sound ends the LED goes off. When a new sound starts, LED again starts at 0 and goes down to -99 quickly.

All that does not happen in b4, there sound LED stays between 0 and -10.

Does it happen in all modes? Even when using A500 quickstart? Same if you disable sound automatic switching? (I still can't find anything in b5 that can cause this kind of problems)

[Toni Wilen]

Of course I found one issue after replying.. Does http://www.winuae.net/files/b/winuae.zip work?

(but you should have reported increased CPU% value instead of SND% because problem had nothing to do with sound.. If this fixes it)

[thomas]

Originally Posted by Toni Wilen

Of course I found one issue after replying.. Does http://www.winuae.net/files/b/winuae.zip work?

It writes a minidump as soon as I try to insert a disk into DF0 on the quickstart panel (see attachment).

(but you should have reported increased CPU% value instead of SND% because problem had nothing to do with sound.. If this fixes it)

With my 3.1 config CPU% was not remarkably high. Now that you asked for an A500 quickstart config, here CPU% jumps to 115% and SND to -165% when crackling occurs. This happens when graphics changes. Tried the Music AmigaBasic demo from the Extras 1.3 disk. Everytime the lines are drawn, the sound crackles. If nothing is drawn, sound is ok but sound LED is a -150% and CPU is at 90%.

[thomas]

Originally Posted by thomas

It writes a minidump as soon as I try to insert a disk into DF0 on the quickstart panel (see attachment).

But yes, it fixes the sound problem.

[Toni Wilen]

Originally Posted by thomas

It writes a minidump as soon as I try to insert a disk into DF0 on the quickstart panel (see attachment).

I noticed you used .ini in your previous log. Does it work if you do not use ini? (there have been some changes in ini handling.., attach the ini it only crashes with ini enabled)

[thomas]

It does not happen without ini file, but it does also happen with an empty ini file.

BTW, the first rom scan on a virgin registry or empty ini file always fails. Although it displays the progress window, it comes up with "one of the following ROMs is required". However, if I then go to the paths page and just click on Rescan without changing any path, all Amiga models are available and if I run WinUAE next time, it does no longer issue the "one of..." requester.

[Toni Wilen]

I can't duplicate.. Create new empty ini, start winuae, exit it and attach winuaebootlog.txt.

EDIT: not finding roms in ini mode is not a bug, I decided that ini by default should mean: do not use anything outside of winuae, default to relative paths. (but it shouldn't "autofix" when run second time either..) EDIT3: AF rom paths are always detected if "rom" or "roms" is not found under winuae path.

EDIT2: I think I found something..

[Toni Wilen]

winuae.zip updated again, fixes possible startup crash, still no idea if it fixes later crashes.. EDIT: disk history crash fixed now (old unicode conversion bug, didn't cause problems until now..)

[thomas]

Originally Posted by Toni Wilen

I can't duplicate.. Create new empty ini, start winuae, exit it and attach winuaebootlog.txt.

EDIT: not finding roms in ini mode is not a bug, I decided that ini by default should mean: do not use anything outside of winuae, default to relative paths. (but it shouldn't "autofix" when run second time either..) EDIT3: AF rom paths are always detected if "rom" or "roms" is not found under winuae path.

Well,

1. paths panel should reflect whichever paths are defaulted to
2. the defaults shown in paths panel should be used for the initial ROM scan.

Currently it looks like you are first scanning for ROMs and then setting default paths.

3. the "one of..." requester comes up when runing without .ini file for the first time, too. Also the paths panel shows the right paths and a manual ROM scan fixes the "one of..." thing without changing any path. Exactly the same behaviour as with .ini file.

winuae.zip updated again, fixes possible startup crash, still no idea if it fixes later crashes.. EDIT: disk history crash fixed now (old unicode conversion bug, didn't cause problems until now..)

Yes, the floppy panel crash is fixed now.

[andreas]

Originally Posted by thomas

Tried the Music AmigaBasic demo from the Extras 1.3 disk.

Really a sensible testing object. No, not (!) ironic , since I used this frequently back in 0.8.8 / 0.8.14 times.

Everytime the lines are drawn, the sound crackles. If nothing is drawn, sound is ok but sound LED is a -150% and CPU is at 90%.

Maybe it is not uninteresting if I mention that this very music demo always required 100% accurate sound emulation (at least) in older versions.
"Emulated" alone would never do, since it would cause anything from showing audio errors, getting audio/gfx sync screwed up - up to breaking off prematurely (from time to time).
Though we're (admittedly) 100 miles away from these ancient builds now, the executed Amiga code always stays the same, hence I'd say you never know...

[Toni Wilen]

Originally Posted by andreas

Really a very good testing object. No, not ironic , since I used this frequently back in 0.8.8 / 0.8.14 times.



Maybe it is not uninteresting if I mention that this very music demo always required 100% accurate sound emulation in older versions.
"Emulated" alone would never do, since it would cause audio errors as well as audio/gfx sync flaws, up to breaking off prematurely (rare). Admittedly, we're 100 miles away from these ancient builds now, but since the executed Amiga code always stays the same, I'd say you never know...

Maybe you should have read all following posts because this had nothing to do with sound and is already solved.

[Toni Wilen]

Originally Posted by thomas

Well,

1. paths panel should reflect whichever paths are defaulted to

Ther has always been "hidden" default rom paths that are always used when scanning (+ the one listed in paths)

2. the defaults shown in paths panel should be used for the initial ROM scan.

It is. (plus "hidden" ones) Note that new AF2010 ROMs seems to have some key issues or something when winuae is run stand-alone.

[thomas]

Ther has always been "hidden" default rom paths that are always used when scanning (+ the one listed in paths)

But the one listed in paths is *not* used for the initial scan.

It is. (plus "hidden" ones)

Then please explain why the initial ROM scan does not find KS 1.3 ROMs while they definitely are in the path shown in paths panel.

Please understand that I do not change anything. I just run WinUAE, watch the scan, get the "one of..." requester, click on Ok, click on Paths, click on Rescan. From my point of view this rescan should do exactly the same as the initial scan, because I did not change the default path. But the second scan finds the ROMs while the first one doesn't.

Note that new AF2010 ROMs seems to have some key issues or something when winuae is run stand-alone.

I use ROM files copied from the AF2008 CD. It's not an installed AF.

[thomas]

I use ROM files copied from the AF2008 CD. It's not an installed AF.

But you are right, it seems to be some kind of "key issue". If I copy unencrypted ROMs to the same directory, it works correctly.

[bagpipes]

Hi Toni. I have problem with this game in new betas. The game hangs up after versus screen (before fight). In WinUAE 2.2.0 game runs correctly.
Here is my configs (run in quickstart mode):

[andreas]

Originally Posted by Toni Wilen

Maybe you should have read all following posts because this had nothing to do with sound and is already solved.

Yes! Missed that in this mess! Sorry.