TK.

I take it that the performance of run-script events is not guaranteed if other EVENTs are triggered? Other events shouldn't affect the performance so much (let's say +/- 1 mS). Say I have a run script that plays a phrase, it loops under push button control. Meanwhile, I edit the sound. What is the worst thing that could happen? The "worst thing" is, that other threads can't access the SD Card as long as the .NGR script is executed. No issue for conditional labels (because they are processed from the same thread), but it could be an issue if you would like to use the MIOS Filebrowser. Best Regards, Thorsten.

These are only warnings, you've to accept them (the curve table doesn't fit into the PIC18F452 memory anymore...) The actual error must be hidden somewhere else? Best Regards, Thorsten.

I will check this on my MBHP_CORE_STM32 module soon to check if I can (somehow) reproduce the issue. How high is the jitter? There is no way to get better results than +/- 1 I even get this excellent result when my MBHP_CORE_LPC17 module is supplied via a cheap USB hub. Best Regards, Thorsten.

cool! :) "save default" will generate a DEFAULT.NGC file from values stored in RAM (also the ones which you haven't specified, but which are active - such as LED_MATRIX_PATTERNs) Since the "LCD" command is directly processed from SD Card, and not stored in RAM (would be a waste of memory), it will get lost and therefore won't be stored. There are two alternatives: - either directly upload the DEFAULT.NGC file without using the "store" function - or write the LCD command into the DEFAULT.NGR file: if ^section == 0 LCD "%C" endif Best Regards, Thorsten.

Hi, J5B.A6 and J5B.A7 are allocated by the third MIDI IN/OUT port, therefore these pins can't be used as analog inputs. And the "parasites" (jittering values) are unfortunately normal - there is no way to fix this properly. The LPC17 has bad ADCs, and they are only working at 3.3V which means that the s/n ratio is lower than for ADC working at 5V. Therefore the usage of the AINSER64 module is recommended. In future, also an inexpensive AINSER8 module for 8 inputs will be available: http://www.ucapps.de/mbhp/mbhp_ainser8.pdf (prototypes are ordered). Due to the simplicity, this "module" could also be built on veroboard (cheapest solution). Best Regards, Thorsten.

This "^tx56 big font" issue is now fixed in V1.022 Best Regards, Thorsten.

.NGR scripts are now supported in V1.022 I implemented more functions than requested ;-) -> http://www.ucapps.de/midibox_ng_manual_ngr.html Best Regards, Thorsten.

The ^label statement is now supported in V1.022 Best Regards, Thorsten.

A new version is available: MIDIbox NG V1.022 ~~~~~~~~~~~~~~~~~ o support for run scripts. See also the new manual page: http://www.ucapps.de/midibox_ng_manual_ngr.html o the new SysEx command ^label has been added. It allows to insert the ASCII code of a label string into a SysEx stream. See also cfg/tests/syxlabel.ngc o big GLCD font now correctly handled by ^txt and ^txt56 SysEx command o line number now displayed on errors in .NGC, .NGL or .NGR file o various bugfixes and improvements Best Regards, Thorsten.

I could provide a special meta event for Inc/Dec value - in one of the future versions ;) Best Regards, Thorsten.

Thank you very much! :) I will test the filename issue soon - it could be, that the delete command doesn't check the attributes of a directory entry. Best Regards, Thorsten.

Hi Pete, the bootloader stores the configuration values in a special flash section to avoid any conflict. Which means, that the EEPROM is free for other purposes. A simple usage example for the EEPROM driver can be found here: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmisc%2Fusb_osc_midi_proxy%2F See presets.* The driver is included from the Makefile, and configured in mios32_config.h: // EEPROM emulation #define EEPROM_EMULATED_SIZE 128 // magic number in EEPROM - if it doesn't exist at address 0x00..0x03, the EEPROM will be cleared #define EEPROM_MAGIC_NUMBER 0x47114200 Note: it's called "emulation" due to historical reasons. For the MBHP_CORE_LPC17 module the external EEPROM. The magic number should be something different than 0x4711* (which is normally used by my own projects) - it's used to identify the data structure format inside the EEPROM (see presets.c) Best Regards, Thorsten.

