TK.

Hi, the clarification of this issue is still on my TODO list. Probably it's related to the way how the Y position is placed at the second line. For big fonts a special case has to be considered, this can only be changed in the firmware, and therefore I guess that I'm the only one who can help here... Best Regards, Thorsten.

Hallo, E131 steht fuer ein ungueltiges Bank Format (irgendetwas stimmt nicht mit den MBSEQ_B*.V4 Files in Deiner Session), FasFS Fehler D9 steht fuer "invalid object" (irgendetwas stimmt mit dem Filesystem nicht) Schau mal, ob Du via "SaveAs" im Hauptmenue eine neue Session anlegen kannst. Falls das nicht funktioniert, am besten vorher die wichtigsten Files auf Festplatte kopieren, und dann mit dem "sdcard_format" Kommando die SD Karte neu formatieren, und die alten Files wieder hochladen - danach sollte eigentlich nichts mehr schief laufen. Gruss, Thorsten.

I'm very sure that I won't start with this - it's like opening pandoras box. You come with a simple request, next people will come up with even more requests, etc... and this based on an outdated microcontroller which is difficult to program and limited in memory -> not with me! However, if I would be a marketing guy, I could just handle this the same way like commercial companies E.g. like Novation: http://createdigitalmusic.com/2015/07/hack-grid-novation-releasing-launchpad-pro-firmware-open-source/ So - actually BLM16x16+X is open source as well, it's well documented (MIOS API), users can "hack the firmware" Best Regards, Thorsten.

Fine! :) Best Regards, Thorsten.

Great work!!! :) Best Regards, Thorsten.

Alright, fine! :) And thanks for the reminder, that I've to rename "std_rgbled" to "std_rgb" in the DEFAULT.NGL file when it's created. (you could edit this with the MIOS Filebrowser) Best Regards, Thorsten.

DETENTED1 war zwar nicht dafuer gedacht, aber schoen wenn es trotzdem (irgendwie) funktioniert! :) Gruss, Thorsten.

Welche Encoder verwendest Du genau? Bestellnummer? Ich befuerchte, dass das Pinout nicht kompatibel ist. Von oben gesehen ist der rechte pin der "common" pin, welcher mit Masse verbunden wird. Falls Du Encoder erwischt hast, bei denen der mittlere Pin "common" ist, muesstest Du entweder die Encoder austauschen, oder einen Weg finden, die mittlere und rechte Leitung zu vertauschen (ich wuerde die Pins dann einfach mit einem Seitenschneider vorsichtig durchknippsen, und dann ueber kreuz verkabeln) Gruss, Thorsten,

Where did you see this message? php55w-gd is installed now, and I restarted the webserver + php_fpm service. So, it could be that the problem is solved. Best Regards, Thorsten.

Hi, there is no need to recompile the firmware, all parameters can be configured in the .NGC file. Could you please show me your configuration? And do you get any error messages while uploading or editing the file? (messages will be print in MIOS Terminal) Best Regards, Thorsten.

Which problems? Note that as long as the DNS entries for midibox.org haven't been moved, parts of the website (incl. forum) will link to the old server. Best Regards, Thorsten.

Server move completed! :) The new midibox.org DNS entry should be propagated in 24h Best Regards, Thorsten.

;-) The most simple way to check if the application is running: enter "help" in MIOS Terminal This typically lists the commands which are supported by the application. Best Regards, Thorsten.

The good news: this is a feature which can be easily enhanced, because I implemented a fully scalable solution (and I'm really proud of this, because usually I can't do this for everything due to memory limitations! ;-) Current divider values: const u16 din_sync_div_presets[] = // 1 2 3 4 6 8 12 16 24 32 48 96 192 384 ppqn, StartStop(=0) { 384, 192, 128, 96, 64, 48, 32, 24, 16, 12, 8, 4, 2, 1, 0 };the maximum possible divider value is 65535, but as you can see, I only prepared up to 384 for 1 ppqn Which additional dividers would be useful? Best Regards, Thorsten.

I don't remember exactly, but it could be that the Curve makes a difference - ensure that V/Oct is selected during calibration. Best Regards, Thorsten.

C7 close to pin 28 C6 close to pin 19 and 20 Best Regards, Thorsten.

