TK.

Very strange - the problem must be hardware related, because I didn't notice such bankstick problems on any MIOS core. Best Regards, Thorsten.

Hallo Andreas, ok, hier die ersten Tips die Du mal ausprobieren solltest: Versorgungsspannung variieren - du verwendest scheinbar das Reichelt Netzteil - bestens, hier kann man verschiedene Spannungen einstellen, probiere einfach mal alle Einstellungen aus, es kann nichts kaputt gehen. Wenn die Spannung zu hoch ist, werden die Spannungsregler (7805, 7812) etwas heiss, aber hier geht es ja zunaechst einmal darum, die Brummquelle herauszufinden... brummt der SID eigentlich auch dann, wenn der MIDI-Stecker nicht eingesteckt ist? Falls nicht, wird das Brummen von einer Masseschleife verursacht (schlechtes MIDI Interface) das gleiche gilt fuer den Audio-Out, aber hier wird es schwieriger. Hast Du den SID mal an eine Stereoanlage o.ae. angeschlossen, brummt es dann immer noch? den Audio-In koenntest Du mal probehalber kurzschliessen (auf Masse legen) Gruss, Thorsten.

Hallo Matthias, Jein. Das mit den Endlosreglern klappt so wie Du es beschrieben hast, hierzu musst Du lediglich in cs_menu_enc_table.inc folgenden Code: CS_MENU_ENC_TABLE ;; OSC "Env" Layer ;; Function name parameter menu offset cursor pos CSENC_ENTRY CS_MENU_ENC_CHANGE_OSC, CS_SID_VOICEx_DELAY, CS_MENU_OSC, 0x03, 0x03 CSENC_ENTRY CS_MENU_ENC_CHANGE_OSC, CS_SID_VOICEx_ATTACK, CS_MENU_OSC, 0x03, 0x04 CSENC_ENTRY CS_MENU_ENC_CHANGE_OSC, CS_SID_VOICEx_DECAY, CS_MENU_OSC, 0x03, 0x05 CSENC_ENTRY CS_MENU_ENC_CHANGE_OSC, CS_SID_VOICEx_SUSTAIN, CS_MENU_OSC, 0x03, 0x06 CSENC_ENTRY CS_MENU_ENC_CHANGE_OSC, CS_SID_VOICEx_RELEASE, CS_MENU_OSC, 0x03, 0x07 ersetzen durch: CS_MENU_ENC_TABLE ;; Env "Assign" Layer ;; Function name parameter menu offset cursor pos CSENC_ENTRY CS_MENU_ENC_CHANGE_MENU_P1, 0x00, 0x00, 0x00, 0x00 CSENC_ENTRY CS_MENU_ENC_CHANGE_MENU_P2, 0x00, 0x00, 0x00, 0x00 CSENC_ENTRY CS_MENU_ENC_CHANGE_MENU_P3, 0x00, 0x00, 0x00, 0x00 CSENC_ENTRY CS_MENU_ENC_CHANGE_MENU_P4, 0x00, 0x00, 0x00, 0x00 CSENC_ENTRY CS_MENU_ENC_CHANGE_MENU_P5, 0x00, 0x00, 0x00, 0x00 Doch die Selektierungstaster sowie das Datawheel werden auch weiterhin notwendig sein, es gibt einige Untermenues (wie bspw. das "Edit Name" menue), in der sie gebraucht werden. Falls Du Platz sparen moechtest, koenntest Du bspw. Alps Encoder mit einem eingebauten Button verwenden. Der Conrad-Link funktioniert nicht... Im PIC18F452 kann man nur einen einzigen Patch abspeichern. Gruss, Thorsten.

Could you please check it with a connected BankStick, just to give me more input? Best Regards, Thorsten.

