monokinetic

Programmer
  • Content count

    302
  • Joined

  • Last visited

Everything posted by monokinetic

  1. Using AOUT with Buchla 1.2v/octave

    As you probably know, the AOUT module is set up to support 1v/octave scaling, and that has been fine for me when I was using it with a Serge modular system. But I have been wondering how I could use my AOUTs with my Buchla-ish modular synth, which uses 1.2v/octave scaling. I contemplated building an opamp based solution, boosting the voltage a bit. But this seemed a bit of a hack to me, so I spent a bit of time understanding the opamp based outputs from the MAX525 DACs. I realised that by tweaking a resistor value I could get the AOUT to put out 1.2v/octave. I've tested this for a bit with two different oscillators (258r and 259r) and it seems fine for my uses. I'm no electrical engineer though, so if this mod blows up your rather expensive equipment I'm afraid you're on your own... That said, for any other Buchla users who want to use an AOUT to output 1.2v/octave, just change RY to 1.8K on any channels you want. That should give you the extra bit of gain required, and then you can trim it to 1.2v/octave. FWIW I usually use the MBSeqV4 app, then use the nice new calibration stuff to get things super accurate. I'm able to get submillivolt accuracy over the whole voltage range. Top voltage is obviously a bit higher in this case, almost 13v from my measurements. That seems to have been fine in my system, but YMMV. Also, I have set my AOUT so that V1-V4 have this tweak (1.8K for RY), and I use them for controlling Buchla oscillators. V5-V8 use the 2.2K resistor for RY still, and I use those channels for modulation CVs and to control the Serge oscillators which run at 1v/octave. All in all I'm most happy with this system and am glad I don't have to mess around with adding more circuitry. Hope that helps someone in the future!    
  2. MIDIbox as base for touch GUI music project

    FWIW I use Lemur on an old iPad v1 and use it for the BLM of the sequencer, and with the MBSID. That communicates over OSC, is rock solid and make me think that going the SPI i2C route would be unnecessary. Only thing is that requires you using a computer to to go USB MIDI -> OSC -> Lemur. I might go computer free at some point using Midibox + an OSC interface, but so far things work so well and I given that I always end up having a computer on to capture MIDI and audio from my jams that it seemed like if it's working I'll get on with making some music :) Maybe before you complicate things trying to communicate using an internal bus, give that a try? Just a suggestion!
  3. Heheh, define easier ;) I'm no Git expert, but if it helps, here's how I'd imagine doing things: Make a directory for this repo i.e. cd ~ mkdir mios_stuff cd mios_stuff Clone the repo to your local dir: git clone https://github.com/midibox/mios32.git Let's check to see which branches are available in the new repo: cd mios32/ ~/mios_stuff/mios32$ git branch -av * master                                      79292db corrected comments in source_me_* files   remotes/origin/HEAD                         -> origin/master   remotes/origin/feature/juce_5_4_3_migration 5e8148f MIOS Studio: updated release script   remotes/origin/feature/mcan                 b7b78c2 corrected mios32_* namespace   remotes/origin/master                       79292db corrected comments in source_me_* files I used the -av option to show all of the branches on the remote repo. Note the * by master, that shows which branch you have checked out at the moment. It looks like TK has set you up the feature/mcan branch. Let's assume you want to do some work on that, so switch to the MCAN branch like this: ~/mios_stuff/mios32$ git checkout feature/mcan Branch feature/mcan set up to track remote branch feature/mcan from origin. Switched to a new branch 'feature/mcan' Here is where things are a bit different to SVN. I'd try and explain it but you'd be better reading this: https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell Then basically you can do your work, doing regular commits. Those go in to the branch you have checked out currently. Then when you are ready to share them with others you push to the repo, ensuring that your push goes to the feature/mcan branch. Eventually, once we know that everything you have done in feature/mcan is OK to add to the full mios32 then someone has to merge the changes in feature/mcan branch into the master branch. Then finally everyone can use MCAN and blow their minds with so many MIDI ports to play with ;) I also recommend looking up how Git stash works (I find that invaluable) :) Sorry for the slightly long post, and apologies in advance for things that a Git expert would tell you are wrong. But that's how I plan to use it so far!
  4. Using AOUT with Buchla 1.2v/octave

    Hi folks, nice to know this info is of use to some! @Rowan I'm afraid both of my attempts at building an AOUT_NG failed so I gave up on that path. But yes to what Zam wrote, basically all I did was recalculate the opamp resistors. Don't know why it didn't occur to me years ago, but that's life :) Good luck with your builds!
  5. [FS] MBSeq4 kit - incl. Heindrich case (price drop)

    Bump for the price drop to 325 Euros, that's a bargain!
  6. I've had this hoarded as a back up in case my seq went down. Now I want a V4+, so here's a good time for you to get an entire kit to build a seq V4.... Includes: MBSeq4 CS PCB + SmashTV full parts kit (PM me for exact contents) Beast panel (with minor defect, hence cheaper PM for details) Plastic LCD windows x 2 (super handy) Heindrich case (rare as hen's teeth ;))   Not willing to separate I'm afraid. Asking price = 400 euros  price reduction to 325 Euros, buyer pays shipping. Also available: OPL3 and 2x DAC chip set 15 euro MBCV 1 from sonicwarrior 10 euro PIC Burner + cable - 15 euro I'm located in Prague, the Czech Republic. Prefer bank transfer, but can do Paypal if you pay fees. IM me if you're interested in anything.
  7. MIDIbox SEQ V4 Release + Feedback

    @TK: oh my, did Christmas just come early :) Excellent to see some updates, thank you! Will test over the coming days. re: the AOUT extended calibration, is there a chance to merge this into MBCV2.0 at some point? I would find it really useful in that app as well..... Just a thought! Warm and festive regards David
  8. MIDIbox SEQ V4 Release + Feedback

    @TK wow this works really quite nicely. FYI I tried v4_095_pre14 on my STM32F4 based MBSeq. I observed the following: - when scrolling through the options using ENC #7 it seems to go min/middle/max/wave. When set to wave there's a full voltage range triangle type wave coming out of CV, is that intended? - once I scroll through to the end of possible values using 7, the last value is Max:. That seems a bit weird over here. When I initially scroll to Max I get almost 0 volts out of the CV channel, then if I touch ENC #8 the offset value on screen jumps to -3700 ish! At that point I get the full voltage out of CV. I guess this might weird out the interpolation a bit? And I started to scroll ENC #8 to get it back to around 0 but it was taking ages and I gave up :) Otherwise, this change seems great. I have used it to play a couple of basic patches from MBSeq to my modular and it seems really accurate, excellent work, as usual! Tiny feature idea: could presses of GP8 cycle through min/0/max offset? for quick changes? Cheers David
  9. MIDIbox CV V2 Concept

    Not sure which type of MIDI control you mean. The Lemur interface is using NRPNs from memory, so any other interface could use that I guess. I'm not sure of the status of CC control, I've not got things hooked up at the moment, otherwise I'd check for you. Prob best to check the code if you want to be 100% sure...
  10. MIDIbox CV V2 Concept

    FWIW I use MBCV2 regularly on an STM32F4 core and an AOUT using MAX525s, and I have some DOUTs doing gates. It works great in my DIY modular synth. Everything you described in your post sounds like it is doable in my experience. Whether you even need the second core running NG is debatable, that'll depend on how you want to connect to the Behinger (which I'm not familiar with, so can't comment). I wouldn't say it's a dead project myself, super usable and the interfacing with Lemur is amazing. Good luck with your project!  
  11. dipCoreF4 and dipBoardF4, a compact Core.

    Great thanks for confirming. Now I know all about Micro-match :) I've added some value versions and luxury versions to my Mouser order for testing.
  12. dipCoreF4 and dipBoardF4, a compact Core.

    Hooray for rain! Looking good, the only thing I see in there which I don't recognise are these "micromatch" connectors. I guess any male 1.27 pitch connector with the right number of pins is suitable for making ribbon cables. I was thinking of using something like these, what do you think?
  13. mnmlCore

    Yeah, and the feature list makes me go whoa! Looking forward to this one 
  14. [FS] MBSeq4 kit - incl. Heindrich case (price drop)

    Adding some photos. As you can see, PCB is still in airtight shrink wrap, all kit components in sealed bags (packed by smashtv himself!!), Heindrich case sealed in plastic, LCD windows in nice tissue paper and unscratched! So everything is basically as new and ready to build, just add LCDs and your CORE and MIDI PCBs and you have a complete unit :)
  15. OLRE16 with Lattice CPLD as Clocking/Addressing interface

    Looking great!
  16. Thanks for all the info on how to adapt pyBLM, that pretty much seals it for me!  
  17. Wow excellent news, thanks for taking the time to do this and contribute it. I was contemplating whether to go the Launchpad route or not and this encourages me to go shopping soon :) I was wondering if it would be possible to use the extra row of buttons to send some MIDI messages, and if so I would suggest something like Program Change messages, which could then be used to control the phrase/song, assuming the MBSeq is configured to respond to them in the Ext. Ctrl page. This is the one thing I find myself missing from using the Lemur BLM extensively. Just a suggestion....  Cheers!
  18. CV setup help

    I know you mentioned the testaoutpin to check connections, but have you tried caliaout? That might be worth a try when the Seq app is running, you can measure the exact voltages on each output. Otherwise could you provide details on the type of track etc that you are configuring in MBSeq to try and test your AOUT_NG? Is it a note track, what is the output set to, and so on. Good luck
  19. MB-OLRE16CS-a_v2b_eC_active view.jpg

    Great stuff! Lovely routing :)
  20. OLRE16, in colors.

    Great work, I really hope there will be a way to get our hands on these. I'd love a few strips of this!
  21. MIDI_CORE_LPC17 PCB?

    Interesting, I didn't know that. I have one more LPC core that I plan to stuff. Does anyone happen to know if LPC1769 revision D, currently available on the embeddedartists site, is compatible with LPC core? They claim that: "the expansion pins (2x27 positions) are mechanically compatible with the original design" but I'd like to check if anyone here has experience with it before I order. 
  22. Patterns Workflow

    Personally I find the pattern mode really useful, especially when coupled with "save and take over patterns". If you haven't tried it, it enables you to assign changes in your song to the 16 GP buttons. For each of the 16 slots, MBSeq stores mutes, can send program changes and mixer maps and then trigger 4 pattern groups (i.e. choose 16 tracks). You have 16 slots like that (i.e. 16 changes) per song. I used it for a live set earlier this year and it was great, sending program changes to all of the midi kit we controlled was pretty much instantaneous and with 3 MBSeq songs set up like this we jammed for an hour. I'm not sure if that would match your snapshot concept, but I'd give it a try. It enables you to decide the structure of the song pretty live IMO :)
  23. MBSEQv4 Beginner's Guide now in the wiki

    Yeah amazing work man, I've been using this sequencer since version 2 and yet still your documentation taught me some cool new tricks! Thanks very much indeed :)
  24. Interesting discussion, and I agree with most of the points. But in regards to this: Personally I think the advantage of a dedicated record button is to be able to quickly toggle between recording state and playing state. So you could hit record to quickly drop into record mode for the last 16 steps of a 64 step pattern and add some notes, then hit record again to avoid recording over existing notes as the pattern loops. Instead of your suggestion, I'd make the shortcut to the Jam page a key-combo with the Record button and another button, for example press Menu and Record or something similar to quickly jump to the Jam page. Otherwise it is still minimum 2 key presses to get to into recording (currently 3) which I find slows down my workflow. Just a suggestion!
  25. BLM 16x16+X PCB and case order [CLOSED/waitlist]

    Oh how I have tried to resist, but I just can't take it any more :) Please put me down for a PCB (BLM and minicore) and case at minimum. Depending on how pricing works out with other things I may even get tempted into a kit.