TK.

Win98: here TEST_PC1 and TEST_PC2 is extremenly important, user reported a lot of driver problems with this old windows version Best Regards, Thorsten.

great! :) Best Regards, Thorsten.

In the last time it happens very often, that people ask questions like "does MIDIbox XX support feature A like my favourite device B". This is what I find a little bit frustrating, because it definitely sounds like a demand, and leads the dialogue into a wrong direction. So, let's talk about these topics on a different basis. I especially find it very important, that you now have descibed your ideas in more detail, this makes it much easier for myself to think about an adequate solution, instead of forcing me to work out a concept which could match with your wishes. there is no special list, I just send the snapshots to people who asked me for beta testing. It is not so easy to provide two additional parameters (min/max limit) for such a minor feature. The reason is the way how I've organized the memory. Currently each track allocates 32 bytes for parameters, in the meantime only one spare byte is available anymore, and this is reserved for really important things, which could be added in future. I don't want to reserve a larger area for track configuration data, since this wouldn't allow me anymore to store 128 patterns in a 64k BankStick (as programmer you propably know, how important the 2^x values are) However, your idea can be realized on a different, and in my eyes on a much more flexible way. There is a CC for semitones, and another CC for octave transpose. Thanks to the internal loopback port it's possible to play these CCs from one track, and to send them to another track. This means in other words, you can control the octave or semitone transpose from a second track. By setting the clock divider of this track to a high value, it's possible to change the transpose value after each 16 steps of the "note track". One track can send up to 3 CCs In addition, there are things possible, about you've propably not thought about yet. :) E.g., the control track can be forwarded with a special progression pattern (what you see in the last video), or randomly, or manually, or ... In general I don't support pitch bend anymore, since the MBSEQ works internally with 7bit values, so using Pitch Bend results into the same like using a CC mapped to a detune (finetune) parameter of the synth. The concept is flexible enough, that I could add a new event mode which sends Pitch Bender events, but I don't see much use for it. But this is only some background information, and not the answer to your question. Do I see it right, that you mean a semitone transpose - than it would work in the same way like for 2) --- yes, it's possible to control a "CC length", which means: CC will be set to the step value for a given gate time, and thereafter set back to 0 Currently this has to be done by setting the gate length to maximum, so that the step will be tied with the next step. By doing so, a note can be held over the whole track length. But it wouldn't be so difficult to add a "sustain flag" - I will do this problem here is, that the sequencer has to memorize the played notes if they should be killed on command. This consumes a lot of memory - since there are 5 MIDI Out ports, and 16 MIDI channels, 10240 notes = 1280 bytes would be required (so much RAM is not free anymore). A "All Note Off" CC could do the same, but most of the synths I own don't support this... Alternatively Note Off events could be sent over all channels and ports, but this consumes a lot of time (for 10240 notes: 10 seconds) (this is possible) unterstood. Problem here is, that I don't know, where to store the pause within the layers. Only possible position would be the gate delay, but it's already 5 bit (due to the 96ppqn resolution), and the remaining 2 bit are used for the double/tribble/quadruble step triggering. What I could do is to add a mode, which turns the double/tribble/quadruble step triggering into a 2x, 3x, 4x pause, but I don't know if this is really flexible enough. And it would mean that I have to do a lot of changes at different places within the firmware, since such a change hasn't been considered at the beginning. It depends, for delay you can only set static values or the "groove intensivity" parameter, which can be changed via CC (think about the loopback possibility). Negative delays are not possible. For Velocity and Length you can set percentages (20%..160% in 10% steps) or the groove intesivity parameter (again) Best Regards, Thorsten.

Hi, MIOS doesn't run on PICs with integrated USB peripheral, this means that you would have to implement the operating system from scratch. In addition, you propably have to write your own windows driver if you want to transmit events which don't comply to the MIDI protocol. However, by using NRPNs or Pitch Bender events, it is already possible to send 14bit values, so one of the fist steps would be to read the MIDI spec (see also ucapps FAQ) What do you understand under "fast"? How many values need to be updated within which time? there is not that much documentation available, only the schematics at ucapps.de there are different ways, they should be documented in the manual which comes with Cubase (I'm not a Cubase user, therefore I cannot help here - for Logic a special LC manual is available, the link is in the Wiki) they use multiple MIDI IO ports (so, it's not chained) the maximum resolution provided by the LC protocol is 14bit (faders send and receive pitch bend events), but the PIC only provides a 10bit ADC Best Regards, Thorsten.

Hi Ole, yes, it's unfortunately required (see also the FAQ: http://www.midibox.org/dokuwiki/doku.php?id=mios_pic18f4620) Is the 5V voltage stable over the whole time, or does is sink slowly? The PIC will reset automatically, once it is sunk below 4.6V (so far I remember) Best Regards, Thorsten.

So, the monitor always receives a 0xff and never another MIDI byte? Which tests of the MIDI troubleshooting guide did you try, and what are the results? They are enumerated now, so it's easy to write down - for example: TEST OUT1: LED flickers TEST OUT2: using a xxx PSU (replace xxx by the one you are using...) ...etc... Best Regards, Thorsten.

;) Have fun! :) Best Regards, Thorsten.

Hi Xavier, if you would have quoted the paragraph below this one, you would find the answer Yes, this can happen when MIDI events are received from a sequencer and CC data is sent out at the same time... Best Regards, Thorsten.

