Our community blogs

  1. ModulBox

    • 2
    • 5
    • 192737

    Recent Entries

    Construction d'un séquenceur,

    SEQ V4 midibox  (2016)



    Après la construction de 2 contrôleurs midi le modulebox et le pushbox, je décide de fabriquer un séquenceur.


    Toutes les infos proviennent du site: Merci T.K.


    1ere étape, construction de la BOM, liste des pièces a commander

    En attendant la réception des circuits imprimés que j'ai commandé sur :

    J'essaye de créer moi même ces circuits imprimés sur kicad:



    après la schématique le routage:




    import et commande chez


    Le 05 juillet 2016

    commande de composants effectuée chez mouser et reichelt selon la BOM suivante :



    Le 18 septembre 2016


    Réception des circuits imprimés du CORE stm32f4 que j'ai redessinés précédemment et fais fabriqués par



    Peuplage d'un PCB


    1er Test :) youpi ça s'allume :





    La face avant wilba n'étant disponible en vente sur aucun site, je décide de la redessiner sur kicad et c'est reparti pour une schématique :





    envoi pour commande à




    prévisualisation avec blender



    2 octobre 2016 ; Commande de PCBs reçue , 


    Et c'est parti pour la soudure :)





    assemblage et test







    fabrication de la boite






  2. When interfacing a Joystick, Modwheel or Pitchbender it is sometimes found that the voltage range on the potentiometer output is well inside the range of the Core ADC input.


    This can often be overcome with digital calibration in the firmware (e.g MIDIbox KB) in some cases there is extreme loss of resolution.


    Presented here is a circuit to overcome this to give the ADC the full range (in this case 0..3.3V) even though the range of the potentiometer is well inside this.

    The design process is very easily done following this app note:sloa097.pdf 230.01K 12 downloads


    I've done a spreadsheet to make it even easier!Scale 2.45K 9 downloads If you don't have MS Excel, you can use it with free tools Google Docs, or Open Office.

    To use the speadsheet you enter numbers into the blue fields. The input range at the top as measured on your pot. In preparing the examples, I played with the value of Rg2 so that Rg2+R1 came close to 10k. This allowed to replace them with a 10k trimpot as in the example circuits. It was just as well, as the trimpot did require some tweaking away from the calculated values, I found.


    I chose LM324 op amp as it's output goes down very close to 0V. It's maximum possible output with a Vcc=5V is about 3.5V which should be quite safe with a 3.3V Core ADC such as LPC17 MBHP Core.

    There are 4 op amps in this device, so 4 scaling/offset circuits can be implemented with 1 chip.


    Here's the circuit with 2 worked examples:



    Here's the test (input on left, output on right) showing 3 points (Modwheel example):



    Here's another test (input on left, output on right) showing 3 points (Pitchbender example):



    Appnote Cct with Examples.jpg

  3. Hi everyone I’m back and my project too.

    It was not easy. Not because of the technical issues, just bad karma.

    In 2011/2012 I made a working firmware and a manager under Max/MSP.

    Because of personal reasons, I put the project on hold.

    End of 2012, I received a message from Eptheca who asked me the status of the project.

    With his help we decided to print 3 PCB’s. Unfortunately during this period, the hard drive of my computer suddenly decided to leave me, and I lost all my work: ((

    I sent the drive to Shanghai to try to recover my data, but of course my disc was one of the non-recoverable 10% (always this bad karma).

    So now we had the box and the electronics but nothing to put in it.

    In February I decided to rewrite everything but it took me some time.



    We've now got a new firmware and the application to manage the box.

    I am inspired by the version 1 MB-SID.

    I kept all the features of this engine.

    I improved the management of banks, I dedicated two envelopes to the voice of the TIA which is free, and a few small details that might please you.

    Here is the features of it:

    • 1 dedicated envelope for each voices(so 2) with optional non-linear curve and Sync which can be assigned to Amplitude and pitch. 3 specifics Mode to mix Modulation matrix and this env
      Env+Mods, Env*Mods, Env+(Env*Mods).
    • 2 additional envelopes with optional non-linear curve and Sync which can be assigned to Amplitude and pitch.
    • 4 additional LFOs with different waveforms and Sync which can be assigned to Amplitude and pitch.
    • Pitch Bender
    • Portamento/Glide function with Optional "Constant Time Slide".
    • Delays
    • 1 Arpeggiator for each voice(so 2) with optional Sync.
    • Poly, Mono and Legato Mode
    • Separate keyboard zones for each voice (key splitting) allows to play voices separately
    • Extended Mode for keys(all note reponse) or non extended with offset and length.
    • 1 velocity response for each voices (so 2) with optional CC assignment
    • Free controller assignments to Modulation Wheel and Aftertouch
    • LFOs, Envelopes, Arpeggios optionally syncable via external MIDI clock (one for each;)
    • BankStick support (4 banks of 128 sound patches per stick, up to 8 can be connected) so 32 banks.
    • And much more.

      Coming soon:

      • wave and CC sequences which allow more percussive sounds (Wavetables) with dedicated banks.
      • Drum or Fx Kit Presets with dedicated banks.
      • 8 Analog I/O
      • 4bit sampling ;)
      • Atari 2600 Joystick and Video touch pad support.

      There's no CS on the cartridge version, but there's enough room in FW to add it. If someone wants to create it, you are welcome. This firmware is only for 18f4685.

      You can add MB-Link too if you need it, PORTA.0-7 and PORTB.0-3 share 8 I/O on the AUX connector.

      No CS; but I designed a Max/MSP Application (windows and Mac compatible):

      And it has iDevice support(sorry for those who boycott Apple products):

      I'm trying to finish a Max4Live version, with a common file between both applications that will retrieve the names of banks, patches and all parameters without having to open the input of the midi track and make a CC request (there's no SysEx in Ableton Live).

      Now i suppose you want to hear it:

      Listen on

      Voilà!!! :smile:

    • 0
    • 0
    • 22768

    No blog entries yet

    • 1
    • 0
    • 22248

    Recent Entries

    MIDIBox SlideControl is a remote control solution for Kodak Carousel slide projectors aimed at event usage.

    It was a sometimes painful process of about 1.5 years to arrive at the solution at last. Success would not have been possible without the great midibox community! Thank you!


    One box "on stage" receives MIDI and button presses to switch slides forward/backwards. Due to the long distances to be bridged (10-50 meters), it was necessary to use the CAN protocol/MBNet to transmit the necessary information to a distribution box (typically up in the rafters/trussing), from where up to 8 slide projectors are controlled in a star topology. Control is achieved by closing an electric circuit of the projector via a reed relay for total electric insulation.

    Preliminary test confirmed that it is possible to transmit control information over 100 meters (!) of ordinary cable. The CAN protocol maximum specified distances lie in the range of 7 kilometers, only dependent on bit rate.

    Due to the nature of the CAN protocol, it is easily possible to add further distribution boxes and daisy-chain them from the first one. One could control more projectors than I care for that way (>=64), only limited by MBNet address space.

    One nice consequence of the design is, that XLR-cables, which are ubiquitous in event production, can be used for the cabling of the whole project (stagebox->distrobox, distrobox->projectors).

    Stage box

    The stage box consists of one PIC8 core stuffed with a 18F4685 (necessary for the included CAN interface), one DIN for the buttons, one standard character LCD, and a small self-designed PCB for the CAN driver/transceiver, all put in some plastic case I had lying around.

    Distributor box

    The distributor box consists of one PIC8 core (with 18F4685 as before), and a self-designed PCB containing half a DOUT, the CAN driver circuitry, and the reed relais. XLR plugs etc. made the whole affair a little cramped (the core is actually stacked on top of the self-made PCB!), but I am very satisfied with how it turned out.

    Some adapter cables and a connection tester made the whole thing complete and ready for action!


    The software is basically a MIDIO128, augmented with the MBNet parts I ripped out of Midibox SIDV2. Due to MBNet only being available in assembly, I had to stay with a programming language I don't actually speak. TK was an invaluable help in merging the relevant source codes together!

    The software forwards button presses to a distrobox. Since the distroboxes have Device ID's starting from one, it was possible to route received MIDI events to distroboxes depending on the MIDI channel, so events on Channel 11 only go to distrobox 1, Channel 12 to number 2, etc. I chose to start with Channel 11 to avoid interference with common MIDI control messages, which are typically on CH1.

    I would rather not just put the code online here, because it is actually quite a hacky solution, and most probably affected with bugs I haven't found, and definitely not programmed elegantly. I only grafted MBSid code onto MIDIO128 in the crudest way possible, and I don't really know how to program assembler, it was much more "educated copy-paste". I will definitely send the code on request, and I did everything in a git repository, so it should actually be possible to follow my changes, and adapt them to you own needs.

  4. Yes, i admit, i'm slow as a turtle. But as a turtle i've put out my head, and today out in direction to the blog! :)

    Ok, jokes apart, in the previous step i've explaned how to get installed the needed tools to compile apps for our beloved Core controller, in this third step we will see how to get the SVN repository and then how to get and app compiled and ready as an .hex file to upload to our Pic Core, or Core32.

    First thing is opening the Terminal.

    Since the last step i assume that we get familiar with the Terminal window so i'll not explain where and how find it in our Macs!

    Once you have the terminal opened, go to your home folder.

    Usually when you open Terminal you're already on the Home folder, and you'll see your mac login name on the left of the cursor.

    Just type

    and hit return. You'll see a list of files and folder, open via finder your home folder, if you see that the files are the same you are surely in the home folder with the terminal. Otherwise you're in another folder and what you have to write in the terminal is the following command
    cd Users/yourhomename
    It will bring you to the home folder. Home folder that will be the folder where we will put the mios, or mios32 repository. With Terminal opened write this command
    svn co svn://
    You'll see that the Terminal will start to download all the repository files in a folder called mios in your home directory. We are downloading this repository in the home folder because we will have to set a .profile file needed to the compiling process. I'll explain his purpose later. Ok, when the Terminal have finished the download, we will see a folder called mios in our home with inside it two folders, trunk and playground. We will concentrate on trunk, the place were all what we need for our apps is placed. But, hey, we forgot the SVN32! Simple task, repeat the same command "svn co" but this time with the svn32 address:
    svn co svn://
    At the end of the download you'll have the core32 repository, always in the home directory. Now we have both core and core32 repository in our home folder. You should see mios and mios32 folders. Well, start to compile! No. Do you remember the .profile file mentioned just before? We have to edit it so the tools installed in the Step 2 will work flawlessy. Don't ask me more about this, as i'm learning like you and sometimes i know that things must go in this way but i don't know why because i haven't yet understood all. I know that's not brilliant, but at the end i've the compiling process working! :) (i hope to explain better why to modify .profile page as soon as possible!) Let's go on modify our .profile page, you braves! On terminal write this command (be sure that you're in the home folder "/Users/yourhomename", not in another folder like mios or music ):
    open .profile
    You'll see a textedit file opened. Put at the top of the file this code if you are using the mios repository:
    # mios
    export MIOS_PATH=/mios/trunk
    export MIOS_BIN_PATH=$MIOS_PATH/bin
    # mios end
    Put this code if you are using the mios32 repository:
    # mios32
    export PATH=$PATH:/usr/local/stm32/bin
    export MIOS32_PATH=/mios32/trunk
    export MIOS32_BIN_PATH=$MIOS32_PATH/bin
    export MIOS32_GCC_PREFIX=arm-none-eabi
    export MIOS32_FAMILY=STM32F10x
    export MIOS32_PROCESSOR=STM32F103RE
    export MIOS32_LCD=clcd
    # mios32 end
    If you're using both the repository put this:
    # mios
    export MIOS_PATH=/mios/trunk
    export MIOS_BIN_PATH=$MIOS_PATH/bin
    # mios end
    # mios32
    export PATH=$PATH:/usr/local/stm32/bin
    export MIOS32_PATH=/mios32/trunk
    export MIOS32_BIN_PATH=$MIOS32_PATH/bin
    export MIOS32_GCC_PREFIX=arm-none-eabi
    export MIOS32_FAMILY=STM32F10x
    export MIOS32_PROCESSOR=STM32F103RE
    export MIOS32_LCD=clcd
    # mios32 end
    Save the file (cmd+S) and then close. Now, to refresh the system with the new .profile file we have to write this in the Terminal window:
    . ~/.profile
    Be careful to include also the first dot! Best way copy and paste. ;) Once the .profile file is refreshed we can now go with our terminal to an app folder and try to compile it. But before i advice you to do always a backup of the folder that contains files needed to compile. My workflow is the following: I need to modify and compile the blm_scalar app. I copy the blm_scalar app folder in another backup folder, folder that can be placed anywhere outside the mios, or mios32 folders. I will have in this way an original copy of the svn downloaded one. Now that we have placed the original copy in a secure place we will start to go into our app target folder with the Terminal: When you are in the home folder with the Terminal write this command
    cd mios/trunk/apps/controllers/blm_scalar
    You'll be in the blm_scalar folder where all the .c, .h and makefile, needed for compiling, are located. Remember that you must go in an app single folder with Terminal to have the compiling process working. I mean, if you need to compile the midibox64 app, you will ahve to go to the midibox64 folder through the command
    cd mios/trunk/apps/controllers/midibox64
    and so on for the other apps. I advice you to check out the apps and the relative folders path via finder, and then write the needed path in the terminal. Ok, returning to the our folder, blm_scalar, we are ready to compile our target app. You should have in terminal this position:
    macname:blm_scalar yourhomename$ 
    What you have to do now is simply write in Terminal
    The terminal will print out some text and then the prompt will be back. And now? Check out what changed in the folder via the Terminal command

    You can check out what changed also with finder going into the blm_scalar folder.

    You should see that some files and a folder were created! should see project.hex, our compiled app ready to be uploaded to our core!

    Ok, now that we had this file how we can upload to our core?

    Simple, we will upload it using MIOS_Studio!

    Download it from here, scroll the page to the bottom, you'll find the download links for mac and windows.

    In the meantime that connect your Core board to your computer via midi, connecting both midi in and midi out.

    Once the MIOS_Studio is downloaded, place it in your applications folder and then launch it.

    Click over the browse button, go on the blm_scalar folder located in /"home"/mios/trunk/apps/controllers/blm_scalar, select the project.hex file and click ok.

    Then click the start button and the progress bar will raise up with the upload of the project.hex file!

    When finished your core will reboot and in the MIOS_Studio you will see a "ready" text!

    You have now your app compiled and uploaded!

    Consider that the same process is valid when you modify apps and the you'll upload them, is the same also if you are working with the mios32 svn.

    But remember always to backup the apps folders and to check if the svn is updated!

    I'll write about the modify of the app later as is something that i've not yet learned.

    In the next step i'll write about the components needed for my specific controller project and write about some other thing that i'll think over in the next days/weeks! Remember the turtle! :)

  5. Zossen
    Latest Entry

    got a broken Farfissa + a working Yamaha :frantics:


    the Farfissa will be for Parts and the Yamaha maybee too but its working so i think its better to clean and sell it.



    Freaky Speaker



























    Its a good base for the next VST Controller

    The Power Supply , Amp (2x30 Watt STK465 ) and the Speakers (2x30cm Full Range) are working fine (reusing the Cinch Terminal :) )

    Maybe a good combination as the next Active Speaker, the front part of wood for the speakers will be left ofter the Top Part gets cuttet from the rest,

    so just a part of the case will be missing.

    Is anybody interested in the Analog Audio PCB's than please PM to me.

    Its the Farfisa 304 Silver Soundboards

    -Delay Lines

    -Rhythm Analog Generator

    -Rhythm Digital Generator

    -Bass & Arpeggio Filter

    -Monophonic Filters

    -Orchestra Filters

    -LM UM Flutes Filters


    - Controls

    -Rhythm Module

    Each PCP inkl. Datasheet & Partlist

  6. SLP's Blog

    • 1
    • 0
    • 20271

    No blog entries yet

    • 0
    • 0
    • 20075

    No blog entries yet

    • 0
    • 0
    • 19647

    No blog entries yet

  7. hey all,

    I am continuing my blog on that way everybody can see how it is going with my project.

    Cheers Jef

    • 0
    • 0
    • 19310

    No blog entries yet

    • 2
    • 0
    • 18955

    No blog entries yet

    • 0
    • 0
    • 18752

    No blog entries yet

  8. taximan
    Latest Entry

    Beat 707 in and out also gorf2 (needs a new cs making),meeblip and shruti.







    • 0
    • 0
    • 17622

    No blog entries yet

  9. It's been a while since I've been able to work on any electronics projects, and while I've been I've been so slammed that I I've not been able to finish my last touches. (Filter pots, mix out, power LED... stuff like that)

    Starting next Tuesday, I'll have at least one recording session every week in my studio until sometime around mid 2014. Being that I'm already so slammed, my life, as far as my "hobby" projects go, will be over, for all practical purposes, until then. Therefore, I thought I'd try to get these last few touches installed before the onslaught of work starts.

    I'll admit I've been dragging my feet a little on this. My box never really worked that well. Notes would stick, cores would randomly go offline (especially if I had more than 2 cores installed) I could use it in the studio, (if it did something freaky, I'd just re-record) but it wasn't reliable to use in a live performance...which was my original inspiration to build this. It was suggested that a nice new linear power supply would be the fix. I don't have the chops at the moment to design and build one of those, and with my new job, I feel I won't have the time to learn... so I figured I'd just have to live with a MB-6582 with some intense personality quirks (much like it's owner) and not use it in a live performance situation. I've certainly learned a lot and had a blast building it, so it wouldn't be a total loss.

    Last night as I was preparing to cut some ribbon cable for the remaining filter pots, I noticed that the J1_SID1 and J2_SID2 jumpers were set for 12V. I'm rockin' 8580's! I had a really good feeling that I had found the problem!

    Initial testing proves correct. It seems to be working better than ever. I still need to test with a full load of 8 SID chips in it, but it's working great with four chips now. Hopefully the fact that I've been using it for the last 6 months or so with the incorrect voltage on SID1 hasn't damaged the first two SIDs. I don't typically leave it on for very long at a time (the longer it was left on, the more quirky it used to act) so, maybe I'm cool.

    This was yet another somewhat embarrassing oversight on my part. (This blog and my posts are chunk full of those.) Well, maybe my willingness to publish my mistakes will help someone troubleshooting in the future.

    I will eventually replace the old C64 power supply by building a linear power supply. I want my SIDs to last. But there is no way I'll have the time to get the expertise and do the build any time soon. However, as the old axiom goes: When you've got the time, you don't have the money...and when you've got the money, you don't have the time. Anyone feel like building me a power supply? :tongue:

  10. jojjelito
    Latest Entry

    Finally mounted all the PCBs on one of the 2 more or less identical modulars we're building over at the labs. I made some 2cm (0.787 inches if you prefer mongoloid units of measurement) thick strips of brass. Those were perforated with a 10mm hole so that they can sit between the pots and the front panel, then I added a small hole for the M3 screw that fixes it all in place. 2 strips per card ends up in too much metal shop for my liking but the end result is surprisingly sturdy.

    We opted for using lots of internal (in-panel) wiring as there are enough wires flying to and from the panel as is. The method of mounting the PCBs for all the modules near their panel space made for short cable runs.

    Now we ended up with one modular with an almost finished pre-wired front panel, one where all the synth PCBs sit where they should. Add the cabinet holding the PSU, add the MB-SEQ PCBs in the top panel of the cabinet, debug beyond the basic short/continuity tests done and we should get some tunage. Grr, it's a long trip but I see the train headlights emerging at the end of the tunnel!

    Basically, the mechanical (BORING!) aspects of it all takes up nearly the same time as the electronics. Le sigh... But, it will make weird sounds soon whistle.png

    • 1
    • 1
    • 15508

    Recent Entries

    I ordered a front panel for my Sequencer (using Wilba's design) from Julian at


    The panel looks great but as anybody following the discussions will know, it isn't easy for Julian to make threaded blinds so we decided to go for blinds that are large enough to fit a hex spacer in. They are 5.72mm diameter x 2mm deep.

    As JB Weld isn't that common in the UK, I thought I would try Loctite "Bond Loc". This is available from Maplin and claims to bond metal very well (it contains stainless steel!).



    I thought I would try the spacers for the LCD, there are 8mm deep (including the 2mm blind) so the LCD stands off 6mm from the back of the panel. Once I have some 2mm perspex/acrylic for the window, this should be fine (hopefully).


    While waiting for the Bond Loc to cure I built the Core32 module that I had earmarked for this. That went without a hitch and seems to work fine!


    The LCD's fit fine, bit of a cock-up though, I bought them cheap off t'ebay and they are Electroluminescent backlight ones. Oh well. One 5v inverter order later (only £12 so not too bad), That works quite well the picture shows it is a blue/green backlight so not unpleasant. I am still undecided whether I like the displays but they will do for now.


    I am now stopped until my PCB and other kit arrives, hopefully in January.


  11. In general I don't recommend starting any project with an enclosure that is smaller than what you can fit a proto version of your project in. But my enclosure supply just about gone, so I'll use what I have. The tekbox from TEKO enclosures. (NOTE: If for some insane reason you decide to emulate this work in progress, buy a tekmar case. It's the same but bigger)


    Stage 1: Planning (barely) ahead.

    Since this isn't a masterpiece by the MB gods, I 'm just going to build the control surface on veroboard (protoboard) and hand wire each component. This gives me that added option of making components sit really close to each other without worrying about PCB traces. My veroboards are from RadioShack. They are pretty standard 0.05" spaced holes and have pads on one side. To make sure the control surface would actually fit in the tekox, I created a new part of the pads in Eagle and then placed each component on the grid. My LCD in this picture is from the SparkFun eagle library. I also placed an optional 4 digit 7 segment display and knobs on the layout. (If you can, always place the knobs on encoder layouts. Even if its just a circle. I have at least 3 old projects that I never use because there isn't enough space for knobs and it looks like crap)

    blogentry-4340-016624400 1297998888_thum

    For all intensive purposes the 4 digit 7 segment display will probably not get populated (but its nice to have the option to put one there).

    Stage 2: Sizing up the competition

    As you can see in the picture below, the 1:1 print layout of the control surface fits perfectly in the recess of the top half of the enclosure. The knobs might protrude on either side of the case recess, but I'll just have to live with that.

    blogentry-4340-002913900 1298167212_thum

    Still not done checking though. I've burned myself enough to know that I'll have to test fit some parts on hand to make sure this is all going to work. After testing the LCD, I realized the SparkFun 16x2 LCD pin out is off by 0.05" but the outside dimension is perfect The SparkFun display was perfect. The Displaytech LCD footprint I used wasn't. I'll adjust the part and retest the fit. In the next version, I've also rotated the swing pot 180 degrees so that I can add the record indicator led next to the shift indicator led.

    Stage 3: 3D Rendering

    This step wasn't even remotely necessary. I'm just playing in sketchup with 3D rendering of eagle layouts. I've modified the EagleUp script and created some new models to generate a 3D rendering of this control surface. I originally had every intention of checking this against the enclosure DXF but OKW (TEKO) didn't have one available, so this is what you get. Still makes me happy to look at it.

    blogentry-4340-020420500 1297998963_thum

    This project is still very much a work in progress. At the time of this writing, I'm still planning the base PCB. If for any reason the MidiBox gods see a train wreck coming, let me know.

    • 2
    • 0
    • 15021

    Recent Entries

    Latest Entry
    The way Augmenter as a system is conceived cannot be easily explained in one sentence.
    The first thing to realize is that it is a whole guitar amplification system.
    It consists of several components, and this compartmentalization is what makes this doable, regardless of the size of the circuit.

    So let's run down the signal chain.
    Starting from the guitar and cable, we arrive in the first major building block, which is the pedalboard unit.
    This consists of several analog fx pedals, a BOSS GT-8 multi-effects unit, a DI and ReAmping interface, and the digital circuitry involved in making the connections between those parts.

    From there on, by means of a balanced feed of several meter length, we move into the actual amplifier. this one consists of two booster stages, level adaption circuitry, another DI-Interface, four preamp channels with flexible tone stacks, two effects loops, two output EQs, and several types of power amplifiers, so output power can be selected due to the prevalent environment.
    And, of course, there is some digital control means implemented here as well, interconnected by MIDI with the pedalboard, or controlled by any other MIDI controller for that matter. So, in essence, there will be two cables running between the pedalboard and the amp head, and that's it.

    That's the system I have in mind, and right now I'm feverishly drawing up circuit diagrams to design the components of this system.
    My personal goal is to make all this fit onto a single 155 square inch circuit board to order from goldphoenix, which I would seperate into individual modules manually,
    and build any missing stuff on perfboard.
    The midibox NG seems like the right start to base the pedalboard switching system on, and the money is still out on the (somewhat simpler) amplifier switching system.
    If I manage to obtain a crossbar switch IC, I will use that as a rather elegant switching solution.

    The power amps I have in mind and that I'd like to implement are LM386, TDA1517, TDA2003 (or TDA 2050) and LM3886. I opt for integrated power amplifiers because, in all fairness, they offer way better quality than anything that can be discretely built (as long as you provide proper cooling and won't let them clip).
    Tubes are out of the question for me; however much I like the sound of tubes, they're just a pain in the ass to get right, and the heat and inevitable wear makes them very problematic.
    One thing I want to avoid like the plague is ground loops, and thus every connection between independently powered devices (pedalboard, amp head, GT-8, ReAmp input, D.I. outputs) is isolated by using signal transformers, eliminating any chance of forming a hum loop.
    • 2
    • 0
    • 13969

    Recent Entries

    Indeed. After i got a message from shuriken. Seems something wrong with date setting.

    Anyway the software is completely new. This was a suprise to me.

    So start blogging!

    • 2
    • 0
    • 13840

    Recent Entries

    I have decided to put my MBFM on hold. And build a MB6582 first. This way i can see how a frontpanel design works out before i order a new design for the MBFM.