TK.

Hi, the AOUT module option integrated into MB64 was made at a time where neither the MBCV firmware, nor the MBHP_AOUT_NG module was available. Today I should probably remove this option to avoid unnecessary confusion (and/or the hope that gates could be provided as well, etc.) I think that the better option for your usecase is a modified MBCV firmware with support for up to 64 pots, up to 128 buttons, and up to 128 LEDs (resp. 120 LEDs, as 8 DOUT pins will be required for the gates if J5 is allocated by AIN modules) This will work under the assumption, that Numerology allows you to configure the MIDI events assigned to these control elements at the software side (at least via MIDI learn). This option will give you the advantage, that only a single core module will be required (-> easy MIDI setup), and that you will get all features of the MBCV firmware (like different output curves, polyphony, storable setups) which are probably not provided by Numerology itself. I can give you the appr. code snippets, and/or could even release precompiled .hex file - but I would need more informations about the MIDI setup capabilities of Numerology. E.g., are buttons/LEDs supported? How many? Does Numerology allow to to send/receive MIDI events to the control surface over different MIDI channels to avoid conflicts with the channels used for CV/Gate? Best Regards, Thorsten.

Hallo, sehr wahrscheinlich ist eins der beiden Kabel zum DIN Modul nicht richtig angeschlossen, oder das DIN Modul selbst hat einen Wackelkontakt. Tritt das Problem denn nur bei einem Encoder, oder bei allen und/oder auch den Tastern auf? In diesem Fall muesstest Du die Verbindungen zwischen Core und DIN Modul ueberpruefen, siehe auch http://www.midibox.org/dokuwiki/doku.php?id=din_module Falls nur ein einziger Encoder betroffen ist, reicht es, die Spannung an den beiden DIN Eingaengen nachzumessen. Beide sollten zwischen 0V und 5V wechseln wenn Du den Encoder drehst. Falls an einem Eingang die Spannung permanent auf 5V steht, weisst Du, welches Kabel nicht angeschlossen ist. Gruss, Thorsten.

_BLM_PrepareCol ; (for C) BLM_PrepareCol ;; increment column SET_BSR blm_selected_column incf blm_selected_column, F, BANKED bcf blm_selected_column, 3, BANKED ; wrap at 8 ;; select next DOUT/DIN column movf blm_selected_column, W, BANKED call MIOS_HLP_GetBitANDMask ; (inverted 1 of 8 code) ;; finally apply inversion mask (required when sink drivers are connected to cathode lines) xorlw BLM_CATHODES_INV_MASK movwf MIOS_PARAMETER1 ;; output on CATHODES* registers #if BLM_DOUT_CATHODES1 movlw BLM_DOUT_CATHODES1 - 1 call MIOS_DOUT_SRSet #endif #if BLM_DOUT_CATHODES2 movlw BLM_DOUT_CATHODES2 - 1 call MIOS_DOUT_SRSet #endif ;; store row*2 offset in IRQ_TMP1 to simplify the addressing of blm_row_green and blm_row_red array SET_BSR blm_selected_column movf blm_selected_column, W, BANKED rlf WREG, W andlw 0x0e movwf IRQ_TMP1 [/code] You also have to adjust the array sizes: [code] #if _BLM_NO_DEBOUNCING == 0 _blm_button_debounce_delay res 1 blm_button_debounce_ctr res 128 #endif blm_selected_column res 1 blm_button_column_ctr res 1 blm_button_row_values res 16 blm_button_row_changed res 16 _blm_row_green res 16 _blm_row_red res 16 If assembler looks like voodoo for you, just have a look into the appr. MIOS32 implementations: BLM: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fmodules%2Fblm%2F and a more generic BLM driver provided by This (it also supports your 16x8 configuration): http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fmodules%2Fblm_x%2F The upcoming BLM_SCALAR firmware (for PIC and STM32) will provide 16x8 and 16x16 duo LEDs. So, if you don't manage to adapt the current BLM driver, just wait for the updates. Best Regards, Thorsten.