No, there is no way. Non-destructive CC (and NRPN) changes have been requested by multiple people in the past - and MBSID V2 is designed to cover these requests (it was a lot of effort!) Only SysEx messages will allow you to address the patch buffer directly. They can be sent from various MBSID editors. Best Regards, Thorsten.

Thanks for testing! :) Any input from Windows and MacOS users? Before an official release I would like to ensure, that the new Juce version hasn't corrupted anything. Best Regards, Thorsten.

Hi, I don't think so - MIOS Studio always loads the current .hex file before sending. Best Regards, Thorsten.

The number of albums was limited to 1 for normal members (I don't know why...) I increased it to 10 Best Regards, Thorsten.

Ich wuerde dafuer heutzutage ebenfalls einen USB Repeater nehmen, das spart eine Menge Verkablungsaufwand. Gruss, Thorsten.

Yes, it would be possible to add a ^label function, I will consider this in one of the next releases. Best Regards, Thorsten.

Wouldn't it be better if you would use MBNG instead? However, this file shows you, how to configure the router nodes: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fsrc%2Fmbng_file_c.c search for "router" Best Regards, Thorsten.

I migrated MIOS Studio to the most recent Juce 2.0.38 version in the hope that this could solve the MIDI communication issues which have been noticed by some Windows users when they are trying to access files from SD Card with the MIOS Filebrowser. Since I'm not able to reproduce these issues on a "modern Win7" and on an "antique WinXP" notebook, I rely on your feedback! Please try out this version and inform me, if they are working at your side (of course, also positive replies are very welcomed): Windows: /edit: obsolete - please download the latest version under http://www.ucapps.de/mios_studio.html MacOS: /edit: obsolete - please download the latest version under http://www.ucapps.de/mios_studio.html Linux: /edit: obsolete - please download the latest version under http://www.ucapps.de/mios_studio.html IMPORTANT: the new Juce version doesn't solve the USB MIDI driver issues under Windows. If even a "query" is failing, you either have to install the GM5 driver, or for the case that this driver also doesn't work, you've to use the "single_usb" option as explained here: http://www.ucapps.de/mios32_bootstrap_newbies.html Best Regards, Thorsten.

Router settings are not stored in EEPROM, therefore they won't be recovered after power-on. Background: if the MBKB application will be replaced by MBNG in future, it isn't worth the effort to "finalize" this one. Best Regards, Thorsten.

Thanks for opening my eyes! :) I updated the bootloader documentation to make clear that the changed parameters need to be stored (in flash memory): http://www.ucapps.de/mios32_bootstrap_newbies.html Great to know that the single_usb option solves the USB issues. Powering two MIDIboxes at the same time: at power-on they will consume a bit more power than during runtime. Are your MIDIboxes supplied from the PC, or from an USB hub with external PSU (recommended)? Changing the device ID won't solve this (actually you don't need a different ID if the MIDIboxes are accessed from dedicated USB ports) Best Regards, Thorsten.

You are using a STM32... this was an important hint! ;-) Yes, please try it in push-pull mode at 3.3V. (set "#define AINSER_SPI_OUTPUTS_OD 0" in your mios32_config.h file) With some luck, the MCP3208 can still be supplied at 5V, which gives you a larger voltage range for the pots. So, try both options: J26 set for 3.3V or 5V Best Regards, Thorsten.

This is indeed a very reduced voltage range. Scaling over such a small range would result into jitter issues -> forget this joystick. :-( Maybe Lars aka. rvlt can give you a hint for suitable pitch/modwheels Best Regards, Thorsten.

It's still unknown, if you've connected the joystick wrongly or not. Which voltages (against ground) do you measure at the wiper (middle pin) if the pot is in max and min position? And do you know the resistance of the pot? Best Regards, Thorsten.