Search options (Page 20 of 137)

Neil Baldwin describes some of it here (for NES):
http://dutycyclegenerator.com/

Basically as far as I know, in the early days, you would either write your own engine or use the in-house engine of the company. Nowadays, there are a couple of publicly available choices of music engines, like XPMCK/MML or Carillon.

And did you have the debugger open at the time?

Which emulator?? Note that it can sometimes appear to be dead for a couple of seconds.

In principle, the clock can be as fast as you like. In practice there are some limits.

• The speed that the silicon in the chip can handle. This is likely a bit above the ~4 MHz that the CPU runs at.

• DMG has a 100 pF capacitor in parallel and 220 ohm resistor in series with each signal, for noise suppression. This will give you an upper limit for the frequency as it also acts as a low pass filter. (See schematic)

• Not to be forgotten, the cable. A typical link cable, if that's what you're going to use, would have stray capacitance and would probably leave a lot to be desired when it comes to signal integrity.

But yes, ultimately you're limited by the CPU anyway. Even if you could send individual bytes faster, there would not be much point since you have to wait between the bytes.

No updates on older nanoloop cartridge support yet, sorry.

As for GB Camera support, this is tested and working. It does not suffer from empty save files or lines in the images like some other flashers. The current output format is a plain sav file, which can be converted using Gijs' online GB Camera converter, for example. It would be easy to add support for directly outputting image files, though.

Edited to make the title overly clear.