The MTT will translate USB 1.1 to 2.0, it won't solve the problem because the actual problem is the missing USB Hub support in the USB drivers provided by ST. Enhancing the code seems to be difficult, I haven't found a ready made (and open source) solution in the internet yet. Best Regards, Thorsten.

Yes, the bootloader starts at 08000000, and if the BSL Hold Pin (for STM32F4: pin PA0) isn't activated, it resets the CPU and continues at 08004000 where the application is located. "Activated" means for PA0: it should be 0V so that the application will be booted (this pin has a pull-down device) Could you please doublecheck that PA0 is at 0V? Best Regards, Thorsten.

Nobody reported such an issue so far. The ignorable upload error can be... ignored! It happens when MIOS Studio uploads a new block while flash programming is in progress. MIOS Studio retries and gets a success message -> flash programming done -> don't worry about this. Depending on the machine you could get 20...30 ignorable errors but application is still uploaded correctly. 8004004 isn't the boot loader section anymore, it's the application section. It's normal that this range will be overwritten. Which .hex file did you compare? The boot loader or MIDIbox SEQ? You could upload the MIDIbox SEQ binary directly with ST-Link, it contains the boot loader + the application code, the result should be the same as if you would upload the application via USB MIDI. This is also the way how you can continue troubleshooting. It's btw. strange that the LCD is blank, the MIOS32 boot loader update application should initialize the LCD and print a message. The only explanation that I have for this effect (application not started, LCD blank) is, that the blue USER button is still pressed for whatever reason (defective button?) - because in this case the boot loader won't start the application. Best Regards, Thorsten.

Hi *, the midibox.org server will be moved to a new location this Friday evening (CET). The forum will be down for ca. 2 hours, thereafter it will be available under http://134.119.32.105/forums Once the updated domain records have been propagated to the DNS server of your service provider, you will be able to use the URL http://forum.midibox.org again! I would like to take this opportunity to thank Twin-X for hosting midibox.org on his server for more than 10 years! He helped us to keep the site online during a difficult situation anno 2005 where bandwidth did matter. I remember the times where the previous midibox.org servers that we tried were dramatically slowed down or just not available for the remaining month once we exceeded the bandwidth limits (typically after new MIDIbox SID V1 demo publications)! No issue after Twin-X jumped in - I was even able to publish videos w/o the downtime danger (for the younger fellows of this forum: the time before YouTube or Facebook which started to provide this possibility for free!!!) Twin-X gave us a solid home which resulted into a growing user base and a nice place to talk with so many people who follow the same DIY spirit! :) Times have changed, technology improved, cloud based servers are common today, easy to setup and fast enough to host a site like midibox.org The new server is owned by myself, and it’s completely founded by the community, thanks to the donations that I got in the last months (I got more „beers“ than I could actually consume!!! ;-) Looking forward for the next years of fruitful discussions & publications about our hobby: MIDIbox DIY fun! Best Regards, Thorsten.

Yes, it will work as well with the same .hex file (no need to re-compile the application, since MIOS8 contains the PIC18F4685 specific parts). Best Regards, Thorsten.

Hi, I added 1) to the wishlist, but (as requested) it will only be an option, because I think that most users won't like this behaviour. To 2) it's only a minor issue which is difficult to fix, therefore I will let it as it is Best Regards, Thorsten.

The sammichSID doesn't scan analog inputs, therefore this is very likely not the reason for this issue. It seems to be related to the connections around the 74HC165 ICs, which scan the buttons and encoders. Best Regards, Thorsten.

Hi, the COM led just shows that no debugger tool is connected. There is no dedicated LCD interconnection test application for MIOS32, where did you find this .hex file? Instead, the test is integrated in some applications, such as the MIDIbox SEQ Just enter "testlcdpin" in the MIOS terminal to get a help page. Best Regards, Thorsten.

There is no AINSER related change between pre15 and the current version. See also: http://svnmios.midibox.org/comp.php?manualorder=1&repname=svn.mios32&compare[0]=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1&compare_rev[0]=2211&compare[1]=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1&compare_rev[1]=2243&comparesubmit=Vergleiche+Pfade Could you please check if one of the examples (such as cfg/tests/ainser64.ngc resp. ainser8.ngc if you are using the unmuxed PCB) is working at your side? Best Regards, Thorsten.