TK.

The USB socket has to sit flat on the PCB, and all 4 pins in the middle of the socket have to be soldered properly with the 4 tracks (circuit paths). Probably one of the 4 pins has a loose contact. Best Regards, Thorsten.

Which links did you try out exactly? The links in the first posting of this thread are working fine - they point to the "latest tested" versions, all other links in this thread are obsolete. Best Regards, Thorsten.

I've to ask you some questions to ensure that I understood you correctly: Which option do you want to use? [AUTO_SNAPSHOT] enabled? And you want that values are stored in BankStick, and that they are sent to the MIDI OUT? Best Regards, Thorsten.

What happens if you put the commands into the DEFAULT.NGC file? Before testing this, create a backup of the current DEFAULT.NGC - the "history" could be important to know for the case that this solves the issue. Best Regards, Thorsten.

Hi, to 1) after installation of the toolchain you've to open the setup_*.asm file that you are planning to use. You don't need an IDE for this, the "wordpad" is suitable for editing as well. Search for CS_MENU_DISPLAYED_ITEMS, set it to 10 Search for CS_MENU_DIN_TABLE, adapt the DIN pin assignments Recompile the source code with "make" to 2) see also this thread: where you can read the details. It's possible to adapt the frequency table, but there is no way to load it from BankStick, since there isn't enough RAM available. Also flash memory is limited (meanwhile), there isn't enough memory free to store multiple tables in flash and to make them selectable from the patch. Best Regards, Thorsten.

Schick' mir mal das Verzeichnis per EMail (PM folgt) Gruss, Thorsten.

The AIN sample frequency was ca. 1kHz, which means that nobody can expect that a usable sinewave (e.g. generated from an analog LFO) could be passed to the synth engine this way. It sounds quantized & aliased in the negative way (!) - a lot of noise, no musical usage. You mention another usage of AINs: for simple parameter control. This will be possible (-> knob functions). It will definitely require an AINSER64 module (btw.: I consider to provide a downstripped PCB called AINSER8 with MCP3208 only for unmuxed inputs), because the analog inputs of the LPC17 jitter too much. Best Regards, Thorsten.

I fear that somebody else has to explain this, if the documentation of the MBHP_* modules under http://www.ucapps.de isn't clear enough (sometimes also wikipedia or google helps to get informations about the used terms) Anyhow, "mapping" means, that the 8 pins of a DOUT shift register reflect the state of 8 buttons connected to certain DIN shift register. If the buttons are configured for toggle mode, the DOUTs will behave accordingly. With the LED map you are able to define, which DOUT shift register should be assigned to which DIN shift register. It gives you some more flexibility. Best Regards, Thorsten.

