WinUAE 3.4.0 beta series

[mritter0]

Beta 2 did not fix SB128 not found issue.

Logs and config attached.

[Toni Wilen]

Originally Posted by mritter0

Beta 2 did not fix SB128 not found issue.

Logs and config attached.

http://www.winuae.net/files/b/winuae.7z should fix it.

[mark_k]

Originally Posted by Toni Wilen

- Hardware info panel move up/down buttons are now disabled when unmovable item is selected.

That doesn't seem to apply to the Fastlane 2140/0B board.

Also, you could disable Move up or Move down if the selected board can't be moved any further up or down.

[Retro-Nerd]

- Low latency vsync fixed.

It's working again but the performance is very poor now. I get 35-45fps, other sync modes shows stable 50fps. I assume you are still working on it?

[Toni Wilen]

Originally Posted by Retro-Nerd

It's working again but the performance is very poor now. I get 35-45fps, other sync modes shows stable 50fps. I assume you are still working on it?

It works exactly like with 3.3.0 here (with fullscreen in secondary normal 1080p monitor).

In other words: Logs! (EDIT: from both 3.3.0 and this beta)

[Arnie]

OS4.1 + Picasso now working again

[Snake79]

Hi there. I'm glad, that new beta series started but it also started problems with my OS41FE config With my config i have endless black screen (hdd is blinking from time to time). Only if i change Display settings from Fullscreen (Low Latency VSync) to Full-window (-) system is booting and i can see desktop. I have spotted also, that drawing speed of windows and menus is slower vs 3.3.0. I have problems with SB128 too. On latest winuae.7z SB128 is there and playing sounds, but with crackling and latest "alpha" causes even AOS freeze.

[Toni Wilen]

Originally Posted by mark_k

That doesn't seem to apply to the Fastlane 2140/0B board.

Also, you could disable Move up or Move down if the selected board can't be moved any further up or down.

Done

Originally Posted by Snake79

Hi there. I'm glad, that new beta series started but it also started problems with my OS41FE config With my config i have endless black screen (hdd is blinking from time to time). Only if i change Display settings from Fullscreen (Low Latency VSync) to Full-window (-) system is booting and i can see desktop. I have spotted also, that drawing speed of windows and menus is slower vs 3.3.0. I have problems with SB128 too. On latest winuae.7z SB128 is there and playing sounds, but with crackling and latest "alpha" causes even AOS freeze.

Does END+F9 show the screen? winuae.7z probably also fixes it.

[mark_k]

I tested the attached config with 3.4.0b2. A4000/040 + Picasso boots OpenBSD. You hopefully have the corresponding HDF for that already, though it may not matter since the problem can be seen at the initial CLI prompt.

In that config, the CPU Idle slider is all the way to the right. Start emulation, type loadbsd at prompt. After a while the CPU% indicator says 0% for much of the time. (In fact it shows 0% just sitting at the CLI prompt.)

Open settings window and move the CPU Idle slider all the way to the left. Continue emulation and CPU% still shows as 0% for much of the time.

In comparison, WinUAE 3.3.0 behaves as I'd expect; CPU% is 18 to 21 at the CLI prompt with CPU Idle all the way to the right, 100% with CPU Idle all the way to the left.

[AMIGASYSTEM]

Excuse Toni, i do not know if it depends on my windows system, i noticed that with 3.4.0 and OS4.1 MP3 feel slow and distorted, with the same configuration (same config.uae) with the old version 3.3.0 MP3 feel good.

[Retro-Nerd]

Originally Posted by Toni Wilen

It works exactly like with 3.3.0 here (with fullscreen in secondary normal 1080p monitor).

In other words: Logs! (EDIT: from both 3.3.0 and this beta)

WinUAE 3.3.0 full version was fine.

[Toni Wilen]

I think it should be quite obvious that you are only wasting your time by reporting something OS4 related unless it is 100% OS4 only!

[Snake79]

Originally Posted by Toni Wilen

Does END+F9 show the screen? winuae.7z probably also fixes it.

In my case END+F9 does nothing on my config (winuae_3400b2 and winuae.7z).
Using latest winuae.7z still have blackscreen in Fullscreen (Low Latency VSync), but Fullscreen (-) is working fine showing the desktop.

[Thom87]

Hi Toni,

