TK.

I also see that your synth chip has potential, and from my side it would be relatively easy to add support for additional sound registers. So, the infrastructure is already there. CS line: I think that an alternative addressing mode could help, so that only one CS line is required. The advantage of two CS lines (the addressing scheme I'm using) is, that I can write to a certain SID seperately, but also access two SIDs the same time. This speeds up register transfers and ensures synchronous configuration (important for stereo sounds, especially when the TEST flag is toggled to reset the oscillators) For the case that it is impossible to provide two CS lines from your side: would it be possible to provide two additional address lines, which allow following access modes: [tt] A6 A5 0 0 SID left channel 1 0 SID left channel 0 1 SID right channel 1 1 SID both channels [/tt] (basically this is propably already the same addressing you are using, only difference is, that by setting A6 together with A5, a register access will be forwarded to both SIDs) Or alternatively: do you think, that a different way to write into emulated SID registers could improve the overall performance? E.g., how about SPI, I think that AVR provides such an interface? By using SPI, the 74HC595 shift registers wouldn't be required anymore at the MIDIbox side, and the MBSID firmware could transfer register values directly to your synth chip Best Regards, Thorsten.

There are new docs and demo samples: Hardware Options http://www.ucapps.de/midibox_sid_manual_hw.html Frontpanel http://www.ucapps.de/midibox_sid_manual_fp.html V1->V2 Upgrade Guide http://www.ucapps.de/midibox_sid_manual_up.html Known Issues and Troubleshooting http://www.ucapps.de/midibox_sid_manual_ki.html Best Regards, Thorsten.

Euphoricgrey - for the case you are still reading the forum: analog inputs are now handled like knobs, which means, a joystick can control 2 * 4 sound parameters of the selected SID(s), and it can be used within the modulation matrix as modulation source. Analog input handling is flexible as never before - so, this hardware option is a good decition for MBSID V2 :) Best Regards, Thorsten.

S&H is especially useful with analog signal sources, so I finally implemented a dedicated AIN handler for MBSID V2, which is officially supported from my side. In addition some other improvements (as usual)... From the ChangeLog of beta4: o an incoming patch or bank change request doesn't update the the patch anymore if it was already selected before. This is to avoid "glitches" when a sequencer sends a program change shortly before a note is played. o the "Knobs" are sending CC values now when the CC function is activated (press SHIFT + Page Up/CC Button to toggle this mode) Other parameters are still not sending CCs over MIDI, as NRPNs are not implemented yet (low priority) The CC numbers are 1 for Knob #1 (Modulation wheel), and 16/17/18/19 for Knob #2-#5 (GP values) In addition, Knob #P sends Pitchwheel Events in CC mode o support for analog inputs (J5:A0..A4) This feature has to be enabled in the setup_*.asm file by setting DEFAULT_J5_FUNCTION to 1 Conversion results of the analog inputs are directly passed to the knob handler. This generic approach has the advantage, that it is possible to control 5*2 parameters within a specified Min/Max range, and that in addition the analog values are available as modulation source within the modulation matrix (K#1..K#5) The feature behaves differently on master and slaves: Master: analog inputs are forwarded to the selected SIDs - use this option as replacement for rotary encoders, or for adding analog control elements like pots/faders/joysticks to your CS Slave: analog inputs are only handled internally - use this option for modulation with analog signal generators [/code] Best Regards, Thorsten.

Ja, richtig - LCD und Button Handling passen auch nur zu den von mir verwendeten Routings. Alternative Routings muessen hart in die Applikation einprogrammiert werden, und erfordern auch eine Ueberarbeitung des User Interfaces. Gruss, Thorsten.

