TK.

Thank you :) Currently I'm mainly busy with testing all the new functions, which mostly results into programming "unplanned" new features (every session leads to new inspirations). But I guess that I will go for a release in about 2 months. However, before the public release, interested guys can already receive a snapshot .zip of the current development, so long they promise, that they won't report bugs or missing stuff that I already know ;-) Matteo: yes, only the PIC needs to be replaced, and at least one reduced MBHP_IIC_MIDI has to be added (MIDI Out only, the simple circuit). It's possible to route the tracks to different IIC modules, so it might make sense to build two or three of them. I will integrate a second MIDI Out into my own MBSEQ very soon, because this allows me to use different instruments without adjusting the MIDI channels all the time I'm trying different combinations. The "internal" (EUSART based) MIDI Out is available as fifth MIDI Out, but it only works without failures so long the sequencer doesn't receive MIDI data. Best Regards, Thorsten.

A video says more than thousand words :) -> Best Regards, Thorsten.

Propably the SID module is not correctly connected, what are the results with the interconnection test? Best Regards, Thorsten.

Ok, so the PIC is propably running, but the MIDI interconnections are not working. When you are doing (really) all the tests, you should be able to find out the root cause. Shortcut: most people just swap the pins on the MIDI In and/or Out jack Best Regards, Thorsten.

There is an even easier solution: just configure the right LED mode in MB64E (I assumed in my posting that you are already aware of this possibility) See also http://www.midibox.org/forum/index.php?topic=4981.0 See also http://www.midibox.org/forum/index.php?topic=6039.0 So, you want to display the MIDI status, and not the button status with the LEDs, which means, that the LED modes should be set to 16..23 Best Regards, Thorsten.

Wenn man die Rasterung entfernt, und den Encoder Modus NON_DETENTED einstellt, liefern sie 64 impulse. Und mit Hilfe des "Fast Speed Mode" wird progressiv beschleunigt, so dass ein Parametersweep ueber den gesamten Wertebereich mit einer Handdrehung durchaus drin ist. Gruss, Thorsten.

It works, even on my old Palm Vx :) But I would also prefer a slider, or better: dedicated menu screens for sound parameter settings with buttons and sliders for intuitive and especially fast usage :) Best Regards, Thorsten.

Hi Ben, yes, I tried a certain P&G Motorfader type some time ago, and the result wasn't very promissing - mainly, because the MBHP_MF module and the MIOS based motorfader driver is not suitable for such fast (and power consuming) faders. The complete details can be found here: http://www.ucapps.de/mbhp_mf.html As for the idea to use 64 level meters: the LC protocol provides only 8 meters and channel strips (Mute/Solo/Select/Rec pair). So, it won't work, even if I would enhance the firmware by additional events, because the whole handling relies on the host software. Best Regards, Thorsten.

Lies Dir bitte nochmal den Thread zur Control Extension genau durch - das Layout wird sich (dramatisch) aendern, und ich werde nicht vor naechstem Jahr daran arbeiten (vorher muss erstmal die MBSID V2 in trockenen Tuechern sein) Die Anordnung der Buttons/LEDs/Encoder wird so spaeter nicht funktionieren. Gruss, Thorsten.

So, the scan matrix sends MIDI events when you are running the example application sm_example1 stand alone, but it doesn't work when you are using the sm_simple.inc inside the MBSEQ application? Seems, that you forgot to insert the hooks into main.asm? (see the header of sm_simple.inc, examples can be found in the main.asm of sm_example1) Best Regards, Thorsten.

-> http://www.ucapps.de/mios/change_id_v1_9c.zip Best Regards, Thorsten.

So, you haven't built in the debug code like proposed above? (Sending MIDI events to display which button has been pressed...) Without such informations (saying "nothing happens") your comment is useless ;-) Best Regards, Thorsten.

Das ist ein Trugschluss, denn bereits der MRST# und der Startup Timer sorgen eine asynchronitaet (siehe Datasheet), die Latenzen von MIDI tuen ihr uebriges. Ausserdem moechte man ja gerade fuer einen analogen Sound keine einheitliche Phasenlage zwischen den Oszillatoren, und wenn man es dann doch mal ausprobieren moechte, kann man auch die OPS (Oscillator Phase Synchronisation) Flags setzen... Viel interessanter ist das gezielte verschieben der Phasen. Hierfuer hat Wilba einen Algorithmus entwickelt, mit dem die Phase stufenlos einstellbar ist. Wenn bspw. OSC2 gegenueber OSC1 um 33% versetzt wird, und OSC3 gegenueber OSC1 um 66%, und alle drei Oszillatoren anfangs mit der gleichen Frequenz laufen, dann ergibt sich in der Summe die dreifache Frequenz. Interessant wird es nun, wenn OSC2 und OSC3 leicht verstimmt werden, dann verschiebt sich dynamisch das Soundspektrum. Und noch interessanter wird es, wenn auf einem zweiten SID die Phasen ebenfalls verschoben sind, hier jedoch mit einem anderen Anfangswert. Der resultierende Stereoeffekt ist einfach fantastisch! (und wird in der MBSID V2 auch allgemein verfuegbar sein :)) Gruss, Thorsten.

