ilmenator

Does the card work with other devices?

That is rather unusual and may be a sign of a low quality product.

Buy one of each and try them out!

That is totally up to you and only a question of personal taste. I for one like the detents - the input is digital (and thus quantized) anyways, so why pretend to be operating an analog device? Also, I don't believe that removing the detent of a new encoder adds to its expected lifetime...

Would it be possible to have the step LEDs (in my config the red ones) stay lit at the current position when I press the "PAUSE" button? Including in the connected BLM?

No, you can adjust that by varying the length of the spacers between frontpanel and PCB. My tact switches are the ones recommended I believe.

Click on 'More reply options' and you get the preview instantly. About quoting, it is not working hassle-free for me either. E.g. if I start editing the quote first, I usually cannot add my own text below the quote any more - the cursor just doesn't get there...

If I remember correctly I started my Ponoko 16x4 BLM panel design using the Frontpanel software and then converted that to PDF for import into Illustrator. When I get home today I will have a look if I can still find that file.

Well if you want your programmer to be "larger" than what the original Virus had to offer in terms of knobs and direct access then you want to go 64 knobs, I would think!?

So I soldered my BLM 16x4 board properly and can now confirm that v1.010_pre1 works as it should - thank you very much TK! It also means that the board has become more universally useful than initially thought. Too bad I sold all my protoboards :tongue:

Well now I feel stupid because indeed I was testing on v1.008. It looks much better now :rolleyes: . I do not have the LEDs soldered on my board yet, so analyzing this systematically is a bit difficult, but I still get two LEDs lit from single note on events - but let's just assume that that is due to the example config file for now. I cannot solder the LEDs before the case is ready, and that will not be tonight. Edit: apparently, that was due to another EVENT_LED_MATRIX statement present in the same config file. So I should confirm that the old 16x4 BLM is working!

Well then I must be overlooking something. When defining # In the SR configuration we assume that the DINs/DOUTs are directly connected to J8/9 of the core # they emulate button/led functions DIN_MATRIX n=1 rows=4 inverted=0 sr_dout_sel1=1 sr_din1=1 button_emu_id_offset=1001 DIN_MATRIX n=2 rows=4 inverted=0 sr_dout_sel1=4 sr_din1=2 button_emu_id_offset=1033 DOUT_MATRIX n=1 rows=4 inverted=1 sr_dout_sel1=1 sr_dout_r1=3 sr_dout_g1=2 led_emu_id_offset=1001 DOUT_MATRIX n=2 rows=4 inverted=1 sr_dout_sel1=4 sr_dout_r1=6 sr_dout_g1=5 led_emu_id_offset=1033 I get the LEDs to react properly, but the buttons send three note-on events each: [19329.809] 90 34 7f Chn# 1 Note On E-2 Vel:127 [19329.819] 90 54 7f Chn# 1 Note On C-5 Vel:127 [19329.830] 90 44 7f Chn# 1 Note On G#3 Vel:127 [19330.314] 90 34 00 Chn# 1 Note Off E-2 (optimized) [19330.324] 90 54 00 Chn# 1 Note Off C-5 (optimized) [19330.335] 90 44 00 Chn# 1 Note Off G#3 (optimized) is what I get for the first button (C-1). For # In the SR configuration we assume that the DINs/DOUTs are directly connected to J8/9 of the core # they emulate button/led functions DIN_MATRIX n=1 rows=4 inverted=0 sr_dout_sel1=1 sr_din1=1 button_emu_id_offset=1001 DIN_MATRIX n=2 rows=4 inverted=0 sr_dout_sel1=4 sr_din1=2 button_emu_id_offset=1033 DOUT_MATRIX n=1 rows=4 inverted=0 sr_dout_sel1=1 sr_dout_r1=3 sr_dout_g1=2 led_emu_id_offset=1001 DOUT_MATRIX n=2 rows=4 inverted=0 sr_dout_sel1=4 sr_dout_r1=6 sr_dout_g1=5 led_emu_id_offset=1033 the buttons work properly, but three LEDs light up at the same time, and they don't correspond to the note-on message. I must be doing something wrong, but what?