Hallo, Du hast Glueck, dieses Routing entspricht der Default-Einstellung. Alle Daten, die in den MIDI In von IIC0..3 reingehen, werden am MIDI Out des Core Moduls ausgegeben. Alle Daten, die in den MIDI In vom Core Modul reingehen, werden zum MIDI Out von IIC0..3 ausgegeben. Im Grunde ist also der MIDI In/Out des Core Moduls an meinem PC angeschlossen, und die restlichen MIDI In/Out Ports mit MIDIbox SID, MIDIbox FM, MIDIbox SEQ und einem Keyboard. Alle Geraete koennen bidirektional mit dem PC kommunizieren (und optional - aber diese Switches benoetigst Du ja nicht - auch untereinander) Gruss, Thorsten.

LED Rings are not supported, and it is impossible to add this to the firmware due to conceptional reasons Best Regards, Thorsten.

1) won't be provided from my side, I will only make proposals I'm happy with my frontpanel as it is, but of course, there is always room for improvements 2) don't know, depends on the community Maybe you should just continue reading here? http://www.midibox.org/forum/index.php?topic=9238.0 (please read the whole thread, not only the first posting) Best Regards, Thorsten.

As mentioned in other threads (today two times, this is the third time): a hardware discussion page will be available this weekend. The more often people are asking for details, the higher the delay... ;-) To give you a quick answer: it will even work with the never released mbhp_core_v1 and mbhp_sid_v1 boards - in MBHP hardware compatibility is a high priority criteria. Of course, you might have to add one or two pull up resistors at the right places, but I think this is not really a killer for the old boards? Best Regards, Thorsten.

beta3 is now available for download. Beside of obligatory minor bugfixes and improvements (e.g. portamento disabled on initial note, bugfix in CS handler, MOD->LFO Depth modulation now even working when static LFO depth of target is 0), I added a new feature for the Modulation Matrix. There is now a "S&H" (Sample & Hold) operator, which samples the value of SRC1 whenever SRC2 changes from a negative to a positive value. The direct integration into the MOD matrix is an unusual, but very powerful solution, as in difference to common synths it not only allows you to capture values periodically (e.g. by using a LFO), but with any pattern. E.g., you could trigger the capturing from the wavetable sequencer, or with a certain modwheel or velocity level (requires a second MOD path which is doing a comparison 1>2) Have fun! :) Best Regards, Thorsten.

It's a more generic solution. The usage of J5 was a workaround for the MAX525 based module, which only provides two gates. And there is another reason: J5 are allocated by MBSID V2 for analog inputs Best Regards, Thorsten.

The SHIFT button is still important, because it's the only way to switch the main encoder to FAST mode (to speed up parameter changes), to change the engine, to init a patch and to send a SysEx dump. I know, there could be an alternative solution, e.g. a well hidden menu page, or a special key combination, just to save this additional button. Just today I spent again thoughts for a way to replace the SHIFT button, but without a conclusion which fits all needs. I'm really sorry for that, but so long I don't see a clear way which is future proven (e.g. the button could get some additional functions in bassline and drum mode), I can only repeat what I'm writing since weeks: please add this button! Best Regards, Thorsten.

You are not the only one who dreams about such a feature, it's on my personal wishlist since years, but it depends on the manufacturers of sequencing software to provide a suitable application interface. Last time we discussed about potential possibilities in this thread: http://www.midibox.org/forum/index.php?topic=9376.msg67062#msg67062 But as you will see: it won't be a trivial task, and it won't work without the support of the music industry (maybe only exception: you are working under Linux and have access to the source code of the host software) Best Regards, Thorsten.

What a beauty! :) What happened with the green power-on LED? Best Regards, Thorsten.

Great! :) Yes, of course, this input will go into the hardware discussion page that I'm planning to write this weekend. I wasn't aware that ECAN behaves so sensible to an unconnected receive input. However, thats the purpose of the beta test - to find out and document all possible issues. Best Regards, Thorsten.

Are you sure, that this isn't a general problem with your core module? A bad connection, or a short somewhere? Do you still see the upload request? Are you still able to download another application? Best Regards, Thorsten.

