The mGB ROM is actually only 32k, the upper 32k are empty. I don't know why it has been padded to 64k.
When nanoloop receives a ROM for A or B, it waits till 32k are received and then starts the ROM.

If mGB or any other ROM starts but shows strange behaviour, that most likely has nothing to do with the transfer. If the ROM starts at all, that means the full 32k were transferred and you also can assume that data were intact. If bytes were missed, it wouldn't start at all but hang at the nanoloop boot screen, waiting for 32k to complete. If bytes were corrupt, the ROM would probably crash immediately.

And yes, for unknown reasons, you first have to press B in mGB.

258

(234 replies, posted in Nintendo Handhelds)

I assume you are on windows. If you're in a command window in the directory where you put the nlmidi tool an the update file, you just type

nlmidi03 -send nanoloop254.mb

and press enter. Then the program will ask you to turn on the Game Boy and press START+SELECT.

You don't need batch files, they just make things simpler. A batch file is a text file that gets passed to the command line when double-clicked. Instead of typing the command each time you use nlmidi, you type the command only once in a text editor (notepad) and save it as a batch file.

259

(234 replies, posted in Nintendo Handhelds)

Nlmidi is a command line tool, it doesn't work by just clicking it.

Open a console window, change to the directory where the nlmidi program is located and then type nlmidi03 -parameter. Available parameters are:

-midi
-sync
-send <filename>
-receive <filename>

To switch to midi or sync mode, you can use a batch file: Create a text file with content

nlmidi03 -MIDI
pause

and save it as midi.bat or sync.bat.

260

(234 replies, posted in Nintendo Handhelds)

I'm really glad to hear that.


Interim summary of this thead after 11 pages:

The adaptor works. There were/are issues, but they all turned out to be PC software glitches, including the nlmidi tool.

261

(234 replies, posted in Nintendo Handhelds)

In sync mode, yes. It also should ignore clock until a start message was received.

262

(234 replies, posted in Nintendo Handhelds)

The adaptor firmware is programmed as follows:

- wait for START
- send 0xff and 0x00 alternating on each CLOCK
- wait for STOP

Nanoloop does not support song position pointers or MTC cueing, just the plain analog-like clock scheme.

To me this still sounds like the device isn't in SYNC mode. What happens when you send additional MIDI data?

263

(234 replies, posted in Nintendo Handhelds)

No, there are no plans for a MIDI-nanoloop. You can load mGB on the nanoloop cart as extra ROM for MIDI stuff.

264

(234 replies, posted in Nintendo Handhelds)

Yes you can return the adaptor for an update.
Pending 2.5 orders will be shipped today.

265

(234 replies, posted in Nintendo Handhelds)

mariomustache wrote:

thanks oliver any planned midi input support?
i understand the device is only to sync the gameboy to say a sequncer from the computer so it plays intime with daw, but a midi input usb device or a buyable non diy midi in device for the gameboy is what im really looking for,

No. The nanoloop USB-MIDI adaptor does basically the same as Arduionoboy: Receive MIDI data and send them byte-wise to the link port. However, neither nanoloop nor LSDj support full control as a synth via MIDI. That's what mGB is for. mGB does exactly that and nothing else. As you can see in the test videos, both devices can be used to play the Game Boy as a MIDI synth with mGB.

Both devices have additional SYNC modes in which they filter the MIDI stream for clock signals and generate the appropriate clock pulses for nanoloop's and LSDj's native sync modes. Arduinoboy has additional modes for triggering LSDj with special MIDI events.

Otherwise, the only difference is that Arduinoboy is for a conventional MIDI cable while the adaptor is for MIDI over USB.


The adaptor is what you're looking for. Unfortunately, it's sold out.

266

(234 replies, posted in Nintendo Handhelds)

-no
-only sync
-no
-no

267

(234 replies, posted in Nintendo Handhelds)

concretedog wrote:

So Oliver...if my nanoloop is running slower than the MTC...do I need to do something regarding throttling??...To reiterate..it ain't useable as it is!

No, throttling is not applied when in SYNC mode.
As I wrote above, in a first test with a freshly downloaded Reaper on OS X, nanoloop was running at the same tempo as Reaper, and, as far as I could see / hear, it was also in sync. Will try on Windows tomorrow.

268

(234 replies, posted in Nintendo Handhelds)

akira^8GB wrote:

Could it be because it's under Windows 7?
I just tried the device on a Windows XP machine, of much lower spec, and the son of a bitch worked better!

I have no idea. I'm willing to test it, but not tonight.

Schedule for tomorrow:

- Test mGB + the adaptor on Vista (don't have Windows 7)
- Test on another OS X machine.
- Further tests with Reaper on different computers

269

(234 replies, posted in Nintendo Handhelds)

Quick Reaper test:

I set "nanoloop MIDI" to "Enable+Clock" in preferences > MIDI devices, inserted a new MIDI item, set it to loop mode and clicked play. I have no other sounds coming out of reaper, but the playback cursor seems in perfect sync with a 4/4 test beat in nanoloop.

This was after a fresh install, I have not touched any other settings for MTC etc.

270

(234 replies, posted in Nintendo Handhelds)

Your recording sounds like the delay may be coming from the computer's OS. Like if there was some harddsik access that slowed down the system so that USB packets were queued in the range of seconds.

271

(234 replies, posted in Nintendo Handhelds)

The same project with the adaptor, at the default throttling (26):

272

(234 replies, posted in Nintendo Handhelds)

I tried your test project and could not hear any difference to the Arduinoboy version. Will post the video here when upload is done.