TK.

I was able to fix this earlier :) New release is available now: MIDIboxSEQ V4.083 ~~~~~~~~~~~~~~~~~ o fixed potential hang-up during pattern change which was introduced with V4.081 I can't see the euclid generator issue, and need some more detailed informations to reproduce this at my side. Best Regards, Thorsten.

Did you follow the configuration steps described in this file? http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmf_multi.ngc Which informations are missing (I will add them) E.g. the MF configuration can be found in this file as well - it has been tested by multiple users. For the case you haven't considered this yet: always ensure that you are using the latest MBNG version. Best Regards, Thorsten.

Hi Luke, :wacko: I will check it this Thursday. Probably it's related to the updated pattern change approach which solved the song sync issue: It seems that I overlooked a corner case. Best Regards, Thorsten.

Thanks for the infos! Great that it's working now :) I compiled MIOS Studio under WinXP to ensure that other people who haven't updated their OS yet can use it as well without compatibility issues. This might make the difference... Best Regards, Thorsten.

Is this linebreak between the ROUTER commands and the arguments are copy&paste error? Do you get an error message while uploading the .ngc file? Best Regards, Thorsten.

Yes, bootloader updates from pre v1.010 versions can be troublesome... :rolleyes: Fortunately there are no potential incompatibility issues anymore with v1.010 and higher :) Best Regards, Thorsten.

No, this was actually a clever question: especially the "sine" function allows you not only to check the calibration values, but it also checks if the motor voltage provided by your PSU is robust enough when all faders are moved concurrently. If the sine function fails as well, then the problem is related to power integrity. If the sine function is working, further debugging is required for the MIDI event forwarding (a MIDI monitor could help to troubleshoot this) Best Regards, Thorsten.

:thumbsup:

Hi, the MIOS32 timers are the best choice for this purpose. You won't notice jitter if the priority is set to MIOS32_IRQ_PRIO_HIGHEST This means, that no other interrupt routine could affect the execution time. Best Regards, Thorsten.

Die MIDI OUTs des STM32F4 sind im Open Drain Mode, deshalb sollten 220 Ohm statt 47 Ohm Widerstaende verwendet werden, ausserdem wird dann M+ der MIDI Buchse via 220 Ohm an 5V (und nicht an 3.3V) angeschlossen. 5V sind am Pin J11E:Vd verfuegbar. Ansonsten sollte es aber so funktionieren. Ich erwarte keine Probleme am MIDI IN, wenn Du den Optokoppler so verschaltest. Gruss, Thorsten.

I appreciate your activities! :) Please consider to make a backpanel for the new MBHP_CORE_STM32F4 module instead of MBHP_CORE_LPC17 (the new module is already available in SmashTVs shop) I consider to work on an enhanced version (called "MIDIbox V4 Plus") which will utilize the additional resources of the STM32F4 Best Regards, Thorsten.

Let's call it an imperfection... ;) In this version inverted and reduced ranges should be supported properly: http://www.ucapps.de/mios32/midibox_ng_v1_030_pre5.zip Rotated LCD view: would only work with graphical LCDs, and would require a special LCD driver (not the universal one) which has to be developed for the specific display. The driver would also consume some memory (which has to be removed from the pool), since direct writes to the display are not possible anymore. And it would slow down display output. So: not supported from my side. Best Regards, Thorsten.

Such a DIY MIDI Looper already exists: http://midisizer.com/midirex/ Best Regards, Thorsten.

Hi Johannes, I've no comparison available for integer vs. float. But if the required shift operation is your only concern, I assume that fixed point is still faster. A shift operation (regardless how many bits) takes only 1 cycle. See also: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0439b/CHDDIGAC.html I know that you don't like this tip, but anyhow: consider to use the special Cortex-M4 DSP instructions for fixed point operations (see also the bottom of the page that I linked above). I guess that they can be embedded into C code by using intrinsics. And in order to keep CPU independency, you could write another set of intrinsics which are doing the same operations with native C code. Best Regards, Thorsten.

