rvlt

Got 'em !! Thank you!

Ahh, I knew I regret not having taken your BLM board someday...

:thumbsup: Yes, snapshot is working fine now, thanks!! There is only one small problem left: in the middle of the (correct) snapshot values is some sysex data and two pitchbend values (-8192 at Ch. 9 and 13). I don't know were that comes from, maybe it's a configuration mistake on my side. This was in version 2.2d as well. But honestly this is not much of a problem in my case. Cheers Lars

Hey, I finally found time to play around with MB_NG tonight and I must say I'm amazed! So simple and yet so powerful. I love the new conditional labels. Great stuff! So far everything is working fine here: LPC17 + LCD 16x2 + DIN2x + AINSer8 (breadboard) I guess I have to upgrade my other MB64e soon... A couple of questions: 1. I'm thinking of upgrading my "midiboxed" Tascam controller which uses the MAX7221. Will this chip ever be supported by MIOS32 / MB_NG? I'm pretty sure the answer is no, but I'd better ask before planning something else. (a simple solution would be to leave a Pic8 core in there just for the LEDs/MAX7221 and connect that to the LPC17. I just hope there is enough space in the case..) 2. Is port J10 reserved exclusively for the SCS, or could this be made available for "normal" buttons, encoders... too? Could be useful for someone (like me;) who only needs a few control elements. Would save a DIN module. Cheers, and Merry Christmas to everybody Lars

Uh, sorry, didn't see there was already a thread about this. Anyway, I just did a quick test with both cards and adapters, and everything is working fine again (did this on OSX 10.6.8). THANKS! :thumbsup: :thumbsup: :thumbsup:

Hello, could anyone do me a favour and test USB mass storage mode (e.g. in MIDIO128 V3 or via USB mass storage application) in conjunction with the OSX Finder? I have a strange problem with that: when I activate USB mode in MIDIO128, my sd-card appears in the finder, but only after ca. 2min, then it takes another minute to read the directory content (40 files), and everything is super slow and unusable. The funny thing is that... -> I tried that with two different SD Cards with different adapters/cables (connected to J16 on a LPC17) -> they seem to work fine for MIDIO128: the config file got read, midi files play and I could save files -> they seem to work fine when I put the cards into my normal external card reader connected to my mac -> they seem to work fine when I use the new file browser tool in MIOS Studio 2.4.0 When I eject the cards via the finder, I get the following message on the LCD of the LPC17: !! HARD FAULT !! at PC=0x05f00120 Could it be that the USB Mass storage support is somehow broken with the new Bootloader? Because I recently upated to the newest version (V1 010). Thanks Lars

@TK sounds great! Btw, I have Bitwig studio running here on a macbook pro / OSX 10.6.8, but it will run on windows and even on ubuntu linux as well. @ilmenator thanks! my keyboard/controller is still running MB64e (which is assembler based, right?), so I can't modify this easily. But I will update this to LPC17 / MB_NG as soon as it is running well. Can't wait to try the MB_NG beta :thumbsup:

Hey, I have two feature suggestions for the MB_NG: 1. Since the MB_NG will support the logic/mackie control protocol, it would be nice if one LPC17 core would emulate multiple logic controls. Imagine that you want to build a 16 channel controller. With the old MB_LC each core would support only 8 channels per port (like the original), so you would have to add 2 cores, 4 midi cables... Since the LPC17 supports 4 midi ports (right?), is it possible to use one LPC17 for this (with just a single USB cable)? 2. Yesterday I spoke to some friends from Bitwig about midi controller support in their software, and I told them I'd love to see a possibilty to have preset names (e.g. from a software sampler) on my LC Display of my (midibox) controller. From what I understand it should already be possible to send that info via midi. Their implementation is based on Javascript, and it will be documented and free for everyone to adapt (their logic control support is already working btw). So what I'd like to see is a way to send midi data (CC, NRPN, Sysex...?) to a midibox controller to display characters on the LCD (GLCD, CLCD...). I hope this makes sense ;) Cheers Lars

A friendly bump :shifty: Any news on an updated MB64e? Would be great to see this working on my MB64e..

Thanks for making this clear, ilmenator. And yes, there is now definitely a PCB (and buttons) for sale from ilmenator. :whistle: Cheers Lars

Hi TK, just to be sure: Are you talking about this matrix? http://www.ucapps.de/mbhp/button_duoled_matrix.pdf Cheers Lars

