TK.

No, it has been temporary disabled to check, if the subversion web-frontend caused the server lags in the last weeks. The repository is still accessible with a SVN client (see Wiki) Best Regards, Thorsten.

Blogged :)

Nice explanation, Seppoman! :) Actually I knew what you mean, but failed to find a video which shows this exactly. I think, that desoldering wick is the last chance for the case, that you are trying this method the first time, and you are not able to remove the solder between the IC legs by heating them up again. But applying more flux before heading up sounds like a good idea - I will try this while soldering the next boards ;) Best Regards, Thorsten.

It was the first time I used flux and desoldering wick after I got an hint from Seppoman - this made SMD soldering really fast (and secure) :) This is an helpful video which shows the approach: http://www.ulrichradig.de/gfx/video/SMD_einloeten.wmv Best Regards, Thorsten.

Yes, except for the In/Out swap it worked immediately! :) It takes ca. 30 minutes to stuff the module. Best Regards, Thorsten.

Thats strange, I haven't noticed this while testing/using different MBSEQ hardwares in the past. From the SW point of view, there is no reason why the LCDs shouldn't be refreshed completely (both screens are refreshed periodically). Therefore more input to replicate this issue would be really helpful. Best Regards, Thorsten.

Do you think that this was an issue in rc19, or could it be related to your private code changes? A typical error is to direct access RAM locations >= 0x60 w/o using BANKED access type (and ensuring, that BSR is set correctly). On such a programming error, you could easily overwrite variables of the CS. thank you! Finally it's possible to give a bassline the real SID touch :) Best Regards, Thorsten.

Unfortunately I swapped the MIDI In/Out labels, accordingly MIDI In and Out jack traces are connected to the wrong pins. It's easy to fix, but very annoying anyhow. Good that we ordered a prototype ;) Best Regards, Thorsten.

It's the free assignable parameter as described in the User Manual (search for "parameter") You can already select the sequences with the 8 row (R channel) and 8 column (L channel) buttons of the LED matrix. Just add them to your CS (w/o LEDs), it's the best solution, it's especially nice if you want to select&play a certain sequence in the edit page (you don't need to change the menu to select a different sequence) Best Regards, Thorsten.

Read Wilba's posting again. Best Regards, Thorsten (loves his new toy :))

There is neither enough RAM, nor free memory in the Patch structure to store sequences of patterns. It's a minor feature anyhow, there are enough alternative possibilities (e.g. sequencing from an external MIDI sequencer) Best Regards, Thorsten.

:) Nice idea, I'm missing this possibility as well! How about following solution: controlling the base note of L and R bassline via MIDI channel and keyboard zones defined for Ensemble Instrument #3 and #4 This would cover following use cases: - pattern selection via INS #1 and #2 settings as today - no transpose so long no MIDI channels are assigned to these instruments - if same channels are assigned to INS #1..4, and seperate zones for #1, #2 and #3/#4, you can control transpose from the same keyboard that you are using for pattern selection - but it would also be possible to play the basslines with different base notes from different zones or channels (-> from a different keyboard, or MIDI sequencer track) - assigning INS #3 and #4 of all SID cores to the same channel/zones would allow to control the base note of 8 basslines from the same keyboard. This could also be perfectly combined with MBSEQ (as it provides a split point for the transpose function as well) Best Regards, Thorsten.

Status Update: - GM5 chips will be available end of July. - I will get the PCB Prototype this or next week. I already got 5 new GM5 samples with most recent firmware for testing - money will be collected once I know the exact delivery dates for GM5 and PCBs Best Regards, Thorsten.

