TK.

Lesen ist auch nicht Deine Staerke? ;-) Lies Dir bitte auch nochmal Hallucinogen's Kommentar durch - in meinem Beispiel ist naemlich ein Fehler Gruss, Thorsten.

Reason: http://www.midibox.org/forum/index.php?topic=5812.0

Hi, in main.asm, set the "USED_AS_KEYBOARD" switch to 1 This allows you to assign different MIDI events to the buttons - it has to be made in buttons.inc Best Regards, Thorsten.

I'm not a layout expert, maybe bypass caps at the power rails help? ;-) Best Regards, Thorsten.

Hi, from the technical point of view this is possible, you could already try to preload a small flash range with the MIOS_BANKSTICK_PageRead and and MIOS_FLASH_Write functions. Once this is working, you could take the required source codes in order to create the bootloader. This isn't trivial if you've never worked with assembly language before... Best Regards, Thorsten.

Hi, if the track is in "controller mode", you will have 16 MIDI controllers for each track. No, it doesn't multiply with the layers Best Regards, Thorsten.

General hint: if the MBSID audio out is routed through a sequencer, then just insert a VST based evelope follower at the beginning of the Fx line - it helps you to eliminate the background noise completely so long no sound is played. And if it supports a lookahead function, the dynamic behaviour of the sounds won't be affected. Best Regards, Thorsten.

So, everything seems to be on place. Are you working with Win98 or WinME? Then it might be useful to add the PATH extensions into the C:\AUTOEXEC.BAT file, and to reboot the PC Best Regards, Thorsten.

Ich halte es fuer sehr unwahrscheinlich, dass der PIC defekt ist. Die Analyse muss systematisch angegangen werden, deshalb mein Vorschlag, zunaechst einmal die MIDIO128 Applikation aufzuladen, um eine "Bestandsaufnahme" zu machen Gruss, Thorsten.

das geht uebrigens wie hier beschrieben: http://www.midibox.org/forum/index.php?topic=2701.0 Gruss, Thorsten.

Excellent! :-) Best Regards, Thorsten.

Hi George, how many shift registers are enabled by the application? The number is normaly set with MIOS_SRIO_NumberSet It's save to set it to 16 (max value) Best Regards, Thorsten.

Hi, note this error message: [tt] e:\miosc\sdcc\bin\sdcpp.exe: eg.c: No such file or directory [/tt] [tt] e:\miosc\sdcc\bin\sdcpp.exe: mclock.c: No such file or directory [/tt] how and from where are you starting the make.bat? Best Regards, Thorsten.

I don't think that this UI will be enough to meet all requirements. E.g., in MIDIbox-SID, some bitfields within the CC value needs to be handled seperately for good results. It will get even more complicated, once a wavetable patch should be generated. Supporting SysEx is a must, because most synthesizers don't provide a way to edit all sound parameters via CC. However, today I've migrated the perl based random patch generator to C, it can be found here: http://www.midibox.org/forum/index.php?topic=5864.0 This application gives perhaps a good basis for your experiments with a user interface. Best Regards, Thorsten.