Hi TK, I just read the part where the MB-NG is used for a DIY keyboard. Does that mean that the planned (direct) controller-support (pots, encoders, switches..) for the MB-KB project is stopped? If so, is there a technical reason for it or is it just an economic decision (save development resources)? How would you link the two cores? Simply via midi (bi-directional) or is there another way? cheers Lars

I will take two. Thanks for making this happen!!

How much current does this board draw now? The reason I ask is I want to put it in a controller (LPC17 with quite a few buttons and leds) which is powered by USB now, and I wonder if this would still be doable if I ad this PCB.

I would definitely take one board, too. Great project!

Great!! That is exactly the same that I was thinking of. SD Card Player and Mellotron is a perfect match, the lack of a looping function doesn't matter in this case, just like the real thing ;) Guess I have to build one, too... Cheers, Lars

Hard to tell, depends so much on personal preferences. But in my case I'd like to see the following external buttons/potis: - Arp on/off - Hold on/off - Tempo - Gatelength (maybe not important for everyone) If I had to build my controller from the scratch, then I would add the following: - Range switch - Mode switch/rotary So basically the same stuff that's in my Juno6 which I use quite often. So simple, effective and you can play around with it in realtime. Cheers.

@Duggle: Thanks, will try this out, hopefully tomorrow... @NorthernLightX: Have you already tested/measured it? My controller-keyboard is also based on an old Midiplus49 keyboard, but right now I'm too lazy to rip it all apart for measuring. Inside is a Mios8 Core and the original pcbs for the keyboard electronic. I would love to upgrade this to a single LPC17. ... and I have a feature request for MB-KB: What about a built-in, simple Midi-arpeggiator? Would love to see that! Cheers, Lars

Hey, I've got a question regarding the mod+pitchwheel: In most keyboards that I know both wheels are just normal potentiometers built into a special mechanical construction that allows the wheel to turn 90° (estimate..), so therefore they do not send the full 0-5V range but only ca. 0-1,7V. The Midi values at the Midi Out are still full range (0-128 or full 14bit pitch bend message), so I guess they get "interpolated" in the keyboard's firmware. What will happen if I connect such a mod+pitchwheel-construction to MB-KB? Is there a way that they send the full range of values? Best regards Lars

Thanks Thorsten! I will report back when I have something useful. Lars

Hi, has anyone an idea how to implement a "delay" or "lag" function for LEDs? Background: My Tascam Remote now "speaks" the Mackie protocol, and I want to make use of the signal LEDs found on the original hardware. According to the manual the host software sends midi channel pressure commands which turn on the signal LED for about 300ms. So, what i basically need is a function which turns the LED off after a period of time (without receiving any other midi message). Right now I have something like this: ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS when a complete MIDI event has been received ///////////////////////////////////////////////////////////////////////////// void MPROC_NotifyReceivedEvnt(unsigned char evnt0, unsigned char evnt1, unsigned char evnt2) __wparam { if( evnt0 == 0xD0 && evnt1 >= 0x01 && evnt1 <= 0x0C ) // receive Channel pressure for Ch.1 { STRIBE_SetLED(2, 2, 0x37, 1); // turns on LED ????; // some delay function... ??? STRIBE_SetLED(2, 2, 0x37, 0); // turns off LED } } I read some thread about people using SR_Service_Prepare to do that but I guess in my case this wouldn't work because all my LEDs are connected via MAX7221. I also fooled around with the MIOS_Delay but it didn't work. I guess I must use Timer or Tick but I have no clue how to do that. Best regards Lars

Cool. Will do.. ;)

Hi, could it be that the same bug made it into the MB64e as well? Because I also get all the CC messages set to zero every time I switch the box on (with snapshot_at_poweron enabled). I guess I'm using version 2.2d Best regards Lars

Hi Lee, that would be great! Unfortunately I can't test / help until I have my audio DAC. But I'll watch this thread closely... :thumbsup: Cheers!

Success!! I soldered 7221 on the board (was SMD but not as tough as I thought) and now I can access every single led. At first I left the DINs in parallel as they were before, and the behavior was exactly the same as with the 7219, but when I changed to a DIN>DOUT chain it worked. Mapping is still a bit weird (have to access stribe numbers 0,1,2 & 3, but I only have three 7221 at all), but anyway... :thumbsup: Best regards Lars