TK.

Hallo, eigentlich ist ein 2x16 Display fuer die StepC Option keine besonders gute Wahl, denn normalerweise moechte man alle 5 Parameter, die zur OSC und ENV Gruppe gehoeren gleichzeitig sehen. Hast Du bereits CS_MENU_DISPLAYED_ITEMS auf den Wert 4 eingestellt? Wenn der fuenfte Parameter dann immer noch nicht sichtbar ist, musst Du wahrscheinlich die sogenannten "Page Offsets" in cs_menu_enc_table.inc anpassen Gruss, Thorsten.

Hallo, an den Shiftregistern liegt es nicht, die capturen bereits sehr sauber, auch ein Kondensator hilft da nicht weiter - die automatische Entprellung wird mit der Funktion "MIOS_SRIO_DebounceSet" initialisiert. Am besten in USER_Init (-> sid_init.inc) einfuegen. Die MBSEQ verwendet standardmaessig den Wert 32, der sollte auch mit der MIDIbox SID funktionieren: movlw 32 call MIOS_SRIO_DebounceSet Gruss, Thorsten.

Dafuer gibt es leider kein Beispiel, und es ist auch etwas komplizierter, einen Treiber fuer mehr wie zwei Displays zu schreiben - mit einer Modifikation in irgendeiner Tabelle ist es natuerlich nicht getan, hier muesstest Du schon selbst einige Zeilen an Code schreiben. Um auf die eigentliche Frage zurueckzukommen: grundsaetzlich werden die LCDs 1:1 parallel an J15 angeschlossen, lediglich die Enable Leitung gehoert an einen Pin, der fuer nichts anderes verwendet wird. In der Software wird das Display dann mit MIOS_LCD_TypeSet selektiert (siehe Dokumentation) --- wichtig: MIOS selbst kann normalerweise nur zwei Displays ansteuern, wenn es noch mehr sein sollen, muss man temporaer mit MIOS_LCD_TypeSet auf das andere Display umschalten, den Text ausgeben und anschliessend wieder auf die urspuenglichen Displays zurueckschalten. Gruss, Thorsten.

Nee, von MIOS werden die alten Disc drives bestimmt nicht unterstuetzt. Der Aufwand waere zu gross, und die meisten drives hatten sowieso ein qualitaetsproblem, nach ein paar Jahren war meistens der Lesekopf hinueber... Gruss, Thorsten.

I also thought about such a feature, maybe in combination with the song mode - therefore I've reserved some memory to store patch informations (and maybe also static CC settings) in the dedicated "song bankstick". It has nothing to do with Meta events, since such MIDI events won't be handled by the sequencer core, but by seq_song.inc. Sorry that I cannot give you much more explicit informations, it would need much more time to describe the required changes than to program it by myself... changes have to be made at many places, not only in seq_song.inc! Best Regards, Thorsten.

Very good! :) Best Regards, Thorsten. FAQMARKER

Hi, there is a step by step troubleshooting guide available here: http://www.ucapps.de/howto_debug_midi.html Did you already check all the debugging suggestions? Best Regards, Thorsten.

I wouldn't use the IIC slave interface for a common MIOS core, since the transfers are so slow that it would stall the whole system (thats also the case if you would use the internal peripheral). MIOS wouldn't be realtime capable anymore - in timing critical applications like MBSID or MBSEQ the IIC slave couldn't be used... So, I would prefer Duggles Idea to use "Gadgets" (PIC16F cores with dedicated firmwares). Of course, you could also use a dedicated PIC18F core -- which doesn't run under MIOS, but with a special IIC slave driver system. A more performant way to connect several PIC18F cores is a parallel interface. I've implemented something like this some months ago, but it isn't finished yet - it's in experimental state, currently words can be transfered in both directions via the LCD port. I haven't found the time (and motivation) to continue with this concept yet, since there are so much other interesting things ;-) But I could send you the application if you want. Best Regards, Thorsten.