A really good question, because this is a point which has not been documented very well yet. so: FAQMARKER the PIC18F offers two different addressing modes: ACCESS and BANKED ACCESS is the default mode, so you don't have to specify it explicitely on every instruction. It's independent from the BSR and allows you to access addresses between 0x00-0x7f and 0xf80-0xfff (SFR range) directly without initializing the BSR for BANKED accesses you have to ensure that the BSR is set correctly. So, if you are doing a lot of BANKED operations to addresses between 0x80 and 0x37f (other addresses are reserved for MIOS), you should initialize the BSR before. so long as the BANKED addresses are in between a page of 128 bytes (0x80), you don't have to reinitialize the BSR before every access. This influences the "coding style": addresses which belong together should be located in between a 128 bytes range in order to reduce code (the need to change the BSR) it's alway possible to copy a register value to another register by using the "movff" instruction independent from the source/target address without initializing the BSR. So, the easiest way to copy any register to the working register is: "movff ANY_REGISTER, WREG" --- but note that the "movff" instruction allocates 4 bytes, a common instruction (also SET_BSR) is only 2 bytes long, so this method should only be used if just only one register has to be copied. As soon as you plan to access more than 2 register of the same 0x80 page, it makes sense to change the BSR or: it sometimes makes sense to address the register indirectly by using FSR0 (main program) or FSR2 (interrupt service routine). The FSR has to be initialized with "lfsr FSRx, ANY_REGISTER", thereafter you can access it via "INDF0", "POSTINC0", "POSTDEC0", "PLUSW0", etc... note that most MIOS function are changing the BSR and FSR1 and don't restore it to the old value (to save execution time). This means: if a change of BSR is notified in the MIOS function description, and if you are using BANKED accesses, you have to restore BSR after every MIOS call. So, if you have a lot of interaction between MIOS and your main program, the use of indirect addressing (FSR0/FSR2) or the use of "movff" should be prefered in order to save code space Hint: registers which have to be accessed very often should just be located below 0x80 so that you don't have to take care for the page pointer. For example, MIOS_PARAMETER[123], TMP[12345] and IRQ_TMP[12345] are located between 0x00-0x0f which makes the use of this most frequently used addresses very easy Best Regards, Thorsten.

Thanks for the input, I will take this into account when I update the MBHP_JDM page next time. Oddly enough that for the 8.7V zener diode you have to decrease the IO delay, however... Best Regards, Thorsten.

Yes, please check the driver application first. Thereafter you are able to integrate the driver into the SID application by replacing the app_lcd.inc file and by selecting the custom LCD like shown in USER_Init Note that I never tried a T6963C display with the SID application, so when it doesn't work, it could be a bug in the driver which I cannot check (I don't own such a display). Note also that the performance of the T6963C in horizontal mode is not high enough for the SID application, so you possibly have to take the veritcal mode Best Regards, Thorsten.

Hi, there are two different IDs: the MIOS ID which addresses the core for code down- and uploads, and the application specific ID (here for the SID application). In a single core environment the MIOS ID should be zero (0x00). It has to be configured when burning the bootstrap loader into the PIC, but it can also be changed later by using the change_id application. You can verify the ID when booting MIOS, because the "upload request" SysEx string already contains it. It depends on the application how to setup and verify the application specific ID. The SID prints it on the LCD, if you don't use a LCD, you could send some pings with different device IDs to the box - once the SID application returns a ping, you are sure that you selected the correct ID Best Regards, Thorsten. FAQMARKER

Did you stuff the 1k pull-up at pin RA4? Best Regards, Thorsten.

Some reverse engineered informations about the houston protocol can be found here: http://www.triac.freeserve.co.uk/houston/ Best Regards, Thorsten.

Hi Flecko, regarding the caps: see the descriptions at the MBHP_SID page - these are the perfect values so far. To get any sound out of the SID, try following settings: write 0x0f to 0x18 (Volume) write 0xfb to 0x06 (Sustain/Release voice 1) write 0x40 to 0x01 (high byte of frequency) write 0x21 to 0x04 (Waveform control register - saw wave, gate on) Best Regards, Thorsten.

Hi Flecko, how do you control the latch? Did you ensure that there is no so called "race condition" (e.g. data and clock at the same time) Best Regards, Thorsten.

Hallo Frank, ich habe weder Erfahrung mit analogen Mischpulten, noch mit Cubase (bin halt Logic User...), deshalb kann ich nur zwei Tips weitergeben, die evtl. weiterhelfen: von Alps gibt es in der Tat Motorfader mit einer Lin- und Log-Spur, vermutlich sind die jedoch sauteuer. Du koenntest mal bei http://www.albs.de (kein Schreibfehler) anfragen. Die Automation koennte ueber 24 MIDI-Spuren geschehen, die ausschliesslich zur Ansteuerung (und Aufnahme) der Motorfader verwendet werden. Gruss, Thorsten. P.S.: geiles Pult! :)

Hi DriftZ, there are some simple examples in the SID application, see: sid_sin_table.inc (reading one entry from a table) sid_lfo_table.inc (reading two entries from a table) retlw and PCL isn't working properly on a PIC18F, you have to use the JUMPTABLE_2BYTES macro instead: MY_INCFILE_GetValue JUMPTABLE_2BYTES 8 ; entries retlw 0x01 retlw 0x42 retlw 0x03 retlw 0x74 retlw 0x35 retlw 0x23 retlw 0x84 retlw 0x23 the GetValue function has to be called in order to get the return value. However, table reads are more elegant. Best Regards, Thorsten.

