TK.

Hi Matrigs, unfortunately there is no straightforward solution to change the purpose of the encoders. It's not only the cs_menu_enc.inc file which needs to be changed, multiple files are affected, and some additional code needs to be implemented to get a special encoder behaviour exactly like you want. If you could give me the encoder functions you are planning to control, I could do the changes for you... (sidenote: the new code wouldn't be compatible with MBSID V2, as the encoder implementation has been changed) Sidenote: you should consider the use of a PIC18F4685, so that MBSID V2 can run. In MBSID V1 the 303 extension was only an add-on which hasn't been considered from the beginning, and therefore is a little bit complicated to use. In MBSID V2 the overall concept has been prepared for such special "engines". For example, in difference to MBSID V1 bassline sequences can be edited on a more comfortable way, and multiple sequences can be embedded within a single patch, so that you can easily switch between them. There will be additional sound parameters especially for those funky C64 like bassline sequences. Also the encoder functions will be changed automatically when the bassline engine is selected, so that the MBSID V2 CS will propably already provide the look&feel for which you are asking. Only problem is, that these are only ideas, and I cannot give you more details before I've implemented the bassline engine (propably it will be much more powerful than I can imagine for now ;) --- see the progress of the Lead engine! :)) You propably need to wait one or two months before the engine is ready for use. Best Regards, Thorsten.

The MIDImerger project uses a software implemented UART which requires so much CPU time, that nothing else can run in parallel. So, it is not possible to use the same approach for any MIOS application - it just needs a second core which scans the second MIDI In. A MBHP_IIC_MIDI extension would require some changes in the MB64 firmware. So, in theory this would be possible, but there is no ready made solution available yet Best Regards, Thorsten.

What happens when all ICs are removed, and pin 27 of the SID socket is connected to ground? Best Regards, Thorsten.

Ueber die RI->SI Verbindung erfaehrt die Firmware, ob ueber den MIDI Input etwas empfangen wurde. In diesem Fall geht das Signal solange auf 0V, bis sich der Master die Daten abholt. Ansonsten steht es auf 5V Das koenntest Du mal ueberpruefen: trenne die RI# Verbindung zum Core (so dass sich die Firmware keine Daten abholt). Nach dem Einschalten sollte RI# auf 5V stehen. Schliesse (erst dann!) ein Keyboard an und spiele eine Note. RI# sollte auf 0V gehen. Schliesse RI# an den Core, das Signal sollte wieder auf 5V gehen Gruss, Thorsten.

Thank you! :) So, you don't need any additional components, right? Just Pin 1 via 220 Ohm resistor the digital output of the 74HC595, Pin 2 to ground, and pin 6/4 to the keyboard. What happens with pin 5? Best Regards, Thorsten.

Hm, then I don't have any ideal for the reason... ICProg has a readout function, right? What has been written between 0x400 and 0x5ff? Best Regards, Thorsten.

Yes, the required adaption of the resistor value is strange. My assumption is, that the MIDI output of the keyboard somehow doesn't comply with the MIDI spec (5mA current loop), so that depending on which kind of optocouplers (or circuitry around the optocoupler) is used, the MIDI signal can be received properly or not. I would start with some current/voltage level measurements, but without a scope this is too difficult... however, as you found a solution, it's fine :) Best Regards, Thorsten.

Sounds more like a problem with the YAC512, since the YMF sends the DAC signal. First I would start to doublecheck the schematic vs. new layout, and the new layout against the old layout, just to ensure that this is no general problem with the interconnections. Check especially that the ICs are stuffed the right way (not mirrored), as this confuses most people Best Regards, Thorsten.

