TK.

Sehr schoener Chip! Hast Du schonmal daran gedacht, das analoge Filter in den Feedback-Pfad einzubauen? Wenn Du dann auch noch die CutOff-Frequenz modulierst, ergeben sich mit wenig Aufwand sehr interessante (pseudo-polyphone) Klangtexturen. Gruss, Thorsten.

Did you also consider, that STM32F4 has already 4 MIDI OUT (and 4 MIDI IN) ports in conjunction with the two (upcoming) MBHP_MIDI_IO boards? (Ignore the RTP MIDI extension at the right side, and IIC MIDI at the left side...) This might be the best solution. :smile: Best Regards, Thorsten.

This reminds me, that I wanted to implement a fallback mode, so that USB MIDI access is still possible, and also some terminal commands for debugging are available (e.g. to dump a memory map for stack analysis) Maybe a nice weekend project :) Best Regards, Thorsten.

Hallo Stephan, sendet der PIC eigentlich einen Upload Request, wenn Du die Spannung anlegst? Du solltest diesen Request (f0 00 00 7e 40 00 01 f7) im MIDI IN Monitor von MIOS Studio sehen. Falls Du den nicht erhaelst, liegt das Problem entweder an der Spannungsversorgung, oder am Quarz. Wenn das nicht weiterhilft, mach' doch mal Fotos von der Platine und stelle sie hier rein - vielleicht sieht dann jemand den (Loet)fehler. Gruss, Thorsten.

It isn't possible yet to forward the J5 based gates to a DOUT SR, but I'm planning this for the future. Because I've the same interest, I want to use my breakout board on a MBCV and MBSEQ Best Regards, Thorsten.

I added some new features today: - the Lemur panel has been overworked, so that global parameters (outside the CV groups) are now accessible with the "G" button at the right side. - added "Force To Scale", which can either be activated at the end of the CV output data streams, or "in between" by using the modulation matrix. The Force To Scale works like a Quantiser which allows to select the note values which should be played - all other notes are forced to the neighbored selected note: In this example: only D# will be played, all other notes are forced to D# In order to use Force-to-Scale, either push the "Force Scale" button in the Main panel, or select the "FTS" operator in the modulation matrix. - support for analog inputs: STM32F4 all 8 inputs at J5A and J5B, and LPC17 currently only J5B.A4 and J5B.A5 (since J5A is used for OLEDs) - later it will be possible to use J5A as well for people who don't use the OLEDs on a LPC17 core (again: there is no limitation for the STM32F4 core) AIN inputs can be selected as source in the modulation matrix. In addition, AIN inputs can be used as external gates, e.g. to trigger the LFOs and Envelopes. In order to activate this function, change to the main page and increase the "Ext. Gate Threshold" value at the left side, which defines the level at which the gate will be triggered. - the envelopes got new curves (Exp1, Exp1Inv, Exp2, Exp2Inv), and it's possible to select different curves for rising and falling ramps: (inspired from the Andromeda synth as demonstrated by Hawkeye! :smile: - the modulation matrix got an offset parameter to increase/decrease the modulation path output: Unfortunately these changes lead to incompatible patches. Since there aren't so many users yet, I haven't worked on a translator -> your old patches will be corrupted (in the ENV and MOD sections). If you don't mind, just delete the old banks with the MIOS Filebrowser (remove MBCV_B1.V2 ... MBCV_B4.V2) Thereafter enter "reset" in the MIOS Terminal so that new banks are created. Please also note, that the updated Lemur panel has to be used as well with the new firmware, otherwise the parameters are not correctly mapped. Best Regards, Thorsten.

You wanted to say "What a pity" ;) I haven't fully understood what you want to achieve. A MIDI Controller with multiple OLEDs and Encoders+LED Rings can already be created with MIDIbox NG regardless of the core. MIDIbox CV is not a MIDI controller, and the OLEDs are used for a different purpose. They don't show messages (like MIDIbox NG would do), but show oscilloscopes for the internally generated waveforms. Best Regards, Thorsten.

MBCV supports only 4 OLEDs because the scopes consume a lot of CPU time. Adding more scopes would increase the latency for display updates so that they are not usable anymore. Another reason is, that the OLEDs are connected differently compared to the normal approach. E.g. on the STM32F4 based core, they are connected at J10B which has only 8 data lines, which are fully allocated (CS/SCLK/DATA/RESET/CS1..4) In general, MBCV is not comparable to a MBNG based MIDI controller, therefore the design constraints might confuse you ;-) Best Regards, Thorsten.

