e.s.c.: you can download the latest 2.5 ROM from www.nanoloop.com/usb. there is still a bug in the song mode though that causes patterns to be skipped / repeated when all rows are in 1/x tempo.
337 Aug 31, 2011 10:06 am
Re: Optimal nanoloop set up [Questions] (39 replies, posted in Nintendo Handhelds)
338 Aug 30, 2011 8:33 pm
Re: Optimal nanoloop set up [Questions] (39 replies, posted in Nintendo Handhelds)
About the DS flash carts wiping out nanoloop data:
I'm still not sure why this happens, but it's difinitely a bug in the R4 etc firmware, not in nanoloop. I have added some code that recognises damaged data and repairs them and this seems to have fixed the problem.
Writing to the flash memory is a complex set of commands that's hardly issued by accident, so R4 and others seem to try actively to write to some flash cart (that by coincidence contains the same chip as nanoloop 2.3) without asking.
My favorite Game Boy for nanoloop 2.x is still a white original GBA. There is some humming going on and the screen has no backlight, but it feels best in your hand. I never liked the laptop-like designs, from GBA SP to DSi. But of course sound-wise and also for graphics, especially in negative mode, DS lite is best.
339 Jul 22, 2011 9:11 am
Re: Nanoloop 2.5 issues solved yet? (12 replies, posted in Nintendo Handhelds)
I Just received note from the factory that the adaptor's PCBs were shipped today, so I can send them out next week (given this first run works as expected). There is indeed still a little bug in the song editor that causes problems when playing 1/x tempo patterns.
340 Jul 7, 2011 11:44 am
Re: Nanoloop 2.5 won't boot on NDS and GBA micro; also buzz problem on GBA (11 replies, posted in Nintendo Handhelds)
Hello
I'm sorry for all the inconvenience.
The issues that appeared with some 2.5 carts (sporadically missing sounds, sometimes nanoloop won't start) are due to a timing problem: In version 2.2, I had set the memory access times (wait sates) to a very low value in order to speed up processing. For 2.3, this setting was not necessary anymore, but it didn't hurt either, so the code remained there. The new chip used in 2.5 appears to be lesss tolerant to such tight timing so that some units occasionally fail. This can be fixed with a software update that sets the timing parameters back to standard values.
I will send out USB-adaptors to everyone as soon as they're ready (which, according to the factory, should be next week).
Oliver