Steht der Encoder Mode auch auf DETENTED (nicht DETENTED2)? Siehe auch http://www.ucapps.de/mios/mios_encoder_modes.gif Vielleicht liefert ein anderes Pinning bessere Ergebnisse. Zum Ausprobieren den Speed Mode am besten auf 0 lassen. Gruss, Thorsten.

PC PSUs are switching power supplies, they need a certain load to work correctly, and they intersperse some high frequency noise into the circuit, which has to be filtered out with coils and caps. There are people who tried this before, some had luck, some not... if you want it newbie friendly, then don't use a switching PSU... yes, there are jacks available which are doing this automatically - they shorten the input to ground when no plug is inside the jack. I never really used the Audio In... Best Regards, Thorsten.

It won't work if toggle is handled at both sides. Either MB64, or Traktor should toggle the button. Traktor should be prefered, so that the LED is always in-sync with the host setup - if the LED is not set correctly, then this is propably a bug in Traktor. Best Regards, Thorsten.

If you want to keep it simple, then just write: SM_NotifyToggle ;; button number (0x00..0x3f) in MIOS_PARAMETER1 ;; the selected track is: MIOS_PARAMETER1[5:4] swapf MIOS_PARAMETER1, W andlw 0x03 call MIOS_HLP_GetBitORMask ; each track has a dedicated bit, use the OR mask pattern for conversion iorlw 0xf0 ; (for track button hold detection bit 7-4 must be 0xf!) SET_BSR SEQ_BASE movwf SEQ_SELECTED_TRKS, BANKED ;; the GP button number is MIOS_PARAMETER1[3:0], we can mask this: movlw 0x0f andwf MIOS_PARAMETER1, F ;; branch to GP button handler goto SEQ_GP_Button [/code] (I haven't tried this code, propably you need to debug a little) Best Regards, Thorsten.

You could build some debugging code into your modifications in order to debug this. Simplest solution: just send a MIDI event which contains the button number and the value, e.g. B0 <button> <value> But remember: MIOS_MIDI* will change the BSR, it has to be changed back to "SET_BSR SEQ_BASE" after the MIOS_MIDI_TxBufferPut functions have been called Best Regards, Thorsten.

Hi, I cannot recomment the use of touch sensors for a Sequencer. In theory it works, but in practice you won't be happy if functions are unintentionally triggered when you go with your fingers fast over the sensors. Just think about, how it would be, if your computer keyboard would consist of touch sensors! Best Regards, Thorsten.

yes, there is a way to provide Inc/Dec MIDI Events instead of absolute MIDI events, only a small number of changes have to be made in the CC handler of sid_midi.inc - but it would only be a "poor" solution, and would work completely with already available stuff. E.g., the VST plugIn wouldn't work anymore, the master/slave system (if SID slaves are connected to the master), etc... But does this really make sense to use Inc/Dec events, when you don't know, which value the CC has reached? I would propose to build a complete Control Surface instead searching for a tinkering solution to get the Doepfer controller properly running. The CS is cheaper, but much more powerful anyhow. And remember, that the CS provides a controller function as well, so that you could sell your Doepfer controller thereafter ;-) Best Regards, Thorsten.

To 1) 15V is specified to be at the secure side if somebody with no electronic background knowledge orders a PSU 14 V PSUs are very rarely available, 15 V are much easier to get and mostly much cheaper. I wouldn't use a PC PSU, too noisy... To 2) so long a voltage source is connected to the Audio In, you won't hear that much additional background noise. General rule: Use the Audio In whenever you want, put the jumper on it when you are not using it in order to achive best results. You can also let the audio In open of course, the jumper measure is just to achieve the optimum! I think that you will quickly notice this, when you are doing the first experiments on your own MIDIbox SID. Maybe you won't hear any change regardless if the Audio In is shortened or not (like most people...) Best Regards, Thorsten.

Warum? Der PIC wird im HS Modus betrieben, somit ist der interne Oszillator aktiv. Der Quarz und die beiden Kondensatoren sind Teil des Schwingkreises (-> analoge Schaltung). Es ist nicht moeglich, die XTAL Pins zweier Oszillatoren einfach zusammengeschalten. Man koennte jedoch einen externen, integrierten Oszillator hernehmen, und diesen an Pin 13 von allen PICs anschliessen. Ich sehe hier jedoch keinen Vorteil - weder technisch, noch preislich. Gruss, Thorsten.

Did you include sm_simple.inc before or after mios_tables.inc? Normaly it should be added at the end of main.asm (e.g. below the "reusable utility functions" comment) to avoid address conflicts Best Regards, Thorsten.

Maybe you've added something to mios_tables.inc, so that the tables don't match into the small address space between 0x3082 and 0x327f anymore. However, thanks to MIOS V1.9, these tables could now be located outside mios_tables.inc again (it was the only trick I found out to add some more code) Especially with the PIC18F4620 there is no memory issue anymore, so ... just put the DIN and DOUT tables into a new .inc file :) Best Regards, Thorsten.

Maybe you need to select the right PIC in the mios.h file? Best Regards, Thorsten.