Jump to content

TK.

Administrators
  • Posts

    15,247
  • Joined

Everything posted by TK.

  1. Take the second one with 25mcd Some days ago I replied to a (really valid) question from Fairlightiii: I'm a bit unsure if the mcd value specified by Reichelt is the correct one. E.g. in the catalog the low-cost LEDs are specified with 8-32 mcd, but at the website the red one with 2,5 mcd The standard LEDs are specified with 1,3 - 5 mcd, and at the website the red one with 1,3 mcd Really confusing... so, is it a typo, and actually the low-cost LED has around 25 mcd? So - recommended value is now 10 or higher - and if they are 25 mcd, then even better! :) Best Regards, Thorsten.
  2. Thanks for the confirmation that it helped! :) Best Regards, Thorsten.
  3. An interesting usecase which I haven't considered yet. To make it as comfortable as possible, EVENT_SENDER (and EVENT_RECEIVER) can now be assigned to a radio_group as well. This could also be helpful for other purposes in future! :smile: MIDIbox NG V1.011 ~~~~~~~~~~~~~~~~~ o EVENT_SENDER and EVENT_RECEIVER can now also be assigned to a radio_group. This can not only be used in conjunction with BUTTON/LED radio groups, but also to distribute MIDI events to from receiver to multiple senders without forwarding chains (which then can be used for a different purpose) o the "sdcard_format" command allows to format the connected SD Card with FAT32 from the MIOS Terminal Take following test as an example configuration: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fbnkledcc.ngc Best Regards, Thorsten.
  4. Fine! :) My first assumption was, that the SD Card has the wrong format (no FAT32). Therefore I added a new "sdcard_format" command into V1.011 - which could be helpful in future Best Regards, Thorsten.
  5. TK.

    Display options

    I will come back to this topic this weekend. :) Best Regards, Thorsten.
  6. Yes, this is possible by using a map, see also mapbtn.ngc For your specific usecase try: MAP1 1 2 3 EVENT_BUTTON id= 1 type=CC chn=1 cc=16 button_mode=Toggle range=map1 Best Regards, Thorsten.
  7. Currently this would require a code modification in seq_ui.c, SEQ_UI_LED_Handler_Periodic() function (search for "sequencer_running") If more people are interested, I could provide this as an option. If you are the only guy who is interested: you know how to build the application by yourself... ;) Best Regards, Thorsten.
  8. You are (almost) right, thanks for the hint! The intended statement is "non-detented and various detented types are supported" (because there is only a single non-detented type) Best Regards, Thorsten.
  9. TK.

    Display options

    This was discussed but it's good to create a separate thread for this topic. I've prepared MBNG for 255 LCDs - but the electrical connections will be a challenge, because you won't be able to connect them in parallel without decoupling and "amplifying" the signals. Also the selection lines would have to be multiplexed - somehow - this will be difficult to handle. The RAM for the LCDs is limited to 512 characters, which means that 64 2x16 LCDs could be handled, or 32 2x16 LCDs, or 25 2x20 LCDs, or 12 2x40 LCDs (I don't want to count the GLCD combinations ;-)) /edit: buffer size has been increased meanwhile - see documentation: http://www.ucapps.de/midibox_ng_manual_lcd.html The LCD size configuration isn't implemented yet - and currently it's especially only possible to use 2 (G)LCDs with up to 64x4 characters. I will work on a more flexible configuration next year. The electrical part will be a challenge - it will probably require dedicated solutions depending on the LCD types being used. So: only recommended for experts who know how to develop the appr. circuits, and would directly implement & test the LCD driver by themself. Current state in v1.010: still only 2 E(nable) lines supported for CLCDs - I have to reserve some time to go through the detailed planning/implementation/documentation process - but my vacation is over. So, maybe next weekend ;) Best Regards, Thorsten.
  10. Weil es so einfach war, habe ich ^cursor, ^txt und ^txt56 in V0.010 eingebaut und released. Beispiel: LCD Messages # Note: we use ^txt56 instead of ^txt, so that the cursor will jump # to the next line after the 56th character has been reached EVENT_RECEIVER id= 4 \ type=SysEx stream="0xf0 0x00 0x00 0x66 ^dev 0x12 ^cursor ^txt56" ^txt56 ist also bereits eine Spezialbehandlung fuer das Logic Protocol. Falls noch weitere Extras erwuenscht sind, einfach bescheid geben. Was ich fuer meinen Anwendungsfall noch benoetige ist bspw. eine Cursor-Map, so dass die 2x56 Zeichen ueber zwei 2x40 LCDs (also 2x80) verteilt werden koennen (mit Spaces dazwischen). Das werde ich wahrscheinlich mit dem MAP Feature loesen, bei dem man dann fuer jede "Host-Cursor-Position" eine "physikalische Position" auf den beiden LCDs angeben kann. Ausserdem fehlt noch die Moeglichkeit, fuer graphische LCDs eine Default-Font zu setzen - kommt dann auch noch... Gruss, Thorsten.
  11. Excellent!!! :rofl: Meanwhile we can at least output received messages via SysEx @Koerby: I also added the ^# label terminator And my given example wasn't working perfectly with v1.009 - a small bar was print in addition on a label which didn't output any character - this is fixed as well in v0.010 Now you can write: label="^clr1^#Osc1^clr2^#Shape:^OSC_Shp" MIDIbox NG V1.010 ~~~~~~~~~~~~~~~~~ o SysEx: added ^cursor, ^txt and ^txt56 identifiers. They allow to send messages to the LCD via SysEx. A usage example can be found under cfg/templates/logictrl.ngc o Labels: ^# allows to terminate a label. E.g. "^label^#MyText" prints "MyText" directly after the specified ^label Best Regards, Thorsten.
  12. Hallo Chris, ja - falls es Probleme gibt, treten sie auch mit der NG Firmware auf. Das wird in Zukunft moeglich sein. Als Usecase sehe ich das http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftemplates%2Flogictrl.ngc'>logictrl.ngc template, bei dem noch die Unterstuetzung der LCD Meldungen fehlt, die von der DAW gesendet werden. Die Implementierung wird sehr wahrscheinlich so aussehen, dass man einen EVENT_RECEIVER scharfschaltet, der auf den SysEx-Header reagiert, und anschliessend mit ^cursor die empfangene Cursor-Position extrahiert (optional), den Cursor setzt und mit ^txt dann die restlichen Bytes bis zum F7 auf dem LCD ausgibt. RGB LEDs werden bereits voll unterstuetzt: mit Hilfe des DOUT_MATRIX Kommandos lassen sich DOUT Register fuer R/G/B definieren. Die Farben werden ueber den Wertebereich gemischt, also bspw. mit range=0:7 sind alle 8 Kombinationen direkt addressierbar. Dimmen wird evtl. mal moeglich sein, doch hier moechte ich nicht zuviel versprechen (ich muesste mir dazu erstmal die Hardware aufbauen...) Gruss, Thorsten.
  13. The label size is currently limited to 40 characters... :-/ However, it could make sense to optimize the size by using a label which is defined in your .NGL file. E.g. with following definitions in the .NGL: # clear first line LABEL clr1 "@(1:1:1)%20s@(1:1:1)" # clear second line LABEL clr2 "@(1:1:2)%20s@(1:1:2)" your label definition will be much shorter: label="^clr1 Osc1^clr2 Shape:^OSC_Shp" And while I'm writing this, I notice that a label terminator beside of space or ^ is missing - therefore I've added a space after ^clr1 and ^clr2, which you probably won't like. In the next version it will be possible to terminate the label identifier with: label="^clr1^#Osc1^clr2^#Shape:^OSC_Shp" Cryptic enough? ;-) Best Regards, Thorsten.
  14. It seems that this template is expired (it has been created many years ago) Could you please try this skeleton application instead? -> http://www.ucapps.de/mios/sdcc_skeleton_v1_1.zip The sources have to be compiled with the "make" command, see also: http://www.midibox.org/dokuwiki/doku.php?id=windows_toolchain_quickstart The usage of perl, "mkmk.pl" etc. is not required anymore. It seems that nobody maintains the old wiki pages :-( (I'm neither a Windows, nor a Codeblocks user) Best Regards, Thorsten.
  15. At the second time nothing will happen, because nothing has changed. You could send a Program Change outside the used range, and then the actual Program Change to trigger the pin. Best Regards, Thorsten.
  16. this is currently not possible, but I can consider this as a future feature. Would it be sufficient to define a couple of id numbers which should be triggered after a certain time to reprint their labels? E.g. something like this: # re-print following labels after 2 seconds inactivity: LCD_DEFAULT t=2 hw_id=Enc:1 hw_id=Enc:2 hw_id=Enc:3 (taking hw_id instead of id to ensure that the currently selected bank will be considered) Yes, the display can be cleared with %C It's also possible to clear a segment before writing to it by setting the cursor within the string, e.g. ... lcd_pos=1:1:1 label="%20s@(1:1:1)New Text" This will: - start at 1:1:1 - print 20 spaces - set the cursor back to 1:1:1 - write a new text (with less than 20 characters) Somehow I knew it, because your descriptions didn't make much sense anymore. However, as we can see small errors at my side can cause a lot of confusion at the user side - I hope that MBNG get's stable soon before more people are working with it, otherwise supporting different versions/effects will become very difficult. Ok, no problem. I'm sure that it will work now - you helped to clarify the only open topic where I wasn't 100% sure (nibblewise inversion). :smile: Best Regards, Thorsten.
  17. Could you please doublecheck that you are using v1.010_pre1? In addition: as mentioned earlier, it's expected that the inverted flag is set to the same value for DIN/DOUT_MATRIX statements which write to the same sr_dout_sel* registers. Best Regards, Thorsten.
  18. ok - in any case, the ground of the analog voltage domain has to be connected to J2:Vs of the core module. The grounds of these PCBs have to be connected together as well. Best Regards, Thorsten.
  19. That's the expected behaviour and related to the way how the matrix is organized. Please try blm16x4e.ngc - it shows, how to change the mapping at the software side. It's better to solve it this way, than adding a DOUT_MATRIX ... special_tweak_for_expired_design=1 option... :wink: Best Regards, Thorsten.
  20. Yes, your assumption is correct. The "radio button"-function of the DOUTs assigned to Program Change won't affect the remaining DOUT pins. Best Regards, Thorsten.
  21. The ground (GND) is available at the right upper corner of the http://xlargex.xl.funpic.de/projects/808/docs/808bdV1.0.pdf'>PCB, connect it to J2:Vs of the core module. Best Regards, Thorsten.
  22. Fine! :) Sidenote: it was intended that DOUT_MATRIX and DIN_MATRIX write to the same selection DOUT, see also the comments below: # 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... This also means, that the inverted flag has to be identical for the DIN/DOUT_MATRIX entries, and this might be confusing. In V1.010 the inversion (resp inversion_sel) flag inverts both nibbles again - meanwhile I know that buttons could also be connected after the sink drivers (proven with the MBSEQV4L frontpanel), which means that it isn't really necessary to add even more inversion parameters. Actually it also wasn't required to use separate DOUT pins for LEDs and Buttons in the BLM 16x4 design - I made this decision at a time I wasn't sure if the LED selection signals could influence the button behaviour... Best Regards, Thorsten.
  23. Ha - alright, finally I understand what was going wrong at my side: I opened my BLM case and noticed, that I added sink drivers some time ago. I haven't added them to the LEDs, but to the buttons (soldering error) - and this was the reason why I integrated the strange workaround with the nibble based inversion ;-) Could you please try: http://www.ucapps.de/mios32/midibox_ng_v1_010_pre1.zip the nibble-wise inversion has been removed, documentation has been updated, and in the configuration file I set inverted=0 again for all matrices. Although it would be nice-to-have, I won't add another parameter for nibble-wise inversion till somebody really need it. There are always simple HW based solutions which I could explain on case-by-case basis. Best Regards, Thorsten.
  24. Hi, does this mean, that Core0 is able to send MIDI events through the second core to your PC? Best Regards, Thorsten.
  25. A new version is available where a (hopefully easy to use) MIDI Learn mode has been added: MIDIbox NG V1.009 ~~~~~~~~~~~~~~~~~ o with a button assigned to 'type=Meta meta=MidiLearn range=0:1' it's now possible to activate a MIDI Learn mode which allows to assign an incoming MIDI event to any control element o with 'type=Meta meta=MidiLearn range=0:2' also NRPN events can be learned (in this case, CC#62 and CC#63 will be ignored!) o MIDI Learn mode can also be activated in the SCS menu Best Regards, Thorsten.
×
×
  • Create New...