This seems to be a regression bug on VICE 3.3, since the undump command of the Monitor API worked fine on VICE 3.2 (although that was on WinVICE 3.2, and now errors on GTK3VICE 3.3 using x64.exe win32 r35872). The exact same snapshot files load successfully when doing so manually through the GUI menu, but VICE complains and often closes itself when loading the same snapshot files through the remote API (used for automated testing).
There are several "VICE Error" dialog messages that appear, but they all seem to be related to sound initialization problems. For example, "Sound: initialization failed for device dx" and "Cannot set Output format for primary sound buffer: Priority level needed". (The priority error happens even when trying to run as administrator with elevated privileges; this error also happens after trying to disable the sound resource in VICE, such that disabling cannot be used as a workaround either, but ideally it would work with sound.)
For the record, the errors happen on the Windows 10 Pro (64-bit) operating system. The snapshot files were created with the exact same VICE 3.3 application; creating them either manually or with the dump API command makes no difference; snapshots load successfully if done manually, but always fail if done through the undump API command. What I expect to happen is for the snapshots to load successfully, as it used to work in VICE 3.2.
I think that the bug was fixed by revision 35897. Try a build that was made after that revision.
Thanks for your feedback, and sorry if this is a dumb question, but where can I find such an official build? I thought GTK3VICE was the way forward (which is why I switched from WinVICE), but the most recent release build for Windows seems to be 35872 (that is the one I used with the problem). The "nightly builds" for Windows only go to "GTK3VICE-3.3-win32-r35896" (short by one revision from the 35897 suggestion).
I did find an official SDL2VICE build for revision 36028 (under "experimental binaries"), but I thought the SDL branch will (similar to WinVICE) also no longer be supported, which is why I'm somewhat reluctant to switch to another obsolete branch.
Or what is the best way forward when using Windows now that WinVICE is no longer an option?
both GTK3 and SDL are still supported (all the others are not).
That said, we do not provide "official" binaries anymore (also the nightly builds are provided by someone else). Some guy on lemon64 provides recent windows builds, see here: https://tinyurl.com/y78fhx2g
Thanks for the clarification.
In case it could help somebody else: As an alternative workaround for this bug, one can also switch the sound driver configuration from DX to WMM (although I noticed a difference in sound quality).
That's probably what I'll do for now to avoid installing an unfamiliar build. (I'm still a bit concerned about the future of VICE without "official" binaries, but that's another topic.)
honestly, the official windows builds never were the best around...
Well, those official Windows builds were good enough for me for many years, and I'd rather have something official/vouched than nothing at all. (Without a default go-to build, being forced to go hunt the web for binaries, it leaves the field wide open for virus-infected builds from unknown sources.)
so can we close this?
As the one who reported this bug, I don't know. It may be fixed (as suspected by user gregdk), but I cannot confirm this since there is no sufficiently newer "official" build available for GTK Win32 (and I'm not able to build it myself). My interim workaround has been to just switch to a non-DX sound driver for now. Ideally the potential fix would be verified before we just close this ticket (but maybe you use a different workflow).
But what I can offer is to try to use the GTK3VICE build of revision 36167 (as found in experimental binaries) and then provide feedback afterwards. That might give us a more definitive answer about closing this ticket.
Unfortunately that experimental build of GTK3VICE revision 36167 is so unstable, the window doesn't even want to open on my machine -- the application simply quits before anything can be tested. So, I still don't know if the issue is fixed or not.
that could give a hint at least :)
can we close this? please try a recent nightly build :)
(if VICE crashes at startup, try x64sc -gtkbackend 0)
repeating the request - please test with a recent build from github
I suspect it is still a problem. But due to overwhelming eldercare responsibilities I haven't been able to look into this myself, and that may not change soon. Can somebody else maybe please test this?
no feedback, quick test works (on linux though) -> closing