monokinetic
-
Posts
325 -
Joined
-
Last visited
-
Days Won
5
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by monokinetic
-
-
Benoit, I'm watching this with great anticipation!
Oh and BTW your product page still describes the RTP-MIDI OEM board as having "Up to 8 RTP-MIDI sessions in parallel".
David
-
Hi Chriss,
Thanks for posting your findings, that just makes me want to get this built into my seq even more!
David
-
Wow this looks perfect, nice work gang! I would vote for a Ponoko type case, ala Sammich devices. If there's a gorup buy for this, I'm in. I'm sure most people who have the Encoder / LED boards would buy into this.....
Maybe the top 3 elements (buttons, LCD, OLEDs) could be split into separate PCBs, then you can order your front panel depending on your preference i.e. left handed or right? Modular designs are always more felxible.
In terms of height of the box, will this attempt to include the AOUT in the same box? I would suggest not. My plan is to put the AOUT behind a panel in my synth, and drive it with the core / front panel controls over a transistor buffer. That means the AOUT can be close to the dual power supply in the modular, and the control panel can be mounted close to the iPad away from all the modular's cables ;)
What would be amazing would be to use this proposed surface as a generic surface to also edit my other devices, MBFM and MBSIDs, all from a central panel :D
-
Wow! I must add that MBCV2 is the most fun thing I have built, since the sequencer :D
I will have to play with it some more to be able to imagine a physical interface. The Lemur usability is really good already IMO.
Maybe something using those screens with encoders arranged around them, with the screens showing encoders values?
TK: could you post the part number for those screens? I think I might have to add them to my panel after seeing the video!
cheers.
-
Wow TK that was fast, you're unstoppable!
I will not be able to test this for a while unfortunately as I am on the road without my Seq :( but will be back mid-January for some testing and promise to follow up with some feedback...
-
J5 is already allocated for Gate outputs, and another problem would be the bad accuracy of STM32 and LPC17 ADCs...
I could support an MBHP_AINSER8 module instead, but this could affect the performance of the sequencer :-/
OK I was thinking the MBHP_AINSER8 module, but wouldn't want to sacrifice performance.
Therefore the usage of CCs is maybe the better approach, just use a second core for the conversion (you could also use it for other purposes as well)Cool. I will either try it with MBCV2 on LPC and AINSER8, or would a PIC core also be suitable?
16 DIN pins to step the 16 tracks individually, right?Sure that would be great, but I'll probably go with only 8 DINs i.e. 1 chip. Could software support routing them to track inputs?
If it's ok to assign a whole DOUT SR (= 8 outputs) for this function, I could easily add this.Great :D
What type of clock outputs would be for interest?Will have to think on that....
Cheers
-
Hi TK,
Thanks for your input as ever.
Aha, I should have mentioned that I was considering using an AIN. Would that be feasable i.e. could MBSeq scan AINs? I will make sure that the modular voltages don't exceend the AIN specs of course....Unfortunately there are no free ADC inputs which could be used for this purpose.
Great! I had been looking at the section controls source code, but I'd really like something at the step level, whereas the section control seems to be limited to 16 subsections.There is no CC available which allows to control a step, but I could add this, especially since the MIDI CC configuration is very flexible meanwhile, so that new functions can be added without much effort at my side.
Can I say both? :smile: I guess no.1 is closer to my original intention, but having 2 would be great as well.....Question is: how should it behave exactly?I see two possible use cases:
1) let's divide the CC value into 128/<number-of-steps> ranges.
E.g. with a 16 step track:
- Step 1 would be selected with 0..7
- Step 2 with 8..15
...
- Step 16 with 120..127
Whenever the CC value changes between one of these ranges, the appr. step would be played immediately
2) like 1, but the appr. step would be played with the next step clock (depending on the track divider value)
Which approach would be preferred?
Were you referring to the idea of using DINs to step through the track with this last comment?If the trigger pulse is > 2 mS, this is feasible
Hmm interesting idea that I hadn't considered. From my (very!) basic understanding of the code, this could potentially be another type of FX.While we are here: multiple clock/divider outputs independent from the tracks would be awesome.
@TK:
Is that an option?
Cheers
David
-
So I've been thinking about how I want to integrate MBSeqV4 further into my analogue modular synth workflow and I would like to ask if it would (theoreticaly) be possible to have an external analogue input to control which step of a track is playing. In other words, you could input a ramp wave into the AIN and that would control which step of a track is output. 0v = 1st step, 5v = last step. Things get interesting when you input other waves :D What started me thinking about this is the Milton sequencer from Peter Grenader, which provides for voltage control of the step (see http://web.archive.org/web/20110708110112/http://www.buzzclick-music.com/about_milton.html for more detailled description if you're interested)
Secondly, would it be possible to do a similar thing with DINs i.e. have DIN control the clock stepping a track? This would probably require a second DIN for reset as well to make things gel well with analogue sequencers....
I realise this is all a bit outside of the inteded use case for MBSeqV4, but am interested if I should persue this idea with the current code or start something new :)
David
-
Super great news, I would take 1 PCB please :)
-
Hi,
I use the Microchip PICKit3 on both OSX and Linux to burn Midibox PICs. Using USB is nice and fast and a lot less problems than the DIY programmers I had built previously :)
Dave
-
Please have a look into the DEFAULT.CV2 file (you can open it with the MIOS Filebrowser).
Under "Misc Configuration" you will find the AOUT_Type, which has to be set to AOUT:
# Misc. Configuration AOUT_Type;AOUT
Bingo, this was the solution for me. Thanks a million TK! FYI, my default.cv2 file had this parameter blank. Editing the file and rebooting the MBCV was enough to get it working :D
Expect some demo noises from MBCV2 soon....
Dave
-
Hello Thorsten,
Thanks a lot for the info. I will check the things you mentioned this evening when I'm back by the hardware. One other thing I noticed is that when I run MBCV2, the MIOSStudio terminal shows this:[ 284.417] Init DHCP [ 284.517] [network_device_init] PHY initialized
and then constantly displays messages like this:
[ 286.420] 144 uS (max: 163 uS) [ 287.421] 139 uS (max: 152 uS) [ 288.423] 140 uS (max: 152 uS)
Is that correct? Does it mean that I also have to use the Ethernet connection?
Thanks
Dave -
I spent some more time testing this today, here's an update:
I have added an SDCard and also tried with Ethernet.
I have recompiled, made sure I chose the correct processor and updated to the latest bootloader.
No change to MBCV behaviour.
I have uploaded MBSeq v4.77 and can run the caliout tests successfully, I get the correct voltage on every pin of the AOUT. Also ran the testaoutpin commands to check the connections are OK, everything passes fine.
When I upload MBCV to the LPC core board, MIOS terminal shows me:
And I tried to run the caliout test with MBCV uploaded and nothing on the AOUT pins. So my conclusion is that the hardware setup is good, something is weird with the software.
Current questions:
Is there some way to choose exactly which AOUT module to use?
Could anyone verify that my method of testing in the first post is correct? If not can anyone provide a simple example of how to create a MBCV2 patch that will for sure generate voltage from an AOUT pin?
Dave
-
Hi gang,
I'm trying to use MBCV2 and am having some problems. The firmware seems to be uploaded OK, as MIOSStudio reports MidiboxCV as a USB device.
I'm using an original AOUT, it was previously tested and working fine with my STM32 based MBSeqV4.
I am connected to the LPC core running MBCV2 via USB and have set the Lemur daemon to route the MidiboxCV MIDI device to Lemur in and out 0. Communication from Lemur on iPad seems to be working OK, i.e. I can change settings on the different CV channels and the surface updates - so communication seems to be working.
My basic test is to make sure I'm on CV channel 1, set the LFO amplitude to max, then the -> CV to max. I would expect to see CV on output 1 of the AOUT, but so far nothing.
I'm not sure if:
MBCV2 needs a hardware config file on the SD Card ala MBseq to configure the type of AOUT settings etc?
MBCV2 is OK with just the USB MIDI connection or if Ethernet is required for full OSC communication?
Thanks in advance for any help
-
+1 to this. sometimes I can't switch it off.Thanks again for such an amazing instrument.and my DAW is always on record :smile:
looking forward to some tutorials TK!
-
Not sure if this is relevant MaG2k, but I had a similar problem going between Inkscape and Illustrator. The root cause was that one piece of software works at 72 DPI, the other at 90 DPI by default (I forget which is which). If you change the DPI setting so that it is equal in both applications, then exchanging .svg between them should not result in size changes.
-
Personally I just copy tracks that I like and then modify the copies. I was wondering what your goal was with this? I'm interested what different outcome you were looking for that a copy wouldn't achieve.So I know this may be asking too much but a feature I've been wanting a lot lately is a "flatten" function. Once I get something crazy going with the direction, length, etc parameters I often want to dub that down to another track.TK, one thing that Luke's post got me thinking about: quite often I'm using a track which is set as an arpeggiator and play a certain set of keys that generate a great pattern. Problem is, next time I send any more MIDI to the track I lose that great pattern and can't remember or replay those last notes! Generally I always record the output of MBSeq because of this. I was wondering if there would be some way to address this in the sequencer itself? Maybe a way to grab the last set of notes the arpeggiator received and paste them into another track? Or to freeze an arpeggiator when you are happy with what it's generating?
Anyone else found ways around this?
Dave
-
When I ran into similar issues combining an older application with a newer bootloader, this helped me to fix it:
if you uploaded an old application by accident which isn't compatible to the new bootloader, you've two possibilities: either stuff the "Boot Hold" jumper J27 on your MBHP_CORE_STM32/MBHP_CORE_LPC17 module, reconnect the USB cable and reopen MIOS Studio to get direct access to the bootloader, or upload the application via traditional MIDI IN1/OUT1taken from this thread:
I used the second option and it fixed it.
-
Assuming they test out OK, I will take a PCB. Thanks for offering :smile:
-
Yes I was hoping that some of the features of AC Sensorizer could be brought in to MBCV. I believe it was even mentioned in this thread?I turned my 8bit core running AC Sensorizer into an 8-channel midi to CV converter
Super :smile:ok, noticed!I understand we won't be able to modulate parameters without some quantisation at 1Khz, but for certain operations 1Khz is fine!
Looking forward to what you come up with.
-
Could I ask approximately what sample rate was possible? Would this limitation also affect other MB based projects reading the analogue ins, for example if ACSensorizer was ported to MIOS32?Analog INs: I tried this some time ago, but had no fun with this option - the achievable sample rate is too low for good results.
Sure, totally understood.Features where I don't see a significant benefit won't be supported, because people will blame me for the bad performance and wrong promises.
Great, I'll add some trigger ins to my panel :smile:DINs: using digital inputs as triggers sounds like a good idea.
OK that makes sense, I'll stick with 1x AOUT + MBCV2.0 for the nice fast synth engines and use my second AOUT on the MBSEQ :DMultiple AOUTs: running synth engines for more than 8 outputs would decrease the sample rate, at the end the results would be worse than today.So: I could only provide "auxiliary AOUTs" to pass static values which are not modulated.
Cheers
-
OK thanks for the info, sent you an PM to discuss a bit more.
-
Hi, just wondering:
How difficult will it be to add the analogue ins to MBCV2.0 and have them available in the mod matrix?
Ditto DINs?
Any plans to support multiple AOUTs ala MBNG?
I plan on adding this to my next panel of modular synth, so want to work out which ins/outs I should plan on being available before drilling!
-
Hiya, just a very gentle and friendly bump to see if you made any progress with this :)
MIDIbox Matrix - MIDI Matrix with (up to) 56 input and 56 output ports
in MIDIbox User Projects
Posted
I have read through the wiki page, excellent documentation. Thanks for sharing! And nice to meet you BOB ;)
Count me in for one of the FPGA boards, and some BOBs as well.