TK.

#%$%$&!! #%$%$&!! #%$%$&!! #%$%$&!!

Thank you! This finally gives me the right hint to help you - it saved a lot of time that you mentioned all the details. In order to preload the EEPROM, just create a file called "presets.asm" (or similar) Add this file to the MAKEFILE.SPEC file (search for MK_SET_OBJ, and add presets.asm like shown here: MK_SET_OBJ pic18f452.c main.c presets.asm within the presets.asm file, write: list p=18f452 radix dec org 0xf00000 ; eeprom base address db 0x01, 0x02, 0x03, 0x04 END [/code] as you can see: the EEPROM address space starts at 0xf00000 The EEPROM size of PIC18F452 is 256 bytes (-> 0x00..0xff), you are preloading this range with db entries. Multiple entries are allowed for better readability IMPORTANT: the ain64_din128_dout128_v2_0.zip package contains an older version of the makefile generator, which doesn't allow to add assembly files. SOLUTION: copy the tools and mios_wrapper directory of the most recent wrapper release (sdcc_skeleton_v1_9a) into your working directory - overwrite all existing files. Thereafter you need to create a new makefile. Under DOS just type "make", this will execute the "make.bat" script -- a new .hex file will be generated, which contains your application + the EEPROM presets Under Linux and MacOS, type "perl tools\mkmk.pl MAKEFILE.SPEC", and thereafter "make" ("make" will start GNU-Make) Best Regards, Thorsten.

Connecting the serial input directly with the serial output (pin 19&20) is an illegal operation mode - this cannot work. It still isn't clear to me, what are you planning to do exactly. Maybe there is a simple software solution? Some more details about your concrete plans would be helpful. Best Regards, Thorsten.

Andrea, could you please write more about the reason, why you want to write something into EEPROM? There are multiple ways for doing this, but to suggest the best way, it's important to know why... Are you planning to program a new MIDIbox application, or did you find this site via google without background knowledge about the purpose of this forum, and assumed that this is a technical board for common microcontroller programming issues? Best Regards, Thorsten.

Der ADC Handler ist noch nicht auf das neue SFR Layout vom PIC18F4620 und PIC18F4685 umgestellt, siehe auch http://www.midibox.org/forum/index.php?topic=9573.0 Ich plane eine neue MIOS Release in den naechsten Tagen (sobald ich mal Zeit finde, es gibt noch weitere Aenderungen) LCD Treiber: hier muss ein "clrf TRISB" eingefuegt werden, um die Ausgangstreiber fuer alle 8 Pins freizuschalten Gruss, Thorsten.

How fast are the signals on the DINs changing? The update period is 1 mS - are changes within a time window of 2 mS? Is the debouncing function disabled? Best Regards, Thorsten.

The patch initialisation time is mainly limited by the BankStick bandwidth, there is no way to improve this anymore (it's ca. 30 mS for 512 bytes) But the good news is, that due to the fact that slaves are connected via ECAN, the MIDI bottleneck (200 mS for 512 bytes) doesn't exist anymore - means: a slave is configured within the same time! :) In both cases "gapless playing" is not guaranteed - the only chance is to use a MIDI sequencer which allows to define a negative delay for program changes - like Logic Audio Best Regards, Thorsten.

Just press the SHIFT button (formerly called LINK button), and then the button below "Init Patch" (it is the fourth select button so far I remember) Of course, parameters won't be zeroed - but they will be set to useful initial values. Only one oscillator is used, all modulators disabled, etc.. you will see and like it :) I would propose to go through the "first steps" guide, it gives you some hints about the general use model: http://www.ucapps.de/midibox_sid_manual_fs.html Best Regards, Thorsten.

no, therefore I recommented the PIC18F4685 - for your project, which especially needs flash, not RAM, it's the better choice. Best Regards, Thorsten.

Hi Axel, I'm very sure that the waveform button is working - currently there is no known bug in the firmware, only missing features. ;-) Follow this guide for troubleshooting: http://www.midibox.org/dokuwiki/doku.php?id=din_module Best Regards, Thorsten.

I added following hint: ...but I'm sure that it wasn't the last time somebody stumbled across this requirement... it just remembers me, how often I had to tell a certain person, that he needs to change the channel on his VCR when he wants to record the same program which is currently visible on TV. Best Regards, Thorsten.

I'm sure that you would miss this important hint if the README would be larger than today. From the README: The required application upload procedure is described under http://www.ucapps.de/mios_bootstrap_newbies.html [/code] And from the newbie bootloader page: [code] The device ID selected in the upload window must match with the device ID of the core which should response to the transfer. Best Regards, Thorsten.

Thanks for your nice feedback! :) only two SIDs, controlled from a single core. I think that more SIDs would just add some unwanted complexity. On the other hand, additional cores/SIDs are nice if you want to have quick and uncomplicated access to different timbres and sequences, e.g. for a break or a smooth crossover to the next tune. It's just SID + feedback. It works with a 6582 or 8580, but not with a 6581 Filter caps: 22 nF No external filter has been used. Important setting: LP and BP are activated the same time, not only LP. This results into a higher resonance when audio out is feedbacked (this can even drive the filter to self-oscillation!). And the EXT flag must be set, otherwise you would only hear a distorted sound. (Note: EXT flag is not set by default in the bassline presets, I will change this in the next release) With MBSID V1 you are propably not able to produce similar sequences, as the V2 engine got a lot of improvements, such as: - modulation paths are calculated with signed 24bit resolution instead of unsigned 16bit - the filter control curve has been completely overworked (now linear with calibration functionality) - alternative decay rate for accented sounds - variable accent for depth parameter - possibility to switch between sequences with a keyboard (which results into much more variations) Some other tips: - use analog pots, faders and/or joysticks to control CutOff/Resonance/EnvMod/Decay and Accent - they give you more direct and faster access than encoders. Encoders are fine for the remaining parameters though (especially due to the total recall capability) - when adding drums, tune them until they are matching with the base note! - add effects (see below) - an analog mixer to amplify the SID outputs -> compressor -> stereo delay (with different settings for both SIDs) -> a stereo frequency spectrum spreader (the one which comes with Logic Audio) for the high pitched bassline And a limiter for the mixer sum (I use the "Classic Master Limiter", which is freeware, but behaves much better than the limiter integrated into logic) no problem! :) Best Regards, Thorsten.

