TK.

granted! :)

I adapted the CV Autotune application to LPC17 and it's working fine! :) -> http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fexamples%2Fcv_autotune%2F Even if you haven't connected an AOUT module (btw.: you haven't mentioned for which purpose you are planning to use frequency measurements...), the current frequency at the J18.CAN pin will be displayed periodically in MIOS Terminal, which is nice for debugging. Best Regards, Thorsten.

It has the same connections like the AOUT module. Best Regards, Thorsten.

The preferred option is to power the core module via USB as well instead of using an external PSU. You can even do this when the sequencer isn't connected to a computer, just us an USB hub like this one: http://www.reichelt.de/USB-Hubs/MAXXTRO-MX-UAP/index.html?;ACTION=3;LA=2;ARTICLE=99781;GROUPID=4831;SID=11TVLbZ38AAAIAAG9MIgIec1e46ae3eb4fc2fe4e011f269170227 I like it because it has a power switch; all my core modules (including MBSEQ V4) are supplied by the PSU of this hub. Nice idea! Instead of using a MKE, the core module could scan the keys via DIN registers :) Measuring results are 200 mA when 220 Ohm resistors are used for the LEDs! With 100 Ohm resistors (as recommended in the schematic) I expect ca. 250 mA maximum. We are using common LEDs, no low-power variants. But they are time multiplexed and not completely saturated ((3.3V-1.8V)/100 Ohm = 15 mA, 15 mA * 8 = 120 mA) Best Regards, Thorsten.

I'm surprised about your statement!!! Is version 4.050 working fine??? Best Regards, Thorsten.

Addendum: I remember that the IRQ handler has to be disabled via the mios32_config.h file, otherwise you won't be able to create an own. And I noticed that the names of the IRQ handlers were taken from STM32 in LPC17xx/mios32_timer.c - I corrected the names! E.g.: #define MIOS32_DONT_ALLOCATE_TIMER0_IRQ 1 Please update your repository. Best Regards, Thorsten.

Hi, I can give you a working example soon, because porting the CV Autotune application from STM32 to LPC17 is on my TODO list :) -> http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fexamples%2Fcv_autotune%2F this won't be required. Timers LPC_TIM0, LPC_TIM1 and LPC_TIM2 are not allocated as long as they haven't been initialized via MIOS32_TIMER_Init() no, but you have to take care that the application doesn't use these timers (there is no automated conflict detection/reporting) Best Regards, Thorsten.

With MIOS32_MIDI_DefaultPortSet Alternatively you can redirect the MIDI events to a hook and send MIDI events to any port (also multiple ports) from there. Example: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidio128_v3%2Fsrc%2Fseq.c search for Hook_MIDI_SendPackage Best Regards, Thorsten.

I'm sorry for this mistake! v4.050 is available now: MIDIboxSEQ V4.050 ~~~~~~~~~~~~~~~~~ o added LED functions for received MIDI IN/OUT events to MBSEQ_HW.V4 o added BPM LED Digit function to MBSEQ_HW.V4 A schematic can be found under http://www.ucapps.de/midibox_seq/mbseq_v4_bpm_digits.pdf o SR1 working again (programming error during MBSEQV4L merge) [/code] Best Regards, Thorsten.

All rates from 1..243 are synchronized to MIDI clock as well, so this would just only be an option for more comfort - but in fact you can already do the typical wobbling basslines, no need to hurry (at my side :) ) To switch between different "meaningful wobble rates", I would propose to enter some good working values into a wavetable, and to select the wavetable position with a knob function, which can be forwarded in the modulation matrix to the LFO rate. You should also consider to reset the LFO with Note On events (-> trigger matrix), play different rhythms (same or different notes) and change the LFO rate interactively - this should result into much more interesting effects. Difficult? I could create an example patch... but not before monday. Best Regards, Thorsten.

I realized that OUT4/IN4 was also activated for the STM32 core - the firmware could crash (resp. random things could happen) if MIDI events are sent to this port! The bug is already fixed in this version: http://www.ucapps.de/mios32/midibox_seq_v4_050_rc1.zip An update is strongly recommended if you are currently using v4.049! Best Regards, Thorsten.

