TK.

A bugfix for this issue is now available in beta14 -> http://www.midibox.org/forum/index.php?topic=6098.0 Best Regards, Thorsten.

A bugfix for the filter mode button is now available in beta14 -> http://www.midibox.org/forum/index.php?topic=6098.0 Best Regards, Thorsten.

The bugfix for the velocity issue is now available in beta14 -> http://www.midibox.org/forum/index.php?topic=6098.0 Best Regards, Thorsten.

+/-15V sind in Ordnung Gruss, Thorsten.

Is there any message during the upload of MIOS which informs you about a checksum error? How many messages do you see? (maybe just copy&paste the whole log here) Best Regards, Thorsten.

Sasa, I must say that it's really difficult to help you, because you are mixing many things, and you are ignoring important tips which doesn't make it easier. So, you want to have some step by step instructions, lets work it out: 1) Have you already installed MIOS Studio? Are you able to work with it, or do you need to know more details about the usage? Best Regards, Thorsten.

Maybe the output impedance of the sensor is too high? Do you know the value (it should be listet in the datasheet) Best Regards, Thorsten.

Hi Stef, it seems that you are mixing something - MIDIbox FM is a MIOS based application which gets use of the hardware YMF262. The PIC18F452 is not qualified for emulating a YMF262. You cannot run programs which are written for PCs or microcontrollers with "more horsepower", but less realtime capabilities. I think that you are in the wrong forum... ;-) Best Regards, Thorsten.

Just found out that Sasa's MIDI environment is a special case ;-) Sasa: could it be that you've changed the ID header of your PIC - when I read your old postings, this isn't so unlikely that you forgot to mention such important details: http://www.midibox.org/forum/index.php?topic=4190.msg27239#msg27239 Assumed, that you made some experiments with the change_id application, it could be, that you've changed the LCD type, so that the wrong driver is selected. The ID must be completely 0 for your MIDIbox So, my proposals: - use MIOS studio, don't use any other tool. - please read http://www.ucapps.de/mios_bootstrap_newbiews.html - upload the official release of the change_id application to change back the ID to 0 - if you are still using an older MIOS version: upload MIOS V1.8 - thereafter upload the MIDIbox application Best Regards, Thorsten.

Unrelated to your experiences, a change of MIOS is in my working queue, where I want to put the bootloader to 0x0000-0x03ff. This has some advantages (e.g. better PIC18F4620 compatibility, more space for MIOS apps) - one side effect will be, that this region can be hardware write protected. Unfortunately only on the PIC18F452... for PIC18F4620 it would be 0x0000-0x07ff, which is too much. However, I'm still very sure that messing up the bootloader is very unlikely, which means: not impossible, but not a normal case. Especially in Sasa's case, we know that he can upload code, therefore I still think, that recommenting to build a PIC burner won't help him - I just want to prevent that people think, that a non-working bootloader seems to be a usual case if something doesn't work, because it definitely isn't! And analysing the problems with the current flow - check if something can be downloaded, if not, work through the MIDI troubleshooting guide. Check CRC of MIOS, check to upload another application - will help to solve nearly 100% of all problems Best Regards, Thorsten.

Die Entscheidung ist mir damals auch nicht einfach gefallen, letztendlich habe ich mich an die Empfehlung von verschiedenen Leuten hier im Forum gehalten. Grundsaetzliche Vorteile das MAX525: gute Linearitaet (das ist bei einem MIDI CV wesentlich wichtiger als die Aufloesung!), 4 Kanaele on Chip (spart im Endeffekt Kosten wenn mehrere Kanaele benoetigt werden), serielles, kaskadierbares Interface (davon gibt es nicht so viele) Na klar, es gibt tausende verschiedene DACs von vielen Firmen, und wer sich mit Hardware auskennt, sollte kein Problem damit haben, den Treiber an einen alternativen DAC anzupassen, hierfuer muessen nur wenige Zeilen im Code geaendert werden. Doch leider kommt es nur extrem selten vor, dass jemand dem MIDIbox Projekt auch mal etwas zurueck gibt, in dem er bspw. solch eine Schaltung entwickeln, dokumentieren und vor allem supporten wuerde... Ich hoffe, es ist verstaendlich, dass fuer mich selbst kein Interesse besteht, nun noch ein drittes AOUT Board anzubieten (mein persoenlicher Bedarf ist ja schon laengst gedeckt...) Gruss, Thorsten.

Das ist wirklich ein erstaunlich guter Support von Maxim! Code Aenderung: folgendes gehoert in das main.asm (nach dem USER_MPROC_NotifyReceivedEvent Label suchen...): USER_MPROC_NotifyReceivedEvent ;; BEGIN --- control DOUT pins via Note events at channel #1 movf MIOS_PARAMETER1, W ; Note Off -> Note On with velocity 0 andlw 0xf0 xorlw 0x80 bnz USER_MPROC_NRE_NoNoteOff USER_MPROC_NRE_NoteOff bsf MIOS_PARAMETER1, 4 clrf MIOS_PARAMETER3 USER_MPROC_NRE_NoNoteOff movlw 0x90 ; check for Note On at channel #1 IFNEQ MIOS_PARAMETER1, ACCESS, rgoto USER_MPROC_NRE_NoNoteChn1 USER_MPROC_NRE_NoteChn1 ;; MIOS_DOUT_PinSet expects pin number in WREG, value in MIOS_PARAMETER1 movf MIOS_PARAMETER3, W ; velocity == 0: off, velocity != 0: on skpz movlw 0x01 movwf MIOS_PARAMETER1 movf MIOS_PARAMETER2, W ; pin number: note number - 0x24, we start with C-2 addlw -0x24 andlw 0x7f call MIOS_DOUT_PinSet USER_MPROC_NRE_NoNoteChn1 ;; END --- control DOUT pins via Note events at channel #1 [/code] Es sind uebrigens nur deshalb mehr wie 10 Zeilen, weil ich noch eine automatische Note Off->Note On Konvertierung eingebaut habe. Die wesentlich besser dokumentierte C version befindet sich uebrigens hier: http://www.ucapps.de/mios_c_set_dout.html Doch MBCV vertraegt sich nicht mit C... Gruss, Thorsten.

