TK.

Sounds like a pulse waveform whose pulsewidth is modulated by one or more LFOs. Once the PW reaches the maximum value, you won't hear a sound - in this case reduce the depth value. Could you please record some of the presets so that I can hear the difference? Best Regards, Thorsten.

Hi, go into the Bank menu and select different banks with the Left/Right button. On which banks do you see an asterix marker ("*"), and are there any banks where you don't see this marker? Try also to format the BankStick by holding the Snapshot button for 2 seconds within the Bank menu Best Regards, Thorsten.

Hallo, ich habe vor langer Zeit mal versucht, einen PIC16F628 mit dem JDM zu brennen - leider ohne erfolg. Ich vermute einen Fehler in IC-Prog, weil zwar Daten ankamen, diese jedoch nicht vollstaendig waren. Ausserdem war ein regelmaessiges Muster zu erkennen (kann mich nicht mehr so genau erinnern, jedes vierte Wort stand auf 3FFF oder so...). Gruss, Thorsten.

Ich darf mich mal selbst zitieren, diesmal auf Deutsch: "MIOS kann alles was Du willst, nur muss es auch jemanden geben, der es so programmiert wie Du willst..." Gruss, Thorsten. P.S.: Dies ist kein ignorantes Posting, nur habe ich gerade keine Zeit, deine Fragen genauso ausfuehrlich zu beantworten, wie ich es schon des oefteren bei anderen Leuten getan habe... hier hilft die Search-Funktion des Forums weiter.

Servus, fuer so etwas nimmt man doch keinen PIC18F452, oder wuerdest Du auch einen Pentium fuer eine automatische Blumengiessanlage hernehmen? ;-) Evtl. waere ein PIC12Cxxx besser geeignet, diese Mini-PICs mit 8 Pins werden vor allem fuer Minimalanwendungen gerne eingesetzt. Den UART muesstest Du softwaremaessig realisieren, aber solange nichts anderes nebenher laeuft, was groessere Latenzen erzeugen koennte, sehe ich darin kein unloesbares Problem. Baudrate/Frequenz: die MIDI-Baudrate liegt bei 31250, oder besser gesagt: alle 32 uS muss der Daten-Eingang ueberprueft werden. Dazwischen ist nicht viel zu tun, das bedeutet, dass Du durch geschickte Programmierung (bspw. verschachtelter Code, siehe auch MBHP_TV) noch eine Menge andere Dinge nebenher erledigen kannst. Gruss, Thorsten.

Sorry guys, no SID for you ;-) It seems that this issue is not caused by MIOS, but by my MIDIsport 2x2, because my merger test didn't fail with other interfaces. I also noticed that the latency of MIDIsport is much higher than on the others, so a buffer overrun inside the M-Audio firmware could be the reason. See also: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=mios_toy;action=display;num=1077232194 Best Regards, Thorsten.

determine the truth about your MIDI interface: ; ; MIDI Performance Measuring Application ; ; This is some kind of benchmark which helps to evaluate the performance ; of your MIDI interface (and computer) ; ; To get the test running you have to create a MIDI feedback loop. ; ; Examples: ; Direct Feedback: CORE1 OUT -> CORE1 IN ; Merger Feedback: CORE1 OUT -> CORE2 IN -> CORE2 OUT -> CORE1 IN ; Computer Feedback: CORE1 OUT -> PC MIDI IN -> MIDI-Ox -> PC MIDI OUT -> CORE1 IN ; ; A MIDI controller event will be sent and should be received "immediately" ; is measured with timer3, prescaler 1:8 - this means, that the counter ; result has to be multiplied by 8 and 100 nS (@40 MHz) to get the ; absolute delay ; ; Note that the delay is always greater than 960 uS, since this is the ; initial transfer time of a controller event ; ; The current, minimal and maximum result will be print on LCD ; To determine the jitter, calculate: (max-min) / 2 ; ; IMPORTANT: remove the feedback loop before uploading a new application, ; otherwise MIOS will wait endless before rebooting the core!!! ; ; And here the results: ; ; o direct feedback: ; Min: 1218, Max: 1262 -> 0.97 mS / 1.01 mS -> +/- 0.02 mS Jitter ; ; o merger feedback (2 cores): ; Min: 1664, Max: 1735 -> 1.33 mS / 1.38 mS -> +/- 0.03 mS Jitter ; ; o RME Hammerfall DSP/Multiface, WinXP, Feedback via MIDI-Ox ; Min: 2497, Max: 2599 -> 2.00 mS / 2.07 mS -> +/- 0.04 mS Jitter ; ; o RME Hammerfall DSP/Multiface, WinXP, Feedback via Logic Audio ; Min: 2565, Max: 3820 -> 2.05 mS / 3.05 mS -> +/- 0.50 mS Jitter ; ; o MBHP_USB (WinXP Legacy Driver), Feedback via MIDI-Ox ; Min: 3320, Max: 4555 -> 2.66 mS / 3.64 mS -> +/- 0.50 mS Jitter ; ; o MBHP_USB (WinXP Legacy Driver), Feedback via Logic Audio ; Min: 3510, Max: 6291 -> 2.81 mS / 5.03 mS -> +/- 1.11 mS Jitter ; ; o MIDIsport 2x2, WinXP, Feedback via MIDI-Ox ; Min: 6219, Max: 9960 -> 4.98 mS / 7.97 mS -> +/- 1.5 mS Jitter ; ; o MIDIsport 2x2, WinXP, Feedback via Logic Audio ; Min: 7608, Max: 13446 -> 6.08 mS / 10.76 mS -> +/- 2.3 mS Jitter Add your results here! :) Best Regards, Thorsten.