[ x ] sound example with MIDIbox SID [ x ] please :) Best Regards, Thorsten.

I've no experiences with using other chips than AN2131SC (note that AN2131S is a different chip!) Dangers are too high, that the firmware won't run without debugging. Therefore I strongly recomment to search for a commercial MIDI interface instead - in europe such interfaces are available for 20 EUR, so that it doesn't really make sense anymore to build an own one Best Regards, Thorsten.

According to the ChangeLog http://www.ucapps.de/mios_changelog.html) the upper border is 0x7fff now. By using the most recent SDCC skeleton, you will get all the required changes in the setup files. Once you hit the border, just use a PIC18F4685 - it provides 96k flash instead of 32k, and it also has more RAM - it would only cost you $10, so no need for wasting time in code optimisations (which wouldn't be possible for MIOS anyhow, only within your own code) Best Regards, Thorsten.

There are new docs and demo samples: Bassline Engine http://www.ucapps.de/midibox_sid_manual_b.html The bassline engine is available in the beta5 firmware (and higher), see http://www.midibox.org/forum/index.php?topic=9457.0 The two patches which I've used in the demos are part of the vintage sound bank now (patch A099 and A100) - have fun! :) Best Regards, Thorsten.

I just had a look on the picture of your core module, the colour code of R5 is wrong. 5,6k is green-blue-red If not available, you could also take a 4,7k resistor (yellow-purple-red) Best Regards, Thorsten.

The PIC doesn't receive MIDI data, and therefore sends upload requests periodically. It makes sense to continue with the remaining input tests - TEST IN6/7 help you to determine, if the optocoupler is working. Best Regards, Thorsten.

yes, both options are available. Currently this isn't possible, but could be added later if really required. I for myself never use such prepared sequence chains - they are too static Best Regards, Thorsten.

Yes, I used a fixed pot setting only for the pulse bassline. With feedback, the resonance is much more intensive. You have to enable the Ext switch within the FIL menu in order to route the audio input through the filter. Yes, these are only 8 sequences. You might have the impression, that there are more... variations can be easily realized by changing quickly between the sequences on the keyboard, or with the pads. This can be done for each bassline seperately. I disabled the synch-to-measure option, so that sequences are selected immediately. Best Regards, Thorsten.

Hi Evilxsystems, yes, you can select the track length from 1..16 steps for each track seperately. And yes, you can synchronize the basslines to an incoming MIDI clock - this is the method I'm commonly using (see this example: http://www.midibox.org/forum/index.php?topic=9599.0) Best Regards, Thorsten.

No, this time drums are coming from the Stylus RMX VST; MBSID V2 is synchronized to MIDI Clock provided by Logic Audio Best Regards, Thorsten.

So, I've continued my work on the bassline engine in the last days. Meanwhile I've added the feedback mod which has been introduced by AlphA. I connected the pot in the same way like described by Wilba (outer pins connected to ground and SID output, slider connected to SID input) Here a very repetitive demo (repetitive, so that everybody can pick out his highlights - my personal highlight begins at ca. 2:35, but also 4:30 isn't so bad) Warning 1: file size >8 MB Warning 2: this is the dumb music our parents warned us! ;-) http://www.ucapps.de/mp3/midibox_sid/mbsidv2_bassline_demo2.mp3 Played live on a Korg Microkontrol: Sequences selected with the pads, sound parameters changed with the faders and the joystick Best Regards, Thorsten.

this last mismatch is ok (it's the configuration area) If you receive pitch bender events, the PIC is running at the wrong baudrate, accordingly the PIC ID header is not programmed correctly. Maybe you are not using P18 to burn the PIC? However, either use P18, or follow the instructions of "TEST SW2" (file:///home/avatar/public_html/howto_debug_midi.html) The use of P18 is easier Best Regards, Thorsten.