thats just a downstripped MIDIbox64. Connection diagrams and a list of modules can be found at the MBHP introduction page. But it will be difficult to display the current plug in and parameters on screen if your host software (digital performer) doesn't send the information via MIDI. Something like this is normaly only supported for Logic/Mackie Control. Does your software support this protocol? Best Regards, Thorsten.

Thanks for the great feedback! Sometimes it's really important for me to read not only about hardware/software problems, but also about things which are running fine :) Majo: don't hesitate to send me pics of your MIDIbox for the gallery. As for the PIC16F port, I guess it's impossible in the meantime since the PIC16F firmware is different at many places (the MIOS version takes advantage of the PIC18F instructions and memory model) and it already allocates the whole RAM and flash. Not at least the upload of a PIC16F firmware takes a long time (about 3 minutes) so that development doesn't make fun. So - try to find another job for those chips, how about some MIDI sensors, mergers and processors? ;-) PayC: I'm glad to hear that your issues are solved with the new MIOS version! Get well soon! :) Best Regards, Thorsten.

Hallo Marc, keine Angst, mit der Autokonfiguration ist alles noch einfacher geworden! Und viele Leute haben es auch ohne geschafft ;-) Eigentlich musst Du Dich nur an die Anleitung zu halten: http://www.ucapps.de/midibox_sid_csB.html ("Preparation of PIC18F cores") Gruss, Thorsten.

And the winner is: Artesia!

Hi, please read the "planned features" list at the MIDIbox64 V2 page: so, it will be a lot of effort to implement this feature, but I've planned to do this sooner or later. However, in general you never need to stop the sequencer, you can always change any parameter, patch or whatever during the sequencer is running... the planned change will optimize the handling... Best Regards, Thorsten.

The final V1.6 of MIDIbox SID is now available for download. It comes with some new features which didn't exist in the alpha versions: a split function which allows to assign the three SID voices to different (or overlapping) keyboard zones. By using the transpose function in addition, you are now able to play each voice individually from a single MIDI channel. This feature is also usefull to layer multiple SID sounds to different keyboard zones (requires SID slaves) the velocity/modulation/aftertouch configuration can now be found in a seperate menu (VMA), the split function can be controlled from the CFG menu an auto configuration for the SID device ID and the CS handler. The SID device ID will be derived from the MIOS device ID. The control surface will be disabled if the device ID is != 0x00 (and therefore the core acts as a slave). This simplifies the configuration of a 4 SID system several setup and .syx files for 6581/8580 with or without control surface are included in this package so that in most cases no assembler is required to configure the application IMPORTANT: from now on, the SCLK input of the SID module has to be connected to port J10:MD (PIC Pin #28/RD5) of the core module The use of MIOS V1.7 is highly recommented (especially CS users will notice advantages - brighter LEDs, brighter modulation matrix!) see also http://www.ucapps.de/mios_v1_7_hardware_mods.html I will update the JSynthLib editor for the new features next weekend. Best Regards, Thorsten.

of course ;-) this is something which can only be determined by starting with the programming. Unfortunately I won't have the time in the next weeks to program on such gimmicks. I can only say, that MIOS itself doesn't need any extensions, the application itself just has to react on "USER_AIN_NotifyChange" and it has to send MIDI messages depending on the time between two events - so if anybody feels interested, step forward! Best Regards, Thorsten.

Zum Thema "ungewolltes Knacken": ich habe mir heute nochmal den Audio Out des SIDs am Scope angesehen - sobald das Gate Bit einer einzigen Voice gesetzt wird, steigt der DC Offset um ca. 200 mV: und wenn drei Voices zum gleichen Zeitpunkt gestartet werden, wie bspw. beim "Slow Intro Sound", addieren sich die Offsets zu ca. 500 mV: In diesem Artikel steht mehr zum Thema Offset (und wie man diese Designschwaeche ausnutzen kann ;-)): http://www.kubarth.de/sid/articles/the_c64_digi.txt Zitat: Gruss, Thorsten.

