TK.

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.

Great, fine! :) Verbose Level 3 generates an extra message for the case that the decoding routine filters out DIN events, so that they are not displayed. It's mainly for people who want to re-use the code, but have to change the decoding. Best Regards, Thorsten.

Press the MENUEXIT button and scroll with the datawheel to the end of the list. CV Configuration is the page before the ethernet configuration. There is no special button combination available to enter this page. Best Regards, Thorsten.

Hi Robin, I finalized the application (at least for my side): - velocity delay values now defined as variables, so that they could be changed during runtime - DOUT now always latched after SRIO scan, because I've a better feeling when outputs are already stable before DINs will be latched some 100 microseconds later - VERBOSE_LEVEL set to 1 for best performance (increase it to 2 or even 3 to get more debug messages) Could you please confirm that the "final" version works properly at your side before adding your changes? For finding the best matching values, the usage of a pot would be perfect. Alternatively you could add a CC handler which receives delay values from an external MIDI controller (disadvantage: only values from 0..127 could be sent) Or an "input terminal" could be implemented which allows to receive commands from MIOS Studio - but this wouldn't really be worth the effort, although you like geeky solutions! alright, done. Thanks! :) Yes, I hope that other people feel inspired and provide customizations for their own systems. Once you've finished your program, we could release it in a different folder as an additional example. Btw.: I'm planning to rename this thread in some days, because the topic "SRIO, DOUT, DIN, 16 bit , 8bit Confusion" doesn't match anymore. Best Regards, Thorsten.

Gridracer.Karma -= 1; Just kidding! You can still feel welcomed for reporting any anomaly that you noticed, you found a lot of issues in the past! :) Grizz: I'm still puzzled about your issue and don't have an answer. There is neither an additional pin, nor something else which would be special. I know that you already checked the SPI connections... so, everything should be fine. On the other hand I improved the initialisation part of the AOUT driver that is integrated into MBSEQ. It should work more robust now - therefore it will be interesting if this already solves your issue. Best Regards, Thorsten.

Du bist wirklich ein Klugscheisser! Gruss, Thorsten.

The default 750 mS delay between SysEx blocks is probably not high enough - the actual programming time depends on the initial content of your EEPROM (BankStick) and the CPU load which is caused by the currently active patch. If you upload the patch again, programming time should be much shorter, as MIOS only overwrites EEPROM pages which are different from the new content. Maybe I should change the default setting in MIOS Studio to 1000 mS to avoid such upload errors. On the other hand: if you would use the MBSID Editor, a patch upload wouldn't depend on such mysterious delay values as the next patch won't be sent before the previous had been acknowledged by MBSID -> most robust solution -> go for it! :) Best Regards, Thorsten.

Hi, You haven't mentioned how you uploaded the patches. Maybe there was an error during transfer which you haven't noticed? If you are using the MBSID Editor a message should pop up. However, it would be interesting if it works if you upload the patches again? Best Regards, Thorsten.

Welcome back! :) No, it neither has been skipped, nor it has been changed. Could you please check that the BUTTON_BEH_ALL variable is set to 1 in your MBSEQ_HW.V4 file? BUTTON_BEH_ALL 1 [/code] it only affects the currently selected layer as expected/suggested. Could you please describe me how I can reproduce this misbehavior with a freshly initialized track? If it only happens with one of your already existing tracks, could you please export the track to a preset file and attach it to this thread? Best Regards, Thorsten.

Thanks! I optimized the loop again, now we are counting from -1 to 15, and handle row==-1 as an "initial state". This leads to better readable code. Could you please try again? I hope that I haven't added another error. Velocity curve: I entered your measuring results into a spreadsheet and assumed, that each "level" reduces the velocity value by -30 (just an assumption) It turned out that the curve is pretty linear: So, instead of using heavy mathematical stuff (like log() or exp()), it could be sufficient to change KEYBOARD_DELAY_FASTEST and KEYBOARD_DELAY_SLOWEST into variables, and to switch between two value sets with a switch. Best Regards, Thorsten.

Bei 100 AUD muss man so oder so Zoll/Mwst. bezahlen, egal ob es ein Geschenk ist oder nicht. Gruss, Thorsten.