Editing Clock Signal
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 2: | Line 2: | ||
|title = Clock Signal | |title = Clock Signal | ||
|logo = CLK_(emulator)_Icon.png | |logo = CLK_(emulator)_Icon.png | ||
− | + | |developer = Thomas Harte | |
− | |developer = | + | |version = {{clkver}} |
− | |version = {{ | ||
|active = Yes | |active = Yes | ||
− | |platform = | + | |platform = macOS<br/>Linux |
|accuracy = Subcycle | |accuracy = Subcycle | ||
− | |target = [[BBC Micro emulators|Acorn Electron]], [[Amstrad CPC emulators|Amstrad CPC]], | + | |target = [[BBC Micro emulators|Acorn Electron]], [[Amstrad CPC emulators|Amstrad CPC]], Apple II, [[Atari 2600 emulators|Atari 2600]], [[ColecoVision emulators|ColecoVision]], Commodore Vic-20, [[MSX emulators|MSX 1]], Oric 1/Atmos, [[Sinclair ZX81 emulators|ZX80/ZX81]] |
|prog-lang = C++; Mac bindings in Objective-C and Swift | |prog-lang = C++; Mac bindings in Objective-C and Swift | ||
− | |download = [https://github.com/TomHarte/CLK/releases Official releases] (macOS | + | |download = [https://github.com/TomHarte/CLK/releases Official releases] (macOS) |
|source = [https://github.com/TomHarte/CLK GitHub] | |source = [https://github.com/TomHarte/CLK GitHub] | ||
− | |||
− | |||
}} | }} | ||
− | '''Clock Signal''', also known as '''CLK''', is an MIT-licensed | + | '''Clock Signal''', also known as '''CLK''', is an MIT-licensed open source emulator of a collection of 8-bit computers and consoles for macOS and for Linux. |
It is unique in its approach to screen emulation and as a result offers worst-case video latency equal to the refresh rate of the screen on which it is being displayed — 1/60th of a second on a 60Hz monitor, 1/120th of a second on a 120Hz monitor, etc — regardless of the refresh rate of the machine being emulated. | It is unique in its approach to screen emulation and as a result offers worst-case video latency equal to the refresh rate of the screen on which it is being displayed — 1/60th of a second on a 60Hz monitor, 1/120th of a second on a 120Hz monitor, etc — regardless of the refresh rate of the machine being emulated. | ||
Line 22: | Line 19: | ||
It is also noteworthy for the degree to which it deploys automatic analysis in an attempt automatically to launch class software: in addition to ahead-of-time static analysis, it can simply run and monitor multiple different machines or machine configurations in parallel to determine what the proper hardware configuration for a particular title should be, often offering a seamless continuous display to the user. | It is also noteworthy for the degree to which it deploys automatic analysis in an attempt automatically to launch class software: in addition to ahead-of-time static analysis, it can simply run and monitor multiple different machines or machine configurations in parallel to determine what the proper hardware configuration for a particular title should be, often offering a seamless continuous display to the user. | ||
− | It generally emulates components internally at single-cycle or half-cycle precision but seeks to decouple execution wherever possible. E.g. even if video and processor share memory which would naively imply running each component for a single cycle in a round robin fashion, the emulator actually applies something analogous to a write-through cache: the processor writing to the shared region will cause video processing to run just-in-time as though it had been interleaving reads until then. | + | It generally emulates components internally at single-cycle or half-cycle precision, but seeks to decouple execution wherever possible. E.g. even if video and processor share memory which would naively imply running each component for a single cycle in a round robin fashion, the emulator actually applies something analogous to a write-through cache: the processor writing to the shared region will cause video processing to run just-in-time as though it had been interleaving reads until then. |
Regardless of this, Clock Signal does not currently offer a perfect emulation of every supported machine. It is an active, developing emulator. | Regardless of this, Clock Signal does not currently offer a perfect emulation of every supported machine. It is an active, developing emulator. | ||
− | + | ==Display Emulation== | |
− | + | [[File:CLK ZX80.gif|right|alt=The emulated display of a ZX80, showing accurate emulation of synchronisation issues.]] | |
− | + | Clock Signal's emulated machines produce a 1d video signal, just as real machines do. Its emulated display therefore has to: | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | ==Display | ||
− | [[File:CLK ZX80.gif|right|alt=The emulated display of a ZX80, showing accurate emulation of | ||
− | Clock Signal's emulated machines produce a 1d video signal, just as real machines do. Its emulated display | ||
* maintain a raster positioning; | * maintain a raster positioning; | ||
* run sync-triggered phase-locked loops to place horizontal and vertical retraces; and | * run sync-triggered phase-locked loops to place horizontal and vertical retraces; and | ||
− | * decode composite | + | * decode composite colour if that's what the machine is supplying. |
It uses this information to paint a virtual phosphor display — in practice just an accumulation of recently-painted material with each new painting undergoing exponential decay. Output to the host screen is simply a capture of that surface as and when the host screen requests a new frame. | It uses this information to paint a virtual phosphor display — in practice just an accumulation of recently-painted material with each new painting undergoing exponential decay. Output to the host screen is simply a capture of that surface as and when the host screen requests a new frame. | ||
Line 48: | Line 34: | ||
An unambiguously desirable result is that machines with variable programmatic sync, such as the Atari 2600, ZX80/81 and Amstrad CPC, should produce the proper display results, even down to rolling, bouncing and other sync issues as and when the programmer diverges, even if only transiently, from PAL or NTSC timing specifications. | An unambiguously desirable result is that machines with variable programmatic sync, such as the Atari 2600, ZX80/81 and Amstrad CPC, should produce the proper display results, even down to rolling, bouncing and other sync issues as and when the programmer diverges, even if only transiently, from PAL or NTSC timing specifications. | ||
− | A further positive effect is that composite video produces the proper per-platform results simply because the timing is correct: e.g. the Atari 2600 and ColecoVision produce an in-phase signal when outputting NTSC so they show obvious fixed vertical banding between strong | + | A further positive effect is that composite video produces the proper per-platform results simply because the timing is correct: e.g. the Atari 2600 and ColecoVision produce an in-phase signal when outputting NTSC so they show obvious fixed vertical banding between strong colour transitions, but the Oric, Electron and PAL Atari are not in-phase so produce undulating diagonals at colour transitions. |
− | The emulator goes as far as to use the Oric's original | + | The emulator goes as far as to use the Oric's original colour ROM for Oric composite video generation — it replays the actual PCM-sampled output values generated by the real machine to produce realistic colour. |
− | Composite | + | Composite colour is optional for all machines on which it was originally optional. Machines such as the Oric, Electron and MSX originally shipped with the option of RGB output, so the emulator offers the same. |
− | ==Sound | + | ==Sound Emulation== |
− | Sound emulation is generally performed by internal generation of original megahertz-rate audio, which is resampled to the output frequency of the host computer. Therefore just | + | Sound emulation is generally performed by internal generation of original megahertz-rate audio, which is resampled to the output frequency of the host computer. Therefore just like the video can scale up to modern low-latency high-refresh-rate displays, the audio can scale up to digital output rates such as 96Khz and 192Khz. |
Filling sound packets is an independent trigger of emulation — the emulated machines will run to make sure they're up to date when the display needs a new frame, and they'll also run to produce the next packet of audio when the previous has been consumed. | Filling sound packets is an independent trigger of emulation — the emulated machines will run to make sure they're up to date when the display needs a new frame, and they'll also run to produce the next packet of audio when the previous has been consumed. | ||
Line 61: | Line 47: | ||
That generally allows the emulator to maintain audio latency guarantees completely decoupled from the frame rate. It aims for between 5 and 10ms of audio latency. | That generally allows the emulator to maintain audio latency guarantees completely decoupled from the frame rate. It aims for between 5 and 10ms of audio latency. | ||
− | ==Host | + | ==Host Environments== |
− | + | For macOS Clock Signal is a fully-native document model application, which means that the user can simultaneously launch as many different machines as they want, sizing and positioning each independently across multiple displays, arranging their machines into a tabbed interface or performing any other standard Mac windowing actions. | |
− | For macOS | ||
− | + | Clock Signal also has an SDL-based kiosk mode, which is compatible with Linux and any other target offering SDL 2.x, at least OpenGL 3.2 and C++11, and which attempts to follow ordinary UNIX conventions as to file naming and locations. It is intended to be launched however the user would normally launch something from the command-line; the target use case is to set up a file association in the user's preferred desktop environment and launch emulated applications by double clicking on them exactly like the user would launch native applications. | |
− | Clock Signal | ||
− | + | In neither case does Clock Signal offer much in terms of appreciable interface. It currently assumes it can always determine the proper machine and machine configuration automatically based on the software the user wants to run and provides those only after the user has nominated their software. | |
− | Clock Signal | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
[[Category:Atari 2600 emulators]] | [[Category:Atari 2600 emulators]] | ||
− | |||
[[Category:ColecoVision emulators]] | [[Category:ColecoVision emulators]] | ||
− | [[Category: | + | [[Category:Emulators]] |
− | |||
− | |||
− | |||
− | |||
− | |||
[[Category:Linux emulation software]] | [[Category:Linux emulation software]] | ||
[[Category:macOS emulation software]] | [[Category:macOS emulation software]] | ||
− | [[Category: | + | [[Category:Multi-emulators]] |
+ | [[Category:MSX emulators]] |