There is still an issue with the LED matrix part, though. The note numbers I send do not match with the LEDs that light up. My current config file looks like this, so I would assume that buttons and LEDs should share the same note numbers (even if they are not triggered internally): # test the configuration of a 16x4 Button/Duo-LED matrix # Schematic: http://www.ucapps.de/mbhp/button_duoled_matrix.pdf RESET_HW LCD "%C@(1:1:1)BLM 16x4" # In the SR configuration we assume that the DINs/DOUTs are directly connected to J8/9 of the core DIN_MATRIX n=1 rows=4 inverted=0 sr_dout_sel1=1 sr_din1=1 DIN_MATRIX n=2 rows=4 inverted=0 sr_dout_sel1=4 sr_din1=2 DOUT_MATRIX n=1 rows=4 inverted=0 sr_dout_sel1=1 sr_dout_r1=3 sr_dout_g1=2 DOUT_MATRIX n=2 rows=4 inverted=0 sr_dout_sel1=4 sr_dout_r1=6 sr_dout_g1=5 # note: actually the sr_dout_sel1 in DOUT_MATRIX could be removed, # since DIN_MATRIX already outputs the selection pulses there # this is just for the case that somebody copy&pastes the definition... # the left half of the BLM will send and receive Note On C-1 (key=36) .. G-3 over channel #1 # the right half of the BLM will send and receive Note On G#3 (key=68) .. D#6 over channel #1 EVENT_BUTTON_MATRIX id=1 type=NoteOn key=36 chn=1 lcd_pos=1:1:1 label="Matrix1 Pin %2p %b" EVENT_BUTTON_MATRIX id=2 type=NoteOn key=68 chn=1 lcd_pos=1:1:1 label="Matrix2 Pin %2p %b" # receive feedback from DAW EVENT_LED_MATRIX id=1 type=NoteOn key=36 chn=1 fwd_to_lcd=1 lcd_pos=1:1:2 label="Matrix1 Pin %2p %b" EVENT_LED_MATRIX id=2 type=NoteOn key=68 chn=1 fwd_to_lcd=1 lcd_pos=1:1:2 label="Matrix2 Pin %2p %b" # TK: I've 4 additional buttons connected to DIN#3 (hw_id=17..20), and 4 Duo-LEDs connected to DOUT#7 (hw_id=49..54) # send CC#16..19 with these buttons # and allow to control the Duo-LEDs with the same controllers EVENT_BUTTON id=17 type=CC cc=16 chn=1 EVENT_BUTTON id=18 type=CC cc=17 chn=1 EVENT_BUTTON id=19 type=CC cc=18 chn=1 EVENT_BUTTON id=20 type=CC cc=19 chn=1 # 0..31: Green LED: off Red LED: off # 32..63: Green LED: on Red LED: off # 64..95: Green LED: off Red LED: on # 96..127: Green LED: on Red LED: on # -> not working yet!!! Green LED will be on if value >= 64! EVENT_LED id=49 type=CC cc=16 chn=1 range=0:63 EVENT_LED id=50 type=CC cc=16 chn=1 range=0:127 EVENT_LED id=51 type=CC cc=17 chn=1 range=0:63 EVENT_LED id=52 type=CC cc=17 chn=1 range=0:127 EVENT_LED id=53 type=CC cc=18 chn=1 range=0:63 EVENT_LED id=54 type=CC cc=18 chn=1 range=0:127 EVENT_LED id=55 type=CC cc=19 chn=1 range=0:63 EVENT_LED id=56 type=CC cc=19 chn=1 range=0:127

The problem actually remains the same - it was not that there was nibble-wise inversion, but that buttons and LEDs share the same DOUT SR - the buttons use the upper nibble, the LEDs the lower one. I have to deactivate either the button part or the LED part to make the other work properly. What I was suggesting was to add a parameter that would make it possible to specify whether the whole SR, or only the upper (or lower) nibble should be used for the scanning. I don't know how much effort that means implementation-wise, but it would allow the use of the original 16x4 BLM as used in SEQ V4, according to this schematic. Well, I still used the old .NGC file with the DOUT_MATRIX inverted - sorry, now it is working properly!

Confirmed. Commenting out the DOUT_MATRIX lines configuring the LED matrix makes the button matrix work like it is supposed to: # DOUT_MATRIX n=1 rows=4 inverted=1 sr_dout_sel1=1 sr_dout_r1=2 sr_dout_g1=3 # DOUT_MATRIX n=2 rows=4 inverted=1 sr_dout_sel1=4 sr_dout_r1=5 sr_dout_g1=6 So I guess to get this running we would need another parameter to configure :unsure: !?

As far as I understand, only these two lines are required to configure the button part of the matrix: DIN_MATRIX n=1 rows=4 inverted=0 sr_dout_sel1=1 sr_din1=1 DIN_MATRIX n=2 rows=4 inverted=0 sr_dout_sel1=4 sr_din1=2 So here is what I have in hardware on my board: The left part of my matrix (8x4 buttons) is connected to DIN SR1 (pins D0...D7) and the second half of DOUT SR1 (i.e. pins D4...D7), with the cathodes of the diodes pointing towards the DOUT SRs. Pins D0...D3 are connected to the cathodes of the LEDs of that matrix. I suspect that the latter might be the problem? Upon repeated button presses I get different Pin numbers in the LCD, with an offset of 8: so e.g. for a certain button it is either Pin 1 or Pin 9 that gets displayed. In the manual of MB NG it says: "rows=4: 4 selection pulses are output by the DOUT register specified with sr_dout_sel1. The pulses are available twice: at D7:D4 and D3:D0 (inverted!)." Hmmhhh?

Well, something is strange - I guess the config file does not match this schematic?

Is that the result with or without the ULNs installed?

Sorry my setup is currently not working - I had to move some stuff around the house, but I'll look into this asap.

Aesthetics is one criteria, another one is ergonomics. In that respect I still find the Waldorf knobs suboptimal. For encoders I'd prefer knobs that measure less in diameter than the Waldorf ones.

That's not the way it works. Try sending a PM to the original initiator of the bulk order and see if there are spares.

I have received my boards today - thanks a lot!

Thinking this to an end, one would also need some kind of status display to know which bank is currently selected - per row. Making it complicated (implementation-wise) this could be indicated by a 1- or 2-digit 7-segment LED. Making it easy, this task could just be taken over by the first (or actually, any) encoder with LED ring in each row. Then it boils down to a purely software-implemented feature and the hardware could stay exactly as it is now on Jerome's board.

I see - that makes total sense if there is a transparent plexi window. Sigh... That's the benefit of large quantities. Having a single Lexan sheet printed is SO expensive.

Yes, but is there a layer of transparent Lexan on top of the window, or is the Lexan cut out where the window is?