Hi, welcome to the forum! :) These topics are (partly) discussed in following threads: 1) 2) Addendum to 2) so long all LED rings should be dimmned from the same PWM signal, it will work. This is a simple programming example (for MIOS32) which demonstrates how to generate the PWM from a single timer IRQ: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F007_mios32_timer%2F there is another (somewhere...) which demonstrates how to generate independent PWM waveforms by using modulo operations (not recommented for PIC) Best Regards, Thorsten.

Why did you receive an upload request (F0 00 00 7E 40 00 01 F7) at the beginning, and additional upload requests (F0 00 00 7E 40 00 01 F7) at the end? Could it be, that you haven't installed MIOS yet? These are the expected messages sent by the core: 00000000011055 ms | SysEx: F0 00 00 7E 40 00 0F 1C F7 00000000011159 ms | SysEx: F0 00 00 7E 40 00 0F 60 F7 00000000011264 ms | SysEx: F0 00 00 7E 40 00 0F 40 F7 00000000011444 ms | SysEx: F0 00 00 7E 40 00 0F 24 F7 00000000011630 ms | SysEx: F0 00 00 7E 40 00 0F 19 F7 00000000013934 ms | SysEx: F0 00 00 7E 40 00 01 F7 00000000015831 ms | SysEx: F0 00 00 7E 40 02 01 F7 [/code] Best Regards, Thorsten.

Indeed this is strange. It seems that you are doing everything correctly. The only explanation I have is, that you are not using the original .hex files which I released under http://www.ucapps.de/mios_download.html but something else. Did you build the files yourself, or did you rename the files? Please download the change_id package again to be 100% sure that you are using "known working" binaries. And I also recomment to pull the other PICs out of the sockets so that you are 100% sure that only the first core receives/sends SysEx messages. Has anybody else successfully used the change_id application in the last weeks? Best Regards, Thorsten.

Thanks Simca, this is really a sufficient demonstration that you own the knobs! ;) Yes, we should move this thread to the bulk order section - done. Best Regards, Thorsten.

Could it be that you forgot to route the MIDI Out correctly, so that you always get the response of the first core? Best Regards, Thorsten.

If you've luck, it will work with the DEFAULT_SRM_* feature, which is described in the setup_*.asm file You have to assign a free DIN and DOUT register, buttons will be available with SR=16+1..16+8 in CS_MENU_DIN_TABLE thereafter. If this doesn't work, you will have to do some experiments with the sm_example1 application which is available at the MIOS download page (programming knowledge required). Once you found out, how to scan the buttons correctly, we could try to integrate the required changes into the MBSID firmware. Best Regards, Thorsten.

This isn't the first time you are asking these questions, and I already gave you the answers (no, it this isn't supported by the driver) Best Regards, Thorsten.

...or change the way how you download files. A single click will download and unzip the file into the Downloads folder. The .jar File won't be unpacked in this case. The layout will be automatically stored when you exit MIOS Studio properly. Don't use Cmd-Q (like for other Mac applications), but use File->Exit Best Regards, Thorsten.

"ww kabel 1" ist just a test that we are able to rename the ports again!!! :thumbsup: Please say "vielen dank" to Ploytec support! :ahappy: Best Regards, Thorsten.

Of course! Thanks! :) Best Regards, Thorsten.

Vista/Win7 users: please try this version: http://www.ucapps.de/gm5/midibox.org_gm5_WIN32_1.0.10.zip (32bit) http://www.ucapps.de/gm5/midibox.org_gm5_X64_1.0.10.zip (64bit) Best Regards, Thorsten.

Hi Simca, I don't mean this as a personal attack against you, but there is a certain danger that Newbies we don't know use this forum for fake deals or as a commercial platform. By answering to this topic, you demonstrated that you are not an automated forum robot - great! ;) Could you please also post a picture of the Knobs next to your MIDIbox to show us, that they are real? Best Regards, Thorsten.

Newbie alarm... Best Regards, Thorsten.