The soldering took 1 hour, the programming 1 hour, and the documentation a whole evening. So I hope that I don't have to spent even more time to answer your questions (please help each other...) The driver can be found under MIOS->Download The wiring diagrams under MBHP->MBHP_LCD I've tested the single LCD with MIDIbox LC, runs fine! With 3 LCDs you've a nice replacement for the KS0107/0108 solution. Note that the graphical layout of MBLC has been designed for 240x64, but with 3 PCD5844 you've 252x48. Therefore the layout has to be adapted (-> lc_glcd.inc) Also the layouts of other applications won't match, since only 14x6 characters are displayed on each LCD --- here you also need to adapt the applications. Have fun! Best Regards, Thorsten.

Did you take into account, that the customized app_lcd.inc driver has to be built into the application? (Just copy the app_lcd.inc into the same directory like the application and add the MIOS_LCD_TypeSet call to USER_Init like described in app_init.inc of the driver package) However, some characters are missing - this means that there is either a problem with the enable line, or that your display is too slow - even slower than the slowest display I ever have tested (a 2x40 HD44780A00) --- normaly, from my experience, every HD44780 compatible controller - especially KS* - is much faster. If you think that the wire to the enable line is ok, then you could add some additional NOPs to USER_LCD_Strobe_Set and USER_LCD_Strobe_Clr (-> app_lcd.inc). If it works thereafter, then you could do the same in the MIOS source code (mios_clcd.inc), recompile it and use it instead of the official version. This saves you from adding app_lcd.inc to every application. Best Regards, Thorsten.

You didn't wrote which application you've used to test the DINs. If you are using the MIDIbox64 application, then: of course, they are assigned to the menu functions. You can disable the menu buttons in main.asm by changing the pin numbers (DEFAULT_DIN_MENU_*) to >= 64 Best Regards, Thorsten.

See mb64e_sysex.inc how MIDI remote works Just assign the SysEx string to a Meta button... Best Regards, Thorsten.

; o PCD5844 in vertical mode: 5543 * 8 * 100 nS = 4.43 mS see also http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1076409658

Hey PayC, here is your LCD in action: options: up to 8 GLCDs w/o additional hardware (more GLCDs would be possible by adding a multiplexer for the chip select lines, but who really wants to kill that much Nokia phones? ;-)) the number of connected GLCD doesn't affect the performance (LCD benchmark result: 5543, thats faster then a KS0107/KS0108 based display) Best Regards, Thorsten.

encoder 1 selects the group encoder 2 selects the bank encoder 3 selects the group encoder 4 selects the bank encoder 5 selects the group encoder 6 selects the bank encoder 7 selects the group encoder 8 selects the bank ... now clear? ;-) Just try it out once your MB64E is ready!!! Best Regards, Thorsten.