For those who feel bored on those dark winter days. This application is just the port of the mk_sid_random.pl script (and TL's patch manager) - if you don't want to use these comfortable PC based programs, but if you are searching for a standalone solution, then this application could be interesting for you: [tt] sid_random V1.0 © 2005 Thorsten Klose (tk@midibox.org) =============================================================================== This application generates random patches for the MIDIbox SID It just requires one core module, a button to "fire" the random patch, and a "true random generator", e.g. based on http://willware.net:8080/hw-rng.html The random generator has to be connected to pin RA0 of the core module (J5:A0) The button to pin RC3 (J6:SI) - a pull-up resistor is already installed there. The MIDI merger is enabled by default, this allows you to connect the random generator between a keyboard/PC and your MIDIbox SID. The additional latency is about 300..400 uS Random constraints can be edited in sid_random.c =============================================================================== A precompiled binary is already part of this package: o project.hex (can be loaded into MIOS Studio) o project.syx (can be loaded into any SysEx upload tool) Following tools are required to recompile the code: o SDCC v2.5.0 o gputils o perl The details are described under http://www.ucapps.de/mios_c.html =============================================================================== Required hardware: o one MBHP_CORE module o one button connected to pin RC3 of the PIC Optional hardware: o random patch will also be generated when any button of a DINX4 module has been pressed =============================================================================== Configuration steps: o check the "general application settings" in main.h if changes are required for your hardware setup (e.g., if no AINX4 multiplexers are connected to the core) o the application can be rebuilt with the "make.bat" file (type "make" in a DOS command shell) o Hint: unused analog inputs must be tied to ground, otherwise the core will transmit a lot of random CC events =============================================================================== Description about the most important files: - mios_wrapper\mios_wrapper.asm and mios_wrapper\mios_tables.inc: The MIOS wrapper code and MIOS specific configuration tables - pic18f452.c: exports PIC18F452 specific SFRs - main.c: the main program with all MIOS hooks - sid_random.c: generates the random patch There are additional .h files for all .c files which contain general definitions and the declaration of global functions/variables These .h files must be included into the program parts which get use of these globals =============================================================================== [/tt] Download: http://www.ucapps.de/mios_download.html Have fun! Best Regards, Thorsten.

To the question "TK - ever considered the VCA leak "fix"? by stopping the OSCs?": yes, I've considered this, but there is no perfect solution, therefore I never spent effort for a workaround and prefered to work on other features. Even your solution is not perfect as you've already noticed, but if you can live with side effects, then you are free to give it a try. So, the waveform has to be changed once the release time of the DCA has been passed. The release time can be derived from the SID_Vx_ENV_SR register (x=1..3). According to the SID datasheet, the highest release rate is 24 s (when the release value is 15). If your timer is part of the SID_SW timer (sid_sw.inc), then the delay counter must have a resolution of 15 bit (24 / 819.2E-6 = 29296). Each voice needs its own delay counter. It can be preloaded in SIDSW_Note_GateClrReq, and decremented at the end of SIDSW_Note so long the gate bit is not set (can be determined with the SID_MODE_GATE_ACTIVE flag) Once the delay counter has reached zero, the SID_SR handler in sid_sr.inc needs to be notified with a flag (for each voice seperately). If this flag is set, you can upload the new value into the control register with: movlw 0x<new-wave-value> movlw 0xe4 ; SID_V1_CTRL (note: reset line must stay 1) movwf MIOS_PARAMETER1 ; address call SID_SR_Write [/code] Value for SID_V2_CTRL: 0x0b Value for SID_V3_CTRL: 0x0c Coding of the control register: see SID datasheet An alternative solution would be to add an external gate like proposed by KD: http://www.midibox.org/forum/index.php?topic=4075.0 Best Regards, Thorsten.

Mir kommt das auch ein wenig seltsam vor. An der Software kann es nicht liegen, aus der Beschreibung geht zumindest nicht hervor, dass die Applikation modifiziert wurde. Warum sollte gerade die Button-Behandlung ploetzlich nicht mehr funktionieren? Gefuehlsmaessig kann es sich nur um ein Hardwareproblem handeln. Von der Hardwareseite her gesehen finde ich es seltsam, dass der Encoder funktioniert! Daraus folgt, dass zumindest zwei digitale Eingaenge erfolgreich eingelesen werden, und somit die Verbindungen zwischen Core und DIN Modul intakt sind. Waere die SCLK oder RCLK Leitung defekt (Kurzschluss oder kalte Loetstelle), so wuerde nur ein Pin (D7) funktionieren. Hinzu kommt, dass der 74HC165 bereits ausgewechselt wurde. Auch die Spannungen scheinen korrekt zu sein (der 74HC165 arbeitet auch noch bei 4.5V) - eigentlich *muessen* die Buttons einfach funktionieren. Koenntest Du mal die MIDIO128 Applikation aufladen? Welche MIDI Events werden gesendet, wenn Du am Encoder drehst/auf die Taster drueckst? Gruss, Thorsten.

Random: The challenge is to find an erconomic user interface - this doesn't require programming skills, just only the right intuition at the right time. So: how should parameters (CC/SysEx) be specified, how should the constraints be entered? How many buttons and encoders are ergonomical enough? Compare it with the already existing PC based solution - will it really make more fun? Is it really worth the effort? Morphing: I'm normaly using the MB64E for such experiments... Best Regards, Thorsten.

A serious random function requires constrainable parameters, and this would blow the memory consumption of MBSID (and MBFM) too much. Also the menu interface would be very complicated. Note that the PIC18F452 contains only 32k of flash memory! However, the perl scripts as well as TL's patch manager allow you to generate a single --> constrainted! <-- random patch, as well as a whole bank of 128 random patches on-the-fly. The results are great, and you are able to change the constraints in order to force the results into a certain direction. This leads to very serious random patches, much better than you know from those freeware synths, it's even better than the random function of the Yamaha AN1x! It seems that nearly nobody has notified this "hidden treasure" yet? Just check the examples: http://www.midibox.org/midibox_sid/mbsid_demo_random_patches.mp3 http://www.midibox.org/midibox_fm/mbfm_demo_random_patches.mp3 Best Regards, Thorsten.

Here comes the next great MIDIbox SEQ design: Michael wrote: I asked him for the source of the rectangular buttons, they are from www.segor.de

Hi Joente, could you please do me a favour and describe, what is wrong with the make.bat? Which messages are print out? (I would like to improve the documentation) Best Regards, Thorsten.

You could map the analog value to a new value, similar to the way how it is done in analog_toolbox. But in general the results won't be good enough for serious work, because you will miss some values! Best Regards, Thorsten.

Hi, the ground area is not visible by default - it will be visible once you type the "rats" ("ratsnest") command. Changing diameters: type the "change" command Best Regards, Thorsten.

In short: C7 is configured as MIDI In, you can use it as common GPIO pin by removing the access to RCSTA in init.inc Shift register processing: possibily the registers are not shifted often enough? Check the loop counter Best Regards, Thorsten.

Unfortunately these devices are still not available, I'm waiting for a customer release since months... I guess that the PIC24HJ256GP206 or PIC24HJ256GP210 would be a nice successor of the PIC18F based MBHP, but there are also drawbacks: SMD package and 3.3V techology... (it will cost some additional hardware to interface a common LCD) However, a MIDIbox SID and MIDIbox FM with a 16bit controller would open a lot of new possibilities, but I fear that we have to wait months or years until this dream comes true! Best Regards, Thorsten.