b9fad184d7
... which means that now it's time to worry about when and how mounted files should actually update themselves. Which will make for some fun with threading, I dare say. |
||
|---|---|---|
| Components | ||
| Concurrency | ||
| Machines | ||
| NumberTheory | ||
| OSBindings/Mac | ||
| Outputs | ||
| Processors/6502 | ||
| ROMImages | ||
| SignalProcessing | ||
| StaticAnalyser | ||
| Storage | ||
| .gitignore | ||
| LICENSE | ||
| README.md | ||
CLK
CLK is an emulator for tourists that seeks best-in-class accuracy while minimising latency.
So its aims are:
- single-click load of any piece of source media for any supported platform;
- with a heavy signal processing tilt for accurate reproduction of original outputs;
- that aims for the lowest possible latency; and
- 100% accurate emulations, naturally.
In terms of platforms, it currently contains emulations of the:
- Acorn Electron;
- Atari 2600;
- Oric 1/Atmos; and
- Commodore Vic-20 (and Commodore 1540/1).
Single-click Loading
Through the combination of static analysis and runtime analysis, CLK seeks to be able automatically to select and configure the appropriate machine to run any provided disk, tape or ROM; to issue any commands necessary to run the software contained on the disk, tape or ROM; and to provide accelerated loading where feasible.
The full process of loading a title — even if you've never used the emulated machine before — is therefore:
- locate it in your OS;
- double click it.
Signal Processing
Consider an ordinary, unmodified Commodore Vic-20. Its only video output is composite. Therefore the emulated machine's only video output is composite. In order to display the video output, your GPU then decodes composite video. Therefore all composite video artefacts are present and exactly correct, not because of a posthoc filter combining all the subjective effects that this author associates with composite video but because the real signal is really being processed.
Similar effort is put into audio generation. If the real machine normally generates audio at 192Khz then the emulator generates a 192Khz source signal and filters it down to whatever the host machine can output.
If your machine has a 4k monitor and a 96Khz audio output? Then you'll get a 4k rendering of a composite display and, assuming the emulated machine produces source audio at or above 96Khz, 96,000 individual distinct audio samples a second. Interlaced video also works and looks much as it always did on those machines that produce it.
Low Latency
The display produced is an emulated CRT, with phosphor decay. Therefore if you have a 140Hz monitor it can produce 140 distinct frames per second. Latency is dictated by the output hardware, not the emulated machine.
The machine update mechanism is influenced separately by both screen refresh and audio stream processing; audio latency is therefore generally restrained to 5–10ms regardless of your screen's refresh rate.
A corollary of emulating the continuous nature CRT, not merely performing end-of-frame transcriptions, is that the most common motion aliasing effects of displaying 50Hz video on a 60Hz display are minimised; you don't have to own niche equipment to benefit.
Accurate Emulation
Cycle-accurate emulation for the supported target machines is fairly trite now; this emulator seeks to follow that well-trodden path. All emulation logic is written in C++ for explicit control over costs but, where a conflict arises, the presumption is towards clarity and simplicity of code. This emulator is willing to spend the processing resources available on modern hardware.
Which are polite ways of saying that it's generally slower than the standard bearers for each supported platform but that if it's comfortably within the processing ability of a semi-modern computer then that's not considered problematic.