I'm experiencing some issues with paula sound on new beta 2 (not tested on beta 1).
Tests been done under Workbench with Hippo Player plaing 4 chanel modules both 50Mhz and ~28Mhz (x8) and quicly WHD - Deluxe Galaga at 28Mhz only.
I'm running on an older Laptop with Windows 7 x64 - it might be a little to slow but I got no access to anything faster to preform tests at the moment.

Last stable vesion (3.3.0) works fine even at 50Mhz clock, however when plaing only 4-chenel modules WinUAE uses about 90+% CPU but no sound issues at all.

Beta 2 (3.4.0) produces crackin sound after about 1-2 seconds when usign Hippo Player and 30-40 seconds on Galaga (it starts when Galaga starting to diplay version number etc). Cracking on Galaga is not so intens but it displays in AGA mode and Workbench is in P96 (1024x768x24). Apart that sound slowing down on P96 with I can't hear on AGA mode. Cracking remain even when music stops for another couple seconds. Beta 2 in general uses less CPU, even up to 10% less.

I hope this report is not confusing as last one.

[Snake79]

mark_k has inspired me in "slider" thing (i was using CPU and FPU -> Stopped M68K CPU idle mode). In term of speed (reaction) results are (OS41FE):
test1 config (slider to left): os menu open in about 1.5s, Ranger shows up in about 15s
test2 config (slider to right): os menu open almost immediately, Ranger shows up in about 4s
OS reaction is much better (windows and menus), if that can help in something...

[vagrant]

Ok with beta 2, low latency modes are working, however I'm getting a consistent screen-tearing effect in the top 20% of the display during smooth scrolls.
I tried to record an example video using fraps, but for some reason the video records without any tearing

Also WASAPI EX still fails to initialize, and sound options automatically set to "disabled but emulated". Attached are logs for this.
Normal WASAPI mode is working fine.
I didn't notice any performance issues using low latency mode, CPU seems ok.

[Toni Wilen]

Originally Posted by Snake79

mark_k has inspired me in "slider" thing (i was using CPU and FPU -> Stopped M68K CPU idle mode). In term of speed (reaction) results are (OS41FE):

It looks like new CPU Idle logic gets stuck in "low speed mode" in PPC only mode. [EDIT: this is now fixed]

Originally Posted by ED-209

Ok with beta 2, low latency modes are working, however I'm getting a consistent screen-tearing effect in the top 20% of the display during smooth scrolls.
I tried to record an example video using fraps, but for some reason the video records without any tearing

Only in no-buffer display mode?

Also WASAPI EX still fails to initialize, and sound options automatically set to "disabled but emulated". Attached are logs for this.
Normal WASAPI mode is working fine.
I didn't notice any performance issues using low latency mode, CPU seems ok.

Try smaller sound buffer size. It returns error that means sound buffer is too large in EX mode. (Oddly enough MSDN says it is Windows7+ feature but at least I can't duplicate it, even with smallest or largest possible buffer)

[michaljarz]

I also noticed a problem with sound. As an example, I tested demo "SPACEBALLS - State Of The Art". Config based from quickstart - A500, 1MB Chip, 68000, 24bit adressing, CPU Frec 2x, ECS Agnus, Cycle-Exact. I tested in window mode, but in full screen is same effects.

Windows XP SP3.
Sound driver - DirectSound.

In latest winuae.7z only "Legacy VSync" works OK.
Attached comparision table and logs from 3.3 and latest 7z.

(EDIT: In table => LegacyVSync+DirectDraw = +23% / +25% sound)

[vagrant]

about WASAPI EX: It is working now after I increase the sound buffer from 1 to 2.

screen tearing in low latency mode: I was also getting some audio pops with the tearing.. and it looks like this is related to sound buffer also! Increasing the buffer in steps slowly fixed the problem, but now it has to be at least 5 for the display to be stable

[Toni Wilen]

Originally Posted by ED-209

about WASAPI EX: It is working now after I increase the sound buffer from 1 to 2.

Ok, so it can also happen when buffer is too small.

Buffer size calculation in wasapi has changed, small buffer is now really small. (pull mode can handle extremely small buffers without glitches, push could not)

screen tearing in low latency mode: I was also getting some audio pops with the tearing.. and it looks like this is related to sound buffer also! Increasing the buffer in steps slowly fixed the problem, but now it has to be at least 5 for the display to be stable

wasapi pull mode is not yet really tuned for low latency vsync.