Hi, in mb64_presets.inc you could change following lines: MB64_Presets_CFG0 db 0x00, 0x00 to: MB64_Presets_CFG0 db (1 << MB64_CFG0_MERGEROFF), 0x00 hope it works.. ;-) Best Regards, Thorsten.

Hi Dan, the BankStick select feature has not been integrated into the application yet, just wait for the next release. I don't see a reason why you would like to select a SID without the control surface? Best Regards, Thorsten.

Hm - no idea - then it must be a wiring problem. A while ago two users sent me their non-working JDM for analysis, and in both cases I found bad or missing solderings (and additionally: in one case the transistor was damaged due to a wrong connection...). So the only hint that I can give you: check the informations given at the MBHP_JDM page again and again. Sooner or later you will find the error - and you will know the circuit better than anybody else ;-) Best Regards, Thorsten.

The houston emulation only provides the Steinberg protocol and doesn't support a customizable setup, stored in the BankStick. This means that you have to exchange the application code (Houston<->MIDIbox MF) via MIDI, or you have to add some code to the emulation so that it provides an alternative mode (also in this case a BankStick probably wouldn't be required, see the General Purpose Controller (GPC) mode of MIDIbox LC) However, nothing is impossible: is there somebody who would start to enhance the houston emulation? - it shouldn't be a big job - I'm not a Cubase user, and I'm satisfied with MIDIbox LC, therefore this isn't interesting for me. Best Regards, Thorsten.

This is still a hidden feature, and it's only possible with the MIOS based version: just change the channels of the three voices in sid_presets.inc - the control surface will provide two new menu entries for it sooner or later (I don't use this by myself, therefore it isn't urgent ;-)) Best Regards, Thorsten.

Is a documentation really necessary? Just compare the two schematics, you have to solder the LCD and the 4051 select lines to other pins, you have to add a 10k pull-up to pin RC2 and RD1, and a 1k pull-up to RA4 (if it isn't there yet). Thereafter MIOS should boot properly Best Regards, Thorsten.

Dafuer gibt es viele Gruende: schlechtes Netzteil, defekter Elko, Masseschleife in der Stromversorgung oder im Audiopfad. Du hast nicht geschrieben, wie Deine Hardware genau aussieht, hier kommt es wirklich auf jedes Detail an. Gruss, Thorsten.

The circuit of the 6581 hasn't been changed, but the chip mask has been shrinked over the years by engineers who possibly didn't know what they are doing - the filter hasn't been adapted to the new dimensions and therefore sounds different (-> faulty) with every new revision. Humming sound is mostly caused by ground loops. I spent a lot of effort to eliminate this kind of noise and the final insights can be found in the mbhp_4xsid_c64_psu_optimized.pdf schematic. Seperating the analog from the digital ground doesn't help here, it's more important to wire the power supply lines "star-like" Best Regards, Thorsten.

Ja, Du solltest ausschliesslich Taster mit "Momentkontakten" verwenden. Empfehlenswerte Taster (am besten gleich bei Reichelt mitbestellen): die Minitaster "Taster 3301D" fuer 0.15 EUR pro Stueck - billig und prellfrei. Ich verwende sie ohne Kappen (ok, weil ich nicht weiss, wo man die bestellen kann ;-)). Fotos: http://www.midibox.org/midibox_lc_photos und http://www.midibox.org/midibox_sid_photos die runden Tasten "DT 6 xx" fuer 0.45 EUR (mit Kappen, gibts in verschiedenen Farben). Fotos: http://www.midibox.org/midibox_lc_photos die rechteckigen Tasten "DTL 2 xx" mit eingebauter LED fuer 1.75 EUR. Foto: http://www.ucapps.de/tmp/16buttonsleds.jpg Zu 4: in der MIDIbox64 applikation wird das Soft-Overtake Feature mit dem Snap-Modus aktiviert, siehe MIDIbox64 tutorial Gruss, Thorsten. /edit: FAQMARKER

Ist nun fuer die MIOS-Version des MIDImons vorgemerkt. Gruss, Thorsten.

Hallo Marc, evtl. ist das nur ein Effekt des Play-Mode Bugs, der in der neuen Version gefixed wurde. Siehe auch MIOS V1.4 Release Posting: Mehr hat sich in dieser Version nicht geaendert. Gruss, Thorsten.