TK.

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.

Symptomatic for the chaotic sorting of website/wiki/forum is, that we already have a wiki page which lists forum highlights, it only needs to be maintained :) Whenever you find an useful/interesting article, just add it here: http://www.midibox.org/dokuwiki/doku.php?id=forum_highlights And there is a special search marker, which helps to find questions&answers, which are not documented anywhere else: FAQMARKER Best Regards, Thorsten.

A programmed PIC shows bars ca. 2 second after power-on (while the bootloader is running), so long MIOS hasn't been programmed, or if the LCD is not completely (or wrongly) connected. You can ensure that the bootloader has been programmed properly by using the verify function of the programmer software. Once you did this, please go through the troubleshooting guide (http://www.ucapps.de/howto_debug_midi.html) and list the results of each particular test - this could help us to analyse the problem. Best Regards, Thorsten.

Maybe issue [2]? http://www.ucapps.de/midibox_sid_manual_ki.html Best Regards, Thorsten.

This would happen if selection input A of the multiplexer is either not connected, or if it would have a short against ground or Vss. Note that this short/open connection/bad solder junction could also be located at the core side Best Regards, Thorsten.

Here a short update: I tested SwinSID last weekend, and was a little bit surprised about the behaviour of the official release. E.g., the pseudo stereo and reverb effect is always active (which eliminates powerful pulse/saw hooks), the DCA envelope is not fully functional (e.g. missing attack phase), and filter is not supported at all. Swinkels informed me, that he is now working on an improved version. I'm curious about the results - from the planned features list it could be a very interesting alternative for the 8th SID socket of my MB-6582 base board :) Best Regards, Thorsten.

Hope that you get it solved! By swapping the J15 socket (unintentionally of course), a LCD can be fried very easily, and one possible effect are random characters. But they normaly don't look like normal characters anymore, sometimes one or two pixel lines are missing, sometimes pixels are flickering. Best Regards, Thorsten (destroyed about 4..5 LCDs in the last years)

Thank you, Dietmar! :) I've added the link to the Wiki: http://www.midibox.org/dokuwiki/doku.php?id=midibox_lc hope that all PC/MIDI issues are solved meanwhile! Best Regards, Thorsten.

Fine - this was the only logical explanation for the missing digit. Best Regards, Thorsten.

For the records: ratsnest is required whenever somebody creates a layout based on an eagle schematic. This is the case for the MBHP_BURNER_V1 layout, which has been done by Mike. As I don't use the schematic module for my own layouts (I don't like the way how the circuit is displayed, and I find it easier to place&route the parts directly), a print out will work even without this well hidden command for most MBHP modules. Thats the reason for this "inconsistency" Best Regards, Thorsten.

Are you using a PIC18F4620 or PIC18F4685? The AIN channel is wrongly selected in the appr. MIOS versions. Since nobody has noticed this before (beside of me), I think that an update is not really urgently required (there are two other changes I want to do for the upcoming MIOS version) If you are using a PIC18F452, it sounds more like a bug in your hardware? Best Regards, Thorsten.

Did you solve the issue meanwhile? If not we could arrange a chat - many things can be clarified faster when we are talking directly Best Regards, Thorsten.

Ok, I added a link to the MIDImon application to clarify the context. Best Regards, Thorsten.

My own encoders are with integrated buttons as well, I connected them all together as an alternative possibility to activate the FAST function (means: when I push the encoder, values are changed faster) Best Regards, Thorsten.

You could check the Chameleon specs - you are propably thinking about a similar device: http://www.chameleon.synth.net/english/index.shtml Best Regards, Thorsten.

Hi Tom, how do you measure the pins, with a scope, or just with a multimeter? I would propose to check the continuity when all ICs are removed from the sockets. In this case, you shouldn't measure a "short" between pin 21 and ground (measuring result: > 0 ohm or even maximum resistance) Note that there is a troubleshooting page: http://www.midibox.org/dokuwiki/doku.php?id=din_module Best Regards, Thorsten.

Theoretical you could define different preload values in SEQ_CORE_ExtClk_Set (seq_core.inc). Currently the preload values are 0, 1, 3 and 7 (2^n-1) But your idea about using a trigger output, controlled by note events from a single track, is much better. It's not only easier to handle, but it would also allow you to add a shuffle Menu button disable encoders: this is possible, yes. But note that the GP LEDs change their purpose while the menu button is pressed (they display the selected menu page). There are also function, like copy&paste, which require that you hold a GP button while moving an encoder So, if you are still in the design phase of your panel: it's strongly recommented from my side to add the GP buttons Best Regards, Thorsten.