17

(37 replies, posted in Trading Post)

Will there be a second batch? PLeaSE

MML export would be great feature smile

Actually, when one thinks about it, better compression just means more songs lost in cart crashes smile

I am not sure how meaningful it is to write a checksum. What to do if checksum compare fails? The song is still broken.

I have considered putting in some better compression... (maybe lz77?) ...but in practice I think RLE does a good job enough, it's very fast, consumes almost no memory, and is very simple (= easy to verify there are no errors).

> 1) Check that block switches ($e0) are valid. The parameter must be > (the current block) and < $1f. Or constants $f0/$f1 for default instr/wave, or $ff for EOF.

In hindsight, having the block switch command seems totally redundant. Since one already has the list of blocks in the block allocation table, one could just look there for where to decode next... I would consider removing it if it wouldn't break backwards compability.

alexras wrote:

I don't want to waste my time writing scripts that nobody's going to use,

I think maybe the biggest problem is the "script" part. In my experience, most people don't even know how to run a script... some kind of GUI application or web page is usually more appreciated.

It could be that you are right. But this is not part of the official format so... nothing is guaranteed smile

4) Another thing you can check, which is the only thing in this list that I don't check in LittleFM, is that the default instrument/wave commands are at output positions that are actually possible. I.e. the instrument command can only output data at positions $3080, $3090 and following aligned addresses. Likewise, waves must be written to $6000, $6010 and so on.

It is actually entirely possible that you have this data in other locations aswell.

I'm not really sure - maybe one option is to try it out with some old tried and true version...
About wiring, you could always try to beep it with a multimeter...

But, this keyboard reading is really a dirty hack - it's a miracle that it works at all - not following any standards or so. So I would not be surprised if it's not 100% reliable...

It sounds 100% likely that either is a problem of hardware or software smile

27

(28 replies, posted in Nintendo Handhelds)

Yes, the transpose column in tables changed for noise channel, after some serious consideration.

28

(28 replies, posted in Nintendo Handhelds)

I suppose you mean this...

2009-07-26: v3.9.e

* make noise table transposes relative to the instrument shape, instead
of relative to the current shape (as is with S command). (thx nitro2k01)

This was after some discussion on LSDj user list, there seemed to be a use for a transpose that was more "fixed". (not relative change from current value, but from instrument value)

29

(28 replies, posted in Nintendo Handhelds)

What's transpose ignore? I don't understand what you are talking about.

A lot of LSDj versions have been broken... however keyboard sync should be repaired with latest versions (4.1.0 and 4.2.1)

xero wrote:

it would be nice to at least be able to hold the copy paste data even when switching songs.

It does this already.