Hi Intellihel, asking questions this way implicates, that you would "only buy the sequencer" if all these features are implemented. Please note that this a DIY design, features are implemented as I find them useful, and as I find the time (currently I don't have that much sparetime) However, to answer your questions: It's already distributed via email to people who have built a MBSEQ V2 I don't know, what this exactly means, could you please elaborate this feature request in more detail? Maybe it's already implemented under another name? no see answer to 2 As described in the wishlist: no Could you please describe a usage example in detail? How should this be used? Maybe it's better when you first build the sequencer in order to get familar with the user interface, thereafter you can give more explicit hints. Sometimes the most difficult thing is not the coding, but to find a way how the user can activate functions without clicking through 100tes of menues... already possible - and not only shuffle, but whole grooves (delay/length/velocity mod) for 16 steps (32 steps: 2*16 steps duplicated) already implemented already implemented I don't like requests like "it must be working like this or that device" - it's working how I find it useful. Of course, inspirations are welcome, but the implemerntation of certain features are sometimes not possible since they conflict with other things (e.g. implementation of the sequencer core engine, or available buttons on the existing user interface). Best Regards, Thorsten.

Hi Jussi, in addition to MIOS, you need to upload the MIDIO128 application, which can be found at the MIOS download page. Thereafter you will be able to upload the configuration file :) (nice to know, that this is the only problem!) Best Regards, Thorsten.

The questions are repeating, I've answered them several times... therefore I've started a FAQ: http://www.midibox.org/dokuwiki/doku.php?id=mios_pic18f4620 Best Regards, Thorsten.

Habe sie nun erhalten. Manchmal bleiben Mails im GMX Spamfilter haengen, mit etwas Glueck finde ich sie dann auch Tage spaeter, doch meistens werden sie ungesehen geloescht - brave new world :-/ Gruss, Thorsten.

Your answers are a little bit confusing, I don't know if we are talking about the same things... First you wrote: Now you write: So, what is the voltage between ground and the input pin of the 7809, which is stuffed on the SID module? And which test passes when 15V are connected to J1 - do you hear a sound? Or do you mean any other test? Please also answer Mike's questions Best Regards, Thorsten.

Here a quick demonstration of the Button/Duo-LED matrix extension: -> it isn't built into a case yet, therefore I had to push the buttons very carefully due to the loose caps. The frontpanel will be ordered today (it's sponsored from the donations! :) Best Regards, Thorsten.

The voltage before the 7809 must be higher than 9V, the voltage after the 7809 must be 9V Best Regards, Thorsten.

Hallo, mit dem V3 PCB ist der zweite 10k Widerstand obsolet - ich habe ihn nun aus der Bauteilliste entfernt Gruss, Thorsten.

This is a MIDIbox SID with CS, built into a Floppy Drive by Clemens :) He wrote:

Hi, If you don't hear any sound (even no digital background noise from the SID), then it's very likely that either the transistor is not connected correctly (compare it with the pictures), that there is a short at the audio out stage, or that the voltage at pin #28 is not 9V Best Regards, Thorsten.

Hi Ole, does it also happen when the LCD backlights are not connected? Then it's definitely a thermal issue, caused by the too high voltage before the 7805 (7..8V would be better) Note: a core module can be supplied even with 12 or 15V at J1, but only if the power consumption is low enough, so that the 7805 doesn't get too hot. The two BLs, and also the LEDs, consume so much power, that a better fitting PSU is required. Best Regards, Thorsten. P.S.: before you buy a new PIC (I don't think that this is a problem!), consider to buy a PIC18F4620 and PIC16F88 (for MIDI out), so that you can use the new MBSEQ V3 firmware :)

fixed.

It's the MIDIbox of Klingen (he informed me about the upcoming article some weeks ago) -> http://www.midibox.org/forum/index.php?topic=4902.0 Best Regards, Thorsten.

Hi, It's a B4 (due to a bug in the application the wrong letter will be displayed) And here the bad news: I also got a B4 from Microchip some weeks ago, it turned out that the EUSART bug still exists. Microchip has released an incomplete errata sheet! I reported this mistake and only got this "typical" answer from the support guys: My hope was, that they update the errata sheet quickly, so that I can take it as a reference - but nothing happened yet! However, I haven't found the time to update all the relevant webpages at ucapps.de and in the wiki again - but the consequence is, that the MBHP_IIC_MIDI workaround will be required for the next years! Best Regards, Thorsten.

-> www.edrum.info Best Regards, Thorsten.

The core sends an upload request, but doesn't receive any SysEx block, therefore doesn't respond with an acknowledge. It's very likely, that the MIDI In port is not working -> the MIDI troubleshooting guide will help http://www.ucapps.de/howto_debug_midi.html Best Regards, Thorsten.

thats correct. In theory you could use optocouplers for the Rx/Tx line of the MAX232 in order to decouble the PC from the core module, but I cannot give you a schematic for this, this would have to be worked out by yourself. Thats interesting, this might explain why the driver hangs up? Maybe because an incomplete event which was received due the "shortened" Rx line (sidenote: it's not completely shorted, because the optocoupler output is open drain - but the signal level at the Rx input of the PIC will be lowered). So - does it work more stable without the optocoupler, then you found a solution. If not, the RS232 link just doesn't work quite well with your PC, and either the LTC circuit has to be enhanced, or a common MIDI connection has to be used. Best Regards, Thorsten.