(28 replies, posted in Other Platforms)

Hmm, very intriguing. So there was some Ukrainian involvement.
More info: http://nodehist.fidonet.org.ua/?address=2%3A461%2F256 http://nodehist.fidonet.org.ua/?address=2%3A461%2F60


(28 replies, posted in Other Platforms)

Thanks for your hard work, Shiru. Any chance of migrating from VCL to CLX though, so the emu could become portable?


(3 replies, posted in Sinclair)

Thanks, detective, much obliged! wink
We had another thread about this stuff: http://randomflux.info/1bit/viewtopic.php?id=153
Sadly punBB doesn't allow to merge topics (only with some 3rd party mod which reportedly doesn't work properly), so I'll have to think about collecting all this info into a sticky master post at some point.

Interesting, always nice to see experiments like this happen.
I don't quite understand what's the difference between this and regular DPCM, though.

You can just load .sna from divMMC. Otherwise there's SnapToTap for .sna->.tap conversion, and z802tzx for .z80->.tzx conversion (which you'll then have to convert to .tap for use with divMMC). See http://www.worldofspectrum.org/utilities.html#tzxtools
Assuming that the programs are written in pure BASIC, you could probably also dump the BASIC from Fuse and then shove it through zmakebas.

Hm, seems these are rather simple tools. But somewhat reasonably priced so still a nice item to have. Looking forward to your User Experience Report big_smile


(3 replies, posted in Sinclair)

Wow, great find! I don't think it's pin-based, actually. Sounds more like a hybrid of Lyndon Sharp's engine and Savage. And 3 channels, too, wow.  Unfortunately the parasite tone is strong in this one, but nevertheless very fascinating to see that something like this existed back in 1990.


(70 replies, posted in Sinclair)

https://chaosconstructions.ru/ looks freshly updated and it's the one they gave as official on demoparty.net etc, so I assume that's the one.

Thanks for posting these, uglifruit. That's quite a massive collection of tools!
Would you be willing to share the sources of the hacks/patches as well? I might be interested in creating some scripts for these, so one can easily include new patterns for the tritone/qchan tweaks.


(70 replies, posted in Sinclair)

So there will be a beeper compo at Chaos Constructions '18 (August 25-26). However, since the organizers in their infinite wisdom decided to make the party website Russian only, I will not participate in this one.

Person111 wrote:

WabbitEmu: "Not the correct model for this calculator" (DoorsCS7.8xk)

Makes sense. TI-83 is not TI-83 Plus. You're emulating the wrong calculator. Means you probably got the wrong ROM image.

Ok, I'm going to need a lot more info to solve this. First of all, which operating system are you using and which version of TilEm/wabbitEmu?
Second, I'll need you to make a list of the exact steps I need to take to reproduce the problem. So, something like:
1) start TilEm
2) Right click, Send File..., select DCS7.8xk
3) Click on APPS button, select DOORSCS7
and so forth.


(7 replies, posted in Sinclair)

Sadly not going to be anywhere near Leicester, but best of luck with your performance! Will there be a video recording, by any chance?

That seems quite unlikely. Did you install a shell? Are you running HT2 via the shell?

Aside from the tracks released in the beeper compo, DiHalt also saw the release of a new beeper music album by AER.

http://events.retroscene.org/files/dh20 … cdisk_.zip

As usual, all tracks made with Savage engine in AER's unique, quirky style.


(6 replies, posted in Sinclair)

Results are up on http://events.retroscene.org/dh2018/ZX_Beeper_Music

Congratulations, Tufty. A well deserved win after all those years of hard work. And congratz Shiru, too!

Ciao arottenbit,

Sadly the 82 Parcus is the most crappy of them all, had a lot of trouble getting it to work in the past myself.

Since screen capture works, I assume your setup is correct (using this driver, right?). First thing to check would be the batteries. They should be relatively fresh, but not completely full. About 80-90% charged would be best (contrast level 2-3). CPU speed on the 82 Parcus can vary wildly depending on battery strength, which can cause longer link ops to go out of sync.

Man, I hope we can get this sorted, would love to hear some calculator metal from you! big_smile


(4 replies, posted in General Discussion)

Yup, tesla coil music is great. I do regard it as a sort of sister scene, actually, because they are using some techniques that we're using as well. They seem somewhat centered on MIDI-driven covers rather than own creations, but on the other hand I've also seen very interesting experiments with PWM sampling, for example. And of course, lots of pulse frequency modulation. Would be nice to get some of these folks aboard here, but it seems they have their own hangout places already. And I don't have the resources to get into their world, either.


(7 replies, posted in Sinclair)

Wow, excellent and inspiring performance! I very much appreciate the innovation you're bringing to the 1-bit world.

Haha, achievement unlocked I'd say wink