Yes, it makes sense, and I definitely want to see an example application made by users (and not by myself this time ;-)) The MIDIBox MM application demonstrates, how to parse SysEx for strings. Search for MM_SYSEX_Cmd_WriteLCD() If one of the previous MIDI devices within the chain sends F0 00 01 0F 00 11 00 10 <pos> <...characters...> F7, the appr. text will be displayed on a LCD. For your own application it might be better to use another SysEx header Best Regards, Thorsten.

The output of the CRC application would be more interesting, a description what this application is doing can (always) be found in the main.asm file, but also at the right column of the MIOS download page: Which just means: compare the output with the CRC of the current MIOS release (it's BB15) it seems that your monitor outputs the data in decimal format. It's better to switch to hex mode, the output should be: F0 0B 0B 01 05 F7 (or in decimal: 240 11 11 01 05 247) Best Regards, Thorsten.

Btw.: you can ensure that MIOS is still complete by uploading the CRC application. It will print out a checksum at the LCD (ok, this doesn't help here), but it will also send the checksum via MIDI Best Regards, Thorsten.

Why should there especially in your case a problem with the bootloader if the LCD doesn't work anymore, there is no relation... in general - and I must highlight this - it is very very unlikely that the bootstrap loader gets messed up! There are some protection mechanisms within MIOS and the bootstrap loader itself to prevent this. Therefore I think that this was a hint into the wrong direction - better to check the hardware connections carefully (and the jumpers at J3), because such errors are the common case (when you read this forum section), and therefore it cannot be suggested often enough. Best Regards, Thorsten.

Here a list of errata/imperfections which have been reported, and which will be fixed in the next release: Velocity Assignment Bug: SID crashes if certain CCs are assigned to velocity (and propably also Aftertouch and Modulation Wheel) - http://www.midibox.org/forum/index.php?topic=6101.0 Filter Mode Button Bug: Filter Mode button not working anymore - http://www.midibox.org/forum/index.php?topic=6252.0 BankStick formatting imperfection: MIDI channel 16, Patch 127, Bank H selected on all SIDs after formatting a "virgin" EEPROM: http://www.midibox.org/forum/index.php?topic=6265.0 Slave Split Note Assignment Bug. Text in german - short translation: if split settings of a SID slave should be saved, MBSID takes the settings of the master instead Best Regards, Thorsten.

Das liegt am Envelope Bug, naehere Infos und moegliche Workarounds gibt es hier: http://www.ucapps.de/howto_sid_wavetables_1.html Wenn Du einfach nur ein fertig gebastelte Drum monoton abspulen moechtest, wuerde ich empfehlen, die beste Aufnahme herauszusuchen und mit einem Sampler abzuspielen. Gruss, Thorsten.

Hallo Chris, Jeder CV Kanal bietet unter anderem einen eigenen MIDI Kanal, einen Event Typ, und eine Split Zone. Du muesstest also lediglich alle CVs auf den gleichen MIDI Kanal legen, den Event Typ Velocity anwaehlen, und die Split Zones auf eine oder mehrere Noten setzen. Die Gates des entspr. CV Kanals koenntest Du somit ebenfalls verwenden. Und die restlichen Gates liefert dann die 10-Zeilen-Erweiterung ueber das/die DOUT register Gruss, Thorsten.

Yes, this setup is possible Best Regards, Thorsten.

No problem, just duplicate the EEPROM content in RAM, and load it into memory while the sequence is played (with each step just the new data). And load it immediately from EEPROM if a step is modified while it hasn't been preloaded yet. The same "step-by-step" method can be used for EEPROM writes. Best Regards, Thorsten.

In the meantime very cheap USB MIDI interfaces are available, like this one for 20 EUR (!): http://www.thomann.de/de/swissonic_midi_usb_1x1.htm Best Regards, Thorsten.

Synchronized pattern switching is implemented in the meantime :) -> see http://www.ucapps.de/midibox_seq_changelog.html Best Regards, Thorsten.

Such small differences don't really matter. Ok, 28.2240 does matter (cannot be used...) But you need an integrated oscillator (4 pin devices). A crystal with 2 legs definitely won't work stand-alone, and building an own oscillator is too error prone Best Regards, Thorsten.

Hi Robin, A reset message could be triggered counter driven from the Tick() task. Just declare a global variable "unsigned int delayed_reset", set it to 0xffff within Init() (this function is only called once after a core reset) Within Tick() decrement the variable until it reaches 0, then send the SysEx message: if( delayed_reset && !--delayed_reset ) { // send SysEx message } [/code] (once the variabled reached zero, it won't be decremented anymore) The delay can be adjusted by changing the default value within Init(). The delay time is not exact, but within an known range Storing patterns: just use the internal EEPROM to store/restore patterns. The EEPROM can be accessed with the MIOS_EEPROM_* functions, it provides 256 bytes You need to store the variables which hold the "stop" configuration, and once they have been restored, you need to call the functions which send the SysEx dumps depending on the stop states Best Regards, Thorsten.