ilmenator

Strange, I have never had any issues like you describe with any of my three boards. I am using a paper knife, too - obviously, you want to cut from both sides, and you want to make sure that the cuts are deep enough, so you use the blade a number of times. Also, you will have to be careful so you don't loose control over where the blade is going. But isn't that just normal when handling a knife? Other than that, I don't think there is a real issue here.

No worries :tongue:

Well you correctly linked the connection diagrams for KB module and AINSER64 module - the answer is in there. I'll make it easy for you: The AINSER64 module connects to J19 on the LPC core board, whereas the KB module connects to J8/J9. So, no chaining possible / necessary.

With the octave keys, is it really necessary to have a two-octave keyboard? I am thinking of having this "module" sitting next to a TPD module, which is around 8cm wide and 9.5cm in height. Unless the keyboard is slightly "condensed", having a two-octave keyboard might get a little too wide overall?

That would be a luxury patch-name editor :shocked:

Look at the MIDI-OX homepage for some details on how to use it, e.g. in the FAQ.

Roel, alternatively you can go for a Ponoko or Formulor panel - it's even possible to have them lasercut a complete case for VERY little money.

Yes this is possible. Do a search here and you'll find a similar project, IIRC using the same device.

IIRC then it is in the lower right area of the board.

Turn the contrast pot for the LCD some and see if text appears.

Nice!

Sound like jittery AD conversion to me. Duggle offers a solution to this in his last post. You don't need to build a complete AINSER64, a single (well, 8-channel) subset will do - this will be available soon, see In the meantime, you could also DIY something according to this schematic.

Oh, I see. I was thinking of creating an editor for Mutable Instruments' Ambika synth, but the patch dump is larger than that, leaving about half of the parameters unaccessible. However, Ambika also provides direct access to its parameter RAM (kind of like the old basic PEEK). I'll see if I can make use of that instead.

The correct resistors' value depends on the LED and the brightness you want to achieve. Whether one uses 220 Ohm or 470 Ohm does not affect functionality in this context!

Have you checked here?

You should probably contact him directly and not via this forum. As far as I know he has a life as well. Have you checked his order status page?

I am trying to remote control a synth that can send its current synthesis parameters as SysEx blocks of data. This is handy because in theory it allows initialization of the NG event settings to the actual values in the synth. The synthesis parameters themselves can be controlled via NRPNs. However, the SysEx data sent by the synth is organized in nibbles. E.g., a parameter value of 63 is sent as 03 15 (0x03 0x0F), and 64 is sent as 04 00 (0x04 0x00). Is there a way to convert that into regular 7bit or 14bit values that can then be output by the NG? Something like EVENT_ENC id=1109 hw_id=9 ports=0000100000000000 type=NRPN nrpn=16 syxdump_pos=2:35 fails because it can only take into account the upper or the lower nibble of the value I'm after, as syxdump_pos points to a single byte in the ^dump only.

Good points, I see!

Maybe I can jump in here with a closely related question to TK: do you still have your stribe controller? Could that be a good target for MAX72xx integration into NG?

Indeed it does, thanks!

Yes, Inc01_Dec41 works. Attached is the MIDI implementation of the C4 Pro, the commands I'm after are on page 2, i.e. it sends: B0 00 01 B0 00 04 B0 00 08 B0 00 0C B0 00 0F B0 00 41 B0 00 44 B0 00 48 B0 00 4C B0 00 4F for increasing (upper block) and decreasing (lower block) values. Edit: attachment is too big, so I skip this... Edit 2: attachment is already.

This is great, thank you! I think there is something wrong with the Inc00Speed_Dec40Speed emu_enc_mode: right-turning (increasing) seems to work fine, but left-turning sets the value to 7F immediately, and that "locks up" the encoder / CC message until I save the .NGC file and thus init the NG app. Best, ilmenator

I don't want to spoil your party, but have you tried looking into a light bulb recently? :pinch:

Good luck with your sale - it would help if you told us where you are located!

Sure, no problem - I would recommend to use the latest bootloader version then, that is version 1.012 available from this page. Just use MIOS Studio to upload it as you would for any other application. For instructions on what to do exactly once the bootloader is in the core read on this page. Good luck!