For PCSPE, I'd be interested in porting it to LV2 some day. Not happening anytime soon though, I guess.

Oh, didn't know littlescale made a 1-bit thingy. Nifty!


(0 replies, posted in General Discussion)

I guess this isn't very interesting for most people, but since I'm currently putting a lot of time into the MDAL project, I thought  I'd post some updates about that here once in a while.


Last year saw the specification of the MDAL standard (standards, actually) and the development of libmdal, which eventually became the back end for bintracker. While the concept itself was reasonably successful, the actual implementation - surprise surprise - turned out to be too limited to support pretty much anything other than the engines that are currently available in bintracker. In fact, the current MDAL can't even support a simple engine like Huby. So, a redesign is needed.

New Standards

In the past months, I've been drafting new standards for MDAL configurations (MDCONF) and the actual MDAL module language (MDMOD). These drafts have now progressed to a state where I can share some details. First up, here are some links:

MDMOD v2 Specification Draft
MDCONF v2 Specification Draft

Obviously nothing is set in stone yet. However, I believe that the MDMOD specification is already quite mature. On the surface it still looks pretty similar to MDMOD v0, but there are a few major breaking changes. These were necessary to facilitate some of the more complex features provided by MDCONF v2. MDMOD v2 does add some boilerplate, but it also adds some syntactic sugar. Overall, it should still be quite human readable/editable even though the focus in v2 will be on machine processing.

The most notable change is that typing and scoping are no longer implicit. In MDMOD v0 you could write something like

  NOTE=a4, FX=fxtable1

and MDAL would automatically infer that "pattern1" is a block of type pattern and fxtable is a block of type "fx". In MDMOD v2, you will need to write this as

:PATTERNS(1)[pattern1] {
  NOTE=a4, FX=1
:FX(1)[fxtable1] {

The stuff in angular brackets is just a name and can be omitted. The good news is that, assuming the block type PATTERNS only provides NOTE and FX fields, you would also be able to write pattern1 like this:

  a4, 1

meaning the field names can be omitted. You still need to specify the field name if you only update some of the fields on the given step, though. Also, there's a new short hand for empty steps. This


becomes this:


Another big news is that sequences (now called ORDER) are now matrix sequences like for example in Famitracker. Garvalf really wanted this I think... and he was absolutely right that this is a good idea. Sequences are now entirely virtual, so in bintracker you will still be able to use the classic "glob" style (and in addition, the new matrix style or automatic sequences like in 1tracker). Also, syntax for sequences and blocks will be exactly the same in MDMOD v2. So, assuming we have a config that specifies something with 3 channels, you can write the sequence as

:ORDER {    // no need to specify the instance if there is only one
  $00, $01, $02
  $00, $01, $02
  $00, $03, $04

or you could write

  $00, $01, $02
  CH2 = $03, CH3 = $04

MDCONF v2, on the other hand, is very much a departure from v1. There is a much higher level of abstraction, with the aim to seperate the input from the output configuration as much as possible. I'm still very much in the process of working out the details, but it's starting to take shape, at least.

One of the most exiting news is that with MDCONF v2, you can define a recursive data structure. This will make it possible to support things like SID subtunes, or the SEQUENCE-CHAIN-PATTERN approach used by LSDJ and Slocum's Music Kit for the Atari 2600. Generally, the approach for v2 is to define input and output Groups (which are an entirely abstract construct), which contain any number of Fields (still derived from Commands like in v1), Blocks (patterns, tables, etc), and, most importantly, other Groups. Anyway, don't want to go too much into detail, as this is of course all super dry and theoretical. If you are really interested, read the specifiaction draft.

Where to go from here

I'm now a couple of months into designing a new libmdal to work with the v2 standards. The new lib is meant to be a fully-fledged tracker backend, so in theory it could be used to build trackers other than bintracker (though I doubt anyone will do it). I'm afraid there's still a few more months worth of work ahead of me, so don't expect to see the results any time soon. Once it's in a working state, I'm intending to write a dedicated GUI library to work with libmdal. Together with a few salvaged bits from the current bintracker, these will eventually become the new, all-powerful bintracker. Yay!

In any case, as mentioned earlier, nothing is set in stone yet. If you have any ideas, suggestions, questions, I'm more than happy to hear them.


(6 replies, posted in Sinclair)

DiHalt 2018 takes place 7-8 July, and as usual they'll have a dedicated beeper compo.


(5 replies, posted in Sinclair)

Ah, bummer. Well, y'always learn something new.
A google search for "spectrum +3 audio fix" turns up quite a few results though, so if you're handy with soldering you might be able to improve things.

Wow, excellent song! Not much of a Musical guy myself, but that's certainly some very solid work.

Very curious about that demo. Let us know if you need help with anything.