Sorry for the trouble! :-( This was due to a corrupted build which can only happen with the special Makefile setup of MBSEQV4L (it uses some source files of the midibox_seq directory). I fixed the release script, the binary is working now. Version: V4L 082a Best Regards, Thorsten.

The changes are now officially release in V4.082: Best Regards, Thorsten.

In the last months I created many preliminary releases, it's time for a new official release: V4.082 From the ChangeLogs: MIDIboxSEQ V4.080 ~~~~~~~~~~~~~~~~~ o SELECT+PASTE transfers the parameter layer, which was active during COPY, to the current parameter layer. If a drum track is selected, it's doing this for the trigger layer (and not for the parameter layer). o SELECT+CLEAR clears only the current parameter layer. If a drum track is selected, it's doing this for the trigger layer (and not for the parameter layer) o it's now possible to control the track steps with CCs. Each track has a dedicated CC which has to be configured in the MIDI->Ext.Ctrl page. o it's now possible to turn off the track clock by enabling the new "Manual" mode in the DIVIDER page. Once enabled, a step will only be played if: - manually triggered in the MANUAL page - set with the new CC based step control feature (MIDI->Ext.Ctrl page) Use cases: - predefined MIDI events, stored in the track layers, should be manually triggered (and not sequenced). E.g. in conjunction with a sampler, you could set each step to a note which "fires" a certain sample. In addition, you can fire CCs, Program Change, Aftertouch etc. from the MANUAL page. - the track should be controlled from an analog modulation source (e.g. a sawwave from a LFO). MIDIbox SEQ doesn't provide analog inputs, so that an external CV-to-MIDI interface is required. Note that this interface also has to scale the CC value over the desired step range. If the modulation source should sweep over step 1..16, then the CV-to-MIDI interface has to scale down the converted value to the CC value range 0..15! MIDIboxSEQ V4.081 ~~~~~~~~~~~~~~~~~ o added USB MIDI workaround for Windows o fixed synchronisation issue in Song mode MIDIboxSEQ V4.082 ~~~~~~~~~~~~~~~~~ o Options in LIVE page are now stored in session specific MBSEQ_C.V4 file o initial release for MBHP_CORE_STM32F4 Best Regards, Thorsten.

The new handling is officially released now because I'm happy with the implementation! :) -> Best Regards, Thorsten.

The new version V4L.082 provides a new CLEAR button and sequence recording handling based on this discussion with Florian: MIDIboxSEQ V4L.082 ~~~~~~~~~~~~~~~~~~ o CLEAR button now allows to clear individual tracks with the GP buttons: - CLEAR+SEQ1: clear entire Seq1 + configuration (*) - CLEAR+SEQ2: clear entire Seq2 + configuration (*) - CLEAR+GP1: clear note triggers (values are kept but not played) - CLEAR+GP2: reset velocity values to 64 - CLEAR+GP3: reset note length values to half step - CLEAR+GP4: clear Track 4 (Pitchbend + last CC lines) - CLEAR+GP5: clear CCs of Track 5 - CLEAR+GP6: clear CCs of Track 6 - CLEAR+GP7: clear CCs of Track 7 - CLEAR+GP8: clear CCs of Track 8 Same for GP9..16 for Seq2 (*) track configuration won't be changed if 'PasteClrAll' set to 0 in MBSEQ_GC.V4 file o changed the track and layer assignment algorithm for CCs in recording mode: Previously new CC lines were recorded into Track 4, Layer B upwards. Now they are assigned the following way: - 1st CC line is recorded into Track 5, Layer A - 2nd CC line is recorded into Track 6, Layer A - 3rd CC line is recorded into Track 7, Layer A - 4th CC line is recorded into Track 8, Layer A - 5th CC line is recorded into Track 8, Layer B - 6th CC line is recorded into Track 8, Layer C - 7th CC line is recorded into Track 8, Layer D - 8th CC line is recorded into Track 7, Layer B - 9th CC line is recorded into Track 7, Layer C - 10th CC line is recorded into Track 7, Layer D - 11th CC line is recorded into Track 6, Layer B - 12th CC line is recorded into Track 6, Layer C - 13th CC line is recorded into Track 6, Layer D - 14th CC line is recorded into Track 5, Layer B - 15th CC line is recorded into Track 5, Layer C - 16th CC line is recorded into Track 5, Layer D - 17th CC line is recorded into Track 4, Layer B - 18th CC line is recorded into Track 4, Layer C - 19th CC line is recorded into Track 4, Layer D Same for Track 12..16 for Seq2 Advantage: if only a few CC lines are recorded, we've dedicated tracks for PitchBend and CCs (Track 4-8, Layer A) which can be individually muted and cleared. Additional CCs populate the remaining layers from Track 8 backwards, so that PitchBend remains an individual track if not more than 17 CC lines are recorded. Best Regards, Thorsten.

The meta events are finally implemented: http://www.ucapps.de/mios32/midibox_ng_v1_030_pre4.zip Usage example: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fcvtransp.ngc So, there is an individual pitchbend (14bit or 7bit) for each CV channel which controls the fine pitch over the configurable pitchrange And there are individual octave and semitone transpose values for each CV channel as well. The example forwards the configuration value from EVENT_RECEIVERs to EVENT_SENDERs. Of course, you could also control the values from another source, e.g. forward from EVENT_AIN to EVENT_SENDER which then performs the meta operation. Best Regards, Thorsten.

Hi Johannes, the numbers came from the EEMBC benchmarks linked above, but I wouldn't take this comparison too serious for your application. E.g. if STM32F4 would only process 8bit values, the benefit isn't so high. Or if a benchmark just toggles a pin, it could be that the performance is almost the same depending on the peripheral bus architecture ;-) The truth is typically in the middle... Anyhow, as you already mentioned above, STM32F4 provides features such as 32bit calculation and DMA, which are advantageous for the use case, and if it turns out that it isn't possible to replace all Atmel CPUs, just take a cheap second one... :smile: There are some apps and tutorials in the respository which give you a good entry: - Output audio via the I2S based DAC in 024_i2s_synth: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F - C++ based synth engine (w/o audio, only controllers like LFO, ENV, etc): http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_sid_v3%2F - another C++ based CV engine: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fprocessing%2Fmidibox_cv_v2%2F - simple project to output audio samples: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsynthesizers%2FSD+card+sample+player%2F We've no specific application which would really get use of the STM32F4 processing power while generating audio - you are in the pole position! :smile: Best Regards, Thorsten.

I like such tutorials! :thumbsup: Best Regards, Thorsten.

Today I spent some hours to make the WebSVN download button working - without success! This seems to be related to some webserver security settings. Due to my limited knowledge about such topics (I don't want to open a security hole!!!), I've disabled the download button now. Only proper way to download files is via a SVN client, such as Tortoise under Windows, or "svn" under MacOS/Linux. With the latest sources we are now able to save/load patches from the SCS! :) move the SCS encoder or trigger GP button #2/3 to select the current patch store/load a patch under Menu->Disk->Patch A001 is loaded after startup Best Regards, Thorsten.

Very cool! :smile: I gave you access to the hidden programmers section of this forum: http://midibox.org/forums/forum/41-programmers-lounge/ I can give you SSH access to the subversion server so that you can upload your code for easier sharing :smile: Best Regards, Thorsten.

A 4x40 display requires a second CS output and some software changes. This isn't supported. Best Regards, Thorsten.