MacVICE

[franticHT]

I am using version: Version 2.1.9-r20692_20090416

When I enable Stereo SID I get the following alert:

"VICE ERROR! Sound: write to sound device failed."

...and after clicking OK VICE crashes. If I disable "Sound Playback" in the options menu, VICE does not crash when enabling Stereo SID. However, when turning "Sound Playback" back on, I get the same error message and VICE crashes after clicking OK. It doesn't matter if I have a cartridge image "plugged in" or not, the error+crash occur anyway.

I have a faint memory that I have used Stereo SID before on the Mac version, and that I got it working that time. Not so in this version...

[MagerValp]

I just tried the MacVICE snapshot 2.1.16-r21487_20090912, cocoa-10.5, and audio is corrupted. I get lots of crunchy noises and general weirdness.

It also appears to be missing the kernal autostart by warp mode feature that I've been enjoying.

[lallafa]

Hmmm... I just tested the snapshot here on my 10.6.1 and sound was ok. Also drag&dropped D64s loaded fine with warp mode toggling.

This is the first 10.6 hosted build on my system... Maybe something broke...
I already fixed some issues here...

Do you have more details for me? Vicerc, log, sysinfo, step-by-step guide

[zCRP]

Hi, I just installed the latest snapshot of MacVice, and noticed something unusual: it appears that the code for key 'a' is 0000, thus whenever I turn on keyset joystick emulation, pressing 'a' triggers the pressing of one of the directions which have not been explicitly assigned. In my case, if keyset joystick is off, pressing 'a' prints the corresponding letter on the screen. If I turn keyset joystick on, nothing is printed on the screen, but in the Control screen, it is as if left+down were pressed.
Is this a bug or have I messed up something?

Thanks
Christian

[lallafa]

@franticHT: stereo sid bug is fixed in [21511] on trunk

@zCRP: on default all keys of the keymap joystick map to 0000 which corresponds to the A key. If you press 'A' it simply maps to all directions and results in some strange directions.

So the first thing you have to do, is to map each direction in the keymap joystick to a different key... then it should work as expected.

[zCRP]

thanks, that did the trick, even though it would be nice to be able to "unassign" a joystick direction in order to leave it blank and use only those keys for joystick emulation that are really necessary.

I'll throw in a feature request: would it be possible to have some kind of indicator in the control window showing if "allow keyset joystick" is on or off?

thanks
Christian

[MagerValp]

Hmmm... I just tested the snapshot here on my 10.6.1 and sound was ok. Also drag&dropped D64s loaded fine with warp mode toggling.

This is the first 10.6 hosted build on my system... Maybe something broke...
I already fixed some issues here...

Do you have more details for me? Vicerc, log, sysinfo, step-by-step guide

Nukeing the VICE prefs seemed to fix everything, so false alarm I guess. Some defaults are weird though:

* Double Scan is enabled, but not Double Size. I get a double size window with black borders on the top and bottom.
* PAL Emulation is disabled by default (though that might be sane for performance reasons).
* ReSID-FP is disabled by default (again, sane for performance reasons, but inexperienced users will not get the best experience).

[MagerValp]

Enabling Stereo SID crashes x64: Resource Inspector -> SID -> Stereo SID -> Enable, gives Sound: write to sound device failed, followed by a crash:

Code: [Select]

Process:         x64 [88151]
Path:            /Users/pelle/Applications/Emul/VICE/x64.app/Contents/MacOS/x64
Identifier:      org.viceteam.x64
Version:         ??? (2.1.16-r21487_20090912)
Code Type:       X86 (Native)
Parent Process:  launchd [136]

Date/Time:       2009-09-24 13:08:40.496 +0200
OS Version:      Mac OS X 10.6.1 (10B504)
Report Version:  6

Interval Since Last Report:          499396 sec
Crashes Since Last Report:           5
Per-App Interval Since Last Report:  8933 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      1513C508-EB4A-4B98-96D6-484D37DA7EEB

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread:  2


