• Content count

  • Joined

  • Last visited

Posts posted by daemonik

  1. I have to reduce some of my music equipment.... and decided to sell my MB-6582, since I barely use it!

    The synth was assembled by me, works perfectly and is in a very good condition! 

    It is a very unique unit!! Find the gallery here: 

    • Case and potentiometer knobs are made of Lego (suitable for SIDchip  sound)
    • The display is in 'rusty-orange' and matches the orange flat-top LEDs.
    • This MB6582 is expanded with an active mixer circuit (+/-12V supply). It has a main L/R out, volume-pot for each engine and a Stereo/Mono switch for each engine (in mono mode the signal is sent to right and left channel)
    • Single outputs are switched, i. e. if a single output is connected to a jack, the signal is not routed to the mixer (can be changed internally)

    Following chips are built in:

    • 4 SID 6582 (1x stereo engine and 2x mono engine at the moment)
    • 3 cores (4th core included)

    This MB6582 requires a power supply of +12v/+5V/-12V/GND. I built my own specific power supply around a MeanWell RPT-60/100kHz, can be operated from 90...264VAC.

    Price: 625€ + shipping

    located in Switzerland but can send to EU from Germany


  2. Ohhh... a new release.. again? awesome! thanks alot.. you are crazy man (in the good sense of course!!!) StepTrigger sounds fantastic - root note handling too (but I only have monophonic synths connected to the SEQ for the moment)

    I have a minor thing that I implemented a year ago (or so) that could be interesting to others too - maybe making it to a next release:

    While in Slave-Mode the SEQ listens to Midi Start/Stop/Continue messages from my DAW... as intended! However when working in the DAW I often want the SEQ to ignore those messages so it does not start everytime I hit play in the DAW. It was important that this function was quickly accessible.. 

    ***Just edited my previous post - since I changed the implemtentation***

    Here is what I did:

    - original function is kept as is (hitting stop/pause in slave mode mutes the sequencer - mute is released by hitting play/pause or by midi start/stop/cont command)

    - I added another seq_core_slaveclk_mute state, called SEQ_CORE_SLAVECLK_MUTE_Permanent. its accessed and released by Menu+Stop but not with any other buttons or Midi Play/Stop/Cont commands. This means I can quickly mute the sequencer from playing when working in the DAW. The great thing is the SEQ stays in sync and passes Midi clock/play/stop/cont commands to connected synths in slave mode or if in master mode it can still send clock/start/stop/... commands over midi. So muting is only applied to the SEQ, not to the MidiRouter and thus the  connected synths.

    This function is actually like muting all tracks but has some advantages to me: it's very quickly applied and the SEQ does not show activity anymore...

    Of course I'm happy to share the code, if interested

  3. I've been extensively investigating the arpeggiator of the SEQ V4 recently. most of the time I play it directly ('live') from a keyboard plugged to the SEQ V4 ...it's AMAZING!!! very sophisticated but still quite easy to use. Sometimes I'm just fiddling for hours with my new combo Keyboard > SEQ V4 > TTSH... very meditative! makes me smile...

    But now my question: The arpeggiator does not seem to forward other information than notes (note stackes) to the respective track via the selected Bus, e.g. PitchBend, ModWheel or other CC

    so i can not play an arpeggio with the keyboard and use PitchBend over the same Bus from the same keyboard at the same time?

    is that true? did I miss anything? workaround?


    btw. same seems to be true for the transposer




  4. For those who are interested

    After excessive code investigation... I finally found I very simple and quick solution.

    Already implemented is the following function: When pressing Stop button while running in slave-mode SEQ goes to 'muted slaveclock' state and stops running but keeps in sync with incoming midiclock - by pressing Play this state is changed to 'off' and SEQ starts playing on next measure again. Same state is set/unset with Pause button in slave-mode.

    What I wanted to avoid is that a MIDI Start/Continue would also set 'muted slaveclock' off and set SEQ running again. So I can play/stop/continue my DAW and choose if SEQ is also fired or not everytime.

    I hope it's clear what I intended with this!


    Currently unmuting of the muted slaveclock state is implemented in SEQ_UI.C Play/Pause Button Functions but also  in SEQ_CORE.C after request of pending Start/Continue/NewSongPosition to SEQ_BPM.C (functions: SEQ_BPM_ChkReqCont / SEQ_BPM_ChkReqStart / SEQ_BPM_ChkReqSongPos in SEQ_CORE_Handler).

    So.. luckily I had only to quote a line of code within each of the 3 if clauses:

    //seq_core_slaveclk_mute = SEQ_CORE_SLAVECLK_MUTE_Off;

    Further I also added the possibility to enter muted slaveclock state when not running by pressing MENU+STOP in slave-mode. As well as a temporary message (SEQ_UI_MSG_USER_R) when entering/ leaving this state.




  5. The MBSeqV4 is still one of my fav. machines... but recently I got myself an Ableton Push. That got me back to work more in Ableton Live again with MBSeqV4 in Auto/Slave Mode and a couple of Synths connected to it.

    In general this setup works seamlessly for me. But now I'm looking to integrate a function to filter midi start/stop/cont events in SlaveMode to keep the Seq from playing notes each time Ableton starts:

    • The function shall be quickly accessible from the UI
    • The function is only accessible in Slave/Auto Mode (makes no sense in Master Mode)
    • Midi Clock shall still be forwarded to Midi-Outs (for sync of Synths)
    • If function is active and Seq in Auto-Slave Mode it shall not switch to Auto-Master Mode (would probably lead to a BPM change)

    So far my solution would be:

    • if in Auto/Slave mode 'Stop'+'Play' stops Seq from running and activates the filter > SEQ_UI.c
    • 'Play' would deactivate the filter again
    • Right now I plan to implement the filter before call of function <SEQ_BPM_NotifyMIDIRx(midi_byte)> in app.c since I m really scared of changing anything in seq_bpm.c

    Since I'm not really deep in to coding I'd be very happy if you could share your thoughts on this before starting: got a better idea, malfunctions i could run into, things I should consider/count in, ...

    Any Input is much appreciated


    I know... if some of you like the idea, TK would integrate it before I hit a key and of course way more properly coded... but anyway it's a nice learning process for me to give it a go.

    Ahh.. and this should be repeated daily: SEQV4 AND ALL THE MB STUFF IS ONE HELL OF GEAR - TK ROCKS!!!!

  6. 2*8580 are gone!

    4*6582 are still available - but only up to 3th of january - cause I'm away for travelling with my family until end of august



    So... If you feel like sponsoring an elephant-ride, or whale-watching or a jungle-trip for my two little girls

    go buy some SID's!!!


  7. Hi


    I've 4x 6582 SID's and 2x 8580 SID's for sale:


    6582's are unused ones (well, quickly tested in a MB6582, they seem to work fine) from wilba's mega-sale.

    asking: CHF 30.- (~25 €) each + shipping


    8580's are used ones, tested in a MB6582, and also working fine

    asking: CHF 24.- (~20€) each + shipping


    If you take all the 6 SID's, it's 120€ + shipping


    If you take all the 4 6582 SID's, its 90€ + shipping


    Shipping is about 2.50€ / 8€ (not insured/ insured) to EU


    There are also 2x spare 18F4685's which I dont need anymore

    asking: CHF 8.- (~6€) each + shipping


    cheers, Nick

  8. Okay...Thanks

    I have to admit, that I'm far from knowing all the functions of the SEQ V4

    that is because it is simply so unbelievable AWESOME :hyper:  ...and I feel like a kiddy turning notes on and off :hyper:


    however the mentioned redundancy makes sense, to me at least:

    While in Live mode I've finished with programming Sequences and want to play with 'em

    But with this option it's possible to quickly play notes from a keyboard during programming of a sequence...


    Maybe I still didn't understand live mode completely.... ? I took some time last evening in learning all the functions but stuck in the track-direction-menu-page twiddling around till late in the night :sleep:  FANTASTIC......


    Since this weekend spring time and barbecue season will finally start... I guess it's time for spending a beer or two to you TK!  

  9. I much appreciate the MidiRouter "Track" Destination introduced in V4.071


    however I slightly changed the code for my purpose so that the router sends incoming midi to the port and channel of the currently selected track:


    @Line 91 of seq_midi_router.c


    else if( n->dst_chn >= 18 ) { // Trk
            fwd_port = SEQ_CC_Get(SEQ_UI_VisibleTrackGet(), SEQ_CC_MIDI_PORT);
            fwd_package.chn = SEQ_CC_Get(SEQ_UI_VisibleTrackGet(), SEQ_CC_MIDI_CHANNEL);


    I didn't investigate the code very deeply, and thus I have no clue of any possible conflicts nor reliability... but up till now it works for me!!!

    I'm no programmer, so I'm far from adding this as additional option instead of replacing.

    Maybe you programming-goddess can add this option in the future...


    btw: with the above code, the compiler gives a warning... do I have to declare the Type of SEQ_UI_VisibleTrackGet() in SEQ_CC_Get(........)?

  10. I'm also not much convinced about using a switching psu! particularly for the analog path! Still I gave it a try... with the option to replace it with a Transformer - Vreg(+/-) and switching 5V regulator. But at the moment I'm fine and can't recognise any noise!


    What about using a Vreg in series with the swichting psu? does the switching noise propagate thru it? since I only use 6582 the whole analog path is essentially fed by a 7809. further an opamp mixer shall be included which will be fed by +/-9V from Vregs.


    Then what about the AOUT-NG Module? is it wise to feed it with +/-12V from the switching psu? what do I have to expect? my Midibox CV V1 is also fed with a cheap 15V switching psu at the moment (yes unipolar) - and up to now I'm quite fine with it


    Thanks for the Power One recomendation :smile:  hopefully soon I will start with a modular.... but probably i will go with an adjustable transformer-Vreg psu

  11. If you don't need the -12V you don't have to connect it.

    I'll use it for the CV-OUT Option (AOUT-NG Modul) and further I want to add an Opamp-Mixer for the 4 SID Modules. If all this doesn't mean anything to you - don't worry about it! you could still connect the -12V later if needed.


    C2 and C4 are 330nF = 0.33uF not 330uF - you can use standard ceramic or film capacitors e.g.: http://it.mouser.com/ProductDetail/TDK/FK24X7R1H334K/?qs=sGAEpiMZZMuMW9TJLBQkXjcE1SaKS%2f8mCuct0Dgx3Ik%3d


    capacity of C4 is not that critically, anything between 100nF and 1000nF will work


    If you don't use 9V: 7809, C11 and C12 are obsolet

  12. I've done it that way: post-8317-0-24517400-1363700098_thumb.pn


    Using the 7pin Connector and a MeanWell RPT-60B


    However I only use 6582 (9V) and don't need to connect the 12V path on the board (beside feeding the 7809)


    For the 12V path you could solder a wire from J25 upper pin (beside the rectifier) to J4 lowest pin

    You could leave the 7809 out if you don't need 9V


    I highly recomend to solder the capacitors C1...C4 !!!!!

    and C11...C12 for the 9V path if used



  13. Finished my external PSU based on the Mean Well RPT-60B last week and can't recognize any additional PSU introduced noize.


    12V > [2200uF and 330nF] > 7809 > [10uF and 100nF] 9V > 6x6582

    5V >  [2200uF and 330nF] > 6x6582 and 4xPIC


    I'll go on and add an active Mixer (OpAmp) stage soon - using 12V/-12V supplies reduced to 9V/-9V by 7809/7909

  14. Hmm! Ich geb mal meinen Senf dazu.. ohne Gewähr!

    -VST ist eine Schnittstelle zwischen DAW und Plugin's

    -Plugins geben keine Daten direkt an irgenwelche Treiber weiter

    -Paramter werden über die VST-Schnittstelle registriert, sind aber teilweise auch via Midi ansprechbar (= Midi-Teil der Schnittstelle)

    -Plugins senden typischerweise (Ausnahmen wahrscheinlich) keine Mididaten an die DAW zurück

    Dies sind mehr Annahmen als Facts meinerseits (habe schon seit einiger Zeit nicht mehr mit VSTs gearbeitet).

    Das von dir gewünscht Feature hat meines Erachtens bisher gerade mal Novation zustande gebracht. Da werden die VST Plugins in ein Novation VST-Plugin Mantel gepackt, welcher dann direkt mit der entsprechenden Hardware kommuniziert. Brauchte aber einige Versionen bis alles "reibungslos" funktionierte.

    Ich lass mich natürlich gerne korrigieren.

  15. Congrats! :thumbsup:

    I love the MIDIBOX CV too, considering building another one/two...

    I also tried to power it with a MFOS wallwart bi-polar power supply but had considerable errors with it! The device didn't power up properly every while and then. That happend in general when turning on shortly (<10sec) after turning the suppy off. It showed, that the positive supply (core + aout_ng) had a slightly negative voltage. I've changed to a unipolar supply since I didn't need bipolar for my current setup...

    but with a DIY modular as future-project I'll get back to this issue.

    No problems with yout power supply?

  16. ahh... nice! thank you Thorsten

    but I doubt that I can apply such long Sysex-Strings to buttons on my controller-Keyboard.

    My idea was that I can change the input (MIDI-Keybord) to output (all SEQ-Outputs) routing by one fingertip on the keyboard....

    For the moment I'm fine with changing the routing in the menu! But I will definitely keep an eye on that...

    btw: i guess 0x00 0x00 are manufacturer- and device-ID? Does the second corespond to the MIOS-Core-ID? or how can i ensure only the intended device reads a SYSEX-DUMP?

    I've built a Midi_Processor (CC to SYSEX conversion for Waldorf-Microwave1) years ago based on the 'MIDIfilter/processor'. the matching of CC# and SYSEX-Parameters can be changed with SYSEX-DUMPS to the Processor. The Device is also adressed with 0x00 0x00, but I guess this can cause problems when using other gear with no specific ID's

    cheers, Nick

  17. Yes you are right! but...

    that way I can only drive 16 midi channels in total from SEQ and keyboard (when setting up nodes for USB-MIDI to midi-out and midi-in to midi-out in parallel its reduced to 8)

    However I need:

    • 4 for NordModular
    • 4 for NordModular G2
    • 4 for MB6582
    • 4 for MIDIBOX CV (4 analog Synths)
    • also ther is a x0xb0x / a Microwave1 / a Machinedrum / ...

    Enjoy the SEQ - it is awesome, the MIDI router functionality alone seriously rocks

    Well... definitely... awesome... I'm blown by it :frantics:

    and I guess I should first start with ENJOYING and think about the possibilities/options later

    at least it also doesn't need a lot of button hits to chang routing within the menu

  18. sooooooooon I will have finished my SEQ V4... everything is working now, last thing to do is the enclosure

    Now as it comes to an end, I'm thinking about how to integrate this AWESOME piece of equipment into my setup....

    I plan to use the SEQ V4 as MIDI 'control center':

    • all synths are connected in (4) chains to the sequencer
    • a keyboard controller is hooked to the midi-in of the sequencer
    • MIDI-ROUTER is used to connect keyboard/USB-MIDI with synth chains

      Within the MIDI-ROUTER:
      • 4 nodes are used to connect USB-MIDI (1-4) to 4 synth chains (IIC-Midi connectors)
      • 1 node shall be used to connect the keyboard (MIDI-In 1/2) to the 4 synth chains (IIC-Midi connectors)

      since I want to be able to switch the output (chain 1..4) that is hooked to the keyboard input, this configuration needs the ability to modify the MIDI-ROUTER settings from external. By reading the changelog I found that this might be possible by using MIOS terminal commands. But I rather want to be able to modify it directly from my keyboard.

      2 possibilities come to my mind:

      [*]change the settings of a node (the keyboard to synth-chains node) with a sysex-string (thus i can assigne appropriate sysex-strings to 4 buttons on my controller-keyboard)

      [*]introduce presets for the router, which can be switched from external

      First option is prefered. Seems to be more easy. All I had to do is to add a function in seq_midi_sysex.c which calls a node-setting-function using the parameters received in a sysex-string.


      Can u follow my explanations?

      Better ideas? Workaround?

      Did I miss something?

      How do you do it? controlling a synth with the SEQ and a keyboard in parallel without booting the PC?

      Any ideas/recommendations/warnings/hints welcome!

      btw. YES i thought about using external Midi-Mergers (it's not an option - I DO WANT to implement it in the code :drool: )

  19. Almost finished my SEQ_V4 :frantics: :frantics: :frantics: :frantics: :frantics:

    have to go ahead with the enclosure!

    However, the very first LED (step9 / SR-1 PIN-0) in the chain is flickering in play mode.

    Can't say if it's an erratic flickering or following a pattern

    Normally this led is the BEAT-Indicator, but I changed the assignement of that led and set all non-used led's to SR-0

    LED works correct when SEQ is stopped - only flickering when playing

    any idea?

    Just currious, I can easily change the order of SR's and leave SR-1 PIN-0 unconnected

    cheers, Nick


  20. Thank you Thorsten...

    of course I won't inverse the direction twice :rolleyes:

    was it intended to connect pinA to D1 and pinB to D0? intuitively I' ve designed the board the opposite ... which turned out to be wrong.

    However this forced me to have a closer look to the code finally ... and I'm going the learn C and programming MIOS-Apps for shure

    BTW. concerning the encoders ALPS STEC11B from Reichelt which work best in DETENTED3 mode:

    The encoders work similar to DETENTED2 (one detent position per cycle) BUT: detent positions are exactly at the rising/falling edge of terminal B (according to the spec-sheet:SPEC-SHEET ). this may explain the wobbly behaviour of the encoders in most modes (at least when turning cw, where inc is detected at the rise of terminal B).

    However, what's different in mode DETENTED3 then?

    cheers, Nick

  21. The step encoders of my SEQ-V4 increment by turning ccw and decrement by turning cw :frantics:

    So I want to change the direction of my encoders within the code of SEQ V4. But I feel unsure what code to add and where.

    My guess (as C and MIOS rookie) is following code either in /core/seq_ui within the Encoder handler:


    // Encoder handler


    s32 SEQ_UI_Encoder_Handler(u32 encoder, s32 incrementer)


    incrementer = 0-incrementer

    or in /core/app:

    void APP_ENC_NotifyChange(u32 encoder, s32 incrementer)


    incrementer = 0-incrementer

    doesn't make any big difference (as long as Idont use debug mode), right?

    thanks for your inputs!

    btw. change of the pinning hardwarewise is not really an option. I've (also for the first time) designed my own boards for Step-encoders, GP-buttons and GP-LED's. Accidentaly I mixed up the pinning of the encoders. The boards use smd parts :afro: and soldering wires between encoders and smd 74hc165 just is too fiddly...