rvlt
-
Posts
164 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by rvlt
-
-
I forgot to commit this file - it's available now.
Great! :smile:
I will release a new version with EVENT_KB (will allow to define a velocity curve via a map) + calibration for AINSER inputs tomorrow.
Best Regards, Thorsten.
Cool, though I have to buy a new MCP3208 to try this. I accidentally destroyed two of them today... :sad: :sad:
-
Hey,
today I accidentally destroyed two MCP3208 while working on my midi-keyboard. At first I thought some electrostatic voltage was the reason for this, but then I investigated further and realized that I had a strange +28V voltage measured between GND and the metal case of my controller.
Ok, here is the setting:
- I have a keyboard controller case with a metal top. It is powered by an internal PSU which gives me a clean +5V for the LPC17. On the mains connector the two AC lines and the GND are connnected to the PSU, and the GND is also connected to the metal case.
- the PSU output is GND and +5V and is connected to J2 of the LPC17. The USB power option jumper and J1 are not even stuffed on the board. As mentioned on ucapps I made a bridge between the outer pins of the missing 7805. The LPC17 and all connected boards, pots, displays etc. run just fine.
- When I connect the LPC17 to a (battery powered) macbook via USB everything is still running fine.
- But as soon as I connect my apple power supply to my macbook, I measure +28V between GND on the LPC17 (or Ainser64) and the metal keyboard case. I just realized that because a GND wire coming from the AinSer64 was touching the case and destroyed the MCP3208 on the AinSer board, two times ...
When I deconnect the macbook's PSU the voltage is gone.
-> Where is my error? Has anyone an explanation for this? Is the keyboard PSU faulty, or the apple PSU, or my macbook?
The solution for me is pretty simple atm, because I don't need the USB connector on that keyboard, so I could simply desolder it, although it is handy sometimes to quickly connect it to a computer.
But If anyone could shed some light into this, please let me know.
-
A new version is available - let's check if MBNG is fast enough to scan velocity keyboards as well :smile:
Hey,
I tried it with my keyboard yesterday and all I can say is it works perfectly. No noticeable latency difference compared to MB_KB or to the original keyboard controller.
Cheers
Lars
-
I have another feature request:
It would be great to use some of the onboard-ports of the LPC17 as additional I/Os with MB_NG. TK already confirmed that J10 will be available for standard digital inputs, and it would be really handy to use J5a/b or J28 as digital outputs as well.
Today I realized that I need one (!) additional dout pin for connecting a LED, so instead of adding another DOUT board (or breadboard one), it would be much easier to simply use J5or J28 directly.
-----
BTW can anybody confirm this: I have a 3-digit LED connected via two shift registers on a DOUTx4:
SR1 D0-7 are connected to the segments
SR2 D0-2 are connected to the commons (no resistors installed)
so SR2 D3-7 are free, but I can't use them for connecting "normal" LEDs, right?
Cheers
Lars
-
Hey,
here are my two controllers:
>> Mini Controller (1x LCD, 1x Encoder, 8x analog Pots@AinSer, 3x Switches)
Event Pool Number of Items: 12
Event Pool Allocation: 723 of 24576 bytes (2%)
>> Tascam Remote (1x LCD, 1x Encoder, 66x small buttons via matrix, 9x big buttons via direct DIN)
Event Pool Number of Items: 92
Event Pool Allocation: 6284 of 24576 bytes (25%)
but this is not finished yet, still 137 LEDs via MAX7221 and 3x 7-Seg LED to do.
-
Ah, right, I just saw the config parameters in your configuration example. Perfect.
Now if only DHL's latency would be less than 7 days... :rolleyes:
-
Great!
I'm desparately waiting for another two LPCXpresso boards, I don't wont to rip apart my other controller again. But I will try this as soon as I get them, hopefully tomorrow...
btw, provided that the keyboard extension works well, will you incorporate the calibration procedure for the mod/pitchwheel as well?
Lars
-
Perfect, thanks!!
-
Yes, I can support the MAX7221 - now where we've generic configuration commands, it isn't a big problem for me to change the purpose of a DOUT_MATRIX by providing additional parameters.
regarding the possible MAX7221 support: do you already know which port of the LPC17 you will use for this? AFAIK it needs a DATA IN, LOAD/CS and CLK (besides 5V and Gnd).
I'm not in a hurry, just wondering how I do the internal wiring of my controller.
Cheers
Lars
-
If there are two cables with DIL16 headers coming from your keybed, I'd say yes. Just order a DIO_Matrix module and give it a go.. ;)
-
"Meifa CO., Ltd. © Copyright Keyboard-R" is printed on the backpanel.
Maybe it's a Fatar clone or something..
-
Hey,
I've managed to install MB_KB today. I spent half a day to measure the matrix layout / connections of my old miditech keyboard, just find out that ....
... the two cables with DIL16 headers coming from the miditech match exactly the two DIL16 sockets on the DIO Matrix. So it is a 1:1 connection, I didn't have to resolder a single cable!!! That was really PLUG'N'PLAY!!
Could have saved my about 5 hours if I just tried to connect them and see what happens, but anyway... :rolleyes:
So far everything's working great. Ready to try MB_NG+KB ... :smile:
Cheers
Lars
-
I can confirm that these LEDs and encoders from Segor Electronics (Berlin) work fine:- LED 3mm rot diffus 630nm 50mcd/20mA--> 6 Cent each for 100+)- PE16C-4015F-N0024 (Drehencoder 24/360' +Gew. D-Achse,h=21mm,nichtrast.)--> 2,32 Eur each for 10+)
-
Hard to tell in theory. Do we have any numbers of other (commercial) midi keyboards to compare with? For me an added latency of max. 1ms still sounds fast, at least for normal (non-percussive) keyboard operation.
I'm thinking of a real world example: Say you want to build a midi keyboard with a few pots, encoders etc., so you add a LPC17 with MBKB software for super low latency. Then you add another LPC17 (with MBNG) for the rest of the controllers. If you want to use only a single USB port (for convenience) to connect your computer, you would have to merge (e.g. via Midi I/O #4) the MBKB midi data with the MBNG controller data in the MBNG, right? Would this process also add latency, maybe even more than 1ms?
So from this point of view a merge between MBKB and MBNG would be much more convenient, and performance-wise on the same level.
But this is all (my) theory, maybe it's best to try it out: If we'd have a beta version of an KB-enhanced MBNG, we could compare these two and see if it "feels" different.
(BTW I'm just waiting for my DIO_Matrix module to arrive from Smash_TV, than I'll try MBKB asap..)
Cheers
Lars -
The calibration feature for the wheels sounds great! Will an AINSer be supported for this as well? I don't trust the onboard a-d conversion of the LPC17 so much..
Actually the wheel calibration is one of the main reasons I want to upgrade my existing controller keyboard to a MB KB version. I had to change the pots of my pitch- and modwheels because they were worn out. I put in pots with the same values, but since every pot has a (slightly) different curve, they don't send the full range of CCs anymore and the mod wheels is jittering now quite heavy. There is no way of calibrating this, so...
MB KB to the rescue! :smile:
-
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..
PSU issues with LPC17, USB, Macbook ...
in Testing/Troubleshooting
Posted
Thank you guys,
novski, there is no connection between these two points, they are isolated.
I tried a different approach today: I disconnected the switching PSU and instead used a simple transformer in conjuntion with the LPC17 onboard PSU (I put in a 7805...). But the result was the same: As soon as I connect my macbook PSU, there is a 28V difference between "LPC17-Ground" and "Earth/Chassis Ground".
I guess most people don't run into this problem because they either use USB power or external wallwarts.
To make this clear again: As long as these two grounds are isolated, everything is working fine. Maybe this is normal? Don't know, but it still sounds weird to me...
Anyway I won't use the direct USB connection from now on.