Unfortunately Ploytec isn't able to reproduce this issue. Something must be different at our side. Therefore I'm asking again: is there any Vista/Windows7 user who got the new driver release successfully running? And to the users who noticed this issue: which configuration (J1/J2/J3/J8 switches) are you using exactly? Best Regards, Thorsten.

Hi, Most simple solution: just upload the MIDIO128 application :) You will find some additional troubleshooting tips for the DIN module here: http://www.midibox.org/dokuwiki/doku.php?id=din_module Best Regards, Thorsten.

I consider to write a benchmark to determine the true speed under MIOS32, since there is no standard for rating SD Cards - as you noticed, "60x" is just a housenumber - It's printed on a noname card that I bought from a supermarket some time ago, and the speed was comparable with the SanDisk SD Card which I'm normaly using. I've another noname card (2GB from Reichelt), which is extremely slow, especially when writing files. No speed infos are print on this card... Some kind of "benchmark" is already part of the firmware I gave you. Nothing is more realistic than directly comparing how long it takes to load a pattern or to process the FAT. :) Best Regards, Thorsten.

:) Could you please upload following firmware: http://www.ucapps.de/tmp/mbseqtest.zip Toggle between the patterns until you notice the glitch again. Thereafter go to the "About this MIDIbox" page, and dump out the System and SD Card informations to the MIOS Terminal (part of MIOS Studio). This firmware uses the Stopwatch to measure the time between Pattern changes. If it takes too long, I've to adjust the timings. Otherwise I need more informations how to reproduce this. E.g., if this happens while switching between two certain patterns, then write them into the preset directory (Track Events->Presets->Save as New Preset") and attach the files to this article. Best Regards, Thorsten.

Beta14 is available: o prepared support for MBHP_BLM_SCALAR. The MIDI port can be configured in Options menu (Utility->Opt.) o various minor bugfixes [/code] Link to BLM_SCALAR emulation (Mac OS Leopard/Snow Leopard only) http://www.ucapps.de/mbhp/blm_scalar_emulation.zip Setup: MIDIbox SEQ: select the MIDI port to which the BLM is linked in the Utility->Opt. page with GP Encoder #16 Emulation: select the same MIDI In/Out port The matrix should be updated automatically. Try different dimensions - 64x16 is a really useful configuration. Currently we have display buttons for Triggers (e.g. Drum patterns), Tracks and Patterns. One function that I'm planning to add next is the possibility to display Accents in the trigger page with the Red LEDs, and to activate accent by pressing "Triggers"+BLM button. Gridracer: it would be interesting if your BLM configuration is still working, since I had to change a lot of code which is also used for common 16x4 BLMs directly connected to the core. Best Regards, Thorsten.

It's the big advantage of the MIDI event scheduler, that even such features are possible now :) Not really, it should work in pause mode. I will check this sooner or later. Best Regards, Thorsten.

Hi Janis, No, this configuration isn't supported by the AOUT_LC driver. Yes, it will be slower. There is a higher danger for MIDI IN buffer overruns. The best solution to get 8x12 bit is the usage of a AOUT_NG module, since it doesn't require to update all channels if only the value of a single channel has changed. This improves the performance significantly. Best Regards, Thorsten.

Sidenote: if this still doesn't help, you have to generate a .syx file in a newer format which is supported by MIDIbox 64 V2 I created this format since so many people were not able to upload large SysEx dumps with their MIDI interface. Details are described here: http://www.ucapps.de/howto_tools_mbsyx.html Meanwhile, mk_syx is part of the midibox64 package, so it's already on your harddisk (-> midibox64_v2_4c/tool/mk_syx directory) Best Regards, Thorsten.

This issue isn't related to MIOS, but to your MIDI interface under Windows. Solution: use MIDI-Ox to upload the .syx file First enter following setup into the configuration window of the SysEx tool: Thereafter load the file into the command window of the SysEx tool: And send it to your MIDIbox: Best Regards, Thorsten.