Search options (Page 1 of 6)

Maybe I misunderstood something but shouldn’t you put the Arduinoboy at the ”5din” place in your picture, or was that how you meant?

The MIDI clock signal (24ppqn) is not compatible with the GB link clock pin (toggles at up to 500khz I think).

Maybe a long shot, but make sure you use a GBP/GBC link cable and not GBA. The pins are in the wrong order on GBA cables.

PriMieon: I did like this on a 32 pin GBA: soldered the positive capacitor leg to the power switch pin with a C above it and the negative to the ground pad to the right next to the switch.

I guessed which holes to use (close to the ones on the 40 pin instructions) and traced them to the power switch with a multimeter. Not 100% sure it’s correct but it reduced the noise a bit I think. If this is wrong please let me know, see it as an experiment for now .

Here is another method that I think seems better, haven’t tried it though. https://support.retrosix.co.uk/support/ … -gba-audio

Yes, I think that’s possible. If you want to disable the last two custom functions, change these lines like the comment says:

————————————————————
// Only 0-6 can be used. Set to 7 or greater to turn off a function and free up a CC.
#define VELOCITY_CC 3
#define TEMPO_CC 4
#define CHORD_CC 5
#define CHANNEL_CC 6
————————————————————

If you set CHORD_CC and CHANNEL_CC to greater than 7, these custom functions will be unavailable and the LSDJ commands X5_ and X6_ will send CC as usual. The CC# are configured in the midiCcNumbers list.

By default the CC values span the whole range 0-127 in steps of 8. So for your needs, send a value greater than 64 to enable, and less than 64 to disable something. E.g. X59=enable, X57=disable.

The values in that list are the MIDI CC numbers sent when you use the X command in LSDJ.
The four last ones cannot be used since they are overridden by my custom functions (velocity, clock, chords, channel).
The rest (1, 2, 3) can be used to send CC from LSDJ. You can change them if you want other CC numbers.
The second digit in the X command is the scaled CC value (will be multiplied with 8).
If you disable a custom function, then it will work as a regular CC.

Examples
X03  (CC#1 value: 3x8=24)
X12  (CC#2 value: 16)
X2F  (CC#3 value: 127)

No prob, let me know if you still have issues with killing chords.

There is no scaling between MIN_BPM and MAX_BPM. These are the bounds for tap tempo (when you ”tap” command X4y every beat) to avoid setting undesired tempos by mistake.
MIN_BPM is also used to set tempo the first time you tap X4y like this:
tempo = MIN_BPM + y*8

So use the closest BPM value the first tap and then let the tap tempo function find the perfect BPM by sending X4y a few more times.

I tested this on my rig today, N00 actually does kill chords for me. I would guess the reason we get different results is this:
N00 generates a MIDI note ON with note value 0. Some synths/drum machines may recognize this as a note OFF, others may see this as the lowest possible note or filter it out as an invalid note.

If this is correct, I can change so that N00 generates a note OFF instead. Or does anyone use N00 to reach the lowest note? I wouldn't want to break things. If nobody seems to do that, I'll probably change this in the next few days.