Once the MIOS screen pops up, the application starts to access the SID via the 74HC595 shift registers. If you would connect an amp to one of the 74HC595 pins, I'm sure that you would hear such digital noise. Are you sure, that there isn't a "hidden" connection between the 74HC595 and the transistor amp stage (compare with http://www.ucapps.de/mbhp/mbhp_sid_v3.pdf Schematic) Best Regards, Thorsten.

Hi Andrea, is this a switch which provides a common pin, which can be select between 6 terminals? Then you could connect it the same way like shown in this schematic: The resistors are connected between the terminals, and the common pin is connected to the analog input. Best Regards, Thorsten.

Hi Enrico, I don't see a risk here --- but which master keyboard are you using? It could be interesting to know for the case that somebody owns the same Best Regards, Thorsten.

Hallo Lars, hast Du den Tip mit dem evtl. fehlenden 1k Pull-Up an der SC Leitung weiterverfolgt? Wenn es ohne IIC Modul funktioniert, ist die Wahrscheinlichkeit sehr hoch, dass es daran liegt. Gruss, Thorsten.

Too bad that the video stops where the bass drum begins! :-( Congratulations for the good marks! :) Best Regards, Thorsten.

Second assumption: I guess that you are not using the audio input of the SID - is it connected to ground? (this is recommented) Best Regards, Thorsten.

Yes, it should behave like a common PIC18F452 Maybe an issue with your programmer? Which one did you use? And did you perform a verify after programming the bootloader to check the flash content? Maybe the code memory protection is activated, so that flash cannot be overwritten via software? Best Regards, Thorsten.

looks fine, does it boot? Best Regards, Thorsten.

It sounds like digital noise, couldn't this be a corrupted patch? You are writing that the testtone application works well - does it mean that you don't hear such noise in background anymore? Then I would say, that it is very likeley that you missed to solder the two 1k Pull-Ups for the SC/SD line of the BankStick? Best Regards, Thorsten.

Hi, some feedback from MBSEQ V3 users about the workflow would also be interesting for me. Best Regards, Thorsten.

This is only an issue for devices which get use of the ECAN peripheral, and for MIDIboxes which are using excotic displays which don't support the 4bit mode properly (currently I'm only aware of issues with PLED (they will be discontinuied anyhow) and VFD displays, common LCDs are working ok - I tested this with all LCDs I own, and I own a lot of different types! ;-) The drawback of the 8bit mode workaround: two IO pins get lost - so this is no general solution. To avoid misunderstandings I repeat this in other words: for MBSID V2 users this issue is not the end of the world, as for the case a LCD doesn't support the 4bit mode there is a workaround. But this workaround is only sufficient for MBSID V2 - it wouldn't work with a MIDIbox which allocates all IO pins. Therefore don't be afraid, the layouts don't need to be changed. :) Best Regards, Thorsten.

Thanks! I will come back to your offer once I've collected some more experiences about this hacking stuff. I own an old Linksys router which was damaged after a thunder storm. The ethernet connection is still working, only the DSL link is affected - after this "accident" I started to think about a new purpose for the device... propably I found it ;) Best Regards, Thorsten.

Mr. Selfservice (a nice matching avatar name btw. ;-)) Could you please add a link to the overworked layout to this wiki page, so that it doesn't get lost: http://www.midibox.org/dokuwiki/doku.php?id=layout_improvements Thanks for your help! :) Best Regards, Thorsten.

Welcome to the forum! :) Would it also be possible to provide a second WR# line instead of an additional address line? This would make your chip compatible to the MBSID V2 stereo SID design (see http://www.ucapps.de/midibox_sid_manual_l.html for sound examples) Best Regards, Thorsten.

I just want to inform you, that the first beta release of MBSID V2 can be expected soon. I'm planning to work out the last details next week. Also some documentation about the multi engine and the new hardware requirements needs to be written, but thereafter a full working firmware with support for Lead and Multiengine + Ensembles should be available. (to give you are more exact date: if nothing else happens - and currently each day something unexpected can happen - maybe next friday or earlier). I'm already curious about your feedback, as this is very important in this phase were I'm going to freeze certains parts of the engine (conceptional changes will be difficult in future). There is no SysEx editor available yet, and I would prefer if somebody else could implement it. Either JSynthLib based, a dedicated java application or something else which is platform independent. So, if somebody with programming skills is searching for a challenge (the synth engine is much more complex than the one of MBSID V1), hands up! :) This means, that people who want to test the new firmware need a control surface. As mentioned in the past, a Step A surface will be sufficient, but you need at least one SHIFT (the previous LINK) button to activate special functions. This also means, that you need to add a second shift register (-> DINX2). And by doing so, you could also add the Page Up/Down (the previous CC/EDIT) button for easier selection of synth elements (e.g. OSC, LFO, ENV, WT, ...) Step B and Step C owners will be able to use the new firmware without additional modifications. Just only the PIC needs to be replaced. And if you have the choice: the stereo option (two MBHP_SID modules controlled from a single core) should be prefered, as this is one of the most important features (I don't use external Fx gear anymore since this option is implemented :)) So, for people who already have a fully stuffed MBSID V1, just leave two slaves unbusy, and connect the SID modules to the master and first slave instead - you will love the fat sound! :) All these requirements will be written down and illustrated in the manual, so please be patient and don't ask here - I will document it with the same quality as known from MBSEQ V3, I just need some more time... Best Regards, Thorsten.

Great! It could be a wireless MIDI server and a cheap embedded OSC->MIDI->OSC translator Than more I'm thinking about it, than more I find such a project attractive. Too bad that MBSID V2 will keep me busy in the next months, but this is maybe a nice toy for long winter evenings Best Regards, Thorsten.

Hi Bob, maybe these buttons are fine for you? They are available at reichelt.de (type "taster" into the search mask), and there are different colours and version available (with or without integated LED). But they are not cheap: 1.85 EUR per piece There are also these round ones which I do prefer: they are available for 0.72 EUR per piece Also conrad.de has a wide variety of buttons. Best Regards, Thorsten.