Search options (Page 10 of 13)

That's even more great news! How many units did you do? Those 9 on the picture?

Stuff like this certainly makes me inspired to work further on a defMON II.

Hi! I managed to track down the bug now thanks to your report. Not sure exactly when I will have the time to actually fix it, but at least it is within reach now. I won't do any promises here, but hopefully I'll fix it within a week or something.

A command to change the multispeed setting is — unfortunately — not very likely to be included since the multispeed stuff is actually handled by the editor (e.g. by the code that calls the player code) rather than the player code itself. Therefore such tunes wouldn't work when played outside the editor, e.g. after packing them. It is a reasonable request though and of course I see that it could be useful in some ways if it would have been implemented.

Hi!

Not sure why one would use such an old version as 20090304 (8 years ago) at all? In general it is advisable to always use the latest build.

Regarding the pattern end-marks, I've noticed this bug from time to time as well. However, it very rarely happens to me myself, whereas for some ppl it seems to happen more often. This bug really confuses me and I'd be happy to get more detailed information that could help track down when it actually happens. The way you describe it here, you seem to imply that it *always* happens to you? Is that really true?

About copy+paste after loading/saving tune, I haven't experienced that myself. Again I'd be happy to get more detailed information on when this might happen. It sounds like something that could be related to the first bug, e.g. that the copy/paste routine freaks out when no pattern end-mark is encountered.

Not at the moment, but it is not entirely impossible that it might some day. It wouldn't be an awful lot of work to make defMON work with an interface like that (if I'd only find the time). I'm not making promises though.

What you're linking to is a standard MIDI interface for the C64 and they are quite straightforward to use from a coder's point of view. There is a whole family of MIDI interfaces for the cartridge port that all more or less work the same way. You can see a list of those interfaces here, and the DATEL one is included there:
https://codebase64.org/doku.php?id=base … interfaces

Just a few years ago there was also a MIDI cart called something like Kerberos MIDI developed, but it is now sold out. That one was also similar to the midi cartridges listed on that codebase page if I remember correctly. Not 100% sure though as I never really looked into that one.

The only "problem" is that in these days most people use something like a 1541 Ultimate cartridge or similar that occupies the cartridge port, so from that point of view using the cartridge port for MIDI connectivity isn't really desirable. This is also the main reason for making that defMON sync interface for the user port instead, since that one is not used by other hardware on most people's C64 setups.

There are also other benefits of having a cartridge like Action Replay, Final Cartridge or Retro Replay in the cartridge port (which is what you would have if you've got a 1541U2 sitting in the cartridge port). For example, defMON makes use of the built in fastload/save routines in these cartridges if they are present. That makes loading/saving tunes a whole lot faster.

Personally I'd much rather see new batches of Scannerboy's sync interface. That one was affordable as well.

I don't have one to sell unfortunately, but just wanted to make sure that you've seen the following:

Would be nice if enough interest for a new batch was generated.

By the way: I think I fixed the defMON wiki to work as it should again.

//FTC

Since defMON is an editor for the Commodore64 and its SID chip, it most definitely won't work on an Atari ST or produce SNDH files. Just had to point that out.

I added a little section on the defMON wiki about the little known "Super Command" mode of defMON:
http://toolsforscholars.com/defmon/doku.php?id=start

It is very brief, but it may at least give a little hint about how the Super Command mode works.