Hi, from my point of view the results are perfect, because they demonstrate that Cubase doesn't send the metering data in the same format like documented in the Logic Control manual. The manual can be found somewhere at the Emagic page. But since Cubase uses another format, this won't really help you. So, I could possibly tell you which function has to be changed exatly if I would know how the format used by Cubase. Are you able to log the MIDI messages sent to your MBLC w/ MIDI-Ox? Best Regards, Thorsten.

Maybe MIOS or the application hasn't been uploaded correctly? If you've received an error message during the transfer - maybe not. In this case (or if you are not sure anymore), try to upload the application again. If it still doesn't work, upload MIOS with the first level bootstrap loader again, thereafter the application... If this doesn't help, you are sure that it wasn't an upload error,. Best Regards, Thorsten.

Hi Ryan, fine that it works now! (in principle) This shows how important it is to follow really every step of the MIDI Troubleshooting Guide You wrote: > so i tried to upload mios v2.2 onto the core But maybe you mean that you've tried to upload the MIDIbox64 V2.2 application into the core. And this won't work so long as MIOS (V1.5b) has not been uploaded. So, now it's time to read the Bootstrap Loader page, especially the topic "The whole upload procedure". Once you've uploaded MIOS, you will be able to upload the application. Best Regards, Thorsten.

MIOS can everything what you want, but there most also be somebody who programs it on the way you want... ;-) It's not possible to handle more than 128 DINs, but on the other hand it would be possible to implement a button matrix scan algorithm in order to save some digital inputs (so that they are free for the encoders). Example: for 64 buttons you could also use 8 digital output pins and 8 digital input pins, combined to a button matrix. Only problem: something like this has to be programmed into the application. And it's currently not provided by MB64E - so if somebody feels motivated for doing this, I can give you some more implementation hints Of course, it would also be possible to control another core from the MB64E application, you can switch banks of another MIOS based MB64/MB64E/MBMF with the MIDI remote feature. You could also control the bank switch inputs of the MIDIbox Plus from another core - in fact you can really do what you want, but don't expect that I will do everything for you ;-) So my suggestion: if you don't want to program it by yourself, ask other people who are planning on exactly the same hardware for help. Best Regards, Thorsten. FAQMARKER

Hi, just swap two of the 74HC165 to test if one of them has a defect. Best Regards, Thorsten.

Whats the result of the Rx/Tx loopback test? http://www.ucapps.de/howtodebug/mbhp_core_extract_io_loopback.gif Best Regards, Thorsten.

This week the Cubase specific controller from Cyril: And a MIDIbox SID from the grandmaster of MIDIboxes - D2k:

This is a locked thread which will be enhanced from time to time. Always follow the MIDI troubleshooting guide first before asking for help. Link: http://www.ucapps.de/howto_debug_midi.html MIOS code upload: http://www.ucapps.de/mios_bootstrap.html Upload of configuration data for MIDIbox64, MIDIbox64E, MIDIbox MF, MIDIO128: http://www.ucapps.de/howto_tools_syxloader_18f.html Other known issues: for MIOS projects please use the PIC18F versions of vmidibox and sysexbox, the upload format is not the same like for the old PIC16F projects Device IDs: the MIOS device ID and the application specific device ID doesn't have the same function. The MIOS device ID is used to address MIOS specific SysEx commands for code up/download and debugging to the core. This ID can only be changed in the ID header of the PIC (see the bootstrap loader page) or with the change_id program (see MIOS Download section). The application specific ID can - if available - mostly be changed in the main.asm header, with special SysEx commands or within a menu provided by the application itself (e.g. MIDIbox64/64E/MF: SysEx Menu, MIDIbox SID: CFG->Dev) no response from core, no data sent to core: is your MIDI interface multiclient capable? If not, close all MIDI application, open only MIDI-Ox or Serge's SysEx Loader for uploading code/data

Of course, as I wrote: all analog inputs. But you could also reduce the number of pots in main.asm of the MIDIbox64 application - this will save you from soldering. One 1 button: check the serial connections. Check also the PCBs for short circuits Did you make the PCBs by yourself? Best Regards, Thorsten.

Do you really mean MD64 or maybe MB64? Then midibox_v2_2 could be interesting for you... :) Best Regards, Thorsten.

Hi Meeshka, I wrote a perl script which sends the code (it's within the MIOS package), but it will also work with the upcoming MIOS studio - a Java based tool written by Wilba. This tool also comes with a MIDI monitor :) Best Regards, Thorsten.