Search options (Page 19 of 21)

That's like the hypnotoad. Pretty cool.

A note on the Phaser technique. It also allows to control duty, even in its simplest form, as seen in the Phaser1, without the extra CPs. Set both oscillators to the same frequency, but reset phase of both to different values, one to 0, another to 32768 or less (32768 gives 50% duty).

I think that to keep things under control and in a convinient way, we should use ABC or MML as a base, but not fully match to the standard. I.e. add convinient shortcuts for things.

For one, we can implement a 'subroutine', just like in BASIC. The subroutine can be either another sequence of notes, or a set of parameter changes. I.e. there would be no instrument per se, just immediate parameters change that could be abstracted as subroutines. For example, ^ used as a call operator (to keep it short) working by a label:

^ins0 C2 E2 G2 R2 ^ins1 C2 E2 G2 R2

ins0:
duty=50
detune=2
ret

Also, to keep it short, I'd suggest to allow using a note name without duration by remembering the last value, i.e. C2 E2 G2 R2 equal to C2 E G R.

Using calls, we actually won't need to have an order list equivalent. Just write patterns with labels and rets, then the entry point will be just series of calls.

^pattern1 ^pattern2 ^pattern1 ^pattern3
stop

pattern1:

C2 E2 G2 B2

ret

...

One thing to think deeper is how to use chords in an convinient way, not split per a number of data sequences. Maybe some operator like + (C+E+G2 for Cmaj).

I imagine this system as being written in some scripting language, such as Python, with infrastructure a bit similar to the 1tracker's, i.e. the compiler script generates text data (DB/DW), then an assembler (maybe just SjAsm/Pasmo, or also written in the script language) gets invoked to compile that into AY/TAP/SNA/etc.

Yes another masterpiece that is also really difficult to support in a tracker.

I thought, maybe instead of the XM conversion or all-for-one tracker we can design and create a MML-like system for these engines? One that compiles a human readable text into a AY/TAP/BIN (so you can hook it up to the Notepad++ and hear the result just by pressing F5 or something). Text allows more flexible input than tracker's row/column based grid, like variable number of channels and parameters.

FM2149 is actually called YM2149, not related to FM sound (synthesis) at all.

I think extended Octode versions should be allowed, as they has quite different timbre. Yes, it opens up a 'lazy' shortcut, but well, original Octode (and ZX-7, actually) wasn't used too much by anyone besides Mister Beep anyways.

Savage newcore, on the other hand, is the same thing as the original Savage, just with cleaner sound, so it makes sense to exclude it.

Overall, yes, I'd propose to disallow Special FX, Huby, Music Studio, Music Box, original Octode, QChan, Phaser1 (any mod), Savage old and newcore, original Tritone. It makes sense to disallow ZX- family, although ZX-3 may be allowed, as it barely had any use as far as I know. Not sure on Lyndon Sharp's engine, it had limited use in modern times, but not much.

Sometime I have a thought that it would be nice to run another compo. However, instead of many categories, do a single one, with a rule - use an unpopular engine. I mean, lately we got tons of new cool engines with huge potential that is waiting to be explored. Of course there is issue with the authoring tools, but those won't develop if no one interested in new engines, so we need to make some push. Not sure on the list of prohibited engines, but it should include Phaser1, Tritone, Special FX, Savage - ones used the most.

Very impressive. There is like 100 engines already, but beeper continues to amaze. So does utz.

VGA is outdated, but it provides very good picture quality, compared to RCA. So if you want to use, say, ProTracker 3 with this device (4x8 font), it will be really tiresome for the eyes, while VGA would give a crisp picture, just like on emulators. Maybe they only thought about playing retro games, that always were blurry with the original hardware that was rarely used with RGB displays.

Nice piece of hardware, but WHY composite only? That's horrible idea these days. VGA or HDMI is a must. And, if one sticks to composite nevertheless, WHY no RCA audio output then, for consistency? Lots of converters and adapters around such small board just to connect it to modern equipment is not that cool.

Sure, just edit palette of the font.bmp, with Graphics Gale or something. It was configurable like that since the very first version. Details on the palette indexes is in the docs/readme.txt