TK.

You could follow the tracks from J2 to J10 with the probes of your multimeter in order to find the error. Best Regards, Thorsten.

You could follow the tracks from J2 to J10 with the probes of your multimeter in order to find the error. Best Regards, Thorsten.

I've shifted the project by at least one year due to other priorities (e.g. MIDIbox SEQ). However, if you only want to mix rotary encoders with pots or motorfaders, MB64E is currently a good choice Best Regards, Thorsten.

I've shifted the project by at least one year due to other priorities (e.g. MIDIbox SEQ). However, if you only want to mix rotary encoders with pots or motorfaders, MB64E is currently a good choice Best Regards, Thorsten.

good idea ;-) Best Regards, Thorsten.

The competition has started! enjoy the logos under http://logo.midibox.org, (try to) find your favourite one (it's difficult, I know) and vote for it in the MIDIbox Portal http://portal.midibox.org In order to avoid manipulations, this survey is restricted to registered members! We will vote in three rounds: 1st round: from 2nd May to 9th May 22 p.m. GMT: all logos 2nd round: from 9th May to 16th May 22 p.m. GMT: the 6 best logos 3rd round: from 16th May to 23th May 22 p.m. GMT: the 3 best logos Best Regards, Thorsten. /edit 2004-05-09: since there were many logos with one vote only, the second round begins with 5 options

Check out the creation of Doc! :) He wrote some interesting comments to his design, the english translation in bold font:

Hi chrom, a very characteristical SID tune, maybe a little bit too much compressor Fx, but I like it! :) Best Regards, Thorsten.

Hi, just send me your project directory so that I can search for the reason. Best Regards, Thorsten.

Hi Doc, so long you are not using the BankStick (or a SID/AOUT module), no hardware changes are required. So, thats ok. But the behaviour of the solo button is very strange! I will check this with my MIDIbox LC once I've adapted the KS0107/KS0108 driver to the new pinning. Best Regards, Thorsten.

Hi, no, this isn't possible w/o a lot of programming effort. Best Regards, Thorsten.

Two new contributions from d2k and Chriss: http://logo.midibox.org

Du schaffst das schon ;-) Bringt ja nix, wenn ich halbherzig an einer Sache arbeite, die ich selbst nicht verwenden wuerde. Ausserdem muss ich erstmal meine eigenen Projekte zuende bringen (das reicht bis zur Rente ;-)) Gruss, Thorsten.

Hi, LC_MPROC_Action_Meter as well as LC_MPROC_Received_D0 already store the received byte in the METER_MODE array (consists of 8 items, one for every meter). So, you can access this array whenever you want to get the "p" bit. Btw: this bit is already displayed by the center LED of every LED ring if meter mode enabled. It's not optimal to use the LC_MPROC_Action_Meter to update additional LEDs, since the mode could also be changed by a D0 event. The most proper method is to hook the additional code to the LC_METERS_Handler in "lc_meters.inc" (see code) Best Regards, Thorsten. P.S.: the result of a mullw instruction can be found in PRODL and PRODH, and not in WREG

Ok, I found the error: it doesn't work with two 32k BankSticks since there is a test which ensures that a 64k BankStick is connected before formating the song partition. This function should not be called on two different 32k BankSticks of course. I tested it with two 24LC512 - and this test passed, therefore I didn't know about this issue. However, you will find a patch under http://www.ucapps.de/tmp/mbseq_v2_0_bs_fix.zip - it will be part of the next release. Best Regards, Thorsten.

Hi, the result of #if LCD_USE_SECOND and #if LCD_USE_SECOND == 1 is the same, so this cannot be the reason. The only changes of the modified lc_mproc.inc and the original lc_mproc.inc of v1.4 are: [avatar@britannia mblc_sonar_mod]$ diff -c /mnt/data/mios_apps/release/midibox_lc_v1_4/lc_mproc.inc lc_mproc.inc *** /mnt/data/mios_apps/release/midibox_lc_v1_4/lc_mproc.inc 2003-09-29 14:22:28.000000000 +0200 --- lc_mproc.inc 2004-03-29 01:43:07.000000000 +0200 *************** *** 360,365 **** --- 360,369 ---- bz LC_MPROC_Action_Query movf LC_MPROC_ACTION, W + xorlw 0x1a + bz LC_MPROC_Action_MCQuery + + movf LC_MPROC_ACTION, W xorlw 0x02 bz LC_MPROC_Action_HostReply *************** *** 373,379 **** movf LC_MPROC_ACTION, W xorlw 0x12 ! bz LC_MPROC_Action_WriteLCD movf LC_MPROC_ACTION, W xorlw 0x13 --- 377,384 ---- movf LC_MPROC_ACTION, W xorlw 0x12 ! skpnz ! rgoto LC_MPROC_Action_WriteLCD movf LC_MPROC_ACTION, W xorlw 0x13 *************** *** 427,432 **** --- 432,463 ---- rgoto LC_MPROC_ActionFinished ;; -------------------------------------------------------------------------- + ;; MIDI Action: MC Query (undocumented) + ;; -------------------------------------------------------------------------- + LC_MPROC_Action_MCQuery + ;; wait until sysex footer (F7) has been received + movlw 0xf7 + IFNEQ LC_MPROC_IN, ACCESS, rgoto LC_MPROC_SysExCheck_End + + ;; send SysEx header + call LC_MPROC_Send_SysExHeader + + ;; send reply + movlw 0x1b + call MIOS_MIDI_TxBufferPut + + ;; send dummy byte (seems to work) + movlw 0x42 + call MIOS_MIDI_TxBufferPut + + ;; send of SysEx footer + movlw 0x01 ; (independend from merger state) + call LC_MPROC_Send_SysExFooter + + ;; finish Action + rgoto LC_MPROC_ActionFinished + + ;; -------------------------------------------------------------------------- ;; MIDI Action: LC Host Reply ;; -------------------------------------------------------------------------- LC_MPROC_Action_HostReply so: the new LC_MPROC_Action_MCQuery and a change for the LC_MPROC_Action_WriteLCD branch (distance between the "bz" and the function was > 128 bytes, therefore a rgoto has to be used). It should work if you just overwrite the old lc_mproc.inc with the modified one. Maybe you've modified the source code in a way which prevents the LC_MPROC_Action_WriteLCD function from being called... Best Regards, Thorsten.