There is a conceptional problem with this option. If the merger setting would be restored on each patch change, you would have to adapt all your patches whenever you've changed your MIDI setup. It would be better to handle it separately like a "global option" (e.g. stored in internal EEPROM independent from the patch), but the application isn't prepared for this. I'm still unsure about the best solution. Best Regards, Thorsten.

Wenn Du in der CS_MENU_ChangePage Funktion (-> cs_menu.inc) folgende Zeilen einfuegst: SET_BSR SEQ_BASE bcf SEQ_MODE0, SEQ_MODE0_CHANGE_ALL_STEPS, BANKED [/code] sollte die ALL Funktion mit jedem Seitenwechsel deaktiviert werden. Gruss, Thorsten.

You won't like such a "digital joystick function", it's hard to use since you won't be able to control the speed properly (e.g. slow or fast fades) Just connect an analog joystick (with two pots) to two free analog inputs, the pot values are available as free assignable knob functions, and also in the modulation matrix (means: you can apply mathematical operations, e.g. for inversion, multiplication, digital stuff like XOR, AND, etc...) -> very useful Best Regards, Thorsten.

Read the source code in app.c (thats part of the practice session ;-) PRINT_MSG_SELECTIONS is only set when a button has been pressed, or a CC event has been received. Note that this is only a simple demo. A sophisticated menu interface would complicate this demo too much. And it should inspire you to create something better! :) (e.g. based on the 027_scs, see for background informations) Best Regards, Thorsten.

The firmware is written in assembly language, therefore changes are error prone (especially if you haven't programmed on the firmware for more than 2 years...) no you could add a pitchwheel to an analog input so that it's available as knob function (and which can be routed to the PitchBender "knob" function). But what do you mean with "at the touch of a button"? Best Regards, Thorsten.

"Random MIDI Traffic" wuerde entstehen, wenn die Software die entspr. Inputs nicht von sich aus rausfiltert. Doch darum geht es hier eigentlich gar nicht. CMOS Eingaenge *darf* man nicht offen lassen, da ansonsten Querstroeme entstehen koennen, die zu sporadischen Aussetzern fuehren, und/oder im schlimmsten Falle den Baustein zerstoeren. Wenn Du die Widerstaende aus aesthetischen Gruenden weglassen moechtest, dann solltest Du die Eingaenge zumindest auf +5V klemmen, bspw. mit blauen Spulendraht, dann ist die Verbindung gut getarnt ;) Oder loete den Eingang einfach an einen benachbarten Pin - so eine Bruecke (aus Loetzinn) faellt nicht auf. Gruss, Thorsten.

Ooof! :-( I'm not aware of a different standard, and I fear that there won't be special IDC sockets available which adapt to the correct size. Best Regards, Thorsten.

Warum loetest Du die Pull-Ups nicht einfach auf der Unterseite der Platine an? :) Gruss, Thorsten.

Ich wusste, dass das irgendwann nochmal jemand braucht ;) Ist zwar kompliziert in der Anwendung, aber hilft offenbar weiter! :) Gruss, Thorsten.

Hi, adding the button functions for playing MIDI notes is easy. I can give you the code once you've build the hardware and you are able to try it out (usually it will have one or two bugs on the first try, so be prepared for some time consuming beta testing sessions! ;) There is only one requirement to make the SW support as simple as possible: add the additional buttons to dedicated shift registers, don't mix it with other shift registers which are used for existing functions. Mute: no way to do this via software, as it would require to fade out/in the volume with high resolution to avoid the "click", but the SID volume can only be controlled with 4bit, which isn't sufficient. In distance, you will hear a click on each volume level change since the DC level changes as well - this "imperfection" was used to output audio samples in the past ;) Best Regards, Thorsten.

Btw.: this was my best investment of the year (7 EUR) http://www.reichelt.de/Crimpzangen/MWZ-214/index.html?;ACTION=3;LA=444;GROUP=D325;GROUPID=572;ARTICLE=13300;START=0;SORT=artnr;OFFSET=16;SID=11TVLbZ38AAAIAAG9MIgIec1e46ae3eb4fc2fe4e011f269170227 It was never so easy to "crimp" IDS connectors as with this inexpensive tool! Best Regards, Thorsten.