WinUAE 2.7.0 beta series

[Dr.Venom]

I can confirm the results by Who for F17 challenge.

I'm guessing the problem is caused by the change in detection between 2.7.0b and 2.6.1 of "fake" interlace such as the Team17 logo (as that's where the buffer problem starts)..

[vagrant]

Yeh I noticed that.. the sound buffer seems unstable in general with many games/demos, not just F17 challenge. I get a maxed buffer quite often compared to 2.6.1 and earlier where it rarely happens at all. With a lot of stuff the max buffer is only temporary, but annoying.
I only used F17 as example because it has consistent extreme result

[Toni Wilen]

I think I know what happened.. Does http://www.winuae.net/files/b/winuae.zip fix the sound buffer unstability? (It may not be 100% as good as old version because this is not fully optimized build)

[Leandro Jardim]

Very good! Finally I can play "Castlevania" on 50 Mhz cycle exact with A/NES, it was a very hard thing to do before this tweak, on my computer. The emulator A/NES is very good, hope his author update it again someday. And WinUAE, its getting better everyday. Its a winner. Long live WinUAE! Hip-hip-Hurra!

Very good this A/NES!

[Mclane]

Originally Posted by Leandro Jardim

Very good! Finally I can play "Castlevania" on 50 Mhz cycle exact with A/NES,

The emulator A/NES is very good,

Very good this A/NES!

I think he likes A/NES, could be wrong

[Dr.Venom]

Originally Posted by Toni Wilen

I think I know what happened.. Does http://www.winuae.net/files/b/winuae.zip fix the sound buffer unstability? (It may not be 100% as good as old version because this is not fully optimized build)

For me it doesn't seem to make a difference when it comes to the testcase by Who. As soon as the fake interlace Team 17 logo comes up, the buffer gets unstable to the point where it stays at -90. This happens for me up to buffer setting 4. At buffer setting 5, it gets in the red, but eventually recovers.

[vagrant]

Originally Posted by Toni Wilen

I think I know what happened.. Does http://www.winuae.net/files/b/winuae.zip fix the sound buffer unstability? (It may not be 100% as good as old version because this is not fully optimized build)

Yes F17 Challenge still behaves the same.
In general the sound does seem more stable. I ran a bunch of games/demos and the buffer was steady at around 20/30 without problems. (In 2.6.1 and earlier it usually sits between 0 and 10)

Although I found a few demos where the buffer behaves the same as F17 challenge.. Captured Dreams & Tint by TBL. (Both are fine on 2.6.1)

[Toni Wilen]

http://www.winuae.net/files/b/winuae_2700b13.zip

Beta 13:

- Standard partition hardfile OFS filesystem check was broken (2.6.1)
- Adjusted sprite xpos == hpos check. (Shed Tears / Ozone scroller)
- 64-bit build didn't load portaudio dll.
- GUI window minimize button worked strangely when emulation window was open.
- Added new interlace emulation modes, first new is same as old one but display is updated every field (Old doubling updated every frame) and another that does same and also blanks every other line.
- Added separate non-laced and lace doubling modes to GUI. (Better labels needed, but there is no space)
- Sound timing calculation wasn't updated to match new long/short field/interlace display emulation timing (b1).

[FreakyDan]

Originally Posted by who

Yes F17 Challenge still behaves the same.
In general the sound does seem more stable. I ran a bunch of games/demos and the buffer was steady at around 20/30 without problems. (In 2.6.1 and earlier it usually sits between 0 and 10)

Although I found a few demos where the buffer behaves the same as F17 challenge.. Captured Dreams & Tint by TBL. (Both are fine on 2.6.1)

I cant even start Captured dreams with the latest beta if JIT is enabled.
I know for sure that have worked before.

[Toni Wilen]

Originally Posted by FreakyDan

I cant even start Captured dreams with the latest beta if JIT is enabled.
I know for sure that have worked before.

Sorry but thats totally useless "report".

Also game or demo and JIT: you are on your own, it probably is completely normal.

[Retro-Nerd]

I can't enter the Windows GUI with F12 anymore in the latest beta. It shows only the Windows mouse pointer. Have to quit then with Alt+F4. Do you need some logs?

[FreakyDan]

Originally Posted by Toni Wilen

Sorry but thats totally useless "report".

Also game or demo and JIT: you are on your own, it probably is completely normal.

For some reason my config files with jit settings had changed to indirect mode. Switching to Direct mode fixed it.

[Toni Wilen]

Originally Posted by Retro-Nerd

I can't enter the Windows GUI with F12 anymore in the latest beta. It shows only the Windows mouse pointer. Have to quit then with Alt+F4. Do you need some logs?

Logs probably won't help. Same in windowed and fullscreen? Which Windows version?

[Retro-Nerd]

Just wanted to edit my post. Yes, in fullscreen only. Windows 7.

[FreakyDan]

Originally Posted by Retro-Nerd

Just wanted to edit my post. Yes, in fullscreen only. Windowss 7.

Same here on Windows 8.1

[Toni Wilen]

Originally Posted by FreakyDan

For some reason my config files with jit settings had changed to indirect mode. Switching to Direct mode fixed it.

This shouldn't break any demos unless they only work accidentally, for example some part must have some specific CPU speed..

Originally Posted by Retro-Nerd

I can't enter the Windows GUI with F12 anymore in the latest beta. It shows only the Windows mouse pointer. Have to quit then with Alt+F4. Do you need some logs?

winuae.zip should fix this (minimize button stuff does not really work nicely in fullscreen..)

[Retro-Nerd]

Thanks, winuae.zip fixed it.

[vagrant]

With beta 13 the buffer it still hitting maximum during interlace sections, I tried all the new options. Although I'm not sure if beta 13 was supposed to fix it

Without going too off-beta topic:
Normally I use wasapi EX with buffer at 1.
I would like use portaudio modes but they always introduce extra latency, even at lowest buffer setting. I even tried setting buffer samples manually from 1024 to 1 and there was still ~20ms lag.
Is there any way get rid of the extra latency?
Btw with portaudio selected the buffer is completely stable during interlace sections

[Dr.Venom]

Originally Posted by who

With beta 13 the buffer it still hitting maximum during interlace sections, I tried all the new options. Although I'm not sure if beta 13 was supposed to fix it

Without going too off-beta topic:
Normally I use wasapi EX with buffer at 1.
I would like use portaudio modes but they always introduce extra latency, even at lowest buffer setting. I even tried setting buffer samples manually from 1024 to 1 and there was still ~20ms lag.
Is there any way get rid of the extra latency?
Btw with portaudio selected the buffer is completely stable during interlace sections

What Portaudio modes are you trying to use? "Portaudio: wasapi-ex" , or "Portaudio: ASIO (or ASIO4ALL)"?

Note that for any of the ASIO modes that the WinUAE setting has -no- influence, the ASIO latency settings are managed outside WinUAE by their own programs. When running ASIO4All it's the little green "play" button that appears in the taskbar/notification area once WinUAE is started, with which you can set the latency.

[vagrant]

Ok, I've had asio4all working in the past and adjusted the buffer in the taskbar etc but found it didn't match the performance of standard wasapi EX.
I was hoping to try portaudio: wasapi or portaudio: creative ASIO for my X-Fi card but could not find any way to adjust the buffer outside of winuae