I know your use case, and I know how to implement this - but working on MIOS Studio is just currently not on my Agenda (I'm currently working on other projects), and for myself I don't see a big benefit (I'm not saying, that the enhancements would have no benefit at your side...) When I'm working with the monitors, I need the full report with history and timestamps, e.g. to check if all MIDI data has been transmitted with expected timings. If something fails in the firmware, I need this information to trace back the reason. You need some kind of dashboard which shows the last transfered values of the message types + some filtering - something what would be useless at my side. Therefore please understand that such extensions don't have a high priority at my side (and as you notice, other users don't see to be interested as well, otherwise you would have got more feedback on the proposals) However, programming with Juce is fun because the library is well documented, and you could also use it for other purposes in future. So, definitely worth to learn this and no wasted time at your side. You've concrete ideas how to implement this, so why not giving it a try? Best Regards, Thorsten.

I hope that I found the root cause for this issue: it seems that some years ago I changed a certain detail in MIOS8 and adapted all applications - except for MIDIbox FM! :rofl: Please try this firmware: http://www.ucapps.de/mios/midibox_fm_v1_4i.zip Best Regards, Thorsten.

I'm sure that some Cubase users are around here, hopefully one will reply... Best Regards, Thorsten.

Hi Robert, yes: currently you are using 0xB0 for each input, which means: send CC over MIDI channel #1 In order to send over MIDI Channel #2, just change this to 0xB1 Please re-solder, it's more consistent Scaling analog values isn't provided by the MIDIO128 applications. If this is required, go for MIDIbox NG! (and btw.: MIDIbox NG allows you to swap min/max without re-soldering the pots) MIDIO128 is a primitive application for beginners: you get what you read in the documentation. ;-) MIDIbox NG is much more flexible, but also requires that you read more documentation... Best Regards, Thorsten.

Funny wording - sounds like MIOS Studio is currently grap, but with your proposed enhancements (ideas stolen from other tools) we could make some $$$ with this tool that I developed during my sparetime? ;-) Anyhow, contributions to MIOS Studio from other programmers are very welcomed! The source code can be found under: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Ftools%2Fmios_studio%2F In order to build the application under Windows/MacOS or Linux you've to unpack the "unpack_me.zip" file under http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Ftools%2Fjuce%2F as well The respository can be downloaded with a common SVN client, URL: svn://svnmios.midibox.org/mios32 Just send me your enhancements, and I will bring them into the official release. Best Regards, Thorsten.

This is a software option, in the bootloader configuration you could mirror the Y axis if you want (but I prefer to have the yellow line at the bottom) Best Regards, Thorsten

For me it looks like a connection problem between PIC and LCD, because the PIC and the MIDIbox SID application is still running. Best Regards, Thorsten.

Fuer mich klingt das plausibel: wenn keine Bank definiert wurde, gibt es auch nichts zu inkrementieren. Wenn Du nun bspw. ein Event mit bank=1, und ein anderes mit bank=2 definieren wuerdest, sollte IncBank von 1 nach 2 umschalten - richtig? Gruss, Thorsten.

They are independent and can't be shared. Best Regards, Thorsten.

Du hast also die richtige Konfiguration fuer die LED Digits gefunden. Der naechste Schritt ist nun, diese in das logictrl.ngc template zu uebertragen, sowie die shift register nummern (sr_dout_r1 und sr_dout_sel1) an Deine Hardware anzupassen. Danach kannst Du nochmal den SysEx-Befehl senden, um sicherzustellen, dass die Anpassung richtig war. Und dann sollte es auch mit Cubase funktionieren. Gruss, Thorsten.

Clocks and Start/Stop are assigned to DOUT pins as well, you only need to add the clock input. I would also use a separate (especially shielded!) cable for the analog inputs, otherwise there will be a lot of crosstalk from the digital signals. Best Regards, Thorsten.

Ok, siehe Seite 11: das Display verhaelt sich wie ein 2x40 LCD, die Konfiguration ist somit set lcd_width 40 set lcd_height 2 set lcd_num_x 1 set lcd_num_y 1 Die dritte Zeile beginnen ab x=21 (y=1 oder 2) Gruss, Thorsten.

Ok, I see. I will check this next weekend. Best Regards, Thorsten.

Both are suitable, but LM3940 is the better choice because the pinning is compatible to LF33 -> buy it! :) Best Regards, Thorsten.

of course, it will compile because the memory is taken from the heap during runtime, and no from the static allocated RAM section during compile time. Best Regards, Thorsten.

Es fehlt u.A. die abschliessende F7, probiere mal: f0 00 00 66 14 10 70 71 72 73 74 75 76 77 f7 Gruss, Thorsten.

Just have a look into the mios32_config.h file of MIDIbox NG - it uses a different way for the stack size configuration: // reserved memory for FreeRTOS pvPortMalloc function #define MIOS32_HEAP_SIZE 10*1024 // UMM heap located in default section (means for LPC17: not in AHB memory, because we are using it for the event pool) #define UMM_HEAP_SECTION // stack sizes which are used by various tasks (see APP_Init() in app.c) #define APP_BIG_STACK_SIZE (2048) #define APP_REDUCED_STACK_SIZE (1024) // for the MIOS32 hooks in main.c #define MIOS32_MINIMAL_STACK_SIZE APP_BIG_STACK_SIZE // for the UIP task #define UIP_TASK_STACK_SIZE APP_BIG_STACK_SIZE no... You have to mention more details about your modifications - with some luck it triggers a deja-vu at my side, otherwise either try to work out the problematic change by disabling the added sections until the crash doesn't happen anymore. Best Regards, Thorsten.