Are you saying that DINs are not working at your side with V1.017 as well? There was no "critical" change between v1.017 and v1.018 which could cause this. Yes, support for keyboards was introduced with v1.018, and this was also the version where I increased the SRIO scan frequency, etc... Therefore it would be interesting, if this is a systematic bug which could "somehow" be reproduced with earlier versions. And of course it would be interesting, if any other user noticed a similar problems with DINs? I check the functionality of cfg/test/*.ngc files regularly with different hardwares, and haven't noticed such an issue yet. Best Regards, Thorsten.

I'm surprised! I thought that any channel will be accepted, and that the MBSEQV4L UI doesn't allow to select a dedicated channel for recording. Did you change anything manually in the configuration files on SD Card? It will be very difficult to provide two different IN ports (I will probably not implement this!) It would be possible to provide different OUT ports in a later firmware version. Something is really strange with your setup... If you are not able to find out the reason, it could make sense to try it out when no SD Card is connected to your MBSEQV4L to ensure that it boots with the default configuration. Best Regards, Thorsten.

Debug messages are mostly sent to USB1, because UART is (much) to slow! With v1.018 the keyboard driver has been introduced. Type "kb 1" and "kb 2" are the din_sr1 and din_sr2 values set to 0? If not, these functions would shadow the "normal" DIN function. Actually EVENT_HW should clear these SR definitions, it's just an assumption. Best Regards, Thorsten.

Could you please try the different versions: http://www.ucapps.de/mios32/backup/midibox_ng_v1_013.zip http://www.ucapps.de/mios32/backup/midibox_ng_v1_014.zip http://www.ucapps.de/mios32/backup/midibox_ng_v1_015.zip http://www.ucapps.de/mios32/backup/midibox_ng_v1_016.zip http://www.ucapps.de/mios32/backup/midibox_ng_v1_017.zip http://www.ucapps.de/mios32/backup/midibox_ng_v1_018.zip http://www.ucapps.de/mios32/backup/midibox_ng_v1_019.zip Once we know the version which doesn't work at your side, we could have a look into the SVN history to get an impression, what has been canged exactly... Bes Regards, Thorsten.

Using higher resistor values is the right way, and there is no problem if you use different values for the DOUT pins. The dim option (only available in MBNG) would be an alternative, SW based solution - maybe you will like it (because it gives you more flexibility), maybe you will hate it (because you've to specify the dim level for each EVENT_* entry ;-)) Best Regards, Thorsten.

Analog INs: I tried this some time ago, but had no fun with this option - the achievable sample rate is too low for good results. Features where I don't see a significant benefit won't be supported, because people will blame me for the bad performance and wrong promises. DINs: using digital inputs as triggers sounds like a good idea. Multiple AOUTs: running synth engines for more than 8 outputs would decrease the sample rate, at the end the results would be worse than today. So: I could only provide "auxiliary AOUTs" to pass static values which are not modulated. Best Regards, Thorsten.

You are using a MBHP_CORE_STM32 module, most people are using a LPC17 module - this could make a difference. It would be interesting if you notice changes if following switches are changed in the src/mios32_config.h file: 1) set MIOS32_SRIO_NUM_SR 16 2) set MIOS32_DONT_SERVICE_SRIO_SCAN 0 3) set MIOS32_SRIO_NUM_SR 16 and MIOS32_DONT_SERVICE_SRIO_SCAN 0 Best Regards, Thorsten.

Nested labels are not supported. It would require a recursive algorithm which increases the "worst case" stack memory consumption dramatically - there isn't enough RAM available for this. But this one: LABEL b1e2 "@(1:9:2) PW %3d" should work. I'm surprised that it doesn't... e.g. the "^std_enc", "^std_btn", ... labels refer to values as well, and they are working. Best Regards, Thorsten. P.S.: as mentioned in another thread, I can't test this before next week.

I'm currently not at home and therefore can't test your file. I forgot to mention, that the "empty file" should contain a RESET_HW command. Without this command, it could be that functions are active which shadow the DIN: - encoders - DIN matrices - KB matrices With RESET_HW these configurations should be disabled. Best Regards, Thorsten.

Here is the starting point: http://www.ucapps.de/midibox_ng_manual.html Yes, the usage of a MBHP_AINSER64 module is strongly recommended for best results. Of course, you could also build the circuit on a veroboard to reduce area. E.g. you could also connect the 8 pots directly to the MCP3208 - no need for a 74HC595 or 4051 multiplexers in this case. Best Regards, Thorsten.

Yes, the STM32 has only weak "open drain" drivers for the SRIO chain. This has been solved on the LPC17 core by using 74HCT541 based buffers. However, it could be that such a special cable already helps: (shielding not required - the inserted resistors are doing the magic! :)) More infos about the cable at the beginning of the MBNG thread. Best Regards, Thorsten.

You've to calibrate the faders individually for best results. Calibration is required due to (slight) mechanical differences. Therefore my recommendation: use the calibration tool to get the "best looking curves". But the described effect matches exactly with the one which has been fixed in 1.004 Or did you disable the touch detection? Then this would explain the effect as well! Please enable it. Best Regards, Thorsten.

You could also start with an empty .ngc file (or just the one which prints "hello world"), the debug mode will always print MBNG_DIN_NotifyReceivedValue() regardless of the EVENT configuration. From the log it looks like the data input (resp. the data output of the DIN SR) is always 0 Best Regards, Thorsten. /edit: the "empty file" should contain a RESET_HW command!

You can compensate this by using different MinDutyUp/Down and MaxDutyUp/Down values for the affected faders. The values can be changed with the MBHP_MF_NG tool in MIOS Studio, after the right values have been find press the "Send" button to store the new settings permanently in EEPROM. could it be that you haven't updated the mbhp_mf_ng firmware to v1_004 yet? Best Regards, Thorsten.

It's normal that the application still shows 4 USB ports (single_usb only affects the USB descriptors) And it's normal that the single_usb command isn't accessible from the MIDIO128 application, it's only available in the bootloader update package. However, I'm sure that it's still enabled. Missing tests: - install the GM5 USB MIDI driver, does it help? - try it on a different computer - any luck? Best Regards, Thorsten.

Hi, OSC commands can't be customized, because there isn't enough RAM available to store the strings. The only possibility would be to change the strings of an existing mode in the source code: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fmodules%2Fuip_task_standard%2Fosc_client.c (you would still have to send MIDI events, which are then mapped to OSC strings by the client) Best Regards, Thorsten.

Hi, there is currently no way to change this without recompiling the firmware. But for the case that you've already installed the toolchain: open src/sid_midi.inc, search for the "SID_MIDI_ProgramChange" label, and enter a return below this label: SID_MIDI_ProgramChange return ; ignore program change handling thereafter build a new .hex file Best Regards, Thorsten.