Thread 2 Crashed:
0   org.viceteam.x64              0x0008e80e 0x1000 + 579598
1   org.viceteam.x64              0x0004362f 0x1000 + 271919
2   org.viceteam.x64              0x00021b4b 0x1000 + 133963
3   org.viceteam.x64              0x000223ed 0x1000 + 136173
4   org.viceteam.x64              0x00024b08 0x1000 + 146184
5   org.viceteam.x64              0x000df46f 0x1000 + 910447
6   org.viceteam.x64              0x00027890 0x1000 + 157840
7   org.viceteam.x64              0x0001750f 0x1000 + 91407
8   org.viceteam.x64              0x0010321e 0x1000 + 1057310
9   com.apple.Foundation          0x91a8f964 -[NSThread main] + 45
10  com.apple.Foundation          0x91a8f914 __NSThread__main__ + 1499
11  libSystem.B.dylib              0x964c8f39 _pthread_start + 345
12  libSystem.B.dylib              0x964c8dbe thread_start + 34


Binary Images:
    0x1000 -   0x171ff7 +org.viceteam.x64 ??? (2.1.16-r21487_20090912) <9D4235ED-DB23-2A2E-8B41-48945A48C0FE> /Users/pelle/Applications/Emul/VICE/x64.app/Contents/MacOS/x64

Model: MacPro3,1, BootROM MP31.006C.B05, 8 processors, Quad-Core Intel Xeon, 2.8 GHz, 10 GB, SMC 1.25f4
Graphics: ATI Radeon HD 2600 XT, ATI Radeon HD 2600, PCIe, 256 MB
Memory Module: global_name
Bluetooth: Version 2.2.1f7, 2 service, 1 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: ATI Radeon HD 2600, Display, Slot-1
Serial ATA Device: WDC WD3200AAJS-41VWA1, 298,09 GB
Serial ATA Device: WDC WD5000AAKS-41YGA1, 465,76 GB
Parallel ATA Device: PIONEER DVD-RW  DVR-112D
USB Device: Keyboard Hub, 0x05ac  (Apple Inc.), 0x1006, 0xfd500000
USB Device: USB-PS/2 Optical Mouse, 0x046d  (Logitech Inc.), 0xc03e, 0xfd510000
USB Device: Apple Keyboard, 0x05ac  (Apple Inc.), 0x0221, 0xfd520000
USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x8206, 0x5d200000
FireWire Device: built-in_hub, Up to 800 Mb/sec
FireWire Device: unknown_device, Unknown


[lallafa]

MagerValp, your x64 is too old The Bug was fixed in [21511] but you tried 2.1.16-r21487_20090912...

BTW... most recent trunk has a complete rewrite of the coreaudio driver that should fix the wrong playback with samplerates != output samplerate... and hopefully does not introduce new bugs

[MagerValp]

MagerValp, your x64 is too old ;) The Bug was fixed in [21511] but you tried 2.1.16-r21487_20090912...

WTH... Oh! I only installed 21532 on my laptop, not on my workstation. Bah...

[MagerValp]

NEW: snapshots for x86_64 and clang are available!

Awesome! Any interesting things found by the analyzer? Performance improvements?

[lallafa]

No findings yet... I was just glad to have the build system cope with all the new compilers, SDKs...

BTW: I am currently experimenting with VSync of the emulator core... Unfortunately my tests run only on NTSC aka 60Hz for now as it is the native sync of my LCD... You mentioned a SwitchResX config you did for PAL... Can you give me details on your modeline?
I tried setting up a 50 Hz Mode for my external analoge Monitor (capable of 50 Hz) connected via VGA to my MBP, but SwitchResX never enabled my 50 Hz Mode for this monitor and always tells me to "Activate by reboot"

[MagerValp]

Yeah, SwitchResX was a pain to use, so I just uninstalled it after the evaluation period ran out.

Is there an official way to open a screen mode with a certain refresh rate on Mac OS X?

[GANDALf]

I'm building trunk for ppc/coca/10.5 for some time now. All versions since 21558 has a nasty bug where everything stops  for a minute or two (even caps lock led or force quit) and than continues for a few seconds... rinse and repeat. I can quit Vice on those working seconds and than everything returns to normal.

Latest version from lallafa works OK (apart from occasionally "Sound: write to sound device failed" error and crash when warp/unwarp).

[lallafa]

@GANDALf

I already suspected that the last video rendering change was causing more trouble than it helped increasing performance...

I reverted the change in [21572].
Plz check if that works for you again...