There is a new release candidate RC21 with some new features, especially useful for MB-6582 users and bassline fetishists :) [tt] o added "Log" flag to ENS->FIL menu: cutoff frequency converted through log function to achieve better linearisation of 8580 filter o Filter Keytracking parameter now also available for Lead Engine, the scaling has been slightly changed, so that the maximum value 255 leads to 1:1 tracking (e.g. if 8580 Log function activated, or an external filter is connected) o added "DOR" flag to the ENS->SID menu: Disable automatic Oscillator Reset during patch change could also be called DAORDPC flag ;-) o MB-6582 setup: swapped page up/down button, added Inc/Dec button function o support for 4x20 LCD has used for MB-6582: DEFAULT_LCD_LINES and DEFAULT_LCD_LINE_Y* can be configured in the setup_*.asm file o MB-6582 screen now centered at 2nd and 3rd line o if DEFAULT_LCD_LINES >= 3, the name of the menu will be print at the upper line TODO: add more informative messages, e.g. selected oscillators, audio channel, LFO, etc... o if DEFAULT_LCD_LINES >= 4: the value of the currently edited parameter will be displayed as horizontal meter bar at the lower LCD line TODO: display bidirectional parameters like "depth" with a left/right splitted meter TODO: update when a new OSC/Channel/SID is selected o the "blinking LCD cursor" which was set to the selected parameter position is disabled by default now (DEFAULT_LCD_PRINT_CURSOR set to 0), since it clashes with the horizontal meter output routine o added experimental features to bassline engine: - new menu page O23 which allows to use OSC2 and OSC3 as slave oscillators - waveforms of slave oscillators can be selected seperately - individual sync and ringmod flags - individual octavewise transpose - individual pulsewidth - optional static note (decoupled from master osc) for nice sync/ringmod effects or chords - phase offset - detune - TODO: Knob assignments and maybe more functions [/tt] Some of the new features are work in progress (missing planned functions are marked with TODO) Best Regards, Thorsten.

It seems, that the EEPROM content (which stores the default ensemble, drum and patch) is corrupted. This can lead to such effects. Other problems could be related to an incomplete application upload as well. Therefore I propose to upload the application via MIOS Studio again. Error messages during the upload will indicate, that something is going wrong (again)... Best Regards, Thorsten.

Did you select the AOUT module correctly in your setup file? There are different numbers for AOUT/AOUT_LC/AOUT_NG. Since AOUT_NG requires some additional configuration, it could be important that you power-cycle your MBSID after the new firmware has been uploaded, just to ensure that AOUT_NG starts properly. Best Regards, Thorsten.

Under http://www.ucapps.de/tmp/mbhp_usb_v1_3_variants.zip you will find two variants of "v1_3" (from March 2006, it has never been released) - it would be interesting, if one of this variant is working better that v1_2 Best Regards, Thorsten.

Yes, v1.2 has been released in February 2004 There is a newer version on my PC (but I haven't used it for the MBHP_USB connected with the Mac) with a new Vendor ID that I got from Voti, and some other optimisations that I don't remember anymore. It could be worth a try, just to check if 0x8ef1 somehow conflicts with another USB device. However, chances are low, especially if we consider, that I'm using a very similar MBP (6 months old) and the latest Leopard release as well Best Regards, Thorsten.

Could you please record the noise with and without connected CS in a short .wav file, and attach it to this thread? Best Regards, Thorsten.

Which firmware version are you using? I remember, that v1_0 (or v1_1?) was compiled with reduced (non-compliant) USB device descriptors as workaround for a WinME bug. v1_2 has been compiled with complete descriptor table. Also the vendor/product ID could be for interest. Go to "Apple->ABout my Mac->More Informations" (naming could differ in your installation), select the USB tab, select MBHP_USB interface. You should see Version: 0.01 Bus-Strom (mA): 500 Geschwindigkeit: Bis zu 12 MBit/s Hersteller: Thorsten Klose Produkt-ID: 0x8ef1 Hersteller-ID: 0xac89 [/code] (german installation) Best Regards, Thorsten.

Works fine at my side. Best Regards, Thorsten.

Ca. one year after Wilba introduced his famous MB-6582 to the world, which became one of the most popular MBSID designs with dozen of PCB/kits orders, he created a new version with a lot of improvements: the MB-6582 MkII More photos (for example with the first happy owner of a MkII :)) can be found at Wilba's flickr page

Great! :) Best Regards, Thorsten.

You could use the 74HC00 based In/Out indicator circuit of the MBHP_LTC or MBHP_USB module Best Regards, Thorsten.

I've a similar issue with my MBP with any MIDI USB interface (e.g. MBHP_USB*, GM5, modified MIDIsport 2x2), whenever the MIDIbox is externally powered, and MIDI In/Out are not isolated against USB power. The interface will only be regognized, when the MIDIbox is not powered while plugging the interface into the USB port. So, are you using optocouplers at the MIDI INs of MBHP_USB and Core module? It makes sense to add them. Best Regards, Thorsten.