Hallo Christian, ja, der Quellcode muss nicht geaendert werden, wenn bestimmte IN/OUT Ports nicht verfuegbar sind. Wenn es sich um einfache Anpassungen handelt, kann ich Dir sicherlich schnell die entspr. C Funktion posten. Bei komplizierteren Aenderungen vielleicht nur ein kleines Programmierbeispiel, dass Du dann jedoch weiter ausbauen muesstest, bis es komplett funktioniert Gruss, Thorsten.

me too - but hasn't this mentioned often enough in this forum section? Best Regards, Thorsten.

The message "this error is expected, please ignore" should appear whenever you are trying to upload MIOS. It's a failsave mechanism. Just ignore it (as it says) Don't know why a MIOS update should be required. With "in the past" - do you mean in the last days with the new PICs, or weeks ago? So long there isn't an error message, the code upload should be fine. datapins: I mean the data pins of the LCD which are currently clamped to ground (or vss, or Vs, or 0V - it's all the same). It would be interesting for me, what happens, if the unusued LCD data pins are open instead - this is just a test which is important to gain experiences with different LCDs D0-D3 of the core are not connected. Later you will use D2 and D3 of the core for the CAN Rx/Tx lines, but I guess you've already connected at least the 1k Pull-Up resistor between D3 and Vdd like shown in http://www.ucapps.de/midibox_sid/mbsid_v2_communication.pdf ? If not I cannot guarantee for anything - don't know how ECAN behaves if it receives random data values. I'm also not sure what happens when no control surface is connected. It's unfortunately impossible for me to test this, as I'm using Wilba's PCB. An unconnected DIN shouldn't be a problem, as nobody has reported an issue in the past. It is important of course, that the 10k pull-up (R9) at J9:SI of the core module is connected, but I guess your core module is (hopefully) completely stuffed? I mean: even the two pull-up resistors for the IIC bus? (I just mention this, as somebody else forgot this and missed to mention this detail...) Best Regards, Thorsten.

Beta2 is now available for download (see first posting of this thread). Please don't report errors of older versions - they could be obsolete. Please always include the version number in your posting for easier tracking. Beside of the new .hex files, beta2 contains 128 "vintage patches" which have been converted from the v1 preset library. I've improved most of the sounds by adding stereo effects. A small number of patches does not work properly due to compatibility reasons - they will be replaced by new patches in future. For those who haven't noticed it yet: MIDIbox SID V2 provides a cloning mechanism, which allows an firmware update via MBNet. Once you've uploaded a new version to the master core, press the MENU button during boot until the "Cloning Slaves" message appears on the LCD. I hope that this special button function is working with your CS, as I've only tested it with my button matrix based hardware. To all beta testers: please let me know if cloning was working successfully. My hope is, that the usage is easier than an update via MIDI. Best Regards, Thorsten.

Fein! :) Werde auch nachher mal einen kleinen Update + Vintage Soundbank releasen. Ich habe die alten Presets mal auf Stereo getrimmt, klingt ziemlich genial :) Gruss, Thorsten.

I would need some more background informations. For example: do you know, why the testtone application was not working yesterday? How do you upload the application? With the latest MIOS Studio release v7.5? Are there any error messages during the upload? And an additional test could be interesting: how does the application behave, when the unused data pins D0-D3 are not connected to ground, but left open? Best Regards, Thorsten.

MBLink connection has to be changed as described in this schematic http://www.ucapps.de/midibox_sid/mbsid_v2_communication.pdf Best Regards, Thorsten.

Great! :) The testtone application should work w/o compatibility problems. The second MBHP_SID module is not serviced of course, but I just changed this in the new version: http://www.ucapps.de/mios/sid_testtone_v2.zip Best Regards, Thorsten.

Look ok - only one comment: unused digital inputs should not be connected to ground (in distance to analog inputs). The pull-ups on the DIN module will pull the "idle" level to 5V, and this is the level required to notify the firmware that the button is not pressed Best Regards, Thorsten.