I guess that a microcontroller based vu meter would require a seperate core module + a lot of external electronic to prepare the audio signal and especially to convert the db scaling + the appr. software. So, it's simpler to use a dedicated IC for this job like the LM3916. See this project http://www.all-electric.com/schematic/quad-met.htm Best Regards, Thorsten.

Hallo, danke fuer das Lob - es motiviert zu weiteren Taten :) Das Poti wird zwischen 0V und 5V geschaltet, die Spannung am Schieber liegt also immer zwischen diesen beiden Werten, unabhaengig vom Widerstandswert. Jedoch: je kleiner der Wert, desto hoeher der Stromverbrauch, je groesser der Widerstand, desto hoeher der Rauschanteil. Deshalb sollte der Poti-Wert zwischen 1k und 10k liegen (Erfahrungswerte) - 100k sind definitiv zu viel. Und der Spannungsverlauf sollte linear sein. Beim Taster spielen die Spannungs/Stromwerte keine Rolle, der Stromverbrauch ist minimal. Gruss, Thorsten.

Ja, wenn MIOS bereits drauf ist, sollte das LCD etwas anzeigen. Gruss, Thorsten.

Theoretisch koennte man Gruppen ueber die MB64E_ENC_UpdateMap Funktion in mb64e_enc.inc realisieren. Hier werden die Encoder momentan je nach selektierter globaler Gruppe auf die entsprechenden Encoder Eintraege gemapped. Dich man koennte natuerlich auch weitere Gruppen definieren... Dafuer stehen allerdings "nur" 128 Encoder Eintraege zur Verfuegung (oder wie ein Amerikaner schreiben wuerde: es steht die absolut gigantische Menge von bis zu 128 Encoder Eintraegen zur Verfuegung, die bei eingehenden MIDI Events sogar gleichzeitig verarbeitet werden koennen - das kann bisher kein anderer MIDI Controller auf dem Markt ;-)). Mehr geht nicht, dafuer ist das MB64E Konzept nicht ausgelegt. Braucht aber auch keiner - denn das Mapping kann man genausogut ueber die Host Software realisieren. Nuendo sollte eigentlich genauso wie Cubase SX in der Lage sein, mit selbstdefinierten Controller Gruppen umzugehen, die sich dann via MIDI umschalten lassen. Auf diese Weise koenntest Du beliebig viele Gruppen definieren, die dann von der Host Software verwaltet werden - oder nicht? Jedenfalls waere das die geeignetere vorgehensweise Gruss, Thorsten.

How does MBSEQ behave with: #define DEFAULT_BANKSTICK_PATTERN_CS 1 #define DEFAULT_BANKSTICK_SONG_CS 0 ? Best Regards, Thorsten.

Hallo, 1 und 2 lassen sich en block beantworten: die Host Software bestimmt die Aufloesung und die Geschwindigkeit, und beides ist durch das Uebertrgaungsprotokoll der Logic/Mackie Control vorgegeben. Wie so oft - auch hier kann man von der Anwenderseite nichts aendern. Nein, es ist nicht moeglich, neben den Motorfadern noch weitere Potis an einem einzigen Core zu betreiben Gruss, Thorsten.

I didn't saw this imperfection since it's already fixed in my private version. Open lc_sfb.inc, go to line 238 and change "rcall" by "call" Best Regards, Thorsten.

Hi Chriss, unfortunately the patch request function of jsynth is still not reliable, but a whol BankStick backup can be realized much easier, just follow these instructions: http://www.ucapps.de/mios/mios_backup.txt My question: has anybody already created more than 128 different patches? ;-) Best Regards, Thorsten.

I guess that you are using the vintage setup, so possibly setup_mbseq_vintage.syx? This would mean that you have to change setup_mbseq_vintage.asm, and you have to assemble this file instead of main.asm Best Regards, Thorsten.