TK.

Symptomatic for the chaotic sorting of website/wiki/forum is, that we already have a wiki page which lists forum highlights, it only needs to be maintained :) Whenever you find an useful/interesting article, just add it here: http://www.midibox.org/dokuwiki/doku.php?id=forum_highlights And there is a special search marker, which helps to find questions&answers, which are not documented anywhere else: FAQMARKER Best Regards, Thorsten.

A programmed PIC shows bars ca. 2 second after power-on (while the bootloader is running), so long MIOS hasn't been programmed, or if the LCD is not completely (or wrongly) connected. You can ensure that the bootloader has been programmed properly by using the verify function of the programmer software. Once you did this, please go through the troubleshooting guide (http://www.ucapps.de/howto_debug_midi.html) and list the results of each particular test - this could help us to analyse the problem. Best Regards, Thorsten.

Maybe issue [2]? http://www.ucapps.de/midibox_sid_manual_ki.html Best Regards, Thorsten.

This would happen if selection input A of the multiplexer is either not connected, or if it would have a short against ground or Vss. Note that this short/open connection/bad solder junction could also be located at the core side Best Regards, Thorsten.

Here a short update: I tested SwinSID last weekend, and was a little bit surprised about the behaviour of the official release. E.g., the pseudo stereo and reverb effect is always active (which eliminates powerful pulse/saw hooks), the DCA envelope is not fully functional (e.g. missing attack phase), and filter is not supported at all. Swinkels informed me, that he is now working on an improved version. I'm curious about the results - from the planned features list it could be a very interesting alternative for the 8th SID socket of my MB-6582 base board :) Best Regards, Thorsten.

Hope that you get it solved! By swapping the J15 socket (unintentionally of course), a LCD can be fried very easily, and one possible effect are random characters. But they normaly don't look like normal characters anymore, sometimes one or two pixel lines are missing, sometimes pixels are flickering. Best Regards, Thorsten (destroyed about 4..5 LCDs in the last years)

Thank you, Dietmar! :) I've added the link to the Wiki: http://www.midibox.org/dokuwiki/doku.php?id=midibox_lc hope that all PC/MIDI issues are solved meanwhile! Best Regards, Thorsten.

Fine - this was the only logical explanation for the missing digit. Best Regards, Thorsten.

For the records: ratsnest is required whenever somebody creates a layout based on an eagle schematic. This is the case for the MBHP_BURNER_V1 layout, which has been done by Mike. As I don't use the schematic module for my own layouts (I don't like the way how the circuit is displayed, and I find it easier to place&route the parts directly), a print out will work even without this well hidden command for most MBHP modules. Thats the reason for this "inconsistency" Best Regards, Thorsten.

Are you using a PIC18F4620 or PIC18F4685? The AIN channel is wrongly selected in the appr. MIOS versions. Since nobody has noticed this before (beside of me), I think that an update is not really urgently required (there are two other changes I want to do for the upcoming MIOS version) If you are using a PIC18F452, it sounds more like a bug in your hardware? Best Regards, Thorsten.

Did you solve the issue meanwhile? If not we could arrange a chat - many things can be clarified faster when we are talking directly Best Regards, Thorsten.

Ok, I added a link to the MIDImon application to clarify the context. Best Regards, Thorsten.

My own encoders are with integrated buttons as well, I connected them all together as an alternative possibility to activate the FAST function (means: when I push the encoder, values are changed faster) Best Regards, Thorsten.

You could check the Chameleon specs - you are propably thinking about a similar device: http://www.chameleon.synth.net/english/index.shtml Best Regards, Thorsten.

Hi Tom, how do you measure the pins, with a scope, or just with a multimeter? I would propose to check the continuity when all ICs are removed from the sockets. In this case, you shouldn't measure a "short" between pin 21 and ground (measuring result: > 0 ohm or even maximum resistance) Note that there is a troubleshooting page: http://www.midibox.org/dokuwiki/doku.php?id=din_module Best Regards, Thorsten.