Hallo, dass der falsche MIDI Kanal eingestellt ist, war mein erster Gedanke, aber dass Dir das passiert, haette ich nicht gedacht. ;-) Ungueltige MIDI Events: bei meiner MBSID sind sowohl die Core, als auch die SID Module mit 1000uF Kondensatoren bestueckt. Ich habe sie damals wegen der Groesse gewaehlt, mit 2200uF wuerde ich das C64 Gehaeuse nicht zukriegen. Vielleicht habe ich somit unbewusst das Problem vermieten, auf das Du nun gestossen bist - aber ich bin mir nicht sicher. Das Problem kannte ich bisher nur von Core Modulen, an denen keine weiteren Verbraucher angeschlossen sind. Warum es nun bei Dir auftritt, kann ich nicht sagen, und deshalb bleibt Dir nur eins: ausprobieren! Encoder fuer 3Of/Save/Name: sieht nach Aufwand aus :-/ Fuer 3Of finde ich evtl. eine Loesung, fuer die restlichen Wuensche habe ich keine Lust/Zeit Gruss, Thorsten.

The scan matrix example can now be found in the download section. Once it has been successfully tested by you in a "real environment", I could write a second example which demonstrates how to handle with up to 1024 buttons, and maybe a third which uses a seperate shift register chain (which is captured more frequently than the "normal" chain) in order to minimize the latency. Please use MIOS V1.7 otherwise the DOUTs are not driven properly. The current release candidate can also be found in the download section Best Regards, Thorsten.

Hallo, wie ich bereits vermutet habe, misst Du falsch - am mittleren Pin des 7805 kann gar keine Spannung anliegen, weil dies der Bezugspunkt fuer alle Messungen ist. Hier ein Schaltplan, der das verdeutlicht: Ansonsten darf ich mich aus einem anderen Posting zitieren: Gruss, Thorsten.

Hallo, wie ich bereits vermutet habe, misst Du falsch - am mittleren Pin des 7805 kann gar keine Spannung anliegen, weil dies der Bezugspunkt fuer alle Messungen ist. Hier ein Schaltplan, der das verdeutlicht: Ansonsten darf ich mich aus einem anderen Posting zitieren: Gruss, Thorsten.

why are you not writing about such a problem before assuming something into the wrong direction? This would make the discussion much easier (and shorter)... I think that there is either a misconfiguration in your program, or you made something wrong during the BankStick upload. A good starting point is to check the BankStick content based on the method described in the bs_xfer example. If the content is like expected (it must contain the original data), you know that your program has an error. In this case just explain how you've setuped the variables of the SysEx sending routine. Best Regards, Thorsten.

To your additional text: I really don't see the problem. Sending a 0xff? Just write: movlw 0xff call MIOS_MIDI_TxBufferPut The problem is that your are thinking about technical aspects which are not relevant. Maybe it's better when you just would play with the code examples I already gave you in order to understand the possibilities. Once you've learned more about sending MIDI events, a discussion would be much easier (or obsolete ;-)) Best Regards, Thorsten.

yes, thats right. You see, it isn't so difficult ;-) Best Regards, Thorsten.

by using a clever multiplex algorithm for the shift register chain, you could multiplex up to 1024 buttons - the scan matrix driver will make this clear. But there are also disadvantages of this method: each button needs an additional diode, higher latency or higher CPU load, higher RAM consumption, and the driver itself is very individual - it depends on your hardware and on the application, and therefore requires some technical as well as programming skills. Therefore this solution is not supported as "standard" by myself, because the guidance would cost a lot of my sparetime. So, I will provide unsupported example programs. Best Regards, Thorsten.

Hi, maybe you should contact Duggle who is also working on an IIC slave driver Best Regards, Thorsten.