TK.

Yes, this isn't nice... :-/ You could disable the assignment to CC#32 in src/sid_cc_table.inc replace: db 0x2c, 0x2d, 0x2e, 0x2f, 0x48, 0x4c, 0x00, 0x00 ; offset 0x20 [/code] by: [code] db 0x00, 0x2d, 0x2e, 0x2f, 0x48, 0x4c, 0x00, 0x00 ; offset 0x20 Best Regards, Thorsten. P.S.: please check your email inbox ;)

Beta30 is available: MIDIboxSEQ V4.0beta30 ~~~~~~~~~~~~~~~~~~~~~ o added LED and BUTTON functions for TRACK_MODE, TRACK_GROOVE, TRACK_LENGTH, TRACK_DIRECTION page to MBSEQ_HW.V4 file MORPH and TRANSPOSE renamed to TRACK_MORPH and TRACK_TRANSPOSE o added LED and BUTTON function for FAST2, which is a second "fast" button with dedicated button behaviour. In distance to the common FAST button, the button behaviour is configured for push (and not for toggle) mode. The intended usecase is to use this function with push-button encoders. o Echo function: support for "dotted delays": 32d 16d 8d 4d 2d In order to keep existing patterns compatible, they are mapped to parameter value 16..21, but displayed/selected in the right order in the Fx->Echo page. Please note that it isn't a bug that 32d is displayed *after* 16T, 16d *after* 8T etc - the entries are ordered by the resulting delay length! o a "Forward MIDI" option has been added to the record page. Previously events played by an external keyboard were always immediately forwarded to the MIDI output. Now it's possible to disable this function for keyboards w/o a "local off" function. o the quantization of recorded MIDI events is now freely configurable in the Record page. Than lower the percentage value, than lower the quantization (-> events not shifted to the next step) [/code] and now I want to see some happy faces! ;-) Some words to the "dotted" delays: after I noticed that 8d is my most favorite setting for audio delays, the motivation to find a solution got stronger. And there is a compatible solution: values are mapped internally - you will only notice this when controlling the delay from external via CC (or loopback) - see also the doc/mbseqv4_cc_implementation.txt file. And another note: some time ago I started a documentation for the OSC option. This is basically copy&paste of an email conversation: http://www.ucapps.de/midibox_seq_manual_osc.html Some informations are still missing, e.g. how to configure OSC in internal applications such as Reaktor or Max/MSP, and how to use the MIDI proxy to remote-control a MIDI synthesizer via ethernet. I will add this sooner or later... but as I'm still the only one who finds this topic interesting, it's low priority ;) Best Regards, Thorsten.

It doesn't matter in which order Program Change and Bank Change are received - both events will change the patch immediately. Best Regards, Thorsten.

Ooofff.. sometimes you're doing challenging projects ;) Pin #8 and #9 should work as outputs with your initialization routine. I just have doublechecked this on my board. You could measure the voltage directly on the pins of the STM32 chip (see schematic), just to ensure that they are correctly soldered. To the original problem (connect the switch to the scan matrix, first topic of this post): did you already add some debug messages just to check if and when the routine is executed, and what are the results in w/x/y/z on any switch movement? Such messages are really helpful to get a better understanding of the internal processing Best Regards, Thorsten.

Works fine at my side. Note that only values 0..7 lead to a bank change, all other values are silently ignored. You could try the bank change with MIDI-Ox - does it work with this program? You could also check if Sonar really sends CC#0 by using a MIDI-Loopback, monitored with MIDI-Ox Best Regards, Thorsten.

Oh, probably you haven't experienced the Force-to-Scale feature yet, which ensures that the sequencer will never play a terrible note. In distance: by changing a parameter slowly, the audience will hear some interesting variants - always in scale. See this video as an example: (at 2:00 pp) Although I'm not editing steps directly here (I'm using some different LFO/Echo parameters instead which are not supported by MBSEQ V3), but the effect is similar if you live-edit a common sequence. Best Regards, Thorsten.

Hi Markus, Since I find such a usage a bit cumbersome (I wouldn't use it by myself), I would only add such a mode if multiple people request it. Each new mode increases the complexity (and hard to find functions - as you already noticed). Best Regards, Thorsten.

Ok, the next release will provide these button functions (and LED functions as well for people who can't resist to use LEDs for everything) Best Regards, Thorsten.

Hi Markus, congratulations for (almost) finishing your MBSEQ! :) No, such an edit mode isn't supported (and impossible with the PIC based MBSEQ due to very reduced RAM resources). Yes: inside the option page enable the "SyncPatChange" function. It also allows you to specify the measure size (by default 16 steps) Best Regards, Thorsten.

Nils will handle the order. He is currently very busy with his diploma thesis, but it seems that he will finish soon! :) Best Regards, Thorsten.

It's great to have such warnings. E.g., in MBSEQ I had to fixed 100s of warnings (took ca. 1 hour), but I found a potential bug which could happened in the past due to function calls with incomplete parameter list (-> random behaviour) I never noticed this before as I forgot to include the header file into the .c code -> accordingly the C compiler allowed me to pass any parameter w/o producing an error about an "undeclared function" or "inappropriate usage". Due to this experience I decided to enable warnings for everybody. Sorry for the inconvenience - you would really like the change if it would have warned you about *THE BUG* that infrequently happened in the past and that you never reproduced during long debugging sessions before. ;) Best Regards, Thorsten.

Hi, the MIOS8 variant for PIC18F4685 always selects 4bit LCD mode, regardless of the SW configuration - this was the easiest way to avoid that users have to consider this, resp. that special application firmwares have to be released for this derivative. MBNET for PIC: only exists (and only makes sense) in assembly language: http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_sid_v2%2Fsrc%2Fmbnet.inc For MBHP_CORE_STM32 a C based variant (customized to the CAN interface of STM32) exists: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fmodules%2Fmbnet%2F It isn't possible to adapt this library to a 8bit controller Best Regards, Thorsten.

Kann ich mir einrichten! :) Gibt es jemanden, dem es an diesem Tag nicht passen wuerde? Gruss, Thorsten.

Diesen Monat wird das wohl nichts mehr, und einige Leute wollten weit im voraus ueber den Termin informiert werden - wir sollten mal den Dezember anpeilen. Gruss, Thorsten.

Beta29 is now available: MIDIboxSEQ V4.0beta29 ~~~~~~~~~~~~~~~~~~~~~ o implemented tap tempo function. It can be accessed in the BPM menu page (rightmost GP button), or with MENU+PLAY o fixed "accent on stretched notes" issue o fixed pattern synchronisation issue at very first played pattern in song mode [/code] Best Regards, Thorsten.

I checked this, it works like expected: the first step won't be changed if not in the selection mask and if you don't use the first rotary encoder to modify all steps. Best Regards, Thorsten.

Welcome to the club! :) I will check this soon Thats related to the MIDI protocol. It isn't possible to change the velocity while holding a note (for glide) w/o retriggering the gate! Unfortunately your request comes too late - the values are hardcoded, a change would make all existing patterns incompatible for all users. Best Regards, Thorsten.

I already ported MIOS32 to STM32F105RC, see also this posting: Adapting the new USB OTG module was a challenge, but I made it. STM32F107RC has the same USB peripheral, so that no additional MIOS32 adaptions are required. You could even compile the code for STM32F105RC, and it will work on a STM32F107RC as well. Best Regards, Thorsten.

here the just-in-time reply (you know :ahappy: ;) I haven't found 100k pots, so that I used 100k trimpots, but they shouldn't make a big difference. As long as I don't touch the middle pin, pot values are stable. Once I put my finger on this pin, values start to jitter by +/- 1 LSB (7bit) I think that you can use the common MIOS32 driver without modifications. The metal case of the pot should be grounded, cables to J5A shouldn't be longer than 10..20 cm, and it also makes sense to add a 100 nF cap from the middle pin to ground to filter high noise jitter. Best Regards, Thorsten.

Waehrend des heutigen Synthesizer Treffens in Muenchen haben mehrere Leute Interesse an einer Jam Session bekundet. Meine eigene Wohnung ist fuer mehr wie drei Leute (+ Synths) zu klein, doch Marco haette Platz fuer 5..7 Leute; ausserdem gibt es in der naeheren Umgebung keine Nachbarn, die sich ueber die Lautstaerke beschweren koennten! ;) Falls also jemand aus dem Raum Muenchen Interesse hat, einfach hier posten, oder mir eine PM zuschicken - es gibt keine "MIDIbox" Pflicht (also auch ideal fuer Leute, die einfach nur mal mit einer MIDIbox herumspielen moechten), aber einen Klangerzeuger sollte schon jeder mitbringen, wir wollen schliesslich Krach machen! Termin steht noch nicht fest, doch das Treffen wird wahrscheinlich an einem Sonntag stattfinden. Gruss, Thorsten.

Could you please test the 12V voltage again under load, I mean when the SIDs and the PIC are plugged into the sockets? Just an idea that your PSU is too weak Best Regards, Thorsten.

An ohmeter test on capacitors doesn't give you usable result. E.g, the resistor value changes if the cap is charged or not... Did you already check that the 6581 are supplied with 12V? Because at 9V the filters won't work properly. Best Regards, Thorsten.

With this one: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Ftools%2Fosc_midi_proxy%2F Alternatively I can use MBSEQ as a proxy (it provides the same functions) and forward OSC events to any MIDI device - either via USB or UART based MIDI. But this wasn't the point - the real MBSEQ has an ethernet interface, it could control the Logic Functions via OSC now instead of MIDI for higher flexibility. Best Regards, Thorsten.

See snapshot: Translation: support for control surfaces based on iOS Apps that utilize the OSC protocol. MBSEQ is prepared! :) Best Regards, Thorsten.

Great how you integrated the sequencer into the case! Also the demo is very nice - blogged :) Best Regards, Thorsten.