Theoretical you could define different preload values in SEQ_CORE_ExtClk_Set (seq_core.inc). Currently the preload values are 0, 1, 3 and 7 (2^n-1) But your idea about using a trigger output, controlled by note events from a single track, is much better. It's not only easier to handle, but it would also allow you to add a shuffle Menu button disable encoders: this is possible, yes. But note that the GP LEDs change their purpose while the menu button is pressed (they display the selected menu page). There are also function, like copy&paste, which require that you hold a GP button while moving an encoder So, if you are still in the design phase of your panel: it's strongly recommented from my side to add the GP buttons Best Regards, Thorsten.

Where did he refer to MidiMon? Best Regards, Thorsten.

Hi, MIDI In and Out port are part of the core module (see MBHP_CORE page). Once you are ready to upload the firmware, MIDI In and Out have to be connected to your computer. This is basically described at the bootloader page. Later you can connect a keyboard, a MIDI controller, a hardware sequencer, your PC (for software sequencing) etc.. to MIDI In for receiving Notes/CCs/Aftertouch/Pitchbender/SysEx. Did you ever control an external synthesizer with your MIDI gear? MIDIbox SID is just the same... :) PSU: some details can be found here: http://www.ucapps.de/midibox_sid_manual_hw.html Please note that most features explained in the manual are only supported by the new MIDIbox SID V2 firmware, which requires a PIC18F4685 Best Regards, Thorsten.

Hi Wicked One, welcome to the forum! :) A second encoder row is not supported, and from the available resources I would say it's impossible to add such a feature. But there are also good news: the DIN sync output has a seperate divider within the BPM menu page :) Best Regards, Thorsten.

Hi abcmann, cool that your MBSID is already working on your first forum post! :-) I've cancled the PIC based USB project, but if the guy writes that his firmware is working, I would propose to try it out. Since I'm using the 2x4 MIDI router, I've no personal need anymore for a USB solution (I prefer direct MIDI routing without the need for a PC in order to reduce latencies) Best Regards, Thorsten.

yes this shouldn't make a difference and is not required Best Regards, Thorsten.

So, you even don't get the MIOS boot message? Did you notice any error message during the code upload? Could you please upload the device_id_00.hex file of the change_id package? This ensures that the ID header is programmed correctly (and especially that the right LCD type is selected) Sidenote: under normal circumstances this doesn't need to be done. I only want to ensure that you are starting from a proper state. The PIC ID header is normaly programmed with the bootloader, and is never touched by any application - only exception: change_id Btw.: who did program the bootloader, and which version are you using? Best Regards, Thorsten.

Absolutely not - and I'm also sure, that you don't need to reburn the bootloader with a PIC programmer. MIOS and firmware can be easily uploaded via MIDI within a couple of seconds, thereafter your installation will be up-to-date again. :) I would recomment to install the latest MIOS version (MIOS V1.9e), and to try MIDIbox SID V1.7303 and MIDIbox SID V2.0beta4 (note: beta4 will be the last one which runs on a PIC18F4620 - with beta5 the 64k border has been reached) I propose this, as I cannot guarantee, that any application version will work with any MIOS version. I can only recomment: whenever you notice a strange behaviour, please always make sure that you are using the latest releases. Please let me know if you still notice random characters after the update Best Regards, Thorsten.

Thats strange, your buttons are looking similar to my own (DT6 from reichelt), and I never noticed such problems. I don't think that a debouncing function would help here. Debouncing is used to filter transients after an event has been sampled, but the initial event will always be forwarded to the application. Let us know how the other buttons are working Best Regards, Thorsten.

LEDs are driven time multiplexed, in addition the weak 74HC595 output drivers limit the current, therefore your calculation is wrong. I just did some measurements. When all steps are activated (all green LEDs on), and the sequencer is running (vertical line of red leds), the current is about 110 mA Best Regards, Thorsten.