Search options (Page 61 of 137)

It's in the full_version folder which is password protected, just like all the other LSDj version files. Unless you mean Johan is doing something mad illegal by distributing Goomba without permission or something.'

http://littlesounddj.com/lsd/latest/full_version/ (Try clicking any of the files. I dare you.)

http://blog.gg8.se/wordpress/2013/01/20 … -midi-rom/

nitromidi1 is a very simple Gameboy MIDI ROM. It can be used with an Arduinoboy or Nanoloop USB MIDI adapter. It’s not meant to be all that practically useful atm. Rather, I created it to have all the plumbing in place for future MIDI software.

It currently responds to the following things:

• MIDI channel 1 only.

• Gameboy pulse channel 1 only.

• Note ons. (But currently not note offs!)

• The typical “panic” button. (Channel mode messages $7B, all notes off and $78, all sound off.)

• The pitch wheel, currently with a fixed range of +/-7 semitones.

• CC 71/$47 which controls the pulse width of the wave.

• CC 72/$48 which is a combined attack/release control, ie. the second nibble of the envelope byte. The control scans from short decay to long decay to constant volume output to slow rise to fast rise. In other word, the following envelope values mapped onto a knob: 1-7,8,F-9.
  As noted above, it doesn’t respond to note offs, so be careful with rising envelopes!

• It has no GUI except a lines pattern indicating CPU usage. This is literally made by changing the background palette when the CPU is busy.

Have fun, and report any bugs/anomalies/feature requests.

With the voice of Richard Stallman, "I'd just like to interject for a moment."

LSDj is nowhere near that accurate. It's using a 4096 clock as its tempo base, which is then divided down to the BPM. This means you can set the time between interrupts in increments of about 0.2 milliseconds. The error for the BPM value varies with the BPM. Higher BPM means lower accuracy. However, there is a trick in place to switch between different values on every tick to increase the accuracy. Which increases the accuracy a small bit.

A real world example: 128 BPM is a tempo that divides from the 4096 Hz clock, and is theoretically completely accurate (to the limit of the clock crystal's accuracy.) 129 BPM is a tempo that divides badly from the 4096 Hz clock, and the real world BPM turns out to be 128.805 BPM. This is 0.151% too low. This one of the worst cases. 130 BPM becomes 130.032 BPM, or about 0.0244%.too high. I think Johan may have made a mistake and meant to say that the worst case error is a factor of 0.005, or 0.5% off. That's still fairly good.

Edit: The algorithm seems to be more complicated than I thought, and the accuracy is higher than the calculations above.

Notice how I purposely used the word accuracy instead of precision. Precision is something different than accuracy. LSDj has a relatively bad precision, ie the time between notes may jitter such that the time between each note varies, even if the long term average converges to the 0.5% or smaller error. This is because the CPU may be busy doing other things when a timer interrupt happens. The culprit is typically kits as well high frequency vibrato, and not using these will reduce the jitter. I haven't made any calculations on the actual error from this but might do so in the future.

Oftentimes chip music involves pressing play rather than "playing" something. (As in one stroke on the instruments generates one tone type of deal.) Maybe it's a subconscious reflection on this. You're more like a dj playing his own tunes on disc, than a rock band.

Here's the technical explanation: http://blog.gg8.se/wordpress/2013/01/16 … planation/

SBthree: Sounds like an interesting idea. I'll keep it in mind.

Well, I'm